NullPointerException fired when using a non XA inbound resource

[arinban]

I am using the connector in synchronous mode to feed MDB components. For performances reasons we can't use XA from our provider (oracleAQ), so I set-up the inbound pool as non-XA. I also set up the bean so transactions are managed by the bean. The application starts properly and the inbound connection pool is successfully created but when the first message is read from the queue I get a NullPointerException :

java.lang.NullPointerException at com.sun.genericra.inbound.sync.SyncDeliveryHelper.runOnceStdNoXA(SyncDeliveryHelper.java:435) at com.sun.genericra.inbound.sync.SyncDeliveryHelper.deliver(SyncDeliveryHelper.java:211) at com.sun.genericra.inbound.sync.SyncDeliveryHelper.deliver(SyncDeliveryHelper.java:194) at com.sun.genericra.inbound.sync.SyncWorker.run(SyncWorker.java:125) at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown Source)

Looking to the code it is because the code call msgDelivered() on coord object while coord object has never been initialised.

private void runOnceStdNoXA() throws Exception { if (msg != null) { // Optionally wrap for ack() call /*

• TODO : The message wrappers need to be optimized
• we might not beed one wrapper class for each message

• type */ msg = mHoldUntilAck ? wrapMsg(msg, coord, -1) : msg; try { deliverMessage(msg); coord.msgDelivered(true); <---- Line 435 }

  catch (ResourceException r)

  { coord.setRollbackOnly(r); }

  Environment

  Operating System: All Platform: All

  Affected Versions

  [current]

[arinban]

Original Issue:https://github.com/javaee/glassfish-genericjmsra/issues/36 Raised By:@glassfishrobot Created at:Wed Jan 14 11:13:01 IST 2009 Assigned To:@glassfishrobot

[arinban]

@glassfishrobot Commented on Wed Jan 14 11:13:01 IST 2009 Reported by alainfaure

[arinban]

@glassfishrobot Commented on Mon Sep 06 18:59:39 IST 2010 nigeldeakin said: This is a duplicate of issue 41, which has now been fixed.

• • • This issue has been marked as a duplicate of 41 ***

[arinban]

@glassfishrobot Commented on Mon Sep 06 19:01:24 IST 2010 nigeldeakin said: Changing target milestone to "not determined" as issue tracker doesn't allow anything more specific.

[arinban]

@glassfishrobot Commented on Wed Sep 15 14:42:47 IST 2010 nigeldeakin said: Fixed in 2.1a

[arinban]

@glassfishrobot Commented on Wed Jan 14 11:13:01 IST 2009 Was assigned to binod

[arinban]

@glassfishrobot Commented on Mon Apr 24 13:03:07 IST 2017 This issue was imported from java.net JIRA GENERICJMSRA-36

[arinban]

@glassfishrobot Commented on Wed Sep 15 14:42:47 IST 2010 Marked as duplicate on Wednesday, September 15th 2010, 2:12:47 am

[arinban]

@glassfishrobot Closed the issue on Wed Sep 15 14:42:47 IST 2010