You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Richard Fox (JIRA)" <ji...@apache.org> on 2015/05/17 17:23:59 UTC
[jira] [Created] (APLO-379) Constant
locator_based.unary_!.||(uow.have_locators) assertion exception warnings
Richard Fox created APLO-379:
--------------------------------
Summary: Constant locator_based.unary_!.||(uow.have_locators) assertion exception warnings
Key: APLO-379
URL: https://issues.apache.org/jira/browse/APLO-379
Project: ActiveMQ Apollo
Issue Type: Bug
Affects Versions: 1.7
Environment: Linux 3.13.0-32-generic (Ubuntu 14.04.2 LTS)
Reporter: Richard Fox
Priority: Minor
Hello,
I have a broker running over a LAN that a lot of people are connecting on to using web sockets.
They don't seem to be able to keep their connection open for long periods of time.
As the disconnect messages appear in the connection.log there are also similarly timed messages containing the following:
{quote}
2015-05-17 10:59:52,235 | WARN | java.lang.AssertionError: assertion failed: locator_based.unary_!.||(uow.have_locators) | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-2
2015-05-17 10:59:52,235 | WARN | java.lang.AssertionError: assertion failed: locator_based.unary_!.||(uow.have_locators) | stacktrace | hawtdispatch-DEFAULT-2
java.lang.AssertionError: assertion failed: locator_based.unary_!.||(uow.have_locators)
at scala.Predef$.assert(Predef.scala:179)
at org.apache.activemq.apollo.broker.store.DelayingStoreSupport$$anonfun$4.apply(DelayingStoreSupport.scala:514)
at org.apache.activemq.apollo.broker.store.DelayingStoreSupport$$anonfun$4.apply(DelayingStoreSupport.scala:509)
at scala.collection.TraversableLike$$anonfun$flatMap$1.apply(TraversableLike.scala:251)
at scala.collection.TraversableLike$$anonfun$flatMap$1.apply(TraversableLike.scala:251)
at scala.collection.immutable.List.foreach(List.scala:309)
at scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:32)
at scala.collection.mutable.ListBuffer.foreach(ListBuffer.scala:45)
at scala.collection.TraversableLike$class.flatMap(TraversableLike.scala:251)
at scala.collection.AbstractTraversable.flatMap(Traversable.scala:105)
at org.apache.activemq.apollo.broker.store.DelayingStoreSupport$class.drain_flushes(DelayingStoreSupport.scala:509)
at org.apache.activemq.apollo.broker.store.leveldb.LevelDBStore.drain_flushes(LevelDBStore.scala:47)
at org.apache.activemq.apollo.broker.store.DelayingStoreSupport$$anonfun$3.apply$mcV$sp(DelayingStoreSupport.scala:495)
at org.fusesource.hawtdispatch.package$$anon$4.run(hawtdispatch.scala:357)
at org.fusesource.hawtdispatch.internal.HawtCustomDispatchSource$1.run(HawtCustomDispatchSource.java:127)
at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{quote}
Our connection logic seems to be reconnecting them fine but i'm still puzzled by what might be causing it.
Here's a snippet of the connection log:
{quote}
2015-05-17 11:05:03,997 Shutting connection '/10.31.249.103:42472' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:03,997 Shutting connection '/10.31.249.208:56436' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:03,996 Shutting connection '/10.31.249.216:58018' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:04,086 connected: local:/10.31.252.14:61624, remote:/10.31.249.208:56438
2015-05-17 11:05:04,086 disconnected: local:/10.31.252.14:61623, remote:/10.31.249.103:42472
2015-05-17 11:05:04,084 connected: local:/10.31.252.14:61623, remote:/10.31.249.103:42475
2015-05-17 11:05:04,087 disconnected: local:/10.31.252.14:61623, remote:/10.31.249.103:42473
2015-05-17 11:05:04,086 disconnected: local:/10.31.252.14:61623, remote:/10.31.249.216:58018
2015-05-17 11:05:04,086 disconnected: local:/10.31.252.14:61624, remote:/10.31.249.208:56436
2015-05-17 11:05:04,086 connected: local:/10.31.252.14:61623, remote:/10.31.249.216:58019
2015-05-17 11:05:04,086 connected: local:/10.31.252.14:61623, remote:/10.31.249.103:42474
2015-05-17 11:05:04,086 disconnected: local:/10.31.252.14:61623, remote:/10.31.248.213:51076
2015-05-17 11:05:07,995 connected: local:/10.31.252.14:61623, remote:/10.31.249.196:53241
2015-05-17 11:05:08,032 connected: local:/10.31.252.14:61623, remote:/10.31.249.196:53241
2015-05-17 11:05:15,667 Shutting connection '/10.31.249.195:34459' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:15,667 Shutting connection '/10.31.249.103:42475' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:15,667 Shutting connection '/10.31.249.196:53241' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:15,668 disconnected: local:/10.31.252.14:61623, remote:/10.31.249.103:42475
2015-05-17 11:05:15,668 disconnected: local:/10.31.252.14:61623, remote:/10.31.249.196:53241
2015-05-17 11:05:15,668 disconnected: local:/10.31.252.14:61624, remote:/10.31.249.195:34459
2015-05-17 11:05:15,668 Shutting connection '/10.31.249.103:42474' down due to: java.io.EOFException: Peer disconnected
2015-05-17 11:05:15,670 disconnected: local:/10.31.252.14:61623, remote:/10.31.249.103:42474
2015-05-17 11:05:15,673 connected: local:/10.31.252.14:61623, remote:/10.31.249.103:42476
2015-05-17 11:05:15,674 connected: local:/10.31.252.14:61623, remote:/10.31.249.103:42476
2015-05-17 11:05:15,687 connected: local:/10.31.252.14:61623, remote:/10.31.249.103:42477
2015-05-17 11:05:15,687 connected: local:/10.31.252.14:61624, remote:/10.31.249.195:34461
2015-05-17 11:05:15,688 connected: local:/10.31.252.14:61623, remote:/10.31.249.103:42477
2015-05-17 11:05:15,688 connected: local:/10.31.252.14:61624, remote:/10.31.249.195:34461
2015-05-17 11:05:15,689 connected: local:/10.31.252.14:61623, remote:/10.31.249.196:53242
2015-05-17 11:05:15,692 connected: local:/10.31.252.14:61623, remote:/10.31.249.196:53242
{quote}
I did a search for this message a few months ago on the JIRA and seem to remember seeing something along the lines of this error message but cannot find it now.
I've therefore decided to submit it. I apologise is there's a ticket floating around that I cannnot see.
Please let me know if you would like any other information.
Here's some general information about our only virtual host's web socket connector:
{quote}
Started Since: 13/05/2015 09:11:44
Bound to: /0.0.0.0:61623
Protocol: any
Currently Connected: 5
Connection Counter: 4979
Outbound Messages: 1999929
Inbound Messages: 0
Data Transferred In: 1.86 mb
Data Transferred Out: 248.02 mb
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)