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.
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. install and start AS
2. add remote-destination-outbound-socket-binding
jboss-eap-6.2/bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)"
result is {"outcome" => "success"}
3. remove remote-destination-outbound-socket-binding
jboss-eap-6.2/bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:remove"
result is {"outcome" => "success"}
4. add remote-destination-outbound-socket-binding
jboss-eap-6.2/bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)"
result is
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: Service jboss.outbound-socket-binding.remote-connection-war-ejb-1 is already registered",
"rolled-back" => true
}
Expected results:
{"outcome" => "success"}
Step 3 should either report reload required or should be fixed
Additional info:
Workaroud is to reload server after step 3
jboss-eap-6.2/bin/jboss-cli.sh -c "reload"
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. install and start AS 2. add remote-destination-outbound-socket-binding jboss-eap-6.2/bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" result is {"outcome" => "success"} 3. remove remote-destination-outbound-socket-binding jboss-eap-6.2/bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:remove" result is {"outcome" => "success"} 4. add remote-destination-outbound-socket-binding jboss-eap-6.2/bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" result is { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: Service jboss.outbound-socket-binding.remote-connection-war-ejb-1 is already registered", "rolled-back" => true } Expected results: {"outcome" => "success"} Step 3 should either report reload required or should be fixed Additional info: Workaroud is to reload server after step 3 jboss-eap-6.2/bin/jboss-cli.sh -c "reload"