[
https://issues.apache.org/jira/browse/OPENEJB-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861298#action_12861298
]
Andy Gumbrecht commented on OPENEJB-1267:
-----------------------------------------
There is a persistent queue issue in the current ActiveMQ release that is
resolved in the latest snapshot.
https://issues.apache.org/activemq/browse/AMQ-2696
I would therefore like to suggest that we use either of the latest 5.3 or 5.4
snapshots in OpenEJB trunk until the next release.
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/
> ActiveMQResourceAdapter improvements
> ------------------------------------
>
> Key: OPENEJB-1267
> URL: https://issues.apache.org/jira/browse/OPENEJB-1267
> Project: OpenEJB
> Issue Type: Improvement
> Components: container system
> Environment: All
> Reporter: Andy Gumbrecht
> Priority: Minor
> Fix For: 3.1.x
>
> Attachments: ActiveMQ.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Hardened the current ActiveMQResourceAdapter start and stop code.
> The adapter should not prevent a server from starting or stopping, and is now
> threaded in context.
> The ActiveMQ5Factory will now override the following configuration options
> which may cause shutdown issues if set to true.
> broker.setUseShutdownHook(false);
> broker.setSystemExitOnShutdown(false);
> The broker is now started, and creates a check point, before it is returned
> to OpenEJB. This ensures that all pools and resources that ActiveMQ initiates
> are up before OpenEJB gains access.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
