Splunk Enterprise

Too-Many connection issue while connecting Solace Queue from JMS_TA(Splunk)

svs26
Engager

 

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 

Labels (2)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...