on 12-10-2011 1:59 AM
Hi All,
I faced an issue in JMS receiver communication channel , channel failed with error :
"Error while processing message '4ee1ba28-e310-5b04-e100-00000a3597a1'; detailed error description: com.sap.aii.af.ra.ms.api.MessagingException: ERROR_CODE_JMS_TRANSMISSION at com.sap.aii.adapter.jms.core.channel.ReceiverChannelImpl.doSend(ReceiverChannelImpl.java:171) ..."
and after some time message got processed after 3 retries automatically.
however we noticed this error cause huge impact on the system which include the slowness in processing for other interfaces.
We are facing this issue quite often in our system .... kindly let me know if anyone faced the same error and any input would be appreciated .
I know this is an old post but for those who stumble upon this error:
I did some tracing with XPI Inspector (50 XI Channel + Messaging System + XI Module Processor) specifying the JMS Channel in channel selection table.
For me, the reason for this nonspecific error was a missing method "com.ibm.msg.client.jms.JmsMessageProducer.send". This issue is described in note 1343759.
This is, what the stack trace looked like
12:35:34:419 | J2EE_GUEST | ~_StockRemovalRequest/BS_D_MQ/]_2876 | ~l.filter.TxManagerFilter.filterRecv | Catching java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsMessageProducer.send(Ljavax/jms/Message;IIJ)V at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:333) at com.sap.aii.adapter.jms.core.connector.SendContextImpl.doQueueSend(SendContextImpl.java:130) at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:53) at com.sap.aii.adapter.jms.core.channel.filter.SendToJmsProviderFilter.filter(SendToJmsProviderFilter.java:138) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.OutboundCorrelationFilter.filter(OutboundCorrelationFilter.java:102) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterRecv(TxManagerFilter.java:76) at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:63) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.OutboundDuplicateCheckFilter.filter(OutboundDuplicateCheckFilter.java:195) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToJmsMessageFilter.filter(ConvertBinaryToJmsMessageFilter.java:87) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.ConnectOnDemandFilter.filter(ConnectOnDemandFilter.java:58) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.ConvertXiMessageToBinaryFilter.filter(ConvertXiMessageToBinaryFilter.java:132) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.OutboundAcknowlegmentFilter.filter(OutboundAcknowlegmentFilter.java:56) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62) at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:199) at com.sap.aii.adapter.jms.core.channel.ReceiverChannelImpl.doSend(ReceiverChannelImpl.java:139) at com.sap.aii.adapter.jms.core.channel.ChannelImpl.send(ChannelImpl.java:460) at com.sap.aii.adapter.jms.core.channel.AdapterImpl.send(AdapterImpl.java:603) at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.sendToAdapter(AdapterServiceFrameImpl.java:203) at com.sap.aii.af.mp.jms.ejb.SendBinarytoXIJMSService.sendToAdapter(SendBinarytoXIJMSService.java:464) at com.sap.aii.af.mp.jms.ejb.SendBinarytoXIJMSService.process(SendBinarytoXIJMSService.java:98) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_8.process(ModuleLocalLocalObjectImpl0_8.java:103) at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:296) at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103) at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:343) at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103) at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:276) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1074) at com.sap.aii.af.ra.ms.impl.core.queue.consumer.ReceiveConsumer.processMessage(ReceiveConsumer.java:296) at com.sap.aii.af.ra.ms.impl.core.queue.consumer.ReceiveConsumer.onMessage(ReceiveConsumer.java:79) at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:1004) at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) | |
12:35:34:420 | J2EE_GUEST | ~_StockRemovalRequest/BS_D_MQ/]_2876 | ~l.filter.TxManagerFilter.filterRecv | TxManagerFilter received an throwable error: java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsMessageProducer.send(Ljavax/jms/Message;IIJ)V in processing message: 521b4d67-e4ea-1070-e100-80000a060198 for ConnectionProfile of channel: CC_JMS_RCV_StockRemovalRequeston node: 3791850 having object id: 6dfbdecc3334372a8a05860e3ba4b57eWill attempt rollback. |
Bottom line:
Use XPI inspector wherever possible to get a more insight view of the problem 🙂
Will keep this thread updated to let you know if the solution described in note 1343759 worked for me.
Cheers
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anuj,
This is because of the huge message size. The channel will pick the message but when it tries to post it to the target and if the target does not accept huge size, then the message will fail in PI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i beleive this error could be connectivity issue btwn PI and JMS System.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anuj,
Try to edit and re-activate the communication channel.
Regards
Ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.