Hi  We're running JMS Modular Input (jmsta) on the Heavy Forwarder on Linux VM. We have 4 Heavy Forwarders with jmsta running on each, we use to get 3-4 millions records from one queue, it taking to much time dequeue data, how to increase the ingestion rate. already increased "-Xms512m","-Xmx1024m" @Damien_Dallimor  ... View more

  We connecting are Solace queue by using Splunk JMS_TA add-on and consuming data from queue but we getting exception too-many connection frequently. Please help on this. Error Details: ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/jms_ta/bin/jms.py" Caused by: ((Client name: XXXXX.com/22109/#037805d3 Local addr: XXXXX Remote addr: XXXX.XXX.com:55555) - ) com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: Max Client Queue and Topic Endpoint Flow Exceeded 0500 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/jms_ta/bin/jms.py" Stanza jms://queue/sys:Q_XX_XX_XX_ERROR : Error connecting : javax.jms.JMSException: Error creating consumer - internal error (503: Max Client Queue and Topic Endpoint Flow Exceeded @baboonbones  ... View more

We connecting Solace queue from JMS_TA app to get queue data into Splunk. We successfully established connection and we able to get data from queue but after some time we getting below error. ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/jms_ta/bin/jms.py" Caused by: ((Client name: XXXXXXXXX/6828/#XXXXXX Local addr: XXXXXXX:XXXXXXX Remote addr: syseai2.XXXX.com:55555) - ) com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: Max Client Queue and Topic Endpoint Flow Exceeded. ... View more

In my logs we have, special character like \r\n\t, i like remove from events while index level. Please help me on this. Example: we have like this events\r\n\t\t\t\t\t ... View more