Why JMS client is facing this issue while receiving message using spring auto configuration ?

Blogs & Tutorials
1

2023-07-23 21:52:11.281 INFO 20384 — [connect_service] c.s.j.protocol.impl.TcpClientChannel : Client-2: Connected to host ‘orig=tcps://ipaas-ump-uat-1.messaging.solace.cloud:55443, scheme=tcps://, host=ipaas-ump-uat-1.messaging.solace.cloud, port=55443’ (smfclient 2)
2023-07-23 21:52:21.498 INFO 20384 — [3_ReactorThread] c.s.j.protocol.impl.TcpClientChannel : Client-2: (Client name: PDC5-L-GVXCLS3/20384/00f60002/rfK1jRnWAa Local addr: 192.168.1.138 Local port: 51088 Remote addr: ipaas-ump-uat-1.messaging.solace.cloud Remote port: 55443) - handleException(): Channel Closed Event (smfclient 2)
2023-07-23 21:52:21.499 INFO 20384 — [3_ReactorThread] c.s.j.protocol.impl.TcpClientChannel : Client-2: handleException(): Channel Closed Event (smfclient 2) with exception: Timeout reading response to ADCTRL operation. ([BRT resource=uat_outlet_ms existingFH=com.solacesystems.jcsmp.impl.flow.FlowHandleImpl@7cacc84f flowType=CONSUMER counter=21]) cur_stack=Thread: “Context_3_ReactorThread” daemon id=246, prio=5: com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.handleException(TcpClientChannel.java:1374) com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.handleException(TcpClientChannel.java:1325) com.solacesystems.jcsmp.impl.flow.FlowTask.handleTimeout(FlowTask.java:37) com.solacesystems.jcsmp.impl.flow.BindRequestTask.handleTimeout(BindRequestTask.java:406) com.solacesystems.jcsmp.impl.timers.impl.JCSMPTimerQueueImpl.runAllTo(JCSMPTimerQueueImpl.java:91) com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor.eventLoop(SyncEventDispatcherReactor.java:168) com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor$SEDReactorThread.run(SyncEventDispatcherReactor.java:338) java.base/java.lang.Thread.run(Thread.java:829)
2023-07-23 21:52:21.500 INFO 20384 — [3_ReactorThread] c.s.j.protocol.impl.TcpClientChannel : Client-2: (Client name: PDC5-L-GVXCLS3/20384/00f60002/rfK1jRnWAa Local addr: 192.168.1.138 Local port: 51088 Remote addr: ipaas-ump-uat-1.messaging.solace.cloud Remote port: 55443) - startReconnect(): Channel Closed Event (smfclient 2); exception: Timeout reading response to ADCTRL operation. ([BRT resource=uat_outlet_ms existingFH=com.solacesystems.jcsmp.impl.flow.FlowHandleImpl@7cacc84f flowType=CONSUMER counter=21]) cur_stack=Thread: “Context_3_ReactorThread” daemon id=246, prio=5: com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.startReconnect(TcpClientChannel.java:1335) com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.handleException(TcpClientChannel.java:1399) com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.handleException(TcpClientChannel.java:1325) com.solacesystems.jcsmp.impl.flow.FlowTask.handleTimeout(FlowTask.java:37) com.solacesystems.jcsmp.impl.flow.BindRequestTask.handleTimeout(BindRequestTask.java:406) com.solacesystems.jcsmp.impl.timers.impl.JCSMPTimerQueueImpl.runAllTo(JCSMPTimerQueueImpl.java:91) com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor.eventLoop(SyncEventDispatcherReactor.java:168) com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor$SEDReactorThread.run(SyncEventDispatcherReactor.java:338) java.base/java.lang.Thread.run(Thread.java:829)
2023-07-23 21:52:22.702 INFO 20384 — [connect_service] c.s.j.protocol.impl.TcpClientChannel : Client-2: Connection attempt failed to host ‘ipaas-ump-uat-1.messaging.solace.cloud’ ReconnectException com.solacesystems.jcsmp.JCSMPTransportException: Timeout reading response to ADCTRL operation. ([BRT resource=uat_outlet_ms existingFH=com.solacesystems.jcsmp.impl.flow.FlowHandleImpl@7cacc84f flowType=CONSUMER counter=21])
2023-07-23 21:52:25.707 INFO 20384 — [connect_service] c.s.j.protocol.impl.TcpClientChannel : Client-2: Stale reconnect task, aborting reconnect.
2023-07-23 21:52:25.709 INFO 20384 — [connect_service] c.s.j.protocol.impl.TcpClientChannel : Client-2: Channel Closed (smfclient 2)
2023-07-23 21:52:25.712 INFO 20384 — [connect_service] c.s.jcsmp.impl.flow.SubFlowManagerImpl : Client-2: SubChannel (smfclient 2, name=PDC5-L-GVXCLS3/20384/00f60002/rfK1jRnWAa, desc=) threw exception, non-recoverable.

