[jboss-jira] [JBoss JIRA] (AS7-3024) AS7 cannot startup with standalone-xts.xml configuration file

[Brian Stansberry (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651357#comment-12651357 ] 

Brian Stansberry commented on AS7-3024:
---------------------------------------

Thanks, Andrew.

One suggestion I have is to strip this xts config file down as much as is reasonable.  That is, exclude subsystems that are unnecessary for what is being illustrated and tested. That reduces the list of things that can fall out of sync. For example, if osgi and messaging aren't needed, remove them.

Also, if the primary usage of this file is for testing but it's not really a good illustration for users, it should probably live in the testsuite and not in the distribution. Until it is considered to be a good example.
                
> AS7 cannot startup with standalone-xts.xml configuration file
> -------------------------------------------------------------
>
>                 Key: AS7-3024
>                 URL: https://issues.jboss.org/browse/AS7-3024
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.0.Beta1b
>            Reporter: Ivo Studensky
>            Assignee: Paul Robinson
>             Fix For: 7.1.0.CR1
>
>
> The docs/examples/configs/standalone-xts.xml seems to be out of date as AS7 fails to start with it.
> See the output snippet:
> {noformat}
> $ sh standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml
> .
> .
> 16:43:10,393 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
>         at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
> 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
> 16:43:10,438 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) null null
> .
> .
> 16:43:14,643 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" started (with errors) in 5839ms - Started 146 of 220 services (7 services failed or missing dependencies, 66 services are passive or on-demand)
> {noformat}
> The problem seems to really be in the outdated standalone-xts.xml file and not in JBossXTS itself since it works correctly when the following patch is applied to standalone-full.xml:
> {noformat}
> --- a/standalone-full.xml
> +++ b/standalone-full.xml
> @@ -29,6 +29,7 @@
>          <extension module="org.jboss.as.web"/>
>          <extension module="org.jboss.as.webservices"/>
>          <extension module="org.jboss.as.weld"/>
> +        <extension module="org.jboss.as.xts"/>
>      </extensions>
>  
>      <management>
> @@ -384,6 +385,9 @@
>              </endpoint-config>
>          </subsystem>
>          <subsystem xmlns="urn:jboss:domain:weld:1.0"/>
> +        <subsystem xmlns="urn:jboss:domain:xts:1.0">
> +            <xts-environment url="http://localhost:8080/ws-c11/ActivationService"/>
> +        </subsystem>
>      </profile>
>  
>      <interfaces>
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira