activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Durable client removal caused broker to shutdown in replicated leveldb
Date Fri, 21 Aug 2015 13:28:00 GMT
I don't see an obvious causal link between those two, though I haven't
looked at that code (my usual trick of going to GrepCode didn't work; maybe
GC doesn't index Scala code?) so I can't say for sure.  Unless you see a
causal link I'm missing and want to explain it?

Hopefully someone who knows that code will provide some insight.  If not,
you could always go track down that code and see what you can figure out.
This list could use an active LevelDB expert, and you're the most active
poster on the topic, so you've presumably got a very good starting point
for becoming an expert on the subject.
On Aug 20, 2015 8:58 AM, "khandelwalanuj" <khandelwal.anuj90@gmail.com>
wrote:

> As we can see that before 'ArrayIndexOutOfBoundsException' we got below
> logs:
>
>  20150817 18:24:42.582 EDT (ActiveMQ NIO Worker 6)
> org.apache.activemq.leveldb.util.Log$class#debug 112 DEBUG] - on rollback,
> the transaction TX:ID:app1.net-38906-1439632105449-7:13:42 does not exist
>
> That's why I am suspecting that could this cause broker to stop ?
>
> Thanks,
> Anuj
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Durable-client-removal-caused-broker-to-shutdown-in-replicated-leveldb-tp4701209p4701241.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message