[
https://issues.apache.org/jira/browse/AMQ-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3782.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Added a check to ensure no access to reconnectTask when its potentially null.
> FailoverTransport throws NPE
> ----------------------------
>
> Key: AMQ-3782
> URL: https://issues.apache.org/jira/browse/AMQ-3782
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.2.0
> Environment: debian java-6-sun activemq 5.2
> Reporter: Wojciech Oczkowski
> Assignee: Timothy Bish
> Fix For: 5.6.0
>
>
> Failover transport occasionally throws NullPointerException
> INFO | jvm 1 | 2012/03/19 09:25:05 | Exception in thread "ActiveMQ
> Failover Worker: 2009192672" java.lang.NullPointerException
> INFO | jvm 1 | 2012/03/19 09:25:05 | at
> org.apache.activemq.transport.failover.FailoverTransport$2.iterate(FailoverTransport.java:125)
> INFO | jvm 1 | 2012/03/19 09:25:05 | at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
> INFO | jvm 1 | 2012/03/19 09:25:05 | at
> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
> It seems like DedicatedTaskRunner starts Thread before FailoverTransport
> finish initializing reconnectTask field.
> Same code is present in 5.5.1 so it's possible that same bug is out there
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
