This content has been marked as final.
Show 4 replies
-
1. Re: ServiceBindingManager and 4.2.0CR1
brian.stansberry Apr 1, 2007 10:02 PM (in response to alpheratz-jb)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.
-
2. Re: ServiceBindingManager and 4.2.0CR1
jerrygauth Apr 2, 2007 9:21 AM (in response to alpheratz-jb)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.
-
3. Re: ServiceBindingManager and 4.2.0CR1
brian.stansberry Apr 2, 2007 9:31 AM (in response to alpheratz-jb)OK, I'll file a JIRA and fix it. Thanks, alpheratz-jb, for the report, and you too, Jerry.
-
4. Re: ServiceBindingManager and 4.2.0CR1
brian.stansberry Apr 2, 2007 9:44 AM (in response to alpheratz-jb)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.