[jboss-jira] [JBoss JIRA] Closed: (JBAS-5856) SBM-compatible JBM remoting connector config

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry closed JBAS-5856.
----------------------------------

    Resolution: Done


SVN is fighting with me about removing the testsuite/src/resources/test-configs/binding-mangerX dirs, but anyway they are empty.  So I'm going ahead and closing this; the new JBM file works with the SBM.

> SBM-compatible JBM remoting connector config
> --------------------------------------------
>
>                 Key: JBAS-5856
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5856
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>            Assignee: Clebert Suconic
>            Priority: Blocker
>             Fix For: JBossAS-5.0.0.GA
>
>         Attachments: remoting-bisocket-jboss-beans.xml
>
>
> Need an altered remoting connector config file that can support using different binding ports per AS instance if multiple instances run on the same machine and don't bind to different addresses. Per discussion on the forum thread, approach will be to have the port defined by a system property, with the a ServiceBindingManager component setting the system property.  The SBM component is ready to go, so just need the file.
> https://svn.jboss.org/repos/jbossas/trunk/testsuite/src/resources/test-configs/binding-manager1/deploy/messaging/remoting-bisocket-service.xml is an example of what such a file would look like. I'm using that now to test SBM functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira