sue, and which version this is going to be
addressed.
If not I'll open a JIRA.
Appreciate your help.
cheers
- mdasari
--
View this message in context:
http://www.nabble.com/FailoverTransport-stops-working-after-a-while-tp22851122p22851122.html
Sent from the ActiveMQ - User mai
at
>>>>
>>>>
>>>> org.apache.activemq.transport.failover.FailoverTransport$2.iterate(FailoverTransport.java:124)
>>>
>>>> INFO | jvm 1| 2009/03/16 21:26:15 | at
>>>>
>>>>
>>>> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
>>>
>>>> INFO | jvm 1| 2009/03/16 21:26:15 | at
>>>>
>>>>
>>>> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
>>>
>>>> INFO | jvm 1| 2009/03/16 21:26:15 | DEBUG FailoverTransport
>>>> - Waking up reconnect task
>>>> INFO | jvm 1| 2009/03/16 21:26:15 | DEBUG FailoverTransport
>>>> - Started.
>>>> INFO | jvm 1| 2009/03/16 21:26:15 | DEBUG FailoverTransport
>>>> - Waking up reconnect task
>>>> INFO | jvm 1| 2009/03/16 21:27:00 | DEBUG AMQPersistenceAdapter
>>>> - Checkpoint started.
>>>> INFO | jvm 1| 2009/03/16 21:27:00 | DEBUG AMQPersistenceAdapter
>>>> - Checkpoint done.
>>>> INFO | jvm 1| 2009/03/16 21:28:00 | DEBUG AMQPersistenceAdapter
>>>> - Checkpoint started.
>>>> -
>>>>
>>>>
>>>> Basically, it was able to deliver a message (and few more prior to that
>>>> time
>>>> period), but for another message that is very close (in time) to the
>>>> previous message it is running into a NullPointerException, after that
>>>> it
>>>> stops functioning totally.
>>>>
>>>> I took a brief look at the FailoverTransport.java code, I'm not an
>>>> expert
>>>> on
>>>> the AMQ code, but I suspect that FailoverTransport.java reconnectTask
>>>> member
>>>> variable is attempted to be used by the task-runner thread before it was
>>>> completely initialized (basically race conditions without proper
>>>> synchronization)
>>>>
>>>> I can provide more details on our network topology if it is required. I
>>>> searched around but didn't find any related issues or bugs. Does anyone
>>>> know
>>>> if this is a known issue, and which version this is going to be
>>>>
>>> addressed.
>>>
>>>> If not I'll open a JIRA.
>>>>
>>>> Appreciate your help.
>>>>
>>>> cheers
>>>> - mdasari
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>>>>
>>> http://www.nabble.com/FailoverTransport-stops-working-after-a-while-tp22851122p22851122.html
>>>
>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
| DEBUG FailoverTransport
> > > - Started.
> > > INFO | jvm 1| 2009/03/16 21:26:15 | DEBUG FailoverTransport
> > > - Waking up reconnect task
> > > INFO | jvm 1 | 2009/03/16 21:27:00 | DEBUG AMQPersistenceAdapter
> > > - Checkpoint started.
> > > INFO | jvm 1| 2009/03/16 21:27:00 | DEBUG AMQPersistenceAdapter
> > > - Checkpoint done.
> > > INFO | jvm 1| 2009/03/16 21:28:00 | DEBUG AMQPersistenceAdapter
> > > - Checkpoint started.
> > > -
> > >
> > >
> > > Basically, it was able to deliver a message (and few more prior to that
> > > time
> > > period), but for another message that is very close (in time) to the
> > > previous message it is running into a NullPointerException, after that
> it
> > > stops functioning totally.
> > >
> > > I took a brief look at the FailoverTransport.java code, I'm not an
> expert
> > > on
> > > the AMQ code, but I suspect that FailoverTransport.java reconnectTask
> > > member
> > > variable is attempted to be used by the task-runner thread before it
> was
> > > completely initialized (basically race conditions without proper
> > > synchronization)
> > >
> > > I can provide more details on our network topology if it is required. I
> > > searched around but didn't find any related issues or bugs. Does anyone
> > > know
> > > if this is a known issue, and which version this is going to be
> > addressed.
> > > If not I'll open a JIRA.
> > >
> > > Appreciate your help.
> > >
> > > cheers
> > > - mdasari
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://www.nabble.com/FailoverTransport-stops-working-after-a-while-tp22851122p22851122.html
> > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > >
> > >
> >
>
own issue, and which version this is going to be
addressed.
If not I'll open a JIRA.
Appreciate your help.
cheers
- mdasari
--
View this message in context:
http://www.nabble.com/FailoverTransport-stops-working-after-a-while-tp22851122p22851122.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> >
> > Basically, it was able to deliver a message (and few more prior to that
> > time
> > period), but for another message that is very close (in time) to the
> > previous message it is running into a NullPointerExce
d to be used by the task-runner thread before it was
> completely initialized (basically race conditions without proper
> synchronization)
>
> I can provide more details on our network topology if it is required. I
> searched around but didn't find any related issues or bugs. Does anyone
> know
> if this is a known issue, and which version this is going to be addressed.
> If not I'll open a JIRA.
>
> Appreciate your help.
>
> cheers
> - mdasari
>
>
> --
> View this message in context:
> http://www.nabble.com/FailoverTransport-stops-working-after-a-while-tp22851122p22851122.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
rched around but didn't find any related issues or bugs. Does anyone know
if this is a known issue, and which version this is going to be addressed.
If not I'll open a JIRA.
Appreciate your help.
cheers
- mdasari
--
View this message in context:
http://www.nabble.com/FailoverTran
