Error in JMS communicatin channel while deleivering to WMQ server

How to check whether a node in Adapter engine is having messaging service active?
I am having one of the JMS receiver node having error :
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_Americas_EDI_Receiveron node: 101565650 having object id: #MSGid# encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException in sending to destination queue:///NASB.UPXI.EDI.INBOUND.AQ, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:3258af50-24e0-11dd-bc98-3c2ac1cacf6e JMSDestination: null JMSReplyTo: null JMSRedelivered: false ReceiverId: ### SenderId:### ISA00 00 124165122352 *08 080 5180935U00401 Another 478 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException"
The second Line for same mssg id provides follwing info:
""JMS error occurred while processing message 'MSGIDe'; error mesage: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException null; error code: MQJMS1016"
Can anyone suggest what can be a fix over this. We have tried restyrting j2ee also but the still persists.
Expect points for sure.
Regards,
Nipun

Hey All,
Following is the solution for the above mentioned JMS receiver channel problem whilst connecting to MQ Series Server.
I assume you are connecting to a MQ series server with version less then 7.xx, or MQ Server 5.xx,
Cause of Problem: The problem appears when you try to send a message through JMS Receiver Adapter channel to a such MQ server and at that particular moment, the server do not accepts the message i.e. the connection with MQ Server drops out; resulting in a Java null pointer error, as the MQ fails to assign the pointer back to the same message, { again until its transferred to MQ.} therefore MQ JMS 2003, MQJMS2007 and MQJMS1016 error appears.
Possible configuration at XI/PI:
1. Add a Advanced additional JMS parameter Connection_Test_Poll = True
2. For XI settings from the drop down of field "Handling of Pending XI messages" select "Bypass Pending Warning and Send Message to JMS(Duplicates possible)" . This will probably cause duplicates at MQ series Server side, make sure you are ready to encounter it there!!
3. If the error still appears, choose In the Error Handling settings, Reconnection if Exception text Starts with provide the error number which the message is currently experiencing. eg. MQJMS1016 or MQJMS2007 or MQJMS2003. Restart the communication channel and restart such message..
After applying the above settings if you still experience errors MQJMS2007, 2003 and MQJMS1016, when connecting and processing messages to MQ server, Then you should try upgrading the MQ Series server! You cannot do much in the XI/PI system else you will create duplicates in the MQ system.
Please Note this error has more to do with the compatibility issue of MQ Series server with PI's JMS adapter.
Do let me know if you have any more queries on this.
Regards,
NIPUN

Similar Messages

Error in JMS Communication Channel not raising alert

Processing Errors in JMS Communication Channel are not raising alerts.
The settings on the communication channel retires are set at 3 and 5min interval.
In RWB the JMS communication channel shows processing errors but an alert is not raised.
The alert are configured in our system and we even have a catch all alert rule with * (wildcard). Errors in PI message processing are raising alerts but errors in Comm Channel are not raising alerts.
The message in SXI_MONITOR shows as processed successfully but when we check the RWB and Comm. Channel Monitoring we see processing errors "Channel error occured; detailed error description: JMS error: Connection to the server has been terminated; Linked error: Connection reset, Error Code:null"
Are we missing any configuration? How do we get alerts/notifications if there are errors in Comm. Channel without having to login into RWB and watch it periodically?
Any help is greatly appreciated.
RM

Hi,
What is the staus of Communication channel in RWB when it fails, RED ??if yes then it should genarate alert.
create one more alert for specific to JMS interface and check it out.
Regards,
Raj

Error in JMS receiver channel

Hi,
I have a JMS receiver channel which is connected to message queue of TIBCO which is working fine.
But if I use the same channel after a day it goes into error and after restart of the channel it again works fine.
Error: Message process failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to write newJMS Message body for message: 343241-......... Connector Exception: ... session ended..
Thanks,
Aravind

Hello Aravind,
I have made similar experiences while accessing JMS queues.
Maybe the JMS queue was not available for a short time. So the receiver channel could not connect.
Best regards,
André

Error in JMS Input channels

Dear all,
We have observed a peculiar issue.
Some of the JMS Input channels are throwing this error:-
"Error establishing JMS connection; error message: MQJMS2005: failed to create MQQueueManager for <IP>:<QM Manager>> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009; error code: MQJMS2005"
Other JMS channels with the same configurations are working fine. But some JMS channels have this error.
If any one has faced a similar issue, kindly share the steps to resolve the same.
Thanks in advance,
Younus

Please ask the MQ Team to restart the MQ queue.I mean to stop and start again.
We faced similar kind of issues and we even tried to restarting the JMS communication channel and MQ Queue.This solved our problem.
As only one JMS channel is not working,there might be connectivity issues with JMS Queues..
Try to restart the JMS Queue and JMS communication channel and see.

Error with JMS receiver channel

Hi,
We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
After the restart of JMS, we are facing issues with JMS receiver channel.
Some of the responses are delivered, and for few we have the error as described below.
Also, one of the cluster node of the JMS receiver channel has the below error.
Please anybody throw some light on this.
Error description:
" Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.. "
Thanks in advance.
Regards
Bhanu Tiruveedula.

