10:08 a.m.
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: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Ivo Studensky
Assignee: Jonathan Halliday
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
10:12 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-3024:
-------------------------------
Assignee: Brian Stansberry (was: Jonathan Halliday)
Component/s: Domain Management
(was: Transactions)
Changing the component.
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: Brian Stansberry
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
10:32 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3024:
---------------------------------------
I really know nothing about this XTS config. Is the only thing needed to make a config
"xts" the addition of the extension and subsystem a la the patch above?
If so I question the point of standalone-xts.xml at all; it's just a file that will
inevitably fall out of sync or require a lot of work to keep in sync, all for the sake of
something that could be trivially explained in some docs.
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: Brian Stansberry
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
10:44 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-3024:
------------------------------------
Brian, could you assign this jira to someone who manage the standalone-xts.xml please? I
had a hard time even to decide which component it should be assigned to. I don't know
why the standalone-xts.xml has been created, but as long as it exists I am trying to use
it my XTS tests as it seems that no one else test it.
Thanks.
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: Brian Stansberry
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
10:44 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky edited comment on AS7-3024 at 12/14/11 11:43 AM:
---------------------------------------------------------------
Brian, could you assign this jira to someone who manage the standalone-xts.xml please? I
had a hard time even to decide which component it should be assigned to. I don't know
why the standalone-xts.xml has been created, but as long as it exists I am trying to use
it in my XTS tests as it seems that no one else test it.
Thanks.
was (Author: istudens):
Brian, could you assign this jira to someone who manage the standalone-xts.xml please?
I had a hard time even to decide which component it should be assigned to. I don't
know why the standalone-xts.xml has been created, but as long as it exists I am trying to
use it my XTS tests as it seems that no one else test it.
Thanks.
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: Brian Stansberry
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
10:46 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky edited comment on AS7-3024 at 12/14/11 11:44 AM:
---------------------------------------------------------------
Brian, could you assign this jira to someone who manage the standalone-xts.xml please? I
had a hard time even to decide which component it should be assigned to. I don't know
why the standalone-xts.xml has been created, but as long as it exists I am trying to use
it in my XTS tests as it seems that no one else uses it.
Thanks.
was (Author: istudens):
Brian, could you assign this jira to someone who manage the standalone-xts.xml please?
I had a hard time even to decide which component it should be assigned to. I don't
know why the standalone-xts.xml has been created, but as long as it exists I am trying to
use it in my XTS tests as it seems that no one else test it.
Thanks.
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: Brian Stansberry
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
1:09 p.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-3024:
-------------------------------------
Assignee: Andrew Dinn (was: Brian Stansberry)
Andrew, can you comment on this?
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
3:12 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
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
3:14 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn reassigned AS7-3024:
--------------------------------
Assignee: Paul Robinson (was: Andrew Dinn)
See previous comment
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
11:03 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
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
8:52 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
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
8:57 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3024:
---------------------------------------
For CR1, can we you manually update the file?
For 7.2 I hope we have some time to devote to tooling related to creating configurations.
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
9:47 p.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3024:
------------------------------
Fix Version/s: 7.1.0.Final
(was: 7.1.0.CR1)
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.Final
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
8:26 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on AS7-3024:
------------------------------------
Brian,
I think updating the file should be acceptable for an interim solution. However, I'd
prefer it if it didn't turn into something that ended up living on forever. How
confident are you that the improved tooling will be available in 7.2?
Ivo,
From a QE point of view, do you think you could update your tests to
edit the standalone.xml? You just need to add ~4 lines in the right place.
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.Final
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
9:39 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-3024:
------------------------------------
Yes, I think the QE tests can live with the editing of the standard standalone.xml file.
Similar approach is already in place for JTS configuration, see
testsuite/integration/src/test/xslt/enableJTS.xsl in AS7.
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.Final
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
2:43 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-3024:
------------------------------------
Paul, the issue has been hit again by my pull request for XTS tests, see [1].
Please, could you fix it?
[1] https://github.com/jbossas/jboss-as/pull/1231
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.Final
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
4:34 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on AS7-3024:
------------------------------------
Pull request created for this fix: https://github.com/jbossas/jboss-as/pull/1296
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.Final
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
9:34 a.m.
[
https://issues.jboss.org/browse/AS7-3024?page=com.atlassian.jira.plugin.s...
]
Paul Robinson resolved AS7-3024.
--------------------------------
Resolution: Done
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.Final
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
4632
days inactive
4681
days old
17 comments
12 participants
participants (12)
-
Andrew Dinn (Assigned) (JIRA) -
Andrew Dinn (Commented) (JIRA)
-
Brian Stansberry (Assigned) (JIRA)
-
Brian Stansberry (Commented) (JIRA)
-
Ivo Studensky (Commented) (JIRA)
-
Ivo Studensky (Created) (JIRA)
-
Ivo Studensky (Issue Comment Edited) (JIRA)
-
Ivo Studensky (JIRA)
-
Ivo Studensky (Updated) (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Paul Robinson (Commented) (JIRA)
-
Paul Robinson (JIRA)