Back to bug 1038465

Who When What Removed Added
Petr Sakař 2013-12-05 07:32:38 UTC Priority unspecified medium
Target Release --- EAP 6.3.0
CC rhatlapa
Alexey Loubyansky 2013-12-05 14:29:24 UTC CC emuckenh
Component CLI Domain Management
Assignee olubyans brian.stansberry
Jeff Mesnil 2014-02-21 11:00:14 UTC CC jmesnil
Link ID JBoss Issue Tracker WFLY-2987
Jeff Mesnil 2014-02-21 11:01:07 UTC Assignee brian.stansberry jmesnil
Summary CLI adding socket binding after remove without reload fails remote outbound socket binding server is not stopped when the resource is removed
Jeff Mesnil 2014-02-25 08:05:21 UTC Status NEW POST
John Doyle 2014-02-25 19:23:01 UTC CC jdoyle
Kabir Khan 2014-02-25 22:31:10 UTC Status POST MODIFIED
CC kkhan
Target Milestone --- DR2
Paul Gier 2014-03-05 23:10:37 UTC Status MODIFIED ON_QA
John Doyle 2014-03-06 19:33:17 UTC CC jdoyle
Petr Kremensky 2014-03-07 11:55:59 UTC Status ON_QA VERIFIED
Jeff Mesnil 2014-06-03 09:00:41 UTC Doc Text Cause:

The remote outbound socket binding server is not stopped when the resource is removed

Consequence:

It is not possible to add a remote-destination-outbound-socket-binding with the same name as the :add operation will fail because there is already a service registered with that name.

Fix:

When a remote-destination-outbound-socket-binding resource is removed, the corresponding service is stopped.

Result:

It is possible to remove and add remote-destination-outbound-socket-binding without any failure
Brian Stansberry 2014-06-03 13:53:29 UTC Doc Text Cause:

The remote outbound socket binding server is not stopped when the resource is removed

Consequence:

It is not possible to add a remote-destination-outbound-socket-binding with the same name as the :add operation will fail because there is already a service registered with that name.

Fix:

When a remote-destination-outbound-socket-binding resource is removed, the corresponding service is stopped.

Result:

It is possible to remove and add remote-destination-outbound-socket-binding without any failure 		Cause:

The remote outbound socket binding service is not stopped when the resource is removed

Consequence:

It is not possible to add a remote-destination-outbound-socket-binding with the same name as the :add operation will fail because there is already a service registered with that name.

Fix:

When a remote-destination-outbound-socket-binding resource is removed, the corresponding service is stopped.

Result:

It is possible to remove and add remote-destination-outbound-socket-binding without any failure
Scott Mumford 2014-06-05 02:14:29 UTC CC smumford
Doc Text Cause:

The remote outbound socket binding service is not stopped when the resource is removed

Consequence:

It is not possible to add a remote-destination-outbound-socket-binding with the same name as the :add operation will fail because there is already a service registered with that name.

Fix:

When a remote-destination-outbound-socket-binding resource is removed, the corresponding service is stopped.

Result:

It is possible to remove and add remote-destination-outbound-socket-binding without any failure 		In previous versions of JBoss EAP 6, the remote outbound socket binding service was not stopped when the resource was removed.

This meant it was not possible to add a remote-destination-outbound-socket-binding with the same name, as the :add operation would fail because there was already a service registered with that name.

In this release, when a remote-destination-outbound-socket-binding resource is removed, the corresponding service is stopped.

As a result it is possible to remove and add remote-destination-outbound-socket-binding without any failure.
John Skeoch 2014-06-18 07:21:07 UTC CC nobody
mark yarborough 2014-06-28 15:39:06 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-06-28 11:39:06 UTC

Back to bug 1038465