Hello Bhanu,
we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
regards,
Ratna

Errors on JMS communication Channel sonicMQ JMS Provider netweaver2004s

After deploying supplier specific jar's Sonic_Client.jar into aii_af_jmsproviderlib.sda.
I get the following error in the communication channel monitoring.
Channel CC_SONIC_RECEIVER is errornous, hence it cannot be started. See error messages ( Error during channel initialization; exception trace: java.lang.ClassCastException
     at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:372)
     at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     ...) before. Reconfigure it or restart the JMS service!
Any suggestions about the cause...

yes the drivertool.bat does it for me
<?xml version="1.0" encoding="UTF-8"?>
<provider-descriptor>
    <display-name>com.sap.aii.af.jmsproviderlib</display-name>
    <component-name>com.sap.aii.af.jmsproviderlib</component-name>
    <major-version>7</major-version>
    <minor-version>0</minor-version>
    <micro-version>6</micro-version>
    <provider-name>sap.com</provider-name>
      <references>
         <reference type="library" strength="weak">jms</reference>
      <reference type="library" strengh="weak">com.sap.aii.messaging.runtime</reference></references>
    <jars>
    <jar-name>sonic_Client.jar</jar-name><jar-name>sonic_XA.jar</jar-name></jars>
<
At this moment i am receiving the following error on the communication channel
Exception caught by adapter framework: The JMS channel with channel ID f055fe2451203cd5b39d81c7647b281e is errornous. Details:Error during channel initialization; exception trace: javax.jms.JMSException: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:2600 at progress.message.jimpl.JMSExceptionUtil.createJMSException(Unknown Source) at progress.message.jimpl.Connection.(Unknown Source) at progress.message.jimpl.QueueConnection.(Unknown Source) ... [104] progress.message.client.ENetworkFailure: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:260

Error in JMS receiver channel - XI - Weblogic

Hi Experts
We are also having the situation that we are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic server.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory----
ConnectionFactory
JNDI Lookup Name of JMS Queue----
queue/IntegrationQueue
Name of JNDi Initial Context Factory: -
weblogic.jndi.WLInitialContextFactory
JNDI Server Address:----
weblogic server ip
JNDI Logon User: -
user
JNDI Password: -
password
We are getting the error in the adaptor like " com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA:"
Could you please tell me if there are any other JAR files for this as i have already deployer weblogic.jar. If yes, Can you please give me some more details on that.
Thank you very much for your time and help.
Manjunath
Edited by: Manjunath Achar on May 23, 2010 4:12 PM

Hi Manju
There could be some problem while deploying the libraries. please check you have deployed the JAR Files correctly.
You need to include the Weblogic Thick client driver 'weblogic.jar' - with all classes under the package 'javax.jms' removed in your aii_af_jmsproviderlib.sda (releases 3.0/7.0) or com.sap.aii.adapter.lib.sda (releases 7.1).
The below links might be helpful for you,
http://wiki.sdn.sap.com/wiki/display/XI/FAQ+J2EEJMS+Adapter
Note 1090516 - XI JMS Adapter and BEA Weblogic JMS: FAQ
Regards
Ramg

MSTDC Error in clustered Environment in while interacting to DB Server from BizTalk server

Hi All,
After completing all my required Biz-talk Integrations (All were related to WCF-Custom Adapter : SQL Binding), I deployed the same to the client environment. But, the same thing which worked for me in my development environment was giving some issues in
the deployed environment.
The main difference was, at client environment - The DB Server was clustered environment and the interaction was through the load balancer.
The first issue I encountered was, there was firewall blocking the access to the DB server from Biz Talk server. Then after enabling and opening the Port 1433, the issue got fixed and I was able to communicate with the DB Server.
After this, I was getting the error related to MSTDC. For this to work properly, in my BizTalk application Configuration, if i set the property for "UseAmbientTransaction" as false under "SqlBinding" for the WCF-Custom Send Port, it is
working as expected!
But, I heard from our Architects that the best approach is to set the property as "TRUE" for "UseAmbientTransaction" property.
So I set the property as true and done the below configurations.
1. Enabling Network DTC using "dcomcnfg.exe"
2. Adding and enabling Fire wall exception for DTC.
Even after making the above changes, I was getting the same error. Then after cross checking with DTCPing and DCTester on both local and deployed copy, i got the below difference.
1. Port 135 (RPC EPM) was opened in my local environment but it was having "Filtered" access at the deployed copy.
So my question is, after opening the above port, will it solve the issue?
Secondly, is there any security threat ter opening the above Port?
Any quick suggestion/solution is highly appreciated.
Thanks in Advance,
Anand

