JMS Message Property in JMS Receiver

Hi there,
I need to set a JMS String property of a message I send. This message is fixed for one channel.
We use XI 3.0 SP 20. I went through the documentation and saw that I can give up-tp 10 properties.
But only the name and the type.
But where can I get a value from.
Documentation sys that the technical name was DCJMSMessageProperty0, ...1 a.s.o.
Is that sth. for the adapter module? Is this a field that needs to have this name in the message? I do not get it.
Could you please lighten a bit the usage of this (strange) mechanism?
Thanks in advance,
Helge

Hi there,
there is a way (and a section somewhere in the help) to set adapter specific attributes in java mappings.
The java doc for that can be found here:
https://help.sap.com/javadocs/NW04/current/pi/index.html
Hope that helps sbd who also has that prob.
Cheers,
Helge

Similar Messages

JMS Receiver Adapter to MQ - additional message property error

Hi,
I'm trying to add addional message properties to a Receiver JMS message for MQ Server queue. Creating the message in the MQ queue only works when I don't try to
add additional message properties. As soon as I try to add additional message properties the XI-Monitor says it's OK but there is no message in the queue.
Our system constellation is a bit odd cause we implemented the JMS/MQ classes of release 5.3 in XI/J2EE.
Our actual used MQ Server is on release 5.1 due to compatibilty reasons of other productive software.
Is there a need to use a MQ server of release 5.3 ?
Has anybody a step by step description for implementing a JMS receiver Adapter for MQ with with additional message property (f.ex. mesType = salesOrder) in the MQ header?
Thanx a lot in advance
Hans

Hi,
You also might want to look at sap note 856346...for this ..
2.6) I am connecting to a JMS provider using JNDI mode. How do I add pass an extra name,value property pair while setting up the JNDI initial context?
Answer: Assuming that your property value is a string, please add the following name, value pair in "JMS Additional properties" table of your channel configuration:
JNDI.InitialContext.property.X=java.lang.String propertyName, java.lang.String propertyValue
where X is a number, the LHS part needs to be put in the name column and the RHS part in the value column of the table respectively.
This note covers frequently asked questions that arise during the installation, configuration or administration of the XI JMS Adapter from the Adapter Framework (AF).
Other terms
JMS - Java Message Service
AF - Adapter Framework
AE - Adapter Engine
SP - Service Pack
Reason and Prerequisites
This note clarifies the frequently asked questions on the XI/PI JMS adapter for released 3.0, 7.0 and 7.1 in the form of an FAQ. References to external information is provided at the end.
Solution
1. Documentation
1.1) Where do I find the JMS adapter documentation?
Answer: In the SAP online help. Go to http://help.sap.com and select SAP Netweaver-> SAP Netweaver 7.1 or SAP NetWeaver 7.0 (2004s) or SAP Netweaver 2004. This opens up SAP Library topic page for that release.
For releases 3.0 and 7.0:
Select SAP Netweaver Library -> SAP Netweaver by Key capability-> Process Integration by Key Capability -> SAP Netweaver Exchange Infrastructure -> Runtime -> Connectivity -> Adapters -> JMS Adapter.
For releases 7.1:
Select SAP Netweaver Process Integration 7.1 -> SAP Netweaver Process Integration Library -> Function Oriented View > Advanced Adapter Engine.
In the topic page click on the JMS Adapter link.
Alternatively, you may simply enter the search string "JMS adapter" and navigate to the documentation page directly from the relevant search results. This is much faster.
1.2) Which JMS providers are supported?
Answer: The JMS Adapter supports JMS 1.02b and 1.1. JMS providers that also claim to be compatible with JMS 1.02b or 1.1 can be accessed using the JMS Adapter.
Furthermore, SAP makes no assertions as to whether a particular JMS provider is tested or can be recommended, because SAP has not set up a certification or testing process.
2. Functions and architecture
2.1) Does the JMS Adapter support JMS topics (publish&subscribe)?
Answer: No. Currently the JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with JMS queues. However, this capability might be planned for introduction at a future release. (no planned time estimate)
2.2) I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?
Answer:
A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI message which can be used the routing, mapping and BPE. The message properties of different adapters are differentiated by namespaces.
If you are on XI 3.0 support pack 18 onwards, the JMS adapter allows you to copy JMS message properties into these XI adapter specific message properties (at the sender JMS channel), and to copy the values of XI adapter specific message properties back into JMS message properties (at the receiver JMS channel).
The JMS adapter currently supports upto 10 JMS message properties to be copied into the XI message properties with the name DCJMSMessageProperty0 to DCJMSMessageProperty9. The configuration details of how to achieve this are explained in the sub-topic pages of the JMS adapter documentation. (See sub topics: "Configuring the Sender JMS adapter", "Configuring the Receiver JMS adapter")
JMS Message properties can have values belonging to types: boolean, byte, short, int, long, float, double, and String (defined in the specification). These are all normalized to strings when converted to the their respective XI message properties at the sender JMS channel.
However, in the receiver JMS channel configuration, you can enter specific JMS message property types, such that these normalized XI message properties may be coerced back into their original types (or any compatible JMS message property type) when translating a XI message into a JMS message.
Transfer of custom JMS Message properties from/to XI adapters-specific message attributes is only supported for JMS compliant messages, i.e. this feature will not work for Websphere MQ in legacy mode.
Deprecated Information on this feature
Between support pack 14 to support pack 18, the JMS adapter allowed the allowed you append only up to two JMS string properties to the XI message in the sender channel, which could then be analyzed in XI routing, mapping and BPE. In the JMS receiver channel, the XI adapter-specific message attributes could be read, and up to two JMS string properties could be set. The names of the (now deprecated) XI message properties were DCJMSStringProperty1 and DCJMSStringProperty2.
Regards
Ravi Raman

