[jboss-jira] [JBoss JIRA] (AS7-3024) AS7 cannot startup with standalone-xts.xml configuration file
Paul Robinson (Commented) (JIRA)
jira-events at lists.jboss.org
Fri Dec 16 09:52:09 EST 2011
[ https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651624#comment-12651624 ]
Paul Robinson commented on AS7-3024:
------------------------------------
Sorry for getting involved late, I didn't notice this particular issue until it was assigned to me. I actually reported this same bug earlier today. I'll go and close it as a duplicate.
As Andrew states the XTS subsystem config may look simple at the moment, but we do have plans to extend it in the future. So having the user build there own based on standalone.xml, isn't going to be a particularly usable option.
I should point out that the primary usage of this configuration is for users who want to use Web service transactions (WS-AT and WS-BA). Yes we do use it in tests, but that is because we are testing WS-AT and WS-BA functionality. Hence we can't cut the file down as we don't know what our users' applications will use. For example they could quite reasonably expect to use OSGi and/or JMS.
I do agree that something needs to be done as what we have at the moment is very brittle. I think this file has become out of sync about 3 or 4 times that I can remember.
Andrew is correct, we do have XTS CI with AS7. This should prove indispensable as we have had many cases in the past where changes to JBossWS has broken XTS.
I think the next step is to find a solution to this problem. Here's a few off the top of my head:
1. We include the XTS subsystem in standalone.xml. As XTS takes a long time to boot (due to essential WS endpoint generation), the service will need to be disabled by default. The problem comes in how we mark it as disabled and how we enable it. Does AS7 provide a mechanism for enabling and disabling subsystems? If it doesn't we could add a property to the XTS subsystem configuration that states whether it is enabled. On boot the XTS subsystem reads this property and decides whether to actually start or not. The user/test would need to edit the standalone.xml before booting the AS, which may or may not be a problem.
2. Is there a way of extending configurations? This way the standalone-xts.xml would just contain the XTS subsytem and extend standalone.xml for the remainder of the config.
3. Is there a way of specifying two configurations? This way the standalone-xts.xml would just contain the XTS subsytem and standalone.xml would contain the remainder of the config.
4. I can think of many other "hacks" that would allow the XTS subsystem to be enabled or disabled via the command line. For example, environment variable, java opts, etc etc. These all seem pretty nasty. Maybe someone can come up with a nice way to do this?
Does anyone have any other ideas?
> 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
More information about the jboss-jira
mailing list