|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
IIB JMS call to Solace router. |
« View previous topic :: View next topic » |
Author |
Message
|
sravan |
Posted: Mon Feb 15, 2021 6:01 pm Post subject: IIB JMS call to Solace router. |
|
|
Centurion
Joined: 02 Apr 2010 Posts: 104 Location: Charlotte
|
Hi,
We are using JMS Java api from Java compute node to call Solace router
along with solace java jms api + JMS Java compute node.
It worked fine in production until an interface is added with high volume and occasioanally we see below issue.
Any idea if this error is a IIB client or the Solace router side and how to fix it.
We are opened a an issue with the vendor but any suggestion will be helpful.
javax.jms.JMSException: Error creating producer - transport error (ClientRequestResponse Timeout (ADCTRL-ProducerOpenFlow)) |
|
Back to top |
|
 |
abhi_thri |
Posted: Tue Feb 16, 2021 12:21 am Post subject: |
|
|
 Knight
Joined: 17 Jul 2017 Posts: 516 Location: UK
|
hi...can you please post the full error details |
|
Back to top |
|
 |
sravan |
Posted: Tue Feb 16, 2021 1:39 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2010 Posts: 104 Location: Charlotte
|
<Message><Environment><BrokerData><LastError><Label></Label><Number>4394</Number><Text>Unhandled exception in plugin method</Text></LastError><RecoverableException><Label>PUB_Batch.GetEnv</Label><Text>Caught exception and rethrowing</Text><Number>2230</Number><Insert><Text>Msg_Flow</Text></Insert><RecoverableException><Label>PUB_Batch.RouteToMessageFlow.MessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.rules matcher</Label><Text>Caught exception and rethrowing</Text><Number>2230</Number><Insert><Text>PUB_Batch.RouteToMessageFlow.rMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.rules matcher</Text></Insert><RecoverableException><Label>MessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.rules matcher</Label><Text>Error detected, rethrowing</Text><Number>2488</Number><Insert><Text>Customer.Customer_IC_STD_NTFY_msg001_DOBChg_rules matcher.main</Text></Insert><Insert><Text>396.4</Text></Insert><Insert><Text>PROPAGATE FINALIZE DEFAULT DELETE DEFAULT;</Text></Insert><RecoverableException><Label>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.1BUS_WBR</Label><Text>Caught exception and rethrowing</Text><Number>2230</Number><Insert><Text>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.1BUS_WBR</Text></Insert><RecoverableException><Label>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.1BUS_WBR</Label><Text>Error detected, rethrowing</Text><Number>2488</Number><Insert><Text>Customer.Customer_IC_STD_NTFY_MSG001_DOBChg_1BUS_WBR_Subscription.Main</Text></Insert><Insert><Text>105.3</Text></Insert><Insert><Text>PROPAGATE FINALIZE DEFAULT DELETE DEFAULT;</Text></Insert><RecoverableException><Label>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.WBR_1BUS__Solaceflow.MQ JMS Transform</Label><Text>Caught exception and rethrowing</Text><Number>2230</Number><Insert><Text>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.WBR_1BUS__Solaceflow.MQ JMS Transform</Text></Insert><RecoverableException><Label>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.WBR_1BUS__Solaceflow.SOLACE_JMSConnection_Java Compute</Label><Text>Caught exception and rethrowing</Text><Number>2230</Number><Insert><Text>PUB_Batch.RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.WBR_1BUS__Solaceflow.SOLACE_JMSConnection_Java Compute</Text></Insert><UserException><Label></Label><Text>Unhandled exception in plugin method</Text><Number>4367</Number><Insert><Text>evaluate</Text></Insert><Insert><Text>RouteToMessageFlow.CustomerMessageFlows.Customer_IC_STD_NTFY_MSG001_DOBChg.WBR_1BUS__Solaceflow.SOLACE_JMSConnection_Java Compute</Text></Insert><Insert><Text><com.ibm.broker.plugin.MbUserException class:com.Enterprise01.solace.Enterprise01Solace_JavaCompute method:evaluate() source: key: message: Unable to resolve message: Source: Key: ></Text></Insert><UserException><Label></Label><Text>Unhandled exception in plugin method</Text><Number>4394</Number><Insert><Text>com.ibm.broker.plugin.MbUserException</Text></Insert><Insert><Text>com.Enterprise01.solace.Enterprise01Solace_JavaCompute</Text></Insert><Insert><Text>evaluate()</Text></Insert><Insert><Text>Enterprise01Solace_JavaCompute.java</Text></Insert><Insert><Text>142</Text></Insert><Insert><Text>javax.jms.JMSException: Error creating producer - transport error (ClientRequestResponse Timeout (ADCTRL-ProducerOpenFlow))</Text></Insert><Insert><Text></Text></Insert><Insert><Text></Text></Insert></UserException></UserException></RecoverableException></RecoverableException></RecoverableException></RecoverableException></RecoverableException></RecoverableException></RecoverableException></BrokerData></Environment></Message> _________________ skr_wmb |
|
Back to top |
|
 |
abhi_thri |
Posted: Wed Feb 17, 2021 12:11 am Post subject: |
|
|
 Knight
Joined: 17 Jul 2017 Posts: 516 Location: UK
|
hi...right, i was hoping that the java error trace might give a bit more diagnostic info.
Anyway, as you mentioned that the transient timeout started happening during high volume scenarios, have you looked at how the connections are managed? For eg:- are the connections opened/closed too frequently which might explain why some attempts are timing out as both sides are busy or is it handled more efficiently (reused for multiple messages)?
there is a similar thread on the solace forum, is that your thread as well?
https://solace.community/discussion/601/solace-jms-transport-errors |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|