[jboss-jira] [JBoss JIRA] Commented: (AS7-1610) NPE on server startup and setup of MDBs.

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622618#comment-12622618 ] 

jaikiran pai commented on AS7-1610:
-----------------------------------

A missing "destination" should not however cause a NullPointerException. It should be reported/handled better. So, IMO, the NullPointerException is still a bug.


> NPE on server startup and setup of MDBs.
> ----------------------------------------
>
>                 Key: AS7-1610
>                 URL: https://issues.jboss.org/browse/AS7-1610
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.0.Alpha1
>         Environment: RHEL 5.5 running AS7
>            Reporter: Jeremy Whiting
>            Assignee: Carlo de Wolf
>            Priority: Blocker
>              Labels: rn-not-needed
>
>  When I start the server with a deployed application (EAR archive) the MDB setup is causing a NullPointerException.
>  The MDB uses annotations rather than declarative XML for it's configuration.
>  14:36:55,642 ERROR [org.hornetq.ra.inflow.HornetQActivation]
> (jca-short-running-threads-threads - 6) Unable to reconnect
> org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter at 2f8541f5
> destination=null destinationType=javax.jms.Queue ack=Auto-acknowledge
> durable=false clientID=null user=null maxSession=15):
> java.lang.NullPointerException
>     at javax.naming.NameImpl.<init>(NameImpl.java:281) [:1.6.0_20]
>     at javax.naming.CompositeName.<init>(CompositeName.java:231) [:1.6.0_20]
>     at org.jboss.as.naming.util.NameParser.parse(NameParser.java:49)
>     at org.jboss.as.naming.NamingContext.parseName(NamingContext.java:393)
>     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
>     at javax.naming.InitialContext.lookup(InitialContext.java:409)
> [:1.6.0_20]
>     at org.hornetq.ra.Util.lookup(Util.java:174)
> [hornetq-ra-2.2.7.Final.jar:]
>     at
> org.hornetq.ra.inflow.HornetQActivation.setupDestination(HornetQActivation.java:436)
> [hornetq-ra-2.2.7.Final.jar:]
>     at
> org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:283) [hornetq-ra-2.2.7.Final.jar:]
>     at
> org.hornetq.ra.inflow.HornetQActivation.handleFailure(HornetQActivation.java:548)
> [hornetq-ra-2.2.7.Final.jar:]
>     at
> org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:591)
> [hornetq-ra-2.2.7.Final.jar:]
>     at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:212)
>     at
> org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
>     at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801)
>     at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
>     at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821)
>     at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
>     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>  Currently the hornetq implementation HornetQActivation expects the HornetQActivationSpec to be configured using properties. These properties are destination and acknowlegment type.
>  This test case shows the implementation is expecting the properties.
>  hornetq-2-2-7/examples/javaee/mdb-cmt-tx-not-supported/src/org/hornetq/javaee/example/server/MDB_CMT_TxNotSupported.java 
>  
>  However the JEE6 tutorial shows a table of the allowed properties for application  and these two are not listed. I checked the spec to make sure.
>  http://download.oracle.com/javaee/6/tutorial/doc/bnbpo.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira