Skip to Content
author's profile photo
Former Member

XI JMS adapter after JMS provider reboot

Hi All,

I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.

After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.

In JMS adapter we have folloving settings and we are connected straight into queue:

Transport Protocol = SonicMQ JMS Provider

General JMS Settings:

Transactional JMS Session is in use

Delivery Mode of Message Producer = Persist JMS messages..

+ Queue user & pw

Error Handling Settings:

Wait After Message Error(msecs) = 60000

Wait Before Reconnect(msecs) = 60000

Does anyone ran into this earlier?

Thanks in advance.

-Kimmo

Add comment
10|10000 characters needed characters exceeded

1 Answer

  • author's profile photo
    Former Member
    Posted on Jan 27, 2005 at 07:09 AM

    Hi Kimma,

    Although my qn is out of context here , i am facing an issue in JMS adapter and from your post could see, u were able to connect to a JMS server from XI. Let know your thoughts on what needs to be chekced in our config.

    we have Sonic MQ , have deployed the Sonic MQ JMS client library - "Sonic_Client.jar" on XI using SDM. deployment looks ok. However when i configure an adapter instance and activate it , i get a vague err message saying "Receiver Channel. Details: null" in the adapterframework.The same happens for sender channel as well. We are on XI3.0 SP9. Is there any additional settings reqd in the "Modules" tab of JMS adpater config ? Where do i get detailed info on this error ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Saravana,

      It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory

      It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.

      We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.

      We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.