Tom, Robert, and other mdsal experts, if any, I'm investigating one of those "Shutting down JVM" bugs in https://bugs.opendaylight.org/show_bug.cgi?id=9061 , and would love your valuable thoughts and feedback on it:
We have seen those before (search list), but in the past, they were always due to an "obvious" root cause, and at start up (such as an java.lang.NoClassDefFoundError or java.lang.IllegalAccessError) - but this one is after a while, under real world load. Can this be related to the many error logs like this seen in the same environment: An exception occurred while committing transaction member-2-datastore-operational-fe-1-txn-10344-0 java.lang.IllegalStateException: Store tree org.opendaylight.yangtools.yang.data.api.schema.tree.spi.LazyContainerNode@3cde34f3 and candidate base org.opendaylight.yangtools.yang.data.api.schema.tree.spi.LazyContainerNode@129ff94a differ. and if yes, what do these really mean, and how would one go about find the root cause of and fixing such problems? There are also a lot of other errors in the log I've attached to Bug 9061, including this: "akka.pattern.AskTimeoutException: Ask timed out on [ActorSelection[Anchor(akka://opendaylight-cluster-data/), Path(/user/shardmanager-operational/member-1-shard-default-operational#856921107)]] after [30000 ms]" - what do those mean, and can they be the cause of this suicide? There are other errors in that log too, so perhaps neither of the 2 above is what's really relevant here... Thanks a lot for any input, M. -- Michael Vorburger, Red Hat vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev