Back to bug 1077156

Who When What Removed Added
Ondrej Chaloupka 2014-03-17 12:22:29 UTC CC hhovsepy
Gytis Trikleris 2014-04-03 11:50:10 UTC CC gtrikler
Gytis Trikleris 2014-04-09 08:52:58 UTC Assignee paul.robinson gtrikler
Ondrej Chaloupka 2014-07-08 14:17:06 UTC CC tom.jenkinson
Assignee gtrikler smaestri
Target Release --- EAP 6.4.0
Scott Mumford 2014-07-10 04:26:45 UTC CC smumford
Doc Text In this release of JBoss EAP 6, it is not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This is because this part of the address must be wrapped in square brackets; `[::1]`.

This issue is expected to be resolved in the next release of the product.
Doc Type Bug Fix Known Issue
Stefano Maestri 2014-07-30 08:22:21 UTC Link ID JBoss Issue Tracker WFLY-3690
Stefano Maestri 2014-07-30 08:22:36 UTC Status NEW ASSIGNED
Stefano Maestri 2014-09-29 07:04:55 UTC Summary Not possible to start XST transaction on IPv6 with server bound to ::1 Not possible to start XTS transaction on IPv6 with server bound to ::1
Assignee smaestri zfeng
Amos Feng 2014-10-18 01:30:26 UTC Status ASSIGNED POST
Amos Feng 2014-10-20 09:26:42 UTC Status POST MODIFIED
mark yarborough 2014-10-26 16:17:21 UTC Keywords Question
mark yarborough 2014-10-26 17:10:21 UTC Keywords Question
Gytis Trikleris 2014-11-04 10:03:00 UTC CC gtrikler
Kabir Khan 2014-11-25 16:54:02 UTC Status MODIFIED ON_QA
CC kkhan
Target Milestone --- DR6
Ondrej Chaloupka 2014-11-26 14:46:55 UTC Status ON_QA VERIFIED
Lucas Costi 2015-01-27 01:45:16 UTC CC lcosti
Doc Text In this release of JBoss EAP 6, it is not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This is because this part of the address must be wrapped in square brackets; `[::1]`.

This issue is expected to be resolved in the next release of the product.
** Needs bug fix text

In this release of JBoss EAP 6, it is not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This is because this part of the address must be wrapped in square brackets; `[::1]`.

This issue is expected to be resolved in the next release of the product.
Doc Type Known Issue Bug Fix
Scott Mumford 2015-03-02 03:21:30 UTC Doc Text ** Needs bug fix text

In this release of JBoss EAP 6, it is not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This is because this part of the address must be wrapped in square brackets; `[::1]`.

This issue is expected to be resolved in the next release of the product.
In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because this part of the address must be wrapped in square brackets; `[::1]`.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required.
Scott Mumford 2015-03-02 03:24:19 UTC CC ochaloup
Doc Text In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because this part of the address must be wrapped in square brackets; `[::1]`.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required.
In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because this part of the address must be wrapped in square brackets; `[::1]`.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required before it is passed to the XTS core.
Flags needinfo?(ochaloup)
Ondrej Chaloupka 2015-03-09 11:28:47 UTC Flags needinfo?(ochaloup)
Lucas Costi 2015-03-09 23:32:43 UTC CC lcosti
Scott Mumford 2015-03-11 01:35:33 UTC Doc Text In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because this part of the address must be wrapped in square brackets; `[::1]`.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required before it is passed to the XTS core.
In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because this part of the address must be wrapped in square brackets; `[::1]`.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required before it is passed to the XTS core.

Note that if you are using the `-b` switch in a CLI comment, do not wrap the address portion of the URL in square brackets as this is contrary to the the specification and will prevent Webservices from starting.
Flags needinfo?(ochaloup)
Ondrej Chaloupka 2015-03-11 09:18:05 UTC Doc Text In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because this part of the address must be wrapped in square brackets; `[::1]`.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required before it is passed to the XTS core.

Note that if you are using the `-b` switch in a CLI comment, do not wrap the address portion of the URL in square brackets as this is contrary to the the specification and will prevent Webservices from starting.
In a previous release of JBoss EAP 6, it was not possible to start an XST transaction on IPv6 with a server bound to address `::1`. This was because XTS core did not separate address from port number with square brackets; `[::1]:8080` as IPv6 defines for URLs.

This issue has been resolved by splitting the URL into discrete sections and inserting square brackets as required before it is passed to the XTS core.

Note that if you are using the `-b` switch when starting JBoss EAP 6 to run on IPv6 address, do not wrap the address in square brackets as this is contrary to the the specification and will prevent Webservices from starting.
Flags needinfo?(ochaloup)
Russell Dickenson 2017-10-10 00:22:03 UTC Docs Contact rdickens
PnT Account Manager 2018-03-06 20:37:17 UTC CC smumford
Jan Kurik 2019-08-19 12:42:44 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2019-08-19 12:42:44 UTC
Jan Kurik 2019-08-19 12:46:22 UTC Last Closed 2019-08-19 12:42:44 UTC
Tora Setya 2023-07-03 00:41:19 UTC CC dinadwimaharani25
Jonathan Wakely 2023-07-04 10:48:00 UTC Comment 16 Tag spam

Back to bug 1077156