[JBoss JIRA] (AS7-3694) Allow management client to associate metadata with DeploymentUnit
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-3694?page=com.atlassian.jira.plugin.s... ]
SBS JIRA Integration updated AS7-3694:
--------------------------------------
Forum Reference: https://community.jboss.org/message/782610#782610
> Allow management client to associate metadata with DeploymentUnit
> -----------------------------------------------------------------
>
> Key: AS7-3694
> URL: https://issues.jboss.org/browse/AS7-3694
> Project: Application Server 7
> Issue Type: Feature Request
> Components: OSGi, Server
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.2.0.CR1
>
>
> Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU.
> As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically
> Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit
> For an OSGi deployment it would be necessary to be able to define that start behaviour and the start level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler closed AS7-6234.
-------------------------------
Assignee: Thomas Diesler (was: Jean-Frederic Clere)
Fix Version/s: (was: 7.2.0.CR1)
Resolution: Rejected
Thanks. Rejecting - seems to be a spring issue
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, server.springapp.log, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-1.0.0-BUILD-SNAPSHOT-no-manifest-works.war, spring-app-source-codes.zip
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBWEB-257) Filter.destroy() exceptions break application undeployment
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/JBWEB-257?page=com.atlassian.jira.plugin.... ]
Jean-Frederic Clere commented on JBWEB-257:
-------------------------------------------
r2129 is the fix for trunk.
> Filter.destroy() exceptions break application undeployment
> ----------------------------------------------------------
>
> Key: JBWEB-257
> URL: https://issues.jboss.org/browse/JBWEB-257
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-2.1.12.GA
> Environment: -JBoss Enterprise Application Platform (EAP) 5.1.2 and earlier
> Reporter: Aaron Ogburn
> Assignee: Remy Maucherat
> Attachments: destroy-linkage-error.war
>
>
> JBoss does not handle any exceptions from custom Filter.destroy() implementations. This is passed on to the JBoss container and disrupts the
> undeployment so the app is not successfully undeployed.
> That causes a potentially critical issue as the application is no longer deployed at that point, but it can't be redeployed due to conflicts with the prior incomplete undeployment. The server has to be restarted to be able to deploy the application again.
> The broken undeployment could be fixed at the container level if org.apache.catalina.core.ApplicationFilterConfig.release() caught exceptions thrown by Filter.destroy()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6238) Deadlock in Module FallbackClassLoader
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6238?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-6238:
-------------------------------------
Should be fixed in jbosgi-framework-2.1.0.CR9
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
> Key: AS7-6238
> URL: https://issues.jboss.org/browse/AS7-6238
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Steve Reed
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.2.0.Alpha1
>
> Attachments: jboss-dead-lock.txt, ThreadDump-2.txt
>
>
> Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar
> Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8...
> During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started.
> The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible.
> I will attach the thread dump to this issue as supporting evidence.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6238) Deadlock in Module FallbackClassLoader
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6238?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler moved JBOSGI-623 to AS7-6238:
--------------------------------------------
Project: Application Server 7 (was: JBoss OSGi)
Key: AS7-6238 (was: JBOSGI-623)
Workflow: GIT Pull Request workflow (was: jira)
Component/s: OSGi
(was: Core Framework)
Security: (was: Public)
Fix Version/s: 7.2.0.Alpha1
(was: JBossOSGi 1.2.0)
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
> Key: AS7-6238
> URL: https://issues.jboss.org/browse/AS7-6238
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Steve Reed
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.2.0.Alpha1
>
> Attachments: jboss-dead-lock.txt, ThreadDump-2.txt
>
>
> Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar
> Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8...
> During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started.
> The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible.
> I will attach the thread dump to this issue as supporting evidence.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6234:
----------------------------------------
I think I found the fix for this, or a workaround. For Spring web app to be deployed as OSGi bundle, it seems you need to supply the dispatcher servlet with a context class, telling it where to find bundlecontext:
<servlet>
<servlet-name>appServlet</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<init-param>
<param-name>contextClass</param-name>
<param-value>org.springframework.osgi.web.context.support.OsgiBundleXmlWebApplicationContext</param-value>
</init-param>
</servlet>
with this supplied, it answers to requests just fine. Without it, HTTP requests go unanswered (I don't know where?).
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Jean-Frederic Clere
> Fix For: 7.2.0.CR1
>
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, server.springapp.log, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-1.0.0-BUILD-SNAPSHOT-no-manifest-works.war, spring-app-source-codes.zip
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JASSIST-162) Correction introduced in JASSIST-127 raises AbstractMethodError on call site
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JASSIST-162?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on JASSIST-162:
--------------------------------------
Donnchadh also reported the https://hibernate.onjira.com/browse/HHH-7884 issue which appears to depend on JASSIST-162 being fixed.
> Correction introduced in JASSIST-127 raises AbstractMethodError on call site
> ----------------------------------------------------------------------------
>
> Key: JASSIST-162
> URL: https://issues.jboss.org/browse/JASSIST-162
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.16.1-GA
> Environment: OSX, JDK 1.6.0_29
> Reporter: Brice Dutheil
> Assignee: Shigeru Chiba
> Attachments: JASSIST-162___correct_patch_for_bridge_methods_and_covariant_return_types.patch
>
>
> The proposed solution in JASSIST-127 doesn't work, the JVM raises an {{AbstractMethodError}} on the call site.
> What happen is that in {{getMethods}} the code now discard method with same name / same arguments as the return type is not taken into account when generating the key.
> Reverting this patch will raises a {{DuplicateMemberException}}, the reason is that {{ClassFile.isDuplicated}} don't see either of the possible duplicate method as bridge.
> I've created a patch that detect methods with covariant type and mark forwarding methods as bridge if relevant.
> Note that the effect is only for method calls that have the very same arguments, as Javassist don't see duplicate methods if the arguments differ, e.g. proxying ({{StringList extends List<String>}}) will see {{add(Object)}} and {{add(String)}}, though the first one is not marked as bridge in the generated bytecode.
> Also, I'm not sure of that one, but the patch also adds a boolean to enable the {{MethodHandler}} to intercept bridge methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5127) Performance bottleneck on Javassist
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-5127?page=com.atlassian.jira.plugin.s... ]
Scott Marlow commented on AS7-5127:
-----------------------------------
HHH-7884 seems to be a regression with the newer Javassist release.
> Performance bottleneck on Javassist
> -----------------------------------
>
> Key: AS7-5127
> URL: https://issues.jboss.org/browse/AS7-5127
> Project: Application Server 7
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 7.1.2.Final (EAP)
> Environment: Sun/Oracle JDK 1.6_32, Linux 64b
> Reporter: Alessandro Lazarotti
> Assignee: Scott Marlow
> Fix For: 7.2.0.Alpha1
>
>
> The method javassist.util.proxy.RuntimeSupport.find2methods has a synch block, called indirectly by ProxyFactory.createClass(). It is a strong bottleneck for frameworks as Hibernate which can use it several times in a large set of data.
> Javassist 3.17.0-GA fixes it. AS7 should update its current javassist version.
> More details in https://issues.jboss.org/browse/JASSIST-163
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5306) DomainControllerMigrationTestCase.testDCFailover intermittently fails
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-5306?page=com.atlassian.jira.plugin.s... ]
Kabir Khan closed AS7-5306.
---------------------------
Resolution: Done
ok :-)
> DomainControllerMigrationTestCase.testDCFailover intermittently fails
> ---------------------------------------------------------------------
>
> Key: AS7-5306
> URL: https://issues.jboss.org/browse/AS7-5306
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Kabir Khan
> Assignee: Bartosz Baranowski
> Priority: Critical
> Fix For: 7.2.0.Alpha1
>
>
> Stacktrace
> {code}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:48)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertTrue(Assert.java:27)
> at org.jboss.as.test.integration.domain.DomainControllerMigrationTestCase.testDCFailover(DomainControllerMigrationTestCase.java:209)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Standard Output
> /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/test-classes/domain-configs/domain-standard.xml
> /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/test-classes/host-configs/host-failover1.xml
> 04:02:08,268 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> 04:02:08,383 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 04:02:08,866 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> [Host Controller] 04:02:09,068 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> [Host Controller] 04:02:09,139 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Host Controller] 04:02:09,998 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.5.GA
> [Host Controller] 04:02:10,006 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.5.GA
> [Host Controller] 04:02:10,016 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.8.GA
> [Host Controller] 04:02:10,071 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (public) port (9990) securePort (-1)
> [Host Controller] 04:02:10,236 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on [::1]:9999
> [Host Controller] 04:02:10,869 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,432 WARN [org.jboss.as.jmx] (Controller Boot Thread) JBAS011305: <jmx-connector/> is no longer supporting. <remoting-connector/> should be used instead to allow remote connections via JBoss Remoting.
> [Host Controller] 04:02:11,493 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,504 WARN [org.jboss.as.jmx] (Controller Boot Thread) JBAS011305: <jmx-connector/> is no longer supporting. <remoting-connector/> should be used instead to allow remote connections via JBoss Remoting.
> [Host Controller] 04:02:11,506 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,507 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,509 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,510 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,511 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:11,513 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:12,204 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server failover-one
> 04:02:12,264 INFO [org.jboss.as.process.Server:failover-one.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:failover-one'
> [Host Controller] 04:02:12,364 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://::1:9990/management
> [Host Controller] 04:02:12,366 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://::1:9990
> [Host Controller] 04:02:12,367 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" (Host Controller) started in 3882ms - Started 11 of 11 services (0 services are passive or on-demand)
> [Server:failover-one] 04:02:13,073 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> [Server:failover-one] 04:02:13,405 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> [Server:failover-one] 04:02:13,505 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Server:failover-one] 04:02:13,625 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.5.GA
> [Server:failover-one] 04:02:13,637 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.5.GA
> [Server:failover-one] 04:02:13,664 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.8.GA
> [Host Controller] 04:02:15,369 INFO [org.jboss.as.domain.controller.mgmt] (proxy-threads - 1) JBAS010920: Server [Server:failover-one] registered using connection [Channel ID 46504c6e (inbound) of Remoting connection 0b412c18 to /0:0:0:0:0:0:0:1:52549]
> [Server:failover-one] 04:02:15,387 INFO [org.jboss.as.logging] (MSC service thread 1-1) JBAS011502: Removing bootstrap log handlers
> [Server:failover-one] 04:02:15,402 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 29) JBAS015537: Activating WebServices Extension
> [Server:failover-one] 04:02:15,413 INFO [org.jboss.as.modcluster] (ServerService Thread Pool -- 28) JBAS011704: Mod_cluster uses default load balancer provider
> [Server:failover-one] 04:02:15,459 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> [Server:failover-one] 04:02:15,551 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
> [Server:failover-one] 04:02:15,557 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 46) JBAS010260: Activating JGroups subsystem.
> [Server:failover-one] 04:02:15,559 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 44) JBAS011800: Activating Naming Subsystem
> [Server:failover-one] 04:02:15,649 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.9.Final
> [Server:failover-one] 04:02:15,653 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) JBAS010280: Activating Infinispan subsystem.
> [Server:failover-one] 04:02:15,689 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)
> [Server:failover-one] 04:02:15,907 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
> [Server:failover-one] 04:02:15,948 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
> [Server:failover-one] 04:02:16,037 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
> [Server:failover-one] 04:02:16,150 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
> [Server:failover-one] 04:02:16,870 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032010: JBossTS Recovery Service (tag: JBOSSTS_4_16_4_Final) - JBoss Inc.
> [Server:failover-one] 04:02:16,975 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012324: Start RecoveryActivators
> [Server:failover-one] 04:02:17,040 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [Server:failover-one] 04:02:17,052 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [Server:failover-one] 04:02:17,256 INFO [org.apache.coyote.ajp.AjpAprProtocol] (MSC service thread 1-4) Starting Coyote AJP/1.3 on ajp-localhost/0:0:0:0:0:0:0:1%1:8009
> [Server:failover-one] 04:02:17,288 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost/0:0:0:0:0:0:0:1%1:8080
> [Server:failover-one] 04:02:17,272 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012296: ExpiredEntryMonitor running at Sat, 4 Aug 2012 04:02:17
> [Server:failover-one] 04:02:17,472 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover1/servers/failover-one/data/messagingjournal,bindingsDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover1/servers/failover-one/data/messagingbindings,largeMessagesDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover1/servers/failover-one/data/messaginglargemessages,pagingDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover1/servers/failover-one/data/messagingpaging)
> [Server:failover-one] 04:02:17,483 INFO [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 54) Initializing mod_cluster 1.2.1.Final
> [Server:failover-one] 04:02:17,523 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (ServerService Thread Pool -- 54) Listening to proxy advertisements on 224.0.1.105:23,364
> [Server:failover-one] 04:02:17,685 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c 0:0:0:0:0:0:0:1%1:5445 for CORE protocol
> [Server:failover-one] 04:02:17,706 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c 0:0:0:0:0:0:0:1%1:5455 for CORE protocol
> [Server:failover-one] 04:02:17,721 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012343: RecoveryManagerImple is ready. Socket listener is turned off.
> [Server:failover-one] 04:02:17,725 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) Server is now live
> [Server:failover-one] 04:02:17,730 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032013: Starting transaction recovery manager
> [Server:failover-one] 04:02:17,730 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.2.18.Final (HQ_2_2_18_FINAL, 122) [b585cf0b-de0a-11e1-839e-7305fde0f34e]) started
> [Server:failover-one] 04:02:17,938 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA032017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_16_4_Final) - JBoss Inc.
> [Server:failover-one] 04:02:17,955 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
> [Server:failover-one] 04:02:17,962 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 57) trying to deploy queue jms.topic.testTopic
> [Server:failover-one] 04:02:18,164 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> [Server:failover-one] 04:02:18,210 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-5) JBAS010406: Registered connection factory java:/JmsXA
> [Server:failover-one] 04:02:18,203 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/topic/test
> [Server:failover-one] 04:02:18,226 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 56) trying to deploy queue jms.queue.testQueue
> [Server:failover-one] 04:02:18,259 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/queue/test
> [Server:failover-one] 04:02:18,261 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
> [Server:failover-one] 04:02:18,302 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-5) HornetQ resource adaptor started
> [Server:failover-one] 04:02:18,303 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-5) IJ020002: Deployed: file://RaActivatorhornetq-ra
> [Server:failover-one] 04:02:18,309 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
> [Server:failover-one] 04:02:18,764 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> [Server:failover-one] JBAS014775: New missing/unsatisfied dependencies:
> [Server:failover-one] service jboss.server.controller.management.security_realm.ApplicationRealm (missing) dependents: [service jboss.remoting.authentication_provider.remoting-connector]
> [Server:failover-one]
> [Server:failover-one] 04:02:18,779 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started (with errors) in 6253ms - Started 138 of 221 services (4 services failed or missing dependencies, 78 services are passive or on-demand)
> [Host Controller] 04:02:18,792 INFO [org.jboss.as.host.controller] (proxy-threads - 1) JBAS010919: Registering server failover-one
> /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/test-classes/domain-configs/domain-standard.xml
> /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/test-classes/host-configs/host-failover2.xml
> 04:02:19,715 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> 04:02:19,835 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 04:02:20,446 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> [Host Controller] 04:02:20,653 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> [Host Controller] 04:02:20,803 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Host Controller] 04:02:22,015 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (public) port (9980) securePort (-1)
> [Host Controller] 04:02:22,015 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.5.GA
> [Host Controller] 04:02:22,059 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.5.GA
> [Host Controller] 04:02:22,102 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.8.GA
> [Host Controller] 04:02:22,319 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on [fccc::2]:9989
> [Host Controller] 04:02:24,415 INFO [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "failover2", JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> [Host Controller] 04:02:24,662 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server failover-two
> 04:02:24,724 INFO [org.jboss.as.process.Server:failover-two.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:failover-two'
> [Host Controller] 04:02:24,734 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://fccc::2:9980/management
> [Host Controller] 04:02:24,736 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
> [Host Controller] 04:02:24,737 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" (Host Controller) started in 4798ms - Started 11 of 11 services (0 services are passive or on-demand)
> [Server:failover-two] 04:02:25,479 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> [Server:failover-two] 04:02:25,808 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> [Server:failover-two] 04:02:26,014 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Server:failover-two] 04:02:26,324 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.5.GA
> [Server:failover-two] 04:02:26,355 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.5.GA
> [Server:failover-two] 04:02:26,386 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.8.GA
> [Host Controller] 04:02:27,913 INFO [org.jboss.as.domain.controller.mgmt] (proxy-threads - 1) JBAS010920: Server [Server:failover-two] registered using connection [Channel ID 28a61589 (inbound) of Remoting connection 21044daf to /fccc:0:0:0:0:0:0:2:54201]
> [Server:failover-two] 04:02:27,971 INFO [org.jboss.as.logging] (MSC service thread 1-5) JBAS011502: Removing bootstrap log handlers
> [Server:failover-two] 04:02:27,986 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 29) JBAS015537: Activating WebServices Extension
> [Server:failover-two] 04:02:27,990 INFO [org.jboss.as.modcluster] (ServerService Thread Pool -- 28) JBAS011704: Mod_cluster uses default load balancer provider
> [Server:failover-two] 04:02:28,060 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> [Server:failover-two] 04:02:28,066 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 44) JBAS011800: Activating Naming Subsystem
> [Server:failover-two] 04:02:28,101 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
> [Server:failover-two] 04:02:28,125 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 46) JBAS010260: Activating JGroups subsystem.
> [Server:failover-two] 04:02:28,142 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)
> [Server:failover-two] 04:02:28,148 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) JBAS010280: Activating Infinispan subsystem.
> [Server:failover-two] 04:02:28,161 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.9.Final
> [Server:failover-two] 04:02:28,275 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
> [Server:failover-two] 04:02:28,329 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
> [Server:failover-two] 04:02:28,452 INFO [org.jboss.jaxr] (MSC service thread 1-4) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
> [Server:failover-two] 04:02:28,567 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
> [Server:failover-two] 04:02:29,090 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-/fccc:0:0:0:0:0:0:2%1:8430
> [Server:failover-two] 04:02:29,114 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [Server:failover-two] 04:02:29,120 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [Server:failover-two] 04:02:29,105 INFO [org.apache.coyote.ajp.AjpAprProtocol] (MSC service thread 1-6) Starting Coyote AJP/1.3 on ajp-/fccc:0:0:0:0:0:0:2%1:8359
> [Server:failover-two] 04:02:29,261 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032010: JBossTS Recovery Service (tag: JBOSSTS_4_16_4_Final) - JBoss Inc.
> [Server:failover-two] 04:02:29,317 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover2/servers/failover-two/data/messagingjournal,bindingsDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover2/servers/failover-two/data/messagingbindings,largeMessagesDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover2/servers/failover-two/data/messaginglargemessages,pagingDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover2/servers/failover-two/data/messagingpaging)
> [Server:failover-two] 04:02:29,318 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012324: Start RecoveryActivators
> [Server:failover-two] 04:02:29,380 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012296: ExpiredEntryMonitor running at Sat, 4 Aug 2012 04:02:29
> [Server:failover-two] 04:02:29,512 INFO [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 54) Initializing mod_cluster 1.2.1.Final
> [Server:failover-two] 04:02:29,587 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012343: RecoveryManagerImple is ready. Socket listener is turned off.
> [Server:failover-two] 04:02:29,589 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032013: Starting transaction recovery manager
> [Server:failover-two] 04:02:29,607 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (ServerService Thread Pool -- 54) Listening to proxy advertisements on 224.0.1.105:23,364
> [Server:failover-two] 04:02:29,821 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-5) ARJUNA032017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_16_4_Final) - JBoss Inc.
> [Server:failover-two] 04:02:29,941 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c fccc:0:0:0:0:0:0:2%1:5795 for CORE protocol
> [Server:failover-two] 04:02:29,955 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c fccc:0:0:0:0:0:0:2%1:5805 for CORE protocol
> [Server:failover-two] 04:02:29,957 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) Server is now live
> [Server:failover-two] 04:02:29,957 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.2.18.Final (HQ_2_2_18_FINAL, 122) [bc931309-de0a-11e1-bf84-3397a847e4d3]) started
> [Server:failover-two] 04:02:29,977 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> [Server:failover-two] 04:02:30,057 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
> [Server:failover-two] 04:02:30,060 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
> [Server:failover-two] 04:02:30,062 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 56) trying to deploy queue jms.queue.testQueue
> [Server:failover-two] 04:02:30,091 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
> [Server:failover-two] 04:02:30,171 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-6) HornetQ resource adaptor started
> [Server:failover-two] 04:02:30,172 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
> [Server:failover-two] 04:02:30,176 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
> [Server:failover-two] 04:02:30,185 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/queue/test
> [Server:failover-two] 04:02:30,187 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 55) trying to deploy queue jms.topic.testTopic
> [Server:failover-two] 04:02:30,241 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name java:/topic/test
> [Server:failover-two] 04:02:30,719 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> [Server:failover-two] JBAS014775: New missing/unsatisfied dependencies:
> [Server:failover-two] service jboss.server.controller.management.security_realm.ApplicationRealm (missing) dependents: [service jboss.remoting.authentication_provider.remoting-connector]
> [Server:failover-two]
> [Server:failover-two] 04:02:30,808 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started (with errors) in 5937ms - Started 138 of 221 services (4 services failed or missing dependencies, 78 services are passive or on-demand)
> [Host Controller] 04:02:30,820 INFO [org.jboss.as.host.controller] (proxy-threads - 1) JBAS010919: Registering server failover-two
> /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/test-classes/domain-configs/domain-standard.xml
> /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/test-classes/host-configs/host-failover3.xml
> 04:02:31,516 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> 04:02:31,632 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 04:02:32,148 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> [Host Controller] 04:02:32,330 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> [Host Controller] 04:02:32,399 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Host Controller] 04:02:32,904 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (public) port (19990) securePort (-1)
> [Host Controller] 04:02:32,906 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.0.5.GA
> [Host Controller] 04:02:32,933 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.5.GA
> [Host Controller] 04:02:32,943 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.8.GA
> [Host Controller] 04:02:33,109 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on [fccc::2]:19999
> [Host Controller] 04:02:36,061 INFO [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "failover3", JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> [Host Controller] 04:02:36,206 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server failover-three
> 04:02:36,263 INFO [org.jboss.as.process.Server:failover-three.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:failover-three'
> [Host Controller] 04:02:36,274 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://fccc::2:19990/management
> [Host Controller] 04:02:36,277 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
> [Host Controller] 04:02:36,277 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" (Host Controller) started in 4533ms - Started 11 of 11 services (0 services are passive or on-demand)
> [Server:failover-three] 04:02:36,910 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA
> [Server:failover-three] 04:02:37,319 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> [Server:failover-three] 04:02:37,531 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Server:failover-three] 04:02:37,828 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.5.GA
> [Server:failover-three] 04:02:37,848 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.5.GA
> [Server:failover-three] 04:02:37,858 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.8.GA
> [Host Controller] 04:02:39,255 INFO [org.jboss.as.domain.controller.mgmt] (proxy-threads - 1) JBAS010920: Server [Server:failover-three] registered using connection [Channel ID 354ca75c (inbound) of Remoting connection 5fb57890 to /fccc:0:0:0:0:0:0:2:35193]
> [Server:failover-three] 04:02:39,425 INFO [org.jboss.as.logging] (MSC service thread 1-5) JBAS011502: Removing bootstrap log handlers
> [Server:failover-three] 04:02:39,445 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 29) JBAS015537: Activating WebServices Extension
> [Server:failover-three] 04:02:39,491 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> [Server:failover-three] 04:02:39,494 INFO [org.jboss.as.modcluster] (ServerService Thread Pool -- 28) JBAS011704: Mod_cluster uses default load balancer provider
> [Server:failover-three] 04:02:39,498 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 44) JBAS011800: Activating Naming Subsystem
> [Server:failover-three] 04:02:39,512 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 46) JBAS010260: Activating JGroups subsystem.
> [Server:failover-three] 04:02:39,525 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
> [Server:failover-three] 04:02:39,543 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) JBAS010280: Activating Infinispan subsystem.
> [Server:failover-three] 04:02:39,651 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.9.Final
> [Server:failover-three] 04:02:39,824 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)
> [Server:failover-three] 04:02:39,981 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
> [Server:failover-three] 04:02:40,012 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
> [Server:failover-three] 04:02:40,033 INFO [org.jboss.jaxr] (MSC service thread 1-4) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
> [Server:failover-three] 04:02:40,127 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
> [Server:failover-three] 04:02:40,332 INFO [org.apache.coyote.ajp.AjpAprProtocol] (MSC service thread 1-4) Starting Coyote AJP/1.3 on ajp-/fccc:0:0:0:0:0:0:2%1:8559
> [Server:failover-three] 04:02:40,372 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-/fccc:0:0:0:0:0:0:2%1:8630
> [Server:failover-three] 04:02:40,430 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA032010: JBossTS Recovery Service (tag: JBOSSTS_4_16_4_Final) - JBoss Inc.
> [Server:failover-three] 04:02:40,490 INFO [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 54) Initializing mod_cluster 1.2.1.Final
> [Server:failover-three] 04:02:40,614 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover3/servers/failover-three/data/messagingjournal,bindingsDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover3/servers/failover-three/data/messagingbindings,largeMessagesDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover3/servers/failover-three/data/messaginglargemessages,pagingDirectory=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover3/servers/failover-three/data/messagingpaging)
> [Server:failover-three] 04:02:40,625 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-3) ARJUNA012324: Start RecoveryActivators
> [Server:failover-three] 04:02:40,626 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [Server:failover-three] 04:02:40,637 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (ServerService Thread Pool -- 54) Listening to proxy advertisements on 224.0.1.105:23,364
> [Server:failover-three] 04:02:40,659 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [Server:failover-three] 04:02:40,707 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012296: ExpiredEntryMonitor running at Sat, 4 Aug 2012 04:02:40
> [Server:failover-three] 04:02:40,823 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-3) ARJUNA012343: RecoveryManagerImple is ready. Socket listener is turned off.
> [Server:failover-three] 04:02:40,823 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA032013: Starting transaction recovery manager
> [Server:failover-three] 04:02:40,937 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-6) ARJUNA032017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_16_4_Final) - JBoss Inc.
> [Server:failover-three] 04:02:41,088 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> [Server:failover-three] 04:02:41,135 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-5) Started Netty Acceptor version 3.2.5.Final-a96d88c fccc:0:0:0:0:0:0:2%1:5995 for CORE protocol
> [Server:failover-three] 04:02:41,143 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-5) Started Netty Acceptor version 3.2.5.Final-a96d88c fccc:0:0:0:0:0:0:2%1:6005 for CORE protocol
> [Server:failover-three] 04:02:41,147 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) Server is now live
> [Server:failover-three] 04:02:41,149 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) HornetQ Server version 2.2.18.Final (HQ_2_2_18_FINAL, 122) [c34b0bab-de0a-11e1-8976-f9b7adac47b8]) started
> [Server:failover-three] 04:02:41,185 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
> [Server:failover-three] 04:02:41,188 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
> [Server:failover-three] 04:02:41,193 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 57) trying to deploy queue jms.queue.testQueue
> [Server:failover-three] 04:02:41,296 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/queue/test
> [Server:failover-three] 04:02:41,297 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 55) trying to deploy queue jms.topic.testTopic
> [Server:failover-three] 04:02:41,332 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name java:/topic/test
> [Server:failover-three] 04:02:41,353 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
> [Server:failover-three] 04:02:41,415 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-4) HornetQ resource adaptor started
> [Server:failover-three] 04:02:41,415 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
> [Server:failover-three] 04:02:41,421 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
> [Server:failover-three] 04:02:41,893 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> [Server:failover-three] JBAS014775: New missing/unsatisfied dependencies:
> [Server:failover-three] service jboss.server.controller.management.security_realm.ApplicationRealm (missing) dependents: [service jboss.remoting.authentication_provider.remoting-connector]
> [Server:failover-three]
> [Server:failover-three] 04:02:41,912 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started (with errors) in 5430ms - Started 138 of 221 services (4 services failed or missing dependencies, 78 services are passive or on-demand)
> [Host Controller] 04:02:41,925 INFO [org.jboss.as.host.controller] (proxy-threads - 1) JBAS010919: Registering server failover-three
> [Host Controller] 04:02:43,393 WARN [org.jboss.as.host.controller] (Remoting "jenkins-slave3:MANAGEMENT" task-2) JBAS010914: Connection to remote host-controller closed. Trying to reconnect.
> [Host Controller] 04:02:43,442 WARN [org.jboss.as.host.controller] (Remoting "jenkins-slave3:MANAGEMENT" read-1) JBAS010914: Connection to remote host-controller closed. Trying to reconnect.
> [Host Controller] 04:02:44,195 INFO [org.jboss.as.host.controller] (MSC service thread 1-4) JBAS010926: Unregistering server failover-two
> [Host Controller] 04:02:48,486 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" stopped in 4325ms
> [Host Controller] 04:02:48,491 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Host Controller] 04:02:48,572 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (public) port (9980) securePort (-1)
> [Host Controller] 04:02:48,594 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on [fccc::2]:9989
> [Host Controller] 04:02:48,702 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,042 WARN [org.jboss.as.jmx] (Controller Boot Thread) JBAS011305: <jmx-connector/> is no longer supporting. <remoting-connector/> should be used instead to allow remote connections via JBoss Remoting.
> [Host Controller] 04:02:49,087 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,097 WARN [org.jboss.as.jmx] (Controller Boot Thread) JBAS011305: <jmx-connector/> is no longer supporting. <remoting-connector/> should be used instead to allow remote connections via JBoss Remoting.
> [Host Controller] 04:02:49,099 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,100 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,102 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,103 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,104 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,106 WARN [org.jboss.as.threads] (Controller Boot Thread) JBAS012400: The 'per-cpu' attribute is no longer supported. The value [10.000000] of the 'count' attribute is being combined with the value [20.000000] of the 'per-cpu' attribute and the current processor count [3] to derive a new value of [70] for 'count'.
> [Host Controller] 04:02:49,474 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010917: Reconnecting server failover-two
> [Host Controller] 04:02:49,571 INFO [org.jboss.as.domain.controller.mgmt] (proxy-threads - 1) JBAS010920: Server [Server:failover-two] registered using connection [Channel ID 3e69e717 (inbound) of Remoting connection 349d963f to /fccc:0:0:0:0:0:0:2:47499]
> [Host Controller] 04:02:49,646 INFO [org.jboss.as.host.controller] (proxy-threads - 1) JBAS010919: Registering server failover-two
> [Host Controller] 04:02:49,652 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://fccc::2:9980/management
> [Host Controller] 04:02:49,653 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://fccc::2:9980
> [Host Controller] 04:02:49,654 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" (Host Controller) started in 1159ms - Started 11 of 11 services (0 services are passive or on-demand)
> [Host Controller] 04:02:54,946 INFO [org.jboss.as.host.controller] (MSC service thread 1-1) JBAS010926: Unregistering server failover-three
> [Host Controller] 04:02:55,026 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015950: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" stopped in 126ms
> [Host Controller] 04:02:55,029 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> [Host Controller] 04:02:55,115 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (public) port (19990) securePort (-1)
> [Host Controller] 04:02:55,135 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on [fccc::2]:19999
> [Host Controller] 04:02:55,709 INFO [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "failover3", JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> [Host Controller] 04:02:55,843 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://fccc::2:19990/management
> [Host Controller] 04:02:55,845 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
> [Host Controller] 04:02:55,846 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" (Host Controller) started in 813ms - Started 11 of 11 services (0 services are passive or on-demand)
> [Host Controller] 04:03:01,118 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/domain/target/domains/DomainControllerMigrationTestCase/failover2/data/content/cc/b78b5f0fba55537206b3b35588797dd288a9c6/content
> [Server:failover-two] 04:03:01,634 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "SimpleServlet.war"
> [Server:failover-two] 04:03:02,267 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Register web context: /SimpleServlet
> [Server:failover-two] 04:03:02,765 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "SimpleServlet.war"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months