Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 21 Mar 2012 18:21:40 +0000 (UTC)
From: "Timothy Bish (Commented) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1999430899.43156.1332354100059.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1020941683.41847.1332341981544.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3782) FailoverTransport throws NPE
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234798#comment-13234798 ] 

Timothy Bish commented on AMQ-3782:
-----------------------------------

Do you have a test case that can reproduce this.  I don't really see a way in the current code that this could happen.
                
> 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
>
> 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