JMS Receiver - set DCJMSMessageProperty value dynamically from message

Hi,
I have a JMS Receiver where I want to set a DCJMSMessageProperty value to a value from the message contents
For example:
Scenario 1:
Message content field <EANCode>123456</EANCode>
DCJMSMessageProperty6 should be set to 123456 in this instance
Scenario 2:
Message content field <EANCode>99999</EANCode>
DCJMSMessageProperty6 should be set to 99999 in this instance
I know how to set this property to a fixed value using the module DynamicConfigurationBean but do not know how to make this value to use message content.

Hi,
As stated earlier, I need to set DCJMSMessageProperty on the communication channel to a value held in the content not a fixed value.
I will use a UDF to do this now as there are only certain dynamic values you can use using the DynamicConfigurationBean such as message ID, interface name etc. I want to use something in the content so a UDF should be able to do this.
Cheers
Colin.

Adapter-specific message attributes for the JMS Receiver adapter

Dear SAP Community,
We are trying to activate some parameters at message level when SAP XI sent an interface (XML data) to IBM Websphere MQ. Programmaticaly, this is done the following way:
       TextMessage outMessage = session.createTextMessage();
       MQQueue replyToQ = new MQQueue("TESTQM01","SYSTEM.ADMIN.ACTIVITY.QUEUE");
       Destination replyTo = (Destination) replyToQ;
       outMessage.setJMSReplyTo(replyTo);
       outMessage.setIntProperty("JMS_IBM_Report_Exception", MQC.MQRO_EXCEPTION);
       outMessage.setIntProperty("JMS_IBM_Report_Expiration", MQC.MQRO_EXPIRATION);;
       outMessage.setIntProperty("JMS_IBM_Report_COA", MQC.MQRO_COA);
       outMessage.setIntProperty("JMS_IBM_Report_COD", MQC.MQRO_COD);
       outMessage.setIntProperty("JMS_IBM_Report_Discard_Msg", MQC.MQRO_DISCARD_MSG);
This code is working fine.
Since the documentation about this feature (Adapter-specific message attributes) is very light, We am not sure about the interpretation we made.
First, we defined the following attributes: MS_IBM_Report_Exception, JMS_IBM_Report_Expiration, JMS_IBM_Report_COA, JMS_IBM_Report_COD, JMS_IBM_Report_Discard_Msg. All of them are with type int.
Then we changed the mapping (XSL) to pass the value to the dynamic configuration, using the technical names (DCJMSMessageProperty0, ..., DCJMSMessageProperty4) and the value of the constants. We also specified a value in the Reply To Queue parameter of the adapter. As a test, We also change another parameter via the mapping (the correlation ID, to use the idoc number) and according to the log of the processed message, every thing is finde. According to the trace of the JMS adapter, everything is fine to. However, this has no impact on the message, only the correlation ID is changed.
The JMS server is IBM Websphere MQ (v6.0.2.1). It is already in production and working fine. This is a change we have been asked to implement.
Has anyone experience with the JMS receiver adapter-specific message attrbitutes ? What have we done wrong ?
Any help is greatly appreciated.
Regards,
Gregory PFISTER
SAP XI Analyst - Holcim

Hi Neha,
pls do chk the below links for SOAP adapter message attributes
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
Regards
Sampath

