ActiveMQ connection failure after sudden power-off

[jochenw <jo...@googlemail.com>]

Hello,

I have a target with ActiveMQ 5.11.1 running in Karaf in an environment
where sudden power-offs can happen. In general, the system restarts without
problems. However, now and then ActiveMQ seems to hang. The logs indicate
the message broker starting correctly, but other OSGi bundles fail
connecting; same for connectiong to a broker network:

2016-02-02 10:23:05,499 | WARN  | ctivemq.server]) |
DiscoveryNetworkConnector        | 50 - org.apache.activemq.activemq-osgi -
5.11.1 | Could not connect to local URI:
vm://MyMessageBroker_94170c6d-3af8-4d7f-af53-9f6ce7f804a9?async=false&network=true:
Server TransportAcceptListener is null.

2016-02-02 10:23:10,112 | WARN  | ActiveMQ Task-1  | FailoverTransport               
| 50 - org.apache.activemq.activemq-osgi - 5.11.1 | Failed to connect to
[vm://MyMessageBroker_94170c6d-3af8-4d7f-af53-9f6ce7f804a9?create=false:61616]
after: 10 attempt(s) continuing to retry.

The retries continue forever. Restarting Karaf once leads to the same
problem. After a second restart, everything works fine again.

Has anybody observed a similar thing, or knows what might be behind the
"Server TransportAcceptListener is null" message?

Best Regards,

Jochen





--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-connection-failure-after-sudden-power-off-tp4706813.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.