Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
None
Description
To reproduce:
1. Update to latest AS7 master
2. mvn install
3. cd build/target/jboss-as-7.1.0.CR1-SNAPSHOT/
4. sh bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml
Observe the following stack trace towards the top of the log:
09:49:07,967 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.messaging.default: org.jboss.msc.service.StartException in service jboss.messaging.default: JBAS011644: Failed to start service at org.jboss.as.messaging.HornetQService.start(HornetQService.java:193) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS011641: Failed to find SocketBinding for connector: netty at org.jboss.as.messaging.HornetQService.start(HornetQService.java:128) ... 5 more
I have attached the boot log.
This error does not appear when using standalone.xml configuration. Problems like this have occurred in the past when a change to standalone.xml has not also been made to standalone-xts.xml.
I have checked all the standalone-*.xml configurations in docs/examples/configs/ and this bug only occurs in standalone-xts.xml.
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
