| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error Making JNI Call |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sosed |
 Posted: Thu Nov 21, 2013 10:57 pm Post subject: Error Making JNI Call |
 |
|
Apprentice
Joined: 24 Aug 2012
Posts: 43
|
Hi everybody!
I use MB 8.0.0.2 in RHEL.
Sometime I get JMS error:
| Code: |
| 3620 - Error making a JMS request. '<<QUEUE_NAME>>' 'jms:jndi:<<QUEUE_NAME>>' '' '300' '0' 'WebSphere_MQ' '' 'bytes' 'com.sun.jndi.fscontext.RefFSContextFactory' 'A SOAP request encountered an error sending a JMS request to the Destination &1.' 'Error Making JNI Call: com_ibm_broker_axis2_Axis2JMSTransportHelper_sendReceiveJmsRequest' |
| Code: |
| [BIPmsgs:4651]BIP4651E: JMSClient. 'Broker '<<BROKER_NAME>>'; Execution Group '<<EG NAME>>'; Message Flow '<<MF NAME>>'; Node '<<SOAP Request node name>>' ' A JMS exception occurred when the node tried to send a JMS message. If available the JMS exception text is : '<<SOAP Request node name>>' ||The node could not send a JMS message on the JMS session. The JMS provider returned an exception. ||Investigate the cause of the JMS exception. If the problem persists, contact the vendor of the JMS provider. : Failure sending JMS message| |
Why SOAP Request node couldn't send a JMS message on the JMS session? What can be a reason of such behavior?
Thanks in advance!
Full exception list is:
| Code: |
3641 - A SOAP Request node had an error making a JMS request.
3620 - Error making a JMS request. '<<QUEUE_NAME>>' 'jms:jndi:<<QUEUE_NAME>>' '' '300' '0' 'WebSphere_MQ' '' 'bytes' 'com.sun.jndi.fscontext.RefFSContextFactory' 'A SOAP request encountered an error sending a JMS request to the Destination &1.' 'Error Making JNI Call: com_ibm_broker_axis2_Axis2JMSTransportHelper_sendReceiveJmsRequest'
3701 - Error Making JNI Call: com_ibm_broker_axis2_Axis2JMSTransportHelper_sendReceiveJmsRequest 'com_ibm_broker_axis2_Axis2JMSTransportHelper_sendReceiveJmsRequest' 'BIP3620E: com.ibm.broker.axis2.MbSoapException: Error making a JMS request.' 'Frame : 0 com.ibm.broker.axis2.MbSoapException: Error making a JMS request.| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.sendReceiveJmsRequest(Axis2JMSTransportHelper.java:214)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.soap.SoapWrapperNode.evaluate(SoapWrapperNode.java:132)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:671)| @: com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:398)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbRoute._propagate(Native Method)| @: com.ibm.broker.plugin.MbRoute.propagate(MbRoute.java:95)| @: com.ibm.broker.soap.SoapExtractNode.routeToOperationLabelNode(SoapExtractNode.java:405)| @: com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:186)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)|Frame : 1 com.ibm.broker.axis2.MbSoapException: A SOAP request encountered an error sending a JMS request to the Destination &1.| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.makeJmsRequest(Axis2JMSTransportHelper.java:274)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.sendReceiveJmsRequest(Axis2JMSTransportHelper.java:130)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.soap.SoapWrapperNode.evaluate(SoapWrapperNode.java:132)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:671)| @: com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:398)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbRoute._propagate(Native Method)| @: com.ibm.broker.plugin.MbRoute.propagate(MbRoute.java:95)| @: com.ibm.broker.soap.SoapExtractNode.routeToOperationLabelNode(SoapExtractNode.java:405)| @: com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:186)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)|Frame : 2 org.apache.axis2.AxisFault: Error sending JMS message| @: com.ibm.broker.axis2.WMBOutboundJMSTransport.finish(WMBOutboundJMSTransport.java:615)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.makeJmsRequestInternal(Axis2JMSTransportHelper.java:340)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.makeJmsRequest(Axis2JMSTransportHelper.java:249)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.sendReceiveJmsRequest(Axis2JMSTransportHelper.java:130)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.soap.SoapWrapperNode.evaluate(SoapWrapperNode.java:132)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:671)| @: com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:398)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbRoute._propagate(Native Method)| @: com.ibm.broker.plugin.MbRoute.propagate(MbRoute.java:95)| @: com.ibm.broker.soap.SoapExtractNode.routeToOperationLabelNode(SoapExtractNode.java:405)| @: com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:186)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)|Frame : 3 com.ibm.broker.plugin.MbRecoverableException: [BIPmsgs:4651]BIP4651E: JMSClient. 'Broker '<<BROKER_NAME>>'; Execution Group '<<EG NAME>>'; Message Flow '<<MF NAME>>'; Node '<<SOAP Request node name>>' ' A JMS exception occurred when the node tried to send a JMS message. If available the JMS exception text is : '<<SOAP Request node name>>' ||The node could not send a JMS message on the JMS session. The JMS provider returned an exception. ||Investigate the cause of the JMS exception. If the problem persists, contact the vendor of the JMS provider. : Failure sending JMS message| @: com.ibm.broker.jmsclientnodes.JMSClientErrors.throwException(JMSClientErrors.java:694)| @: com.ibm.broker.jmsclienthelper.JMSClientHelper.sendOutputMessage(JMSClientHelper.java:3036)| @: com.ibm.broker.jmsclienthelper.JMSClientRequestResponseHelper.makeJMSRequest(JMSClientRequestResponseHelper.java:1329)| @: com.ibm.broker.axis2.WMBOutboundJMSTransport.finish(WMBOutboundJMSTransport.java:589)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.makeJmsRequestInternal(Axis2JMSTransportHelper.java:340)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.makeJmsRequest(Axis2JMSTransportHelper.java:249)| @: com.ibm.broker.axis2.Axis2JMSTransportHelper.sendReceiveJmsRequest(Axis2JMSTransportHelper.java:130)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.soap.SoapWrapperNode.evaluate(SoapWrapperNode.java:132)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:671)| @: com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:398)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)| @: com.ibm.broker.plugin.MbRoute._propagate(Native Method)| @: com.ibm.broker.plugin.MbRoute.propagate(MbRoute.java:95)| @: com.ibm.broker.soap.SoapExtractNode.routeToOperationLabelNode(SoapExtractNode.java:405)| @: com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:186)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)'
|
|
|
| Back to top |
|
 |
