From your boot log:
21:04:38,785 DEBUG [ServerInfo] jboss.service.binding.set: true
21:04:38,785 DEBUG [ServerInfo] program.name: ports-01
So it was trying to read the binding set "true" rather than "ports-01".
Hence you got the error message "NoSuchBindingException: No binding tcp_sync-bind_port found for service JGroups in set true"
Looks like you're not starting up with correct command, check your startup command / script and make sure the path / parameters are all set correctly, especially on windows sometimes you got double quotes " " / single quotes ' ' missing / not paired correctly and it's difficult to point out.
Tested on my laptop and same line from boot.log :
15:29:55,538 DEBUG [ServerInfo] jboss.service.binding.set: ports-01
15:29:55,538 DEBUG [ServerInfo] program.name: run.sh
BTW it is JBoss EAP 5.2.0 / JDK 6 you're using, quite old already, and there is no more bug fixes / security enhancements on these, recommend you to upgrade to latest EAP 6.x (6.4 just released) with JDK 7/8.
Thanks for your reply.
I also tested in JDK 7 + Win 7,the error is same.
My entire startup command is "run.bat -Djboss.service.binding.set=ports-01",and I didn't use any double quote or slash or back slash in startup command .
There isn't any problem in EAP 5.1.x with same command.
How to change the setting about "jboss.service.binding.set: true"? I'm using the default setting of bindings-jboss-beans.xml.
The end, I'll test in linux later.
Probably try specify this in "run.conf.bat" and try again with a new vanilla installation...?
I tested in RHEL 6 + OracleJDK 7.
There is no problem with the same startup command,and the same default setting file.
I guess that it is EAP 5.2.0's issue in Windows.
And I could reproduce it in two Win7 machines.
Could you help me to verify my reporting just using all default setting with command "run.bat -Djboss.service.binding.set=ports-01"?
Thanks in advance.
Trying on my win7+Oracle JDK 7
If I use "run.bat -Djboss.service.binding.set=ports-01" I get the same results as you did.
But if I setup this in "run.conf.bat", and then use "run.bat" to launch, it can be set correctly.
Thanks for your helpful test.
It can work as you mentioned work-around.
Could you tell me the root reason of this problem?
Since the same startup without errors in EAP 5.1.x,but can't startup in EAP 5.2.0,should we raise this a bug for EAP 5.2.0?
I know EAP 5.x is still in the phase of maintenance support,and EAP 5.2.0 is the latest version of EAP 5.x.
Thanks for your rely.
I haven't the account to access Redhat Customer Portal,so I post this issue to this forum.
I just want to remind a problem that I had,if someone have the same problem,I hope this thread could be a help.