[OPENEJB-1938] Embedded ActiveMQ broker startup and shutdown fails to observe configured timeout

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: (not version related)
• Fix Version/s: 4.5.1
• Component/s: container system
• Environment: All
• Assignee: Andy Gumbrecht
• Reporter: Andy Gumbrecht
• Created: 15/Nov/12 14:40
• Updated: 15/Nov/12 14:41
• Resolved: 15/Nov/12 14:41

Description

The org.apache.activemq.ra.ActiveMQResourceAdapter was starting in internal thread (of which we have no control) that continued after 5 seconds irrelevant of the broker status.

This meant that our own thread (that has a configurable timeout) was never actually waiting longer than 5 seconds for the broker to start.

Now that this issue is fixed in trunk it is up to us to manage the broker 'stop' call.