OpenJPA
  1. OpenJPA
  2. OPENJPA-882

Upgrade to latest Geronimo Spec releases

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.3.0, 2.0.0-M2
    • Fix Version/s: 1.3.0, 2.0.0-M2
    • Component/s: build / infrastructure
    • Labels:
      None

      Description

      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

      1. OPENJPA-882-trunk.patch
        0.7 kB
        Donald Woods
      2. OPENJPA-882-branches13x.patch
        1 kB
        Donald Woods

        Activity

        Hide
        Donald Woods added a comment -

        Patch for trunk (Rev739297) to upgrade to latest Geronimo JMS and JTA spec maintenance releases.

        Show
        Donald Woods added a comment - Patch for trunk (Rev739297) to upgrade to latest Geronimo JMS and JTA spec maintenance releases.
        Hide
        Donald Woods added a comment -

        Ready for a committer to review and commit.

        Show
        Donald Woods added a comment - Ready for a committer to review and commit.
        Hide
        Donald Woods added a comment -

        Patch to upgrade to the latest Geronimo Specs for branches/1.3.x at Rev739360.

        Show
        Donald Woods added a comment - Patch to upgrade to the latest Geronimo Specs for branches/1.3.x at Rev739360.
        Hide
        Michael Dick added a comment -

        Thanks for the patch Donald!

        Show
        Michael Dick added a comment - Thanks for the patch Donald!
        Hide
        Pinaki Poddar added a comment -

        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?

        Show
        Pinaki Poddar added a comment - 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?
        Hide
        David Jencks added a comment -

        I think this upgrade only actually changes some maven metadata and possibly osgi compatibility. It certainly doesn't affect the contents of the jms api itself. To change the behavior of your jms cache sync you'd have to change something about the configuration of the jms implementation actually used for synchronization. For instance AcitveMQ has a number of (IIUC) easy to configure ways to have failover connections and exponential backoff on reconnect attempts.

        Show
        David Jencks added a comment - I think this upgrade only actually changes some maven metadata and possibly osgi compatibility. It certainly doesn't affect the contents of the jms api itself. To change the behavior of your jms cache sync you'd have to change something about the configuration of the jms implementation actually used for synchronization. For instance AcitveMQ has a number of (IIUC) easy to configure ways to have failover connections and exponential backoff on reconnect attempts.

          People

          • Assignee:
            Unassigned
            Reporter:
            Donald Woods
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development