JMS Adapter troubleshooting

[Former Member]

Hello,

I have a JMS adapter configured for MQ and can get messages to / from it. However, in troubleshooting with the MessageTransferBean my messages seem to dissappear into the JMS ether

How can I see the contents and more detailed error messages for the JMS adapter in XI/PI? Runtime Workbench shows only a portion of the error and I can't figure out where to find the rest.

Any advice on how to monitor the SAP JMS layer and see helpful troubleshooting logs are greatly appreciated!

Many thanks,

Aaron

[Former Member · Accepted solution]

Hi Aaron,

The JMS or any adapter related logs are written to the J2EE server default trace files (located in /usr/sap/<SID>/<instnace>/j2ee/cluster/server<x>/log/ directory as defaultTrace<x>.trc files). BASIS admins should be able to get the files for you. Or if you have a standalone logviewer tool, you should be able to access these yourselves. If you want a detailed log, you should have your BASIS admins increase the log/trace level to debug for the JMS adapter (can be done from the log configurator in Visual Admin). Here is the SAP note which has the details on how to increase the trace level for the JMS adapter - 761921. Hope this helps

Thanks

-Sai.

[Former Member · Accepted solution]

Thank you Sai,

I'm sorry I did not mention in my post, but our Basis admins did have a look at the J2EE logs and increased the debug level, but they said there is so much information they cannot find anything usefull about JMS to give to me. The logs are big and slow so the stand alone log viewer and Visual Admin are unusable at our site (servers hosted elseware).

I'm thinking of using the Hermes tool (or something similar if anyone has good experience with another tool) to get a closer look into the JMS queue and see if there are dead messages waiting in there.

Thanks again,

Aaron

[Former Member · Accepted solution]

You can try MQJ explorer (old but working perfectly) - quite a good tool to connected and research the queues - even for testing purposes.

http://www.kolban.com/mqjexplorer/

Regards,

Kai

[Former Member]

By using an iterative loop of sending test files filtering through the queue -> letting the MessageTransformBean fail -> begging my Basis guys to send me the most recent J2EE trace, and then searching for the errors I was eventually able to work through the errors. There must be a better way!

Thanks again everyone, I awarded points to all who answered. If anyone knows a better way to see this type of info, say in Runtime Workbench, please share the love.

Aaron

[Former Member]

Hi all,

As I know, j2ee engine has a default JMS provider, but when i open the Adapter monitoring in RWB, the JMS link is inactive (cannot choose to see the status). I checked in the Visual Administrator, there is JMS provider default. Pls give me idea about this situation. Thanks a lot.

Thien Duong

[Former Member]

Instead of Adapter Monitoring choose Communication Channel Monitoring, then filter by adapter type JMS and you should see it.

[Former Member]

Hi Aaron,

I mean, the JMS adapter is not installed, although I do all the ways that mentioned in the XI Configuration guide. Pls someone shows me how to check if I installed successful or not.

Thanks a lot.

[Former Member]

After the drivers are installed, you can configure an adapter with your parameters in Integration Builder and then see if the channel can initalize in Runtime Workbench.

Back to the reason for this thread... after loading the most current XI service packs (up to 23 now) we now see much better logging information for JMS channels inside Runtime Workbench. It will now show message payloads and a listing of process steps. Before it only displayed one step. Now I won't have to sift through the Java logs anymore. 😄

[JoelTrinidade]

Hi Aaron,

I am giving you all the chapters from the bible of jms adapters.

1)notes for JMS adapter

Go thru these notes 790963,747601,746393,856346,802754,

837501 and 790224.

2)information regarding use of JMS Adapters,Go thru these links of help.sap.com

JMS Adapter:

http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm

Configuring the Sender JMS Adapter:

http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm

Configuring the Receiver JMS Adapter:

http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm

JMS-Provider-Specific Settings:

http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm

And to deploy the jars which are given in the JMS Adapter link go thru this article "How To Install and Configure External

Drivers for JDBC and JMS Adapters"

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4...

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60237e74-ef19-2b10-5a9b-b35cc6a2...

http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

Regards

joel

Edited by: joel trinidade on Mar 26, 2009 11:22 AM

[Former Member]

Thank you very much Joel, that is a great list of resources and probably would have saved me much time up to this point!

However, most of that info has to do with getting the communications channels working from a basic level. We have the drivers loaded and messages flowing, but having difficulty troubleshooting the message parsing with the Content Conversion module (Message Transform Bean).

I've seen multiple references to a document on SDN "How-to Guide: How to use content conversion module in the JMS Adapter" including the SAP Note you referenced 856346 (JMS FAQ). But the document seems to be missing!

I think it should be located here:

[ [original link is broken]| [original link is broken]]

If anyone knows where to find this now it would be greatly appreciated. I found similar information in the SAP library here:

[http://help.sap.com/saphelp_nw04/helpdata/en/57/0b2c4142aef623e10000000a155106/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/57/0b2c4142aef623e10000000a155106/content.htm]

I have the parameters all plugged in but when the module has trouble parsing the file it only gives me the useless JMS error in Runtime Workbench.

Any advice on an effective way to troubleshoot the message parsing step of the MessageTranformBean is greatly appreciated. Perhaps the only way is to filter through the cumbersome J2EE debug logs?

Best regards,

Aaron