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

[Andrew Dinn (Commented) (JIRA)]

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

Andrew Dinn commented on AS7-3024:
----------------------------------

I can comment although the person you really need to speak to is Paul Robinson who has taken over responsibility for XTS (I am now in the Java team).

The history here is that I integrated XTS into AS7 back in August, adding the relevant config to standalone.xml -- with just one optional config element at that point (although this also meant I had to add the JBossWS config which was also optional in the base config). Jason relocated the config for these two extensions into standalone-xts.xml in order to avoid any issues passing the Web Profile TCK. Your prognosis is not just correct it is also a post-gnosis -- this is the second occasion (that I know of) where changes required to standalone.xml have not been propagated to standalone-xts.xml.

You are correct to assume that the XTS extension is optional and is indeed best left excluded from normal startup until it is wanted. However, the resolution is not quite so simple as just deleting the file and documenting the required config changes.

Firstly, the config needs to be more complex than at present. The reason for the minimal config at the time of integration were twofold: there was no time to expose the limited amount of wholly internal config; and JBossWeb/JBossWS were not exposing the info (binding and web ports) necessary to allow externally dependent config options to be exposed. So, the eventual config when we get to EAP will not be trivial,. A version of standalone-xts.xml containing a tested, working config would be a very helpful addition to the final release for those customers who want to use XTS.

Secondly, the main point of having a config with the XTS stuff included is to ensure that other dev teams can easily (preferably, automatically) test the XTS extension when they change the AS. I believe Paul/Ivo are working on (or maybe have completed) extensions to the standard smoke tests which do this. I doubt that many other devs are aware of the need to run these tests so we have to get to the point where they run them automatically. Deleting this file may well cause problems for those tests. Paul might have more to say on the subject. I will reassign the JIRA for him to follow up.

                
> 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: Andrew Dinn
>             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