[
https://issues.jboss.org/browse/AS7-6659?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-6659:
--------------------------------
Summary: Invalid TimeoutException on OSGi web app bundle start (was: Timeout OSGi web
app bundle start)
Invalid TimeoutException on OSGi web app bundle start
-----------------------------------------------------
Key: AS7-6659
URL:
https://issues.jboss.org/browse/AS7-6659
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Environment: Windows 7, 64-bit
Reporter: Jarkko Rantavuori
Assignee: Thomas Diesler
Fix For: 8.0.0.Alpha1
Sometimes activating a complex OSGi-war bundle throws timeout exception, even though
activation does work and war answers to requests just fine. It seems exception + message
is unjustified and no roll back actually occurs. Stack trace attached.
{code}
15:37:41,041 ERROR [org.jboss.as.osgi] (management-handler-thread - 6) JBAS011909:
Management operation 'start' failed:
org.jboss.osgi.deployment.interceptor.LifecycleInterceptorException: JBAS018100: Timeout
context service activation: service jboss.web.deployment.default-host./manageclinic-web
at
org.jboss.as.osgi.web.WebContextLifecycleInterceptor.invoke(WebContextLifecycleInterceptor.java:108)
at
org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:265)
at
org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:226)
at
org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:215)
at
org.jboss.osgi.framework.internal.HostBundleState.startInternalNow(HostBundleState.java:313)
at
org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:199)
at
org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:406)
at
org.jboss.osgi.framework.spi.BundleLifecyclePlugin$BundleLifecycleImpl.start(BundleLifecyclePlugin.java:102)
at
org.jboss.as.osgi.service.BundleLifecycleIntegration$BundleLifecycleImpl.start(BundleLifecycleIntegration.java:218)
at
org.jboss.osgi.framework.internal.AbstractBundleState.startWithOptions(AbstractBundleState.java:537)
at
org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:525)
at
org.jboss.as.osgi.management.BundleResourceHandler.handleOperation(BundleResourceHandler.java:106)
at
org.jboss.as.osgi.management.BundleResourceHandler.executeRuntimeStep(BundleResourceHandler.java:58)
at
org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139)[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108)[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296)
[jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
[jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_24]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.1.0.Final.jar:2.1.0.Final]
Caused by: java.util.concurrent.TimeoutException: JBAS018100: Timeout context service
activation: service jboss.web.deployment.default-host./manageclinic-web
at
org.jboss.as.web.deployment.WebDeploymentService$ContextActivator.awaitStateChange(WebDeploymentService.java:287)
at
org.jboss.as.web.deployment.WebDeploymentService$ContextActivator.start(WebDeploymentService.java:225)
at
org.jboss.as.osgi.web.WebContextLifecycleInterceptor.invoke(WebContextLifecycleInterceptor.java:104)
... 27 more
{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