Description of problem:
Adding EAP 6 server with additional outbound socket binding ref to the inventory will incorrectly add the same binding to the mail configuration of the JBoss ON Server resource (RHQ Server). 

Version-Release number of selected component (if applicable):
JBoss ON 3.2 and 3.2.1

How reproducible:
Always

Steps to Reproduce:
1. On the first box (server1) unzip JBoss ON 3.2.1 zip file;
2. Change $JON-SERVER/bin/rhq-server.properties file, set the following properties and save the file:
...
# Email settings used to connect to an SMTP server to send alert emails.
rhq.server.email.smtp-host=my.smtp.server.com
rhq.server.email.smtp-port=25
rhq.server.email.from-address=test@server.com
... 
3. Install JBoss ON 3.2.1 and it's components;
4. Install plugins for EAP;
5. Start storage nodes, JBoss ON Server and JBoss ON Agent and import RHQ Server into inventory;
6. Navigate to RHQ Server resource -> mail -> Mail Sessions -> java:jboss/mail/Default -> smtp and confirm that only one Outbound Socket Binding Ref is listed there (mail-smtp).
7. On another box (server2) install and configure JBoss ON Agent 3.2.1 to connect to the first box (server1);
8. On the server2 install EAP 6.x server in standalone mode, add management user and start the server;
9. Using JBoss CLI, execute the following to add new outbound socket binding:

/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=redhat:add(host=my.smtp.server.com,port=25)
{"outcome" => "success"}

so should have something like:

/socket-binding-group=standard-sockets:read-resource(recursive=true)
{
    "outcome" => "success",
    "result" => {
        "default-interface" => "public",
        "name" => "standard-sockets",
        "port-offset" => expression "${jboss.socket.binding.port-offset:0}",
        "local-destination-outbound-socket-binding" => undefined,
        "remote-destination-outbound-socket-binding" => {
            "mail-smtp" => {
                "fixed-source-port" => false,
                "host" => "localhost",
                "port" => 25,
                "source-interface" => undefined,
                "source-port" => undefined
            },
            "redhat" => {
                "fixed-source-port" => false,
                "host" => "my.smtp.server.com",
                "port" => 25,
                "source-interface" => undefined,
                "source-port" => undefined
            }
        },
...

10. Import this EAP instance and platform to the inventory of the JBoss ON Server (installed on server1);
10. In JBoss ON UI navigate to the RHQ Server resource -> mail -> Mail Sessions -> java:jboss/mail/Default -> smtp -> Configuration and check Outbound Socket Binding Ref.


Actual results:
Outbound Socket Binding Ref will show two radio buttons and two values (first one originally configured and the second one that is configured in the EAP instance installed on the server2)

Expected results:
Outbound Socket Binding Ref shows only one value - the one that was originally configured.


Additional info:
If, for some reason, second (incorrect) option is selected, configuration saved and JBoss ON server restarted, during server restart it will throw the following Exception: 

***********************************************************************
15:11:37,704 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.outbound-socket-binding.redhat (missing) dependents: [service jboss.mail-session.java:jboss/mail/Default] 

15:11:37,920 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:6990/management
15:11:37,920 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
15:11:37,921 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started (with errors) in 39016ms - Started 4934 of 5045 services (1 services failed or missing dependencies, 104 services are passive or on-demand)
***********************************************************************
and JBoss ON Server will not be able to send emails any more. 

However, if we revert back to the original setting, the JBoss ON Server will be correctly started and emails will be properly sent.