Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 887828

Summary: Unable to use created binding set via JON server
Product: [JBoss] JBoss Operations Network Reporter: Radim Hatlapatka <rhatlapa>
Component: Plugin -- JBoss EAP 5Assignee: Thomas Segismont <tsegismo>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.1.2CC: myarboro
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-14 15:30:07 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 Radim Hatlapatka 2012-12-17 12:24:04 UTC 
Description of problem:

If I create new Service Binding Set in JON and I try to use it via property -Djboss.service.binding.set=new-binding-set, the binding is not used and default binding is used instead.

In $JBOSS_HOME/server/default/data/attachments/bindingservice.beans-d99ec44380d5fa31a10d73963e853054/502e49d4cde22b4d298255f5ae41607b.attachment.xml I have found configuration for the new service binding set created by JON server. But when I try to run the EAP using ./run.sh -c default -Djboss.service.binding.set=new-binding-set all services are bound according to default setting instead of using new setting


Steps to Reproduce:
1. Start JON server, JON agent and EAP 5
2. Import EAP 5 to JON server
3. In service binding manager create new binding set. Use name of your choice and set port offset (e.g. 500), save the setting.
4. stop the server
5. start the server with -Djboss.service.binding.set=new-binding-set (where new-binding-set is your chosen name)
6. check ports to which the server is bound (should be moved by 500 => default port should be instead of 8080 8580)
  
Actual results:

Even after restarting the server it is bound to default ports


Expected results:

The services should be bound to ports increased by specified port offset


Additional info:

If I want to use different binding set than the default which is defined in ../server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml it works as expected.
Comment 2 Thomas Segismont 2013-05-14 15:30:07 UTC 
I don't think this is a JON bug.

When you create a Service Binding Set programmatically it is saved in the data/attachments/bindingservice.beans-*.attachment.xml file as you said. But in this file there is also this:

            <ns2:property name="activeBindingSetName">
                <ns2:simple>ports-04</ns2:simple>
            </ns2:property>

To change this value you must update the "Active Binding Set Name" property in the Configuration tab of the Service Binding Manager resource view in JON. And then restart your server (from JON or manually) and you'll see the port changes.

Don't forget to update the Connection Settings tab if you change the JNP port otherwise the agent will no longer be able to connect to the EAP server.
Comment 3 Radim Hatlapatka 2013-05-15 10:01:48 UTC 
Ok, I have verified, that it works this way. But once it is set this way, the only way to change binding set is by changing the activeBindingSetName property (using -Djboss.service.binding.set no longer works)
Comment 4 Thomas Segismont 2013-05-15 10:05:24 UTC 
(In reply to comment #3)
> (using -Djboss.service.binding.set no longer works)

Yes. That's probably something to discuss with EAP team
Comment 5 Radim Hatlapatka 2013-05-15 10:50:05 UTC 
Ok, I have created new BZ against EAP 5: https://bugzilla.redhat.com/show_bug.cgi?id=963178