cancel
Showing results for 
Search instead for 
Did you mean: 

Message not delivered to jboss jms queue with PI 7.1 receiver jms adapter

Former Member
0 Kudos

Hi guys,

We are trying to connect to a JBOSS 4.05 JMS queue with our PI 7.1 receiver adapter.

We have succesfully deployed the following JAR files by adding them to the

com.sap.aii.adapter.lib SDA file:

jmx-invoker-adapter-client.jar

jboss-common-client.jar

jbossmq-client.jar

jboss-system-client.jar

jnp-client.jar

log4.jar

This is suggested in note [1086306|https://websmp230.sap-ag.de/sap(bD1ubCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1086306]

In the configuration we used the following data:

JNDI connection factory: ConnectionFactory

Queue: queue/kob.Queue.Req01

ContextFactory: org.jnp.interfaces.NamingContextFactory

JNDI Server adress: jnp://ourdomain.nl:59616

Although we do not get any errors (all messages are processed succesfully according

to the communication channel monitoring), the messages are not put in the queue.

When we look at the default trace file in the logviewer (NWA), also no errors can be

discovered.

We tried to connect to the JBoss queue using the same jar files using the Hermes tool:

this works fine.

Please help,

Regards,

Jeroen

Accepted Solutions (0)

Answers (1)

Answers (1)

prateek
Active Contributor
0 Kudos

PI is unable to receive the message. You may check the following:

1. Your port is correct at JNDI Server adress.

2. Your JMS service is running in Visual Admin or nwa.

3. Sender communication channel is Active and running.

Regards,

Prateek

Former Member
0 Kudos

Prateek,

The message is not delivered in the JMS queue, so:

Message is send to PI (in this case using a SOAP sender adapter)

Routing is executed

Message leaves the receiver JMS adapter with a status succesfully processed

But no messages are found in the receiving JMS queue on JBOSS application server.

Port is ok, as we also use this port in Hermes.

Former Member
0 Kudos

Hi,

Increase the trace level to debug for your JMS adapter in visual admin...then execute the end to end to scenario....then go back to your visual admin and revert the trace level...NOW ANALYZE the default trace for that specific time on the server...It should have all the information, to which queues its exactly writing, with the parameters e.t.c

Hope this helps...

Ravi

Former Member
0 Kudos

Hi

Check with your Visual admin logs. What doest it say?

All queues at AF should have successful then only message will be available with JBoss.

Thanks

Gaurav