PI Receiver JMS RabbitMQ Integration

[Former Member]

Hi,

We need to create an integration using JMS RabbitMQ.  We had install these drivers:

Also we configured JMS receiver channel with this adittional parameters:

But we are getting this error:

Thanks.

[Former Member · Accepted solution]

Hi Vadim

Im with Sandra working together in this issue.

These are the screenshots from the server side configuration...

1. The plugin configuration:

2. Rabbitmq exchange configuration:

3. Rabbitmq queue configuration:

Now you can see that we are quite similar as your post.

[vadimklimov · Accepted solution]

Hi Sandra and Juan,

Thank you for providing so many details, looks much less uncertain about your configuration. One other thing I noticed: in deployed libraries that you have in com.sap.aii.adapter.lib, there is no geronimo-jms_1.1_spec-1.1.1.jar. It shall be located in the folder "dependencies" in the distribution of JMS Connector for RabbitMQ. Can you please deploy it, too?

If this will not resolve an issue, can you please collect verbose trace of the affected JMS receiver channel (e.g. using XPI Inspector), so that we can together have a look and try to figure out why submitted parameters are ignored by connection factory class?

Regards,

Vadim

[Former Member · Accepted solution]

Hi Vadim, we already had trace information, It's about 1.28Mb, How can we send to you?

[vadimklimov · Accepted solution]

Sandra, can you please split the trace into chunks (every one being not larger than 1 Mb) and attached to this forum thread? (in advanced editor, you can attach files to your reply). Then not only me, but other experts can also analyze a trace and provide help.

Regards,

Vadim

[Former Member · Accepted solution]

Hi All,

These are trace files.

We really appreciate any help you can provide.

573b1aa3-88a8-1970-e100-80000acb0a3b_xpi_message.txt.zip

00_xpi_jvm_params.txt.zip

78776c0ae8c8362793a8c6b113ffd985_xpi_channel.txt.zip

[Former Member · Accepted solution]

These are other trace files.

Thanks.

2_xpi_traces_Part2.txt.zip

2_xpi_traces_Part3.txt.zip

2_xpi_traces_Part1.txt.zip

[vadimklimov · Accepted solution]

Hi Sandra,

I'm sorry, even though I can extract files that you attached, they are not very well readable. Can you please send me the original XPI Inspector trace (mail at Vadim.Klimov@gmail.com)?

Regards,

Vadim

[Former Member · Accepted solution]

Hi Vadim

Yesterday I sent it, thanks a lot.

[vadimklimov · Accepted solution]

Sandra, I got nothing in my mailbox from you. Would you mind checking if you specified recipient address correctly? Otherwise, can you upload a complete XPI Inspector trace to some external site from where we all can download it afterwards?

Regards,

Vadim

[Former Member · Accepted solution]

Hi Vadim,

I already shared it to you in Google Drive...

[vadimklimov · Accepted solution]

Hello Juan,

I was finally able to download XPI Inspector trace. Looking into details of an exception that Sandra got, the nested exception NoClassDefFoundError caught my attention:

As it can be seen, the PI system failed to find and load class org.slf4j.LoggerFactory. This class is located in one of dependency libraries that are shipped with JMS connector for RabbitMQ (slf4j-api-*.jar). Alternatively, SLF4J library can be downloaded from the official site (SLF4J). Between these two options, I would suggest you to use the one distributed with JMS connector for RabbitMQ in order to avoid any version mismatch.

Can you please deploy this library together with other libraries assembled in com.sap.aii.adapter.lib.sda and try again? If the error remains, please ensure that the mentioned class is properly loaded and well recognized by the PI system - you can use AS Java Telnet utility llr for this purpose, as described in .

Regards,

Vadim

[Former Member · Accepted solution]

Hi Vadim,

Finally it worked!

The problem was the missing SLF4J library itself.

Thank you so much for all you help and your timely responses to our issues.

[vadimklimov · Accepted solution]

You are welcome, Juan. Glad to know the root cause was finally identified and the problem was resolved.

Regards,

Vadim

[vadimklimov]

Hello Sandra,

There is mistype in name of the parameter JMS.QueueConnectionFactoryImpl.method.setHost - based on the provided screenshot, it is JMS.QueueConnectionFactoryImpl.method.setHostj (with unnecessary "j" at the end).

Regards,

Vadim

[Former Member]

Thanks Vadim,

I deleted the j character, but I still have the same issue.

[nabendu_sen]

Can you check 'JMS server plugin' is installed in RabbitMQ server?

Check: by

Regards,

Nabendu.