You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2009/02/01 04:12:59 UTC

[jira] Commented: (OPENJPA-882) Upgrade to latest Geronimo Spec releases

    [ https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669326#action_12669326 ] 

Pinaki Poddar commented on OPENJPA-882:
---------------------------------------

OpenJPA depends on JMS via one of its L2 cache synchronization mechanics as provided in org.apache.openjpa.event.JMSRemoteCommitProvider.
1. Any analysis/comment on the impact on this class of JMS version upgrade?
2. JMSRCP currently does not have any reconnect-on-failure or back-off policy of reconnect attempts -- does upgrade to JMS 1.1.1 help on any of these accounts?
   

> Upgrade to latest Geronimo Spec releases
> ----------------------------------------
>
>                 Key: OPENJPA-882
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-882
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: build / infrastructure
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Donald Woods
>            Priority: Minor
>             Fix For: 1.3.0, 2.0.0
>
>         Attachments: OPENJPA-882-branches13x.patch, OPENJPA-882-trunk.patch
>
>
> Pickup the latest Geronimo Spec releases.
> Upgrade geronimo-jms_1.1_spec from 1.0.1 to 1.1.1
> Upgrade geronimo-jta_1.1_spec from 1.1 to 1.1.1

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.