Send Idoc flat file message in JMS receiver adapter

Hello,
I am working on a scenario where we send Delvry 03 idoc from ECC to external system. To external system, we send the whole Idoc in flat file structure through JMS queue. I have used Idoc to flat file program in my interface mapping and have configured JMS receiver adapter with just default Module configs but, I am getting an error in communication channel monitoring for the messages.
Please note that Idoc xml to flat file structure conversion is already done in the mapping, I need to just pass this idoc flat structure in the jms adapter. Hence ther eis no content conversion i nthe adapter..
Please give some inputs..Here are the modules in my receiver adapter and nothing else..
SAP XI JMS Adapter/ConvertMessageToBinary
SAP XI JMS Adapter/SendBinarytoXIJMSService
The error I get is in audit log
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_R:ca336a6689f837da8bd3387140fc4447
in turn the message has this error if I open the message
Whitespace is not allowed at this location. Error processing resource 'http://host:port/mdt/messageconten...
and it shows one of the lines from idoc..flat file
Any idea is greatly appreciated..Thank you..Thanujja

The difference in what I suggest is that it is way simpler.
Maybe you did not understand this, so will try to explain it better. Its not the best thing to do, but if JMS adapter doesn't budge then you can give it a shot.
1. You continue to use the ABAP mapping in your interface mapping to map the Idoc xml to Idoc flat.
2. Write a Java Map that will take the output of the ABAP mapping ; and then create a XML output which would be something like,
<Root>
<Idoc_Flat>
<Data>ABAP Mapping Output<Data>
</Idoc_Flat>
</Root>
3. Now use the simple content conversion in the JMS adapter to convert this to flat file.
Regards
Bhavesh

JMS Message Property

Hello Experts,
we have a JMS to JMS scenario. A third party system sends a message to the JMS Queue (JMS Provider is the J2EE SAP Web AS, XI system). Via JMS Message Selector (configured the JMS Sender Adapter) the right integrationprocess get the message.The integrationsprocess sends the message to another JMS Queue. Because the integrationprocess have lost the JMS Header information (message properties) we configured the JMS Sender Adapter and the JMS Receiver Adapter to copy message properties. Described under help.sap.com:
you want to set additional JMS message attributes, select Specify Additional JMS Message Properties (Maximum of 10).
· In the table, enter the names of the JMS message properties whose values are to be included in the message header of the XI message.
The technical names of the additional attributes are DCJMSMessageProperty0, DCJMSMessageProperty1, ..., DCJMSMessageProperty9.
You can enter more than 10 properties in the table, but only the first 10 are taken into account.
The attribute namespace for the adapter is http://sap.com/xi/XI/System/JMS.
I debug and saw that the message properties was sucessfully copied to the header (receiver queue). But now if I use another selector the message will not found. It doesn't work with a third party system and with SAP XI (I've created another integrationsprocess, to read the queue)
Thanks very much, for your help.
Regards,
Jürgen

Hi there,
there is a way (and a section somewhere in the help) to set adapter specific attributes in java mappings.
The java doc for that can be found here:
https://help.sap.com/javadocs/NW04/current/pi/index.html
Hope that helps sbd who also has that prob.
Cheers,
Helge

Message to JMS Receiver

Hi All,
I have an XML output and I want to send it to a queue so that a JMS receiver listens to the queue and grabs the message. I am wondering as how to send the XML output tho.Any ideas?/
Thanks.

Hi All,
I have an XML output and I want to send it to a queue so that a JMS receiver listens to the queue and grabs the message. I am wondering as how to send the XML output tho.Any ideas?/
Thanks.

How can a remote jms receiver detect loss of connection to Messaging server

Plan:
Messaging server (like JbossMQ /SonicMQ) is hosted on one machine.
A JMS receiver (MDB/core java program) on another machine receives messages from the messaging server.
Secnario:
The JMS receiver is now continuously listening or occasionally reading messages from a certain queue of the server using a JMS connection.
Now the messaging server has this receiver in its list of receivers for that particular queue.
For some reason the messaging server is down and then restarted.
The JMS connection of the receiver is now invalid.
When the messaging servers comes up again its list of receivers is empty.
Required Solution:
Can you please help me on how the JMS receiver can detect the above scenario and re-establish the connetion to the messaging server, the next time the server is up.
Observations:
When I create a message consumer or queue receiver in a j2se program, and take messages from JbossMQ I have some additional threads running on my JVM. These threads are not directly created by the program and servers only for receiving messages. One of these threads is catching an exception and printing a stack trace when it detects that the connection is lost. This will also result in the closing of JMS connection. The problem is that the exception is not thrown for the programmer to catch and handle it at some level. I also tried ExceptionListener and waited for ping interval. Is there a concept of receiver listening to the periodic heart beat of the server. Please give me guidance, solutions or corrections.
For comments on this, Thanks in advance

