jms_defaultConnection : java.lang.nullpointerexception

Posted by sharma.abhishek2207 on 14-Oct-2010 04:02

Hi

I am facinig an issue while connecting with jms_defaultConnection. The url of jms_defaultConnection and http_defaultConnection is right and same as that of application broker. When I send a message, I got the following exception and the system goes in an infinite loop. The exception is

[10/10/14 13:22:57] ID=dev_ESBTest (info) Connection to endpoint 'THPSProcessEntry.Q' (re)established for connection 'jms_defaultConnection' at tcs308737:2506

java.lang.NullPointerException
at com.sonicsw.xq.connector.jms.JMSEndpoint$JMSEndpointListener.onMessage(JMSEndpoint.java:515)
at progress.message.jimpl.Session.deliver(Session.java:3027)
at progress.message.jimpl.Session.run(Session.java:2390)
at progress.message.jimpl.Session$SessionThread.run(Session.java:2775)

If anybody have an idea, please help  me.

Thanks in advance.

Abhishek Sharma

Technology Partner - Forum

All Replies

Posted by tsteinbo on 14-Oct-2010 04:28

Abhishek,

which Sonic version do you use?

Thomas

Posted by sharma.abhishek2207 on 14-Oct-2010 04:36

Thanks for reply.

I am using sonic version 7.6

Posted by tsteinbo on 14-Oct-2010 05:18

I would need the exact version including service pack level and build number to pinpoint the problem please. You can obtain the e.g. from the container log of dev_ESB.

Posted by sharma.abhishek2207 on 14-Oct-2010 05:27

Hi Thomas,

The version details of sonic which I am using is

Sonic Management Release 7.6.0 Build Number 351

Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT enabled: jitc))

Posted by sk185050 on 14-Oct-2010 05:44

Can you share the configuration details of THPSProcessEntry.Q endpoint? If this is Q, I means mapped with the Q as destination can you please check after end point is created there is queue available at SMC?

Posted by tsteinbo on 14-Oct-2010 05:46

Abhishek,

Thanks for the version information.

Given that I could verify that this problem is fixed in service pack 1 or later. I suggest you apply the latest service pack 2.

Thomas

This thread is closed