com.solacesystems.jcsmp.JCSMPTransportException: (JCSMPTransportException) Timeout reading response to ADCTRL operation. ([BRT resource=uat_outlet_ms existingFH=null flowType=CONSUMER counter=14])
at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel$ClientChannelReconnect.call(TcpClientChannel.java:2439) ~[sol-jms-10.13.1.jar:na]
at java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264) ~[na:na]
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
at java.base/java.lang.Thread.run(Thread.java:829) ~[na:na]
Caused by: com.solacesystems.jcsmp.JCSMPTransportException: Timeout reading response to ADCTRL operation. ([BRT resource=uat_outlet_ms existingFH=com.solacesystems.jcsmp.impl.flow.FlowHandleImpl@7cacc84f flowType=CONSUMER counter=21])
at com.solacesystems.jcsmp.impl.flow.BindRequestTask.handleTimeout(BindRequestTask.java:412) ~[sol-jms-10.13.1.jar:na]
at com.solacesystems.jcsmp.impl.timers.impl.JCSMPTimerQueueImpl.runAllTo(JCSMPTimerQueueImpl.java:91) ~[sol-jms-10.13.1.jar:na]
at com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor.eventLoop(SyncEventDispatcherReactor.java:168) ~[sol-jms-10.13.1.jar:na]
at com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor$SEDReactorThread.run(SyncEventDispatcherReactor.java:338) ~[sol-jms-10.13.1.jar:na]
… 1 common frames omitted

2

It says there was a timeout. Can your client reach the broker at 55443?

3

@amackenzie yes in solace admin we can see client connected . As well as we can also see that number of consumer available.

4

@amackenzie wherever in queue there is large payload then for that we are facing highlighted issue while consuming the data.

5

we need urgent help. we are getting this issue with large json payload like one payload has 9236 records.
we are using following for the configuration :

public DefaultJmsListenerContainerFactory cfFactory(ConnectionFactory connectionFactory, MsgErrorHandler errorHandler) {
DefaultJmsListenerContainerFactory factory = new DefaultJmsListenerContainerFactory();
factory.setConnectionFactory(connectionFactory);
factory.setSessionAcknowledgeMode(4);
factory.setErrorHandler(errorHandler);
factory.setConcurrency(“5-10”);
factory.setMessageConverter(jacksonJmsMsgConverter());
return factory;
}
com.solacesystems.jcsmp.JCSMPTransportException: (JCSMPTransportException) Timeout reading response to ADCTRL operation. ([BRT resource=qa_outletattributes_ms existingFH=null flowType=CONSUMER counter=2])
at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel$ClientChannelReconnect.call(TcpClientChannel.java:2439) ~[sol-jms-10.13.1.jar:na]
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
Caused by: com.solacesystems.jcsmp.JCSMPTransportException: Timeout reading response to ADCTRL operation. ([BRT resource=qa_outletattributes_ms existingFH=com.solacesystems.jcsmp.impl.flow.FlowHandleImpl@10e1fbdb flowType=CONSUMER counter=9])
at com.solacesystems.jcsmp.impl.flow.BindRequestTask.handleTimeout(BindRequestTask.java:412) ~[sol-jms-10.13.1.jar:na]
at com.solacesystems.jcsmp.impl.timers.impl.JCSMPTimerQueueImpl.runAllTo(JCSMPTimerQueueImpl.java:91) ~[sol-jms-10.13.1.jar:na]
at com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor.eventLoop(SyncEventDispatcherReactor.java:168) ~[sol-jms-10.13.1.jar:na]
at com.solacesystems.jcsmp.protocol.nio.impl.SyncEventDispatcherReactor$SEDReactorThread.run(SyncEventDispatcherReactor.java:338) ~[sol-jms-10.13.1.jar:na]
… 1 common frames omitted

6

@Aaron @amackenzie
can we get help here?

7

are you a supported customer? A support ticket is the best way to get urgent support.

8

yes we are we have asked for event log for broker also @amackenzie

9

@amackenzie when ever data is more than 4mb it is throwing error with adcntrl response time out. For smaller payload it is working fine. am i missing any configuration which we can set at connection factory level ?