[jboss-jira] [JBoss JIRA] (AS7-1627) Handle NPE for missing destination property on hornetq MDB activation.

Jeff Mesnil (JIRA) jira-events at lists.jboss.org
Thu May 3 04:03:19 EDT 2012


     [ https://issues.jboss.org/browse/AS7-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil resolved AS7-1627.
------------------------------

    Resolution: Done


there is nothing to do for this on the AS side. HORNETQ-916 is the only fix to apply
                
> Handle NPE for missing destination property on hornetq MDB activation.
> ----------------------------------------------------------------------
>
>                 Key: AS7-1627
>                 URL: https://issues.jboss.org/browse/AS7-1627
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: JMS
>    Affects Versions: 7.0.0.Beta1
>         Environment: RHEL 5.5
>            Reporter: Jeremy Whiting
>            Assignee: Jeff Mesnil
>            Priority: Minor
>
>  When a destination property is missing on the hornetq activationConfig the AS7 server throws a NPE. Instead the HornetQActivation object could catch the exception and log a message telling the user to define the missing property.
>  This is the exception stack trace when AS7 starts up.
> 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)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list