JMS Channel in Error

Hi,
In one of the our production systems we are facing a problem with JMS Communication channels (both sender and receiver) for one of the synchronous interface.
Though the messages are processing successfully we see the channel status in error(RED LED). This happend after upgradation of sevice pack. Is there any SAP note that has to be implemented?
Any pointers will be highly appriciated.
Thanks and Regards.
Saipriya.

Though the messages are processing successfully we see the channel status in error(RED LED).
During the upgrade the channel might have got some request to be processed and could have not been able to do it....so the status would have turned to red.....normally in such cases one option is to Stop and Start the channel...but since it is a production environment avoid using this option (at least during message processing period).
Sometimes the status does not change to green (even if the channel is working fine)
Regards,
Abhishek.

Similar Messages

EOIO JMS Sender Channel in Error

Hi All,
We have a error on JMS sender channels in Pre-Production environment.
Let me explain you the problem.
On Dev and QA there is no cluster environment. On Pre-production we have 3 clusters. We tested this Sender JMS channel on Dev and QA without giving a Cluster ID and it worked.
Now on Pre prod, we had not mentioned the cluster ID and when messages were picked from the Queue, the channel went into a error mode stating the " Channel is locked due to EOIO".
Then when we added the cluster ID to the channel, in RWB the channel goes into inactive mode. The status is " The EOIO channel has been made inactive on Node 206485150"
The node mentioned in channel is 251902150. This means that the other node has been made inactive. That sounds logical as it is not supposed to process the message.
But the node which is mentioned in the channel has also gone into error mode.
" Error creating JMS connection. failed to create MQManager for ' Hostname:Channel name'". An MQException occured: Completion code 2, Reason 2009
MQJE016: MQ queue managerclosed channel immediatly during connect. Closure reason= 2009, and erro code as MQJMS2005
After this all other sender JMS channels have gone into the same error mode on this node.
We have stopped the JMS service and started it. We also restarted the XI server but no change was encountered.
Please let us know whether JMS sender with EOIO works with cluster ID as I'm not able to find any document which says that JMS with EOIO works succesfully.
Please also let us know how to overcome the error on this node.
Thank you.
Regards,
Sarvesh Desai

Check if there is any unprocessed message stuck in the queue:
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework

Sender JMS Channel Error

Hi all,
I have been facing with this problem with sender JMS channel, any pointers as to where can be the solution for it
The error details are as follows
JMS and XI identifiers for the message are ID:414d512056515933444e41575445202048aa8802235bad01 and a2d32e30-7aae-11dd-ae1c-001125cc0c0c respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:963)
at com.ibm.mq.jms.MQMessageConsumer.receiveAsyncQ(MQMessageConsumer.java:2539)
at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4262)
Messages are not being placed in the Queue. the Queues are newly created is there something which has been missed out during the creation of the Queues
Rgds
Aditya

Hi Aditya
Try this way:
1. uncheck JMS transactional session check box in JMS sender communication channel.
2. Once it is done, insert new message in JMS queue.
Thanks
Sai

Error in JMS channel

Hi ALL,
I am getting the below error in Communication channel monitoring short log of JMS channel.
"Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing; ensure that JMS provider library 'aii_af_jmsproviderlib.sda' contains all required resources"
This error looks like the deployed .sda file dint contain the class specified.Can u let me know where i can find the aii_af_jmsproviderlib.sda file with all required classes in it .
We are on SAP XI 7.0 SP 14 and the MQ version is 7.0.
Kindly let me know if any one had faced the same error.
Regards,
Rajesh

Hi, check this links.
XI to IBM Websphere Default JMS Provider with JNDI
JMS receiver adapter configuration error
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Edited by: Marco Salazar on Dec 9, 2009 5:24 PM

Receiver JMS Channel Error

hi,
I am facing an issue with the JMS Receiver Communication channel.Data is not getting inserted in the JMS Queue.CC Monitoring is showing the below ERROR:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_r_CustomerLedgeron node: 7065651 having object id: 340fa47e4dc33a04a4f8a5a108708f07 encountered error: Error sending message in sending to destination custLedgerReplication, the message message: TextMessage[null, <?xml version="1.0" encoding="...]: weblogic.jms.common.JMSException: Error sending message.
can someone helpme out.
thanks,
robin

Hello Robin,
did you resolve this issue? I have now the same problem.
Do you have connections with two (or more) BEA servers using the same Adapter Framework?
Note 1090516 describes a problem with credentials confusion when connecting to more servers.
It could be the cause.
With regards
Tomas

JMS Channel error

JMS Channel is thrrowing error with an error code:2007.
Error code description is "CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)".
But i didnt understood this jargon.
Could anyone help me what i need to do to fix this .
Thanks in advance.

Hi Pola,
I have never faced this error but as in my helping nature here are some pointers:
CharAttrLength (MQLONG) - input
Length of character attributes buffer.
This is the length in bytes of the CharAttrs parameter, and must be at least the sum of the lengths of the character attributes specified in the Selectors array. Zero is a valid value if there are no MQCA_* selectors in Selectors.
CharAttrs (MQCHAR×CharAttrLength) - input
Character attributes.
This is the buffer containing the character attribute values, concatenated together. The length of the buffer is given by the CharAttrLength parameter.
The characters attributes must be specified in the same order as the MQCA_* selectors in the Selectors array. The length of each character attribute is fixed (see Selectors). If the value to be set for an attribute contains fewer nonblank characters than the defined length of the attribute, the value in CharAttrs must be padded to the right with blanks to make the attribute value match the defined length of the attribute.
If the CharAttrLength or SelectorCount parameter is zero, CharAttrs is not referred to; in this case, the parameter address passed by programs written in C or System/390 assembler may be null.
Regards
joel

JMS Sender Channel: Linked Error

Hi All,
I'm working on a synchronous JMS to Proxy scenario. I have created Sender JMS channel. In RWB, the status of the channel is error.
The error is:
Channel Error occured. Detailed error (if any): JMS error: MQJMS1024: session closed, Linked error: Error code: MQJMS1024
This channel was working fine few weeks back. Since last week we are facing this issue.
I deleted the communication channel and created a new one but the error persists.
We also tried by restarting the J2EE engine but still no change.
Also gave a try by restarting the Queue manager still there was no change.
Please provide your suggestions to solve this issue.
Regards.,
Sarvesh Desai
Edited by: Sarvesh Nispat Desai on Oct 27, 2009 12:37 PM

Hi Sarvesh,
*Are you using Websphere MQ JMS server? *
If yes check this note Note 1278718 - IBM MQ Connectivity Issues with JMS Adapter
also this error requires restarting the session
ftp://ftp.software.ibm.com/software/mqseries/fixes/wbimbfev50/fixpack03/C3466662.pdf
Regards
Suraj

JMS Channel error reson code : 2019

JMS Channel is throwing error with an reason code : 2019.
Decription for reason code 2019 is : The object handle Hobj is not valid, for one of the following reasons:
The parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
The value specified was not returned by a preceding MQOPEN call.
The value specified has been made invalid by a preceding MQCLOSE call.
The handle is a shared handle that has been made invalid by another thread issuing the MQCLOSE call.
The handle is a nonshared handle that is being used a thread that did not create the handle.
The call is MQGET or MQPUT , but the object represented by the handle is not a queue.
Can any one tell me what is to be done to fix this error.
Thanks in advance.

Hi
Yes this is an MQ Series "Reason Code", Where each reason code for failing is assigned a number. For this one please refer to the following link:
http://www-01.ibm.com/support/docview.wss?uid=swg21229508
For all reason codes have a look at:
http://middleware.its.state.nc.us/middleware/Documentation/en_US/htm/csqzak06/csqzak065m.htm
Thanks
Damien

PI 7.0 SP15 alerts JMS Duplicate message error

Hi all,
We have a scenario where in we receive BAPI calls to R/3 from web through MQ and XI.
WEB -> MQ->XI->R/3 (Request / Response send back similarly)
We have modular configuration in the channel.
All these BAPI messages are queries needed to build an order for example product information / customer information etc.
We have PI 7.0 SP15
Sometimes we receive the error ' Duplicate JMS message with JMS ID##### detected.Duplicate will be ignored' in the sender JMS channel.Because of this error XI is not able to process subsequent messages and the channel keeps on throwing the same error.We need to clear the queue and then restart the channel to make it work.
Can any one please tell me what is the reason for occurence of this error..?
Is this ID generated in JMS or in XI?If so how this could be handled without clearing the queue's..?
When we analyzed the messages in the queue we found out same xml messages been send twice which i would imagine the query been send twice(which is a possiblity from the web) would that have caused this JMS duplcate message error??!!
Also because of this error XI is throwing multiple alert messages at the rate of 3 per second which is causing the huge performance hit as the alert inbox gets filled up..We did put the suppress multiple alert check..but before somebody reacts to these alerts there are numerous of them created..any suggestions on this is much appreciated..
Thanks for your help in advance
Larry

Larry,
Is that alert rule is generic or interface specific? If it is generic then please make it interface specific.
Thanks,
Sunil

Zip or unzip a payload in sender JMS channel

Hi,
My scenario is to unzip a payload in sender JMS channel and I have configured the sender JMS module in the below format,
Processing sequence
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
Module Configuration
Modulekey            Parameter Name                    Parameter Value
zip                        zip.mode                                unzip
I have tried this format also,but it is not working
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
(or)
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
While performing testing,it throws the below error in sender JMS channel,
The detailed error (if any) is : com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable pattern: NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'pattern'at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:185)
Can someone help me on how to extract a payload in sender JMS channel.
Also please guide me on how to extract a multiple payloads in one zip file in sender JMS channel.

