Bug 1038465
Summary: | remote outbound socket binding server is not stopped when the resource is removed | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Petr Sakař <psakar> |
Component: | Domain Management | Assignee: | Jeff Mesnil <jmesnil> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | medium | ||
Version: | 6.2.0 | CC: | brian.stansberry, emuckenh, jmesnil, kkhan, nobody, rhatlapa, smumford |
Target Milestone: | DR2 | ||
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-28 15:39:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Sakař
2013-12-05 07:31:32 UTC
Verified on EAP 6.3.0.DR2 |