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é

Similar Messages

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

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

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

JMS Receiver channel EOIO

Hi,
In SAP help, for one of the parameters of JMS Receiver channel it is mentioned that:
Delivery Mode of Message Producer :
Specify the quality of service of the message producer. You have the following options:
u2022 Persist JMS Messages in the JMS Provider
u2022 Do Not Persist JMS Messages in the JMS Provider
Does this means EOIO/EO. I have proxy to JMS scenarios & like to send the data to JMS in EOIO.
We are using Transport Protocol " Access JMS Provider with JNDI"
With this I want to achieve, EOIO for Proxy to JMS. Pls let me know if Delivery Mode of Message Producer parameter would help & what should be the value.
Thanks.

Exactly Once messages are handled by default using status information in the J2EE server. All adapter error statuses and program terminations initialized externally are also handled in this mode. i.e.
= persist jms messages in the jms adapter.
Now if you specifically want to have dedicated queue; check manage queues under SXMB_ADM.
See if you can set dedicated queue to your interface so that the messages can be processed in the sequence they have received.
Also, once it is out of PI into target system (queue) the order will be maintained.
Cheers!

Error in File Receiver Channel

Dear All,
I am Getting below error in File Receiver Channel.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: User ABC cannot log in.
Regards,
Manikandan

Hi Manikandan,
Check the username and the password for the FTP server. If the username or the password is wrong then you would be able to post the message.
Also, there might be a timout issue, In the timeout parameter enter some value.
Ref: FTP Server connection Problem
Check and update us.
Thanks,

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

Heartbeat possibilty in JMS receiver channel?

Hi,
Does anyone know if it is possible to define a heartbeat interval in JMS receiver channels.
Is there maybe a possibility in the additional JMS paramters fields?
We need this to prevent connections being shut down by firewalls due to long inactivity. Once a JMS receiver channel is inactive due to this there is no automatic activation of the channel possible (I think).
The sending JMS channels pose no problem since XI AF seems to poll these every 5 seconds and thu sthe connection remains alive.
thanks
Tom

Hi Shai,
We are using XI 7.0 with SP 12 and we entered this parameter in advanced settings in JMS receiver adapter called "CONNECTION_TEST_POLL" as true and it does the polling to see if the adapter is active...
Hope this helps.
Regards,
TJ

"Error establishing socket" error on JDBC Receiver Channel.

Dear All,
Scenario: Soap to JDBC.
I m getting error on JDBC Receiver Channel. messages are processed succesfully on ABAP Stack and receiver channel is on below error:
ERROR : Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://156.5.202.194:3312;DatabaseName=ODW': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
Note: i already tested another interface with this same IP and it was fine with different port.
jdbc:microsoft:sqlserver://IP:PORT;DatabaseName=Name
Regards,
Manikandan

and it was fine with different port
socket exception is (always) related to port....did you check with the network team about this new Port?

JMS Receiver channel : No Correlation ID

Hi,
JMS Receiver channel to WebSphere MQ,
I want to put a message on the queue with correlation ID left blank (= no correlation ID), because this causes problems on the receiving side.
Is there a way to achieve this?
I have tried several different settings, but the message appears always with correlation ID.
Kind Regards
Edmond Paulussen

I think you should use the notify response bean on the sender channel
Configuring the Sync/Async Bridge Using the JMS Adapter - Adding Modules to the Module Processor - SAP Library
Sync/Async communication in JMS adapter without BPM (SP19)

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

Error in JMS-Receiver-Adapter when restarting MQ-Channel

Dear all,
we've configured a scenario with a JMS-Receiver (MQ-Series). When the MQ-Channel or the MQ-Queue-Manageris restarted, the connection to MQ get lost and is not re-established even when we restart the communication channel. When we restart the whole J2EE-Server things work fine, but we can't do this in productive environment.
Could this be a configuration issue? How can we solve this?
Kind regards, Stefan

solved by ourselves

Error in JMS receiver adapter: "Error creating initial context with environment"

Hello,
I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
The message in adapter monitoring is:
A channel error occurred. Detailed error (if any) :
com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
(JndiConnectorImpl.java:152)<br> ....
Message processing failed. Cause:
com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
Might there be a problem with the JMS drivers?
Regards,
Marcus

Hi Marcus,
Have a look at below thread
Connecting to PI 7.11 JMS Queue from other PI 7.11 Server

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 file receiver channel "Unknown payload format 0 in the message"

hello
there is an errror in my receiver file channel with the status "Unknown payload format "
my channel is file receiver channel.
we implemented one sap note 1295430 and after that channnel is giving the error.
Please forward your views.
thanks.

Hi there,
First of all, what TBDL means - It means that the message was successfully delivered from Integration Server and that the messages are handed over to the Messaging System.
TBDL occurs when the message is put into the receiving queue of the Messaging System.
What can be done?
Go to Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
If this was executed successfully, then the MS returns HTTP 200 to the Integration Server and the status TBDL moves to DELIVERING (check whether you have authorization to go to the above link).
--> Log-in to SAP using - XIAPPLUSER & XIAFUSER, and check if they are blocked
--> Check the messages:
AF
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
AS
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
Also, worth reading - /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Let us know if you have more questions.
regards,
Neetesh

Error in JMS receiver channel

Similar Messages

Maybe you are looking for