Hi,
Your module sequence seems to be incorrect.
Try like this,
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
(or)
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
Regards,
Praveen Gujjeti

Unzip a payload in sender JMS channel

Hi,
My scenario is to unzip a payload in sender JMS channel and I have configured the sender JMS module in the below format,
Processing sequence
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
Module Configuration
Modulekey            Parameter Name                    Parameter Value
zip                        zip.mode                                unzip
While performing testing,it throws the below error in sender JMS channel,
The detailed error (if any) is : com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable pattern: NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'pattern'at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:185)
Can someone help me on how to extract a payload in sender JMS channel.
Also please guide me on how to extract a multiple payloads in one zip file in sender JMS channel.

Hi,
Your module sequence seems to be incorrect.
Try like this,
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
(or)
SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
Regards,
Praveen Gujjeti

Receiver JMS ( websphere MQ ) error - No transition found from state:ERROR

Hi all
we are using JMS adapter to connect to the Queue manager . whenever the queue manager restarts , the messages is not getting thru and it is struck in the adapter engine with status " not to be delivered "
i am getting error in receiver communication channel audit log....its showing
*MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_XXXXXXXXX:15fa03eb9fd837849906f512610314c4*
note : already i have gone thur many forum and nothing helps.
Thanks in advance
Faheem

If you are using the FCC then this could be because of that. What is the connection status with MQ? Are there any connection errors with MQ.
If you are using FCC in your Receiver JMS channel then just to confirm, first remove the FCC configuration and try to send a xml file. If the xml file goes in successfully then the problem is in your FCC configuration.

JMS channel issue

Hi
My XI system is set-up with alerts frame-work and we are able to raise almost all the system generated alerts. But we are facing one issue with JMS channel alerts. Lets me explain the problem.
We have a JMS channel connected to JMS Server and we are publishing the messages on JMS queue. When JMS server is down, the channel status is not turning into red and it is staying in gree only. If we see the messages in adapter engine (through message monitoring) they are in delivering mode and they are not going into system error state. So either of the things are not triggering any system alerts. So are there any parameters that we can set-up in JMS channel or somewhere so that when JMS server is down, we can raise the system alerts ?? We are using the EMS server for hosting the JMS queues.
thanks
kumar

