[jboss-jira] [JBoss JIRA] Updated: (JBAS-5856) SBM-compatible JBM remoting connector config
[
https://jira.jboss.org/jira/browse/JBAS-5856?page=com.atlassian.jira.plug...
]
Ron Sigal updated JBAS-5856:
----------------------------
Attachment: remoting-bisocket-jboss-beans.xml
I've attached a copy of remoting-bisocket-jboss-beans.xml. AS 5 starts up fine when I
run it with this file instead of remoting-bisocket-service.xml.
Notes.
1. It's a lot of editing. It may be worth looking it over for anything I missed
(though I've checked it several times).
2. I deleted "numberOfRetries", which is no longer used.
3. I removed "socket.check_connection", which defaults to false.
I'm working on a remoting-sslbisocket-jboss-beans.xml.
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-co...
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