| Sosed |
| Posted: Mon Dec 02, 2013 6:27 am Post subject: |
|
|
Apprentice
Joined: 24 Aug 2012
Posts: 43
|
I discovered, that the problem occurs when input message is about 4 Mb. When message payload is less than 4 Mb, flow successfuly processes it.
Firstly, I have checked MQ queues's "max message length" property. It had value 104857600 bytes (100 Mb).
Than, I have tried to create JMS queue definition via JMSAdmin with predefined "max message length" property. But I couldn't. There are no properties like
"MAXMSGS", "SIZE", "MSIZE", "MAXSIZE", "MSGSIZE"
"MAXMSGL", "LENGTH", "MLENGTH", "MAXLENGTH", "MSGLENGTH"
in the JMSAdmin tool.
Guy, Do you know how to set up max message size on a JMS queue definition? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Dec 02, 2013 7:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There is a little more to setup properly in these cases.
This http://www.ibm.com/developerworks/websphere/library/techarticles/0506_barrago/0506_barrago.html
will help you understand that at least one other WMQ object need to have it's length setup correctly.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Esa |
| Posted: Mon Dec 02, 2013 10:24 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| Sosed wrote: |
Firstly, I have checked MQ queues's "max message length" property. It had value 104857600 bytes (100 Mb). |
I guess you are putting messages in a remote queue, which means that the message is being put in a transmission queue. For compatibility reasons transmission queues usually default to 4 MB max msg length... |
|
| Back to top |
|
|
| Sosed |
| Posted: Wed Dec 18, 2013 5:16 am Post subject: |
|
|
Apprentice
Joined: 24 Aug 2012
Posts: 43
|
| Esa wrote: |
I guess you are putting messages in a remote queue, which means that the message is being put in a transmission queue. For compatibility reasons transmission queues usually default to 4 MB max msg length...
|
Hi, Esa.
Thanks for your reply.
It is a interesting supposition, but I have no transmittion queues. All queues are local.
Hi, smdavies99.
Yes, it has helped. I've changed channel's message max length, restarted broker, mq and it worked. Error doesn't appear anymore.
Thank you for your help. |
|
| 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
|
|
|
|
