Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10623

Back port of JBMessaging-1926 into EAP 5.1.0

    XMLWordPrintable

Details

    • Support Patch
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Done
    • EAP_EWP 5.1.0
    • One Off Releases
    • Messaging
    • None

    • EAP 5.1.0

    • Hide
      PATCH NAME:
              JBPAPP-10623
      PRODUCT NAME:
              JBoss Enterprise Application Platform
      VERSION:
              5.1.0
      SHORT DESCRIPTION:
              Back port of JBMessaging-1926 into EAP 5.1.0
      LONG DESCRIPTION:
              Back port of JBMessaging-1926 into EAP 5.1.0
       
      MANUAL INSTALL INSTRUCTIONS:
              1. Copy jboss-messaging.jar to $JBOSS_HOME/common/lib
              2. Copy jboss-messaging-client.jar to $JBOSS_HOME/client
              
      COMPATIBILITY:
              None
      DEPENDENCIES:
              JBoss EAP 5.1.0
      SUPERSEDES:
              None
      SUPERSEDED BY:
              
      CREATOR:
              Tom Ross
      DATE:
              8th February 2013
      Show
      PATCH NAME:          JBPAPP-10623 PRODUCT NAME:         JBoss Enterprise Application Platform VERSION:         5.1.0 SHORT DESCRIPTION:         Back port of JBMessaging-1926 into EAP 5.1.0 LONG DESCRIPTION:         Back port of JBMessaging-1926 into EAP 5.1.0   MANUAL INSTALL INSTRUCTIONS:         1. Copy jboss-messaging.jar to $JBOSS_HOME/common/lib         2. Copy jboss-messaging-client.jar to $JBOSS_HOME/client          COMPATIBILITY:         None DEPENDENCIES:         JBoss EAP 5.1.0 SUPERSEDES:         None SUPERSEDED BY:          CREATOR:         Tom Ross DATE:         8th February 2013
    • NEW

    Description

      Back port of JBMessaging-1926 into EAP 5.1.0

      Attachments

        Issue Links

          incorporates

          Bug - A problem which impairs or prevents the functions of the product. JBMESSAGING-1926 Root cause of XAException.XA_RBCOMMFAIL is never logged

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jbn-patch-team JBN Patch Team list
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: