[ 
https://issues.apache.org/jira/browse/OPENEJB-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Gumbrecht updated OPENEJB-1267:
------------------------------------

    Attachment: OPENEJB-1267.patch

This is my current ActiveMQ state - Ok, not quite, as I am using snapshot 5.4 
due to a specific bug I hit in 5.3.
Several code improvements, and RA start/stop hardening.

NOTE: This adds a test dep on hsqldb to the project pom due to a requirement to 
test against a live (in memory)  database. I am NOT a maven wiz, so there may 
be a better way or pom location to do this?

> 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, OPENEJB-1267.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.

Reply via email to