ServiceBindingManager and 4.2.0CR1

[alpheratz-jb]

I tried setting up ServiceBindingManager according to the wiki:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfiguringMultipleJBossInstancesOnOneMachine

I find that when I start up the FIRST instance, I get an error telling me that port 4446 is already in use.

The wiki says:

AS 4.0.2 has a known bug : one of the ports (4446) is not included in the sample-bindings.xml file and therefore will continue to conflict even after selecting an alternate port configuration in your jboss-service.xml. To fix this simply select an alternate port (something other than 4446 that is not being used) in cluster-service.xml configuration (obviously not necessary if you are not using the ALL configuration with clustering support). This bug is being fixed in our next release.

I came across this on a pristine box which had never seen another version of JBoss.

Apologies, don't have the log file with me now (posting from home, not work); have probably already lost the file...

Just thought someone might like to know...

Cheers,

Alph

[brian.stansberry]

If you get a port conflict when you only have one JBoss instance running, the conflict is with some other software running on your system. Use netstat to find what it is.

[jerrygauth]

Brian - this report appears to be correct. If you start a single instance of JBoss 4.2 using the sample bindings, there's a conflict on port 4446. A quick examination of the default bindings file shows that port 4446 is specified in two different bindings for ports-default.

[brian.stansberry]

OK, I'll file a JIRA and fix it. Thanks, alpheratz-jb, for the report, and you too, Jerry.

[brian.stansberry]

JIRA is http://jira.jboss.com/jira/browse/JBAS-4284. alpheratz-jb, the JIRA has a workaround description that shows you how to fix the issue for 4.2.0.CR1.