[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-5884:
----------------------------------
Assignee: Kabir Khan (was: Brian Stansberry)
> CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5884
> URL: https://issues.jboss.org/browse/AS7-5884
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Wolf-Dieter Fink
> Assignee: Kabir Khan
> Priority: Critical
> Labels: deployers, domain, eap, jboss
> Fix For: 7.2.0.CR1
>
>
> If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1.
> In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group.
> But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available.
> The second deployment can be used as long as there is a action to it (e.g. restart).
> In that case a FATAL error is thrown:
> [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart."
> [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
--
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-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-5884:
----------------------------------
Component/s: Domain Management
> CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5884
> URL: https://issues.jboss.org/browse/AS7-5884
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Wolf-Dieter Fink
> Assignee: Brian Stansberry
> Priority: Critical
> Labels: deployers, domain, eap, jboss
> Fix For: 7.2.0.CR1
>
>
> If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1.
> In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group.
> But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available.
> The second deployment can be used as long as there is a action to it (e.g. restart).
> In that case a FATAL error is thrown:
> [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart."
> [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
--
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-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-10353 to AS7-5884:
------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5884 (was: JBPAPP-10353)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.3.Final (EAP)
(was: EAP 6.0.0)
Security: (was: Public)
Fix Version/s: 7.2.0.CR1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5884
> URL: https://issues.jboss.org/browse/AS7-5884
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Wolf-Dieter Fink
> Assignee: Brian Stansberry
> Priority: Critical
> Labels: deployers, domain, eap, jboss
> Fix For: 7.2.0.CR1
>
>
> If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1.
> In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group.
> But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available.
> The second deployment can be used as long as there is a action to it (e.g. restart).
> In that case a FATAL error is thrown:
> [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart."
> [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
--
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-5723) Allow detection caller management operation
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5723:
-----------------------------------
Summary: Allow detection caller management operation
Key: AS7-5723
URL: https://issues.jboss.org/browse/AS7-5723
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management, OSGi
Reporter: Thomas Diesler
Assignee: Brian Stansberry
Currently we have a hack in place where we detect a running management operation using a ThreadLocal. The called code can take an alternative route and not execute a nested management operation which would deadlock.
See usages of org.jboss.as.osgi.management.OperationAssociation
--
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-4292) Invalid bundle deployment does not fail in domain
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-4292:
-----------------------------------
Summary: Invalid bundle deployment does not fail in domain
Key: AS7-4292
URL: https://issues.jboss.org/browse/AS7-4292
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, OSGi
Reporter: Thomas Diesler
Assignee: Brian Stansberry
Fix For: 7.1.2.Final
Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE!
on the server I see
{code}
15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
Caused by: java.lang.NumberFormatException: For input string: "bogus"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29]
at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29]
at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29]
at org.osgi.framework.Version.<init>(Version.java:125)
at org.osgi.framework.Version.parseVersion(Version.java:218)
at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204)
at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153)
at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63)
{code}
--
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
13 years, 6 months
[JBoss JIRA] (LOGMGR-42) StringIndexOutOfBoundsException in exceptionFormatStep
by Marcus Klimstra (JIRA)
Marcus Klimstra created LOGMGR-42:
-------------------------------------
Summary: StringIndexOutOfBoundsException in exceptionFormatStep
Key: LOGMGR-42
URL: https://issues.jboss.org/browse/LOGMGR-42
Project: JBoss Log Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 1.3.1.Final
Reporter: Marcus Klimstra
Assignee: David Lloyd
StringIndexOutOfBoundsException is thrown when the path does not contain a jarName.
In my case path is "/com/.../Foo.class" (from a custom classloader).
Stacktrace:
java.util.logging.ErrorManager: 5: Formatting error
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.charAt(String.java:686)
at org.jboss.logmanager.formatters.Formatters$12.renderExtended(Formatters.java:524)
at org.jboss.logmanager.formatters.Formatters$12.renderRaw(Formatters.java:388)
at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:150)
at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86)
at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35)
at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49)
at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:290)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.Logger.logRaw(Logger.java:721)
at org.jboss.logmanager.Logger.log(Logger.java:539)
The exception occurs here: (last line with while)
if (jarName == null) {
// OK, that would have been too easy. Next let's just grab the last piece before the class name
int endIdx = path.lastIndexOf(classResourceName);
if (endIdx != -1) {
do {
endIdx--;
} while (path.charAt(endIdx) == '/' || path.charAt(endIdx) == '\\' || path.charAt(endIdx) == '?');
Since there is nothing before the initial /, endIdx becomes -1.
--
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
13 years, 6 months
[JBoss JIRA] (AS7-5828) Intermittent failures in
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5828:
-------------------------------------
Summary: Intermittent failures in
Key: AS7-5828
URL: https://issues.jboss.org/browse/AS7-5828
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Reporter: Brian Stansberry
Assignee: Thomas Diesler
Fix For: 7.2.0.CR1
We've been getting intermittent failures in HttpServiceTestCase for the last few days. There were commits in this area merged on Oct 17, so that's a potential cause.
I am going to @Ignore these tests.
Some details from http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/172
{code}
Error Message
JBOSGI011200: sref is null
Stacktrace
java.lang.IllegalArgumentException: JBOSGI011200: sref is null
at org.jboss.osgi.framework.internal.AbstractBundleContext.ungetService(AbstractBundleContext.java:363)
at org.jboss.as.test.integration.osgi.http.HttpServiceTestCase.testServletAccess(HttpServiceTestCase.java:113)
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.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
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.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
at org.junit.runner.JUnitCore.run(JUnitCore.java:136)
at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65)
at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128)
at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107)
at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:214)
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:502)
at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246)
at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:911)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:145)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Standard Output
[0m19:16:35,403 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011003: Bundle stopped: example-jta:0.0.0
[0m[0m19:16:35,406 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011005: Bundle uninstalled: example-jta:0.0.0
[0m[0m19:16:35,407 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment example-jta in 5ms
[0m[0m19:16:35,412 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m19:16:35,413 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m19:16:35,414 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m19:16:35,414 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m19:16:35,415 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m19:16:35,415 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m19:16:35,422 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-master-ignore/testsuite/integration/osgi/target/jbossas/standalone/data/content/ac/3e5e7b44c78d3821bca4035b8dbbe0673054ae/content
[0m[0m19:16:35,423 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "example-jta"
[0m[0m19:16:35,513 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-master-ignore/testsuite/integration/osgi/target/jbossas/standalone/data/content/84/06809c72844c003ab943c94bbb9c4d61fb9522/content
[0m[0m19:16:35,517 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "http-service-example"
[0m[0m19:16:35,529 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: http-service-example:0.0.0
[0m[0m19:16:35,544 INFO [org.jboss.as.arquillian] (MSC service thread 1-2) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config.http-service-example,unit=http-service-example,tests=[org.jboss.as.test.integration.osgi.http.HttpServiceTestCase]]
[0m[0m19:16:35,560 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002: Bundle started: http-service-example:0.0.0
[0m[0m19:16:35,568 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m19:16:35,569 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m19:16:35,569 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m19:16:35,570 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m19:16:35,571 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m19:16:35,572 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m19:16:35,580 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "http-service-example"
[0m[0m19:16:35,651 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-1-thread-1) BeanManager not found.
[0m[31m19:16:35,686 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-1-thread-1) Failed: org.jboss.as.test.integration.osgi.http.HttpServiceTestCase.testServletAccess: java.lang.IllegalArgumentException: JBOSGI011200: sref is null
at org.jboss.osgi.framework.internal.AbstractBundleContext.ungetService(AbstractBundleContext.java:363) [jbosgi-framework-core-2.0.0.CR39.jar:2.0.0.CR39]
at org.jboss.as.test.integration.osgi.http.HttpServiceTestCase.testServletAccess(HttpServiceTestCase.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_29]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) [arquillian-service:]
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) [arquillian-service:]
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) [arquillian-service:]
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) [arquillian-service:]
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) [:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-service:]
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-service:]
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) [arquillian-service:]
at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) [arquillian-service:]
at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) [:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-service:]
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) [arquillian-service:]
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) [:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) [arquillian-service:]
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) [arquillian-service:]
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) [:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) [arquillian-service:]
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) [arquillian-service:]
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) [:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) [arquillian-service:]
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) [arquillian-service:]
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-service:]
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) [arquillian-service:]
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) [arquillian-service:]
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) [arquillian-service:]
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) [arquillian-service:]
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) [arquillian-service:]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) [arquillian-service:]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) [arquillian-service:]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) [arquillian-service:]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) [arquillian-service:]
at org.junit.runners.ParentRunner.run(ParentRunner.java:300) [arquillian-service:]
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) [arquillian-service:]
at org.junit.runner.JUnitCore.run(JUnitCore.java:157) [arquillian-service:]
at org.junit.runner.JUnitCore.run(JUnitCore.java:136) [arquillian-service:]
at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) [arquillian-service:]
at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) [arquillian-service:]
at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:]
at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:214) [arquillian-service:]
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) [:1.6.0_29]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_29]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_29]
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) [rt.jar:1.6.0_29]
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) [rt.jar:1.6.0_29]
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) [rt.jar:1.6.0_29]
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) [rt.jar:1.6.0_29]
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) [rt.jar:1.6.0_29]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) [rt.jar:1.6.0_29]
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) [rt.jar:1.6.0_29]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:502) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:911)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:145)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
{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