Hi Leendert,
do you want to use the JMS API directly? In this case you have to create the connection factory on system X. From system Y, you access the JNDI on system X and look up the connection factory. Since you are accessing the JNDI on system X from outside, you need to set some properties to create the InitialContext:
    Properties env = new Properties();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
    env.put(Context.PROVIDER_URL, <system X>:<p4 port>); // replace with your settings
    env.put(Context.SECURITY_PRINCIPAL, <user name>); // replace with your settings
    env.put(Context.SECURITY_CREDENTIALS, <password>); // replace with your settings
    naming = new InitialContext(env);
Hope that helps.
Regards,
Sabine

JMS Type in JMS Receiver

Experts
I need to send JMS Type to the JMS Receiver.
The following UDF was used.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSType");
String a="341";
conf.put(keyHeader1,a);
return "";
Selected ASMA in the Receiver channel. Anything else needs to be done ?
Thanks and regards,
J Augastine

Abhishek
Modified the UDF.
Also
In the JMS Receiver channel did the following
- Checked the box for 'Use Adapter Specific Message Attributes'
- Checked the box for 'Fail if Adapter Specific Message Attributes missing'
- Checked the box for 'Specify Additional JMS Message Properties'
- Defined property in the table and set the Java type
DCJMSMessageProperty0 String
Under the Module tab,
- Added the module AF_Modules/DynamicConfigurationBean in position 1 with module key HEADER
- Added module configuration as follows:
Module key HEADER
Parameter name key.0
Parameter value write http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0
Module key HEADER
Parameter name value.0
Parameter value JMS DCJMSMessageProperty0
What change needs to be done ???

Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper

Hello
Has anyone managed to set the DCJMSCorreleationID dynamic attribute in a JMS RECEIVER using Seeburger AttribMapper module?
Here is how I configured the JMS_RECEIVER:
In the module tab, I added a new module:
Module Name     Module Type     Module Key
localejbs/Seeburger/AttribMapper     Local Enterprise Bean     map
And I added the following parameter:
Module Key     Parameter Name                                                       Parameter Value
map                     http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When I process a message, I can see in the adapter engine Audit log the following lines:
SEEBURGER/AttribMapper: Setting dynamic property http://sap.com/xi/XI/System/JMS - DCJMSCorreleationID = TEST
SEEBURGER/AttribMapper: Finished succesfully, 1 properties set or deleted
However looking at the Message Content/SOAP Document, I can see no dynamicConfiguration (it should be the case according to Seeburger documentation).
If I check the message properties on the JMS queue, I can see the correlation ID is not set to TEST.
Any idea?
Thanks in advance!
Greg

Are you using the AttribMapper in the Sender or in the Receiver Channel ? Please be aware that you will not be able to see the change of attribmapper in the message content in receiver channels (they are not updated/persisted there).

Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

Hello,
I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
In the module tab, I added a new module:
Module Name Module Type Module Key
localejbs/Seeburger/AttribMapper Local Enterprise Bean map
And I added the following parameter:
Module Key Parameter Name Parameter Value
map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When processing a message, I get the following error on the Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
Does anyone has an idea on how to fix this problem?
Thanks for your help!
Benoit

HI,
Refer the discussion of
Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
Dynamic subject in AS2 receiver
Thanks
Swarup

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

Erro in JMS receiver Comm Channel

