The issue which we experienced is little different. If anyother thought or
any configuration which will lead us to avoid the same in future will be
greatly helpful.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-1-Error-tp3026574p3031696.html
Sent from the Ac
Hi Dejan,
Yes, it appears that my problem has been resolved in the latest snapshot
build. That's great! Thanks for referencing that for me.
So, I guess I can't reproduce ajitroy's issue.
-Jim
On Thu, Nov 4, 2010 at 10:17 AM, Dejan Bosanac wrote:
> Hi Jim,
>
> what you're describing sounds l
Hi Jim,
what you're describing sounds like
https://issues.apache.org/activemq/browse/AMQ-2935 which is resolved
on the trunk.
This null pointer exception seems different than one one shown in that
issue. Can you confirm when kind of exception are you getting after
the restart (and try 5.5-SNAPSHO
I can reproduce this.
On Windows, start a brand new broker. Once everything is up and running,
use Task Manager to forcefully kill the executable. Attempt to start the
broker, and it will never come up. It has gone into a wedged state upon
abnormal termination.
If that is enough of a detailed
Not exactly. It happened once and we can get going only after deleting KahaDB
folder. However i can say for sure it happened after restart. Before restart
it was working all fine and then it started giving this exception and same
case with subsequent restart.
--
View this message in context:
ht
Can you reproduce it? If you can, please raise a Jira with detailed steps.
Cheers
--
Dejan Bosanac
-
FuseSource - The experts in open source integration and messaging.
Email: dej...@fusesource.com
Web: http://fusesource.com
Twitter: http://twitter.com/dejanb
ActiveMQ in Action -