Hi Anand,
Performing operations on SQL Server using BizTalk Server always involves two resources—the adapter connecting to SQL Server and the BizTalk Message Box residing on SQL Server. Hence, all operations performed using BizTalk Server are performed within the
scope of an MSDTC transaction. So, to use the SQL adapter with BizTalk Server, you must always enable MSDTC. To enable the adapter to perform operations within the scope of an MSDTC transaction, you must configure MSDTC both on the computer running the SQL
adapter and SQL Server. Also, you must add MSDTC to the exceptions list of Windows Firewall. That is the reason why recommend setting for this binding property is
true; otherwise you might either experience message loss or duplicate messages, depending on whether you are performing inbound or outbound operations.
Exception is for operations where the adapter client does not write any data to the SQL Server database, such as a Select operation, you might not want the additional overhead of performing the operations inside a transaction. In such cases,
you can configure the SQL adapter to perform operations without a transactional context by setting the
UseAmbientTransaction binding property to false.
Just refer the link fo all the details:
Configure MSDTC on SQL Server and Adapter Client
Rachit
Rachit
Please mark as answer or vote as helpful if my reply does

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

JMS receiver channel Error !!

Hi All,
We are facing problem in all JMS receiver communication channels, all rcevr channels are failing with following error,
Error while processing message '498499a3-e65c-0086-e100-80000a05260c';
detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Pending message discovered: 498499a3-e65c-0086-e100-80000a05260c.
The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards. at
com.sap.aii.adapter.jms.core.channel.filter.OutboundDuplicateCheckFilter.filter(OutboundDuplicateCheckFilter.java:153) ...
does anybody know whats the exact error??
is it due to Adpater engine message buffere is full ?
regards
biplab

Biplap,
1) Did you restarted the Java Engine ? If so deactive & active the JMS Adapter,
2)Check any EOIO message got struck in Adapter Engine ( RWB-Communication channel- JMS Adapter )
3) Sxmb_moni - Look for the below message status - 498499a3-e65c-0086-e100-80000a05260c
Cheers
Agasthuri Doss

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 sender channel error

hi,
i am using pi 731 single stack.
i have a jms sender channel. The jms sender channel is connecting to Webshere MQ version 6.0.2.10.
the error is -
Error creating JMS connection : The JMS provider gave the error message as MQJMS2005:failed to create
MQQueueManager for x.y.com:QMgr1 MQJE001 completion code 2,Reason 2059,and the error code as MQJMS2005
What could be the issue. The JMS drivers are successfully installed.

Hi,
As Indrajit said seems to be a JMS configuration problem. Check this thread in stackoverflow with the same error: java - Always receive MQJE001: Completion Code &#39;2&#39;, Reason &#39;2059&#39;. ERROR - Stack Overflo…
Regards.

Error in JMS Adapter Configuration.

Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.

you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info

Error in JMS Sender Adpater

Hi
I am doing Weblogic-PI-File scenario
when i try to pick the XML file from Weblogic JMS queues its giving the follwing error
Error occurred while processing message: 552eec87-b6c3-4035-2675-cc3cd57b5487. Detailed error (if any): com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_File_Sender xmlns:ns0="urn:XXXXXXXX.com:JMSReciever"><SalesOrderDetails><MRNNumber>1234</MRNNumber><FirstName>ABC</FirstName><LastName>CDE</LastName><SocialSecurity>1234567890</SocialSecurity></SalesOrderDetails></ns0:MT_File_Sender> to XI message for message: 552eec87-b6c3-4035-2675-cc3cd57b5487: TransportException: No MIME header found
Edited by: S V on Jan 27, 2009 1:08 AM

Hi I am using Weblogic JMS Queues ..
and the connection parameters i am using :
JNDI LOOKUP NAME FOR QUEUE CONNECTION FACTORY:
mm.jms.VendorConnectionFactory
JNDI LOOKUP NAME OF JMS QUEUE: mm.jms.PIOutboundTestQueue
NAME OF JNDI INITIAL CONTEXT: weblogic.jndi.WLInitialContextFactory
JNDI SERVER ADDRESS : t3://vendor.xxx.xxxxxxx.com:6107
JNDI LOGON USER : xxxxxx
JNDI LOGON PWD : XXXXXX
did i miss anything ... or do i have configure anything on JMS sender adpater so that it will convert the text message into Binary

Error reading jms message from MQ-queue

Hi,
To be able to use async-sync bridge in JMS adapter, we recently patched XI 3.0 from SP 15 to SP21. But the jms sender adapter has problem reading the message from the MQ-queue, see detail of error-message at the end of this message.
I did change the adapter to use modules use RequstResponseBean and ResponseOneWayBean as explaned on help.sap.com.
The async-sync bridge worked once and the it started failing.
Detailed error message in communication channel monitoring:
Error while processing message '3c5a0640-9c03-11dc-82f2-000255d3bbf7'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ...
/Maria Lande

Hi,
I fixed it myself. I hade to do a Xi Data Cahe Refresh.
Navigate to Administration section on the SAP Exchange Infrestructure start page. On the Directory tab page, choose Cache overview under the heading Administration of Locks and Caches. Do a Full Cache Refresh on the adapter engine.
/Maria Lande

Error in JMS communicatin channel while deleivering to WMQ server

Similar Messages

Maybe you are looking for