Hi,
I am working on a scenario File(Sender) JMS (Receiver).The input is a text file The file sender polls this input file and the file sender CC does the content conversion and puts the XML message into the JMS Queue. But in the receiver JMS comm channel i get the error saying
Error sending message in sending to destination ABCF, the message message: TextMessage[null, <?xml version="1.0" encoding="...]: weblogic.jms.common.JMSException: Error sending mess
Please help me on this

Hi,
Please have a look at your message in SXMB_MONI and see if the payload is correct.
Also have a look at the MDT (http://<server>:<port>/MDT) and see what errors occur for your message.
Regards,
Yaghya

JMS receiver error

Hello,
I have maintained a JMS receiver adapter to an existing MQ system (IBM WebSphere 6.0)
After deploying the modules to PI (7.11) the adapter goes green but allways says "Sucessfully disconnected from destination".
When sending a message through this adapter I get the error message:
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: No transition found from state: STARTING, on event: process_commence for DFA: JMSReceiver_ATLAS_MQ:4b9d8e8dfe883ebeb7ab5af79e59cdf6"
I can not find out where the problem can be....I played arrounf with the several options for QM Manasger, channels.....
I do not use any "Advanced Adapter options"
Anybody who can help me????
best regards
Werner

I still have checked all the notes and blogs....
But nothing helps, I still have the same problem.
The problem can be, that I am not a MQ specialist, but I have access to the MQ and I can see the settings.
Do I have to use adapter specific atributes???
I only use QManager, Chanell, queue....
ANd there is somehting other really strange.
I have create several components for different scenarios.
When I create an Adapter in one component, I get the error I listed before.
But in some components I get the error:
"Channel Has Internal Error" in the RWB overview and in the node
"Adapter had not provided any status infomration about this channel"
I tried with Creating new channel, copy channel between the components....
but allways the same...in some components I get this error
in other components I get the message "Successfully discponnected from destination"
Werner
Edited by: Werner Magerl on Sep 28, 2010 1:59 PM

JMS receiver adapter Error

Hi Experts,
Any idea about this error. We are getting following in JMS receiver adapter in PI 7.1.
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connector for ConnectionProfile of channel: JMS_Receiver_THQPRD2_Slow_Replyon node: 284760550 having object id: cf2f6eb7d6c93902b64b27bfcaad0ba5 encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>' in sending to destination queue:///QR.EAIPRD.THQPRD2.REPLY.SLOW?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:ID:414d5120504c535748353533202020204e6324ae23eb5b2d JMSDestination: null JMSReplyTo: null JMSRedelivered: false XPLOR PIPXSDI2030 45219q00282YSDI2030PROCESS_MQSERIES PLSWH553 Another 12,761 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>'.
Thanks,
Hari

Hello,
The error indicates a JMS driver issue.
Another customer resolved this issue by updating their MQ and the MQ drivers version (in their case to 6.0.2.8.)
You could try contacting IBM for advice on a similar upgrade.
#1086303 XI JMS Adapter and IBM Websphere MQ: FAQ
12)What is the recommended version of MQ drivers for the PI JMS
Adapter - IBM MQ connectivity ?
Kind regards,
Sarah

JMS Receiver Adapter Catching MQ Exceptions

Hi Experts,
We are running into an issue with our JMS receiver adapter failing PI. We are trying to send transactions via the adapter to a MQ Series' queue but it is failing after no transactions have been sent after a period of 3 hours or more. The only way we can flush the queue is to change the setting on the adapter to Bypass, restart the adapter and then resend the message. Once we do this, everything runs fine throughout the day. It seems to be the amount of time between transactions be processed on the queue.   For instance, last night the last transaction processed successfully was at 7:36pm EST. Then around 11:40pm EST we tried sending another and this is when we caught an exception from MQ once again. We have tried everthing that we know of u2013 we thought it might have been a background job running on PI that causes the issue but last night proved that it wasnu2019t the issue since it occurred before midnight. I feel that the issue is between our JMS connection and your MQ. Below is the message log of the transaction:
What course of action should we take next in diagnosing the issue?
Audit Log for Message: 1c728f10-2044-0441-0a04-604e2cf00000
Time Stamp     Status     Description
2009-05-21 22:40:48     Success     Message successfully received by messaging system. Profile: XI URL: http://bus0157:52000/MessagingSystem/receive/AFW/XI Credential (User): PIPISUSER
2009-05-21 22:40:48     Success     Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-05-21 22:40:48     Success     Message successfully put into the queue.
2009-05-21 22:40:48     Success     The message was successfully retrieved from the receive queue.
2009-05-21 22:40:48     Success     The message status set to DLNG.
2009-05-21 22:40:48     Success     Delivering to channel: JMS_IDOC_SPK_RCV
2009-05-21 22:40:48     Success     MP: Entering module processor
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService
2009-05-21 22:46:48     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP
Time Stamp     Status     Description
2009-05-21 22:46:48     Error     Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP?targetClient=1 JMSReplyTo:      null JMSRe
2009-05-21 22:46:48     Error     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: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP.

Ok, would you mind taking a look at my forum question titled "Multiple Message Types into one Websphere Message Queue", it may be an easy one for you since you are already doing this!
Best regards,
Aaron
[Multiple Message Types into one Websphere Message Queue|Multiple Message Types into one Websphere Message Queue]

JMS Message Property in JMS Receiver

Similar Messages

Maybe you are looking for