[
https://issues.apache.org/jira/browse/OPENEJB-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated OPENEJB-1267:
------------------------------------
Attachment: ActiveMQ.patch
Updated patch.
Fixed the test - Due to the fact that for ActiveMQ5 I now start and checkpoint
the broker before returning it, the test needs a valid DataSource.
I just use an in memory hsqldb - So added this dep to the pom.
I have not done so in this patch, but the hsqldb version should be updated to
1.8.0.10 from 1.8.0.7 - I'll let you decide if we need that.
Also added a startup thread timeout - Using a default of 5 seconds, but maybe
this should be much higher or at least configurable?
> 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, 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.