Hi Moorthy
yes! as you said, my main problem is..... channel is not turning into red, eventhough my JMS server is down and there by not able to raise the alert in either of the two cases. (Adapter Engine based standard alerts or CCMS Alerts). Is there any option to set through which when jms server is down, channel will become red ??
thanks
kumar

"Unable to find channel ID" error.

Hello experts,
We are building an IDOC->XI->JMS scenario.
Sending the IDOC gets it into the XI and it is visible inside the SXMB_MONI. Looking at a trace level 3 on the trace section of the message you can see that all pipeline activities are performed as normal.
The last action of the Outbound Binding is successful and the correct Communication channel name (from the Receiver Agreement) is displayed in the trace - meaning was selected.
Looking in the RWB on the details of the message show that:
- message was received from http://xiserver:50000/MessagingSystem/receive/AFW/XI
- The message goes in and out of the receive queue.
- the message status set to DLNG
- Unable to find channel ID.
- ... error stuff..
This Channel ID error is the one who causes us trouble.
Looking at the same place for a PROXY->XI->JMS scenario shows that the correct channel is selected. this channel is the channel in the receiver determination - the name only exists there so it doesn't relate to any other channel (like MQ channel).
Could really use help finding this problem source or activating J2EE traces the could point to what's wrong.
Thank's - Yoad.

Hi,
One thing which could be wrong is the cache. Try in the IB:Directory to see if all things have been succesfully committed to the CPA.
Then try to refresh the CPA cache. http://xiserver:50000/CPACache/refresh?mode=full (Login as XIDIRUSER)
If you are on SP 12, you could use NW administrator on http://xiserver:50000/nwa -> select Monitoring -> Logs and traces and in the blank dropdownbox select Default trace.
Hope this helps

Communication Channel in error

Communication Channel in error though the error has been resovled. New files are processed succesfully !!!
CC still in RED.
I tried the basic steps which can change the status .( by deactivating the channel and activating the same , stopped and started the same ) . It resulted the same.
Thanks,
Karthik

The information that is displayed for the status of a channel on the individual cluster nodes is status information that is accumulated to give the overall status of the channel in the table of communication channels.
If the cluster nodes have at least one status that is above all other statuses in the status hierarchy, the channel receives this status as the overall status. The possible statuses correspond to those in the table of communication channels and have the following hierarchy: (red), (yellow), (green), and (gray). A combination of green or yellow with gray is not possible.
○       The information displayed for the processing entries of the selected cluster node is current runtime information on message processing. You get to Message Monitoring by selecting the message ID displayed.
Depending on the adapter used, the type and occurrence of the information here can differ. The information forms the entry in the Processing Errors column in the table of communication channels. The newest result is taken from the table of the cluster nodes.
○       The information about channel administration displays when and by whom a channel was previously started or stopped. You can only start or stop a communication channel for an entire server cluster, not on individual cluster nodes. However, since errors can occur on individual cluster nodes during the execution of these actions, error information is also displayed for each cluster node.
○       If the channel is controlled by availability times, the Availability Times tab page is displayed. All other availability times that are relevant for this channel are also displayed. You can exclude specific availability times and, if necessary, reschedule them.
Since only active availability times are displayed, it is possible that availability times do exist for the selected communication channel even if none are displayed.
○       The information on the Settings tab page displays how often an attempt is made to send messages to this channel, and at what time intervals.
The default settings are taken from the outbound properties for the J2EE service SAP XI Adapter: XI. You can overwrite and save these values. You can also restore overwritten values.
Information about changes made to the settings is always displayed.
The Settings tab page is only relevant for receiver channels and is therefore only displayed for channels of this type.
regrads
chandra

JMS Channel in Error

Similar Messages

Maybe you are looking for