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]

• Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/36
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@glassfishrobot

[arinban]

@glassfishrobot Commented Reported by alainfaure

[arinban]

@glassfishrobot Commented 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 nigeldeakin said: Changing target milestone to "not determined" as issue tracker doesn't allow anything more specific.

[arinban]

@glassfishrobot Commented nigeldeakin said: Fixed in 2.1a

[arinban]

@glassfishrobot Commented Was assigned to binod

[arinban]

@glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-36

[arinban]

@glassfishrobot Commented Marked as duplicate on Wednesday, September 15th 2010, 2:12:47 am