cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Access JMS with JNDI

Former Member
0 Kudos

Hi all,

I am trying DB>XI>TIBCO (EMS).

I have included tibjms.jar library in aii_af_jmsproviderlib.sda and deployed using SDM.

In JMS receiver adapter I am using the following:-

Transport protocol: Access JMS Provider with JNDI.

JNDI Lookup Name of Queue connection factory: com.tibco.tibjms.TibjmsQueueConnectionFactory

JNDI Lookup Name of JMS Queue: com.tibco.tibjms.TibjmsQueue

Name of JNDI Initial Context Factory:

com.tibco.tibjms.naming.TibjmsInitialContextFactory

In RWB i am getting the following for this scenario:

2005-04-17 19:55:05 Success Using connection AFW. Trying to put the message into the receive queue.

2005-04-17 19:55:05 Success The message was successfully retrieved from the receive queue.

2005-04-17 19:55:05 Success The message status set to DLNG.

2005-04-17 19:55:05 Success Deliver to channel: TIB_Receiver_JNDI

2005-04-17 19:55:05 <b>Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.</b>

2005-04-17 19:55:05 Success XI message converted to binary format successfully

2005-04-17 19:55:05 <b>Error Delivery of the message to the application using connection AFW failed, due to: Object not found in lookup of XIJMSService..</b>

2005-04-17 19:55:05 Success The asynchronous message was successfully scheduled to be delivered at Sun Apr 17 20:00:05 GMT+05:30 2005.

2005-04-17 19:55:05 Success The message status set to WAIT.

Kindly help what other configurations are required.

Regards,

Arpit Seth

Accepted Solutions (1)

Accepted Solutions (1)

former_member189324
Contributor
0 Kudos

Hi Arpit,

You can check the status of the JMS Receiver in the RWB>Component Monitoring-> Adapter Engine-> Adapter Monitoring>JMS, after activating the Object.

Look for more detail errors..

Thanks

Prasad

Former Member
0 Kudos

Hi Prasad,

I had checked the status of the JMS Reciever in the RWB>Component Monitoring-> Adapter Engine-> Adapter Monitoring>JMS, after activating the Object and it is showing following error:

<b>Channel Name Error</b>

TIB_Receiver_JNDI Receiver Channel. Details: null

Looking for solution.

Thanks,

Arpit Seth

former_member189324
Contributor
0 Kudos

Hi Arpit,

I would suggest to check the following J2ee file system logs for the Adapter Engine.

1. D:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log\services\com.sap.aii.adapter.jms.svc

2. usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log\applications\com.sap.xi\AdapterFramework----->af.trc

Thanks

Prasad

Former Member
0 Kudos

Hi Prasad,

is it possible to test the connectivity to TIBCO using the generic JMS adapter of XI in order to ensure low level connectivity at all? We are running into the same issue as above. We have tried all kinds of Transport Protocol settings (SonicMQ, JMS with JNDI, JMS generic). The log file directories you are suggesting do not exist on our server (AIX). However, we do have a trace file (debug mode according to SAPnote 761921).

Can you pls. help?

Kind regards,

Colin.

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi all,

It's several years later, but now I face this problem.

Has anyone solved it??

Please share the solution.

Thanx!!!

Best regards, Walter.

Former Member
0 Kudos

Hi all,

Me too have the same problem.

I am trying to integrate XI with OpenJms (server) using JMS adapter.

But the error that i am getting is similar to yours:

Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.

I am very interested to the solution.

Thanks in advence.

Best regards.

Lemin

Message was edited by: lemine ould-cheikh

Former Member
0 Kudos

any breakthrough..?

I am badly struck. Kindly let me know of ur progress/solution.

Former Member
0 Kudos

Hi,

Gr8 to see that atleast somebody is also working on JMS adapter on the other side of the world )

Me too have the same problem. I am trying to integrate XI with SoniqMQ using JMS adapter. But the error that i am getting is similar to yours.

Receiver Channel. Details: null

If you find the solution,Do help me out.

Regards,

Siva Maranani.