Details

    • Type: Task Task
    • Status: Closed Closed (View Workflow)
    • Priority: Critical Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: JBossAS-4.2.0.CR1
    • Component/s: JMS (JBossMQ)
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Environment:
      WebSphereMQ 5.3 with Extended TX client
    • Similar Issues:
      Show 10 results 

      Description

      http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossASPart2

      we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling

        Activity

        Hide
        Luc Texier
        added a comment -

        Hi Weston,

        Thanks for all your efforts to make it happen

        What we need now is very simple. We need a standalone test case that we can provide IBM support with.

        Would you be able to produce such code or does it have to be executed within JBossAS?

        Show
        Luc Texier
        added a comment - Hi Weston, Thanks for all your efforts to make it happen What we need now is very simple. We need a standalone test case that we can provide IBM support with. Would you be able to produce such code or does it have to be executed within JBossAS?
        Hide
        Weston M. Price
        added a comment -

        Moving to 4.0.6

        Show
        Weston M. Price
        added a comment - Moving to 4.0.6
        Hide
        Dimitris Andreadis
        added a comment -

        Now, I'm not sure if this need fixing in both Branch_4_0 and Branch_4_2 ???

        Show
        Dimitris Andreadis
        added a comment - Now, I'm not sure if this need fixing in both Branch_4_0 and Branch_4_2 ???
        Hide
        Weston M. Price
        added a comment -

        I believe we should put this only on 4.2. It's fairly significant change that really doesn't warrant being fixed in a SP release.

        Show
        Weston M. Price
        added a comment - I believe we should put this only on 4.2. It's fairly significant change that really doesn't warrant being fixed in a SP release.
        Hide
        Weston M. Price
        added a comment -

        A new JcaXAResourceWrapper has been added to allow for the isSameRMOverrideValue mechanism. This will enable JBoss to enlist multiple WASMQ resources in the same transaction. Note, the configuration for this will be specified on the Wiki, but the short of it is that the isSameRMOverrideValue is now configurable per datasource/connection-factory definition; it is not just for JDBC resources. Depending upon demmand, this fix may need to be ported to previous JBoss releases to address WASMQ integration issues.

        Show
        Weston M. Price
        added a comment - A new JcaXAResourceWrapper has been added to allow for the isSameRMOverrideValue mechanism. This will enable JBoss to enlist multiple WASMQ resources in the same transaction. Note, the configuration for this will be specified on the Wiki, but the short of it is that the isSameRMOverrideValue is now configurable per datasource/connection-factory definition; it is not just for JDBC resources. Depending upon demmand, this fix may need to be ported to previous JBoss releases to address WASMQ integration issues.

          People

          • Assignee:
            Weston M. Price
            Reporter:
            Luc Texier
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: