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

JBoss Transactions does not support IPv6



    • Bug
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Deferred
    • 4.2.0.GA_CP07, 4.3.0.GA_CP06
    • TBD
    • Transaction Manager
    • None
    • Not Required


      In running through IPv6 testing for the EAP CP releases, issues were discovered concerning the use of IPv6 addresses and JBoss Transactions. I had a discussion with Jonathan over the course of a few emails, and here is a summary (where I have omitted some context but the key points remain):

      1. The TransactionManager is displaying use of IPv4 addresses when the AS is started with an IPv6 bind address

      > ./run.sh -b 3ffe:ffff:100:f101::1 -c default

      2009-11-09 21:01:07,011 DEBUG [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Starting jboss:service=TransactionManager
      2009-11-09 21:01:07,011 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      2009-11-09 21:01:07,011 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Setting up property manager MBean and JMX layer
      2009-11-09 21:01:07,185 DEBUG [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_1] - Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 59724
      2009-11-09 21:01:07,188 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] TransactionStatusManagerItem - host: port: 59724

      2. Current versions of JBossTS don't support IPv6. It's on the roadmap for 4.9

      3. 4.9 is projected to be released in December, and will not be going into the maintenance lines for EAP 4.x or 5.x, it's only for AS trunk.

      4. The real problems stem from the use of IPv6 addresses in Uids, which requires substantial alterations and a new representation for most ObjectStore contents. In short, it's not compatible, hence not going into the maintenance lines.

      This issue seems to be a blocker for any attempt at certifying EAP 4.2, 4.3 and 5.0 for IPv6 compatibility. There are many issues associated with IPv6 compatibility and described in JBPAPP-434, but most of these have been resolved.


        Issue Links



              tajinder Patrick Macdonald
              rachmato@redhat.com Richard Achmatowicz
              0 Vote for this issue
              4 Start watching this issue