[JBoss JIRA] (AS7-6577) Deployment descriptor parsing of META-INF/permissions.xml
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6577?page=com.atlassian.jira.plugin.s... ]
David Lloyd commented on AS7-6577:
----------------------------------
We should additionally support a {{jboss-permissions.xml}} descriptor with the same schema/syntax. If such a file is present in a top-level deployment, it should take precedence over {{permissions.xml}}; if present in a subdeployment, it should replace the permissions for that subdeployment's code source (and any other nested JARs contained therein) only.
> Deployment descriptor parsing of META-INF/permissions.xml
> ---------------------------------------------------------
>
> Key: AS7-6577
> URL: https://issues.jboss.org/browse/AS7-6577
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: Anil Saldhana
> Assignee: Stefan Guilhen
> Fix For: 8.0.0.Alpha1
>
>
> EE 6.2.2.6 Permission declarations must be stored in META-INF/permissions.xml file
> within an EJB, web, or application client archive in order for them to be located
> and subsequently processed by the deployment machinery of the Java EE Product.
> The permissions for a library are the same as the permissions for the code that
> EE.6.2.2.6.2 Permission Declaration Example
> <?xml version="1.0" encoding="UTF-8"?>
> <permissions>
> <permission>
> <classname>java.io.FilePermission</classname>
> <name>/tmp/abc</name>
> <actions>read,write</actions>
> </permission>
> <permission>
> <classname>java.lang.RuntimePermission</classname>
> <name>createClassLoader</name>
> </permission>
> </permissions>
> The EE7 spec draft has a schema for permissions.xml
--
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, 2 months
[JBoss JIRA] (AS7-6635) EJB2 CMB beans: ejbActivate callback is called after the bean creation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6635?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6635:
----------------------------------------------
baranowb <bbaranow(a)redhat.com> made a comment on [bug 914738|https://bugzilla.redhat.com/show_bug.cgi?id=914738]
This issue should have different status.
> EJB2 CMB beans: ejbActivate callback is called after the bean creation
> -----------------------------------------------------------------------
>
> Key: AS7-6635
> URL: https://issues.jboss.org/browse/AS7-6635
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Labels: cmp, ejb, entities, entity
>
> Called ejbActive after the create() call on home interface is incorrect by spec.
> 10.1.3
> There are two possible transitions from the pooled to the ready state: through the ejbCreate<METHOD> and ejbPostCreate<METHOD> methods, or through the ejbActivate method. The container invokes the ejbCreate<METHOD> and ejbPostCreate<METHOD> methods when the instance is assigned to an entity object during entity object creation.
> The container invokes the ejbActivate method on an instance when an instance needs to be activated to service an invocation on an existing entity object—this occurs because there is no suitable instance in the ready state to service the client’s call or the ejbTimeout method.
--
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, 2 months
[JBoss JIRA] (AS7-6586) JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-6586?page=com.atlassian.jira.plugin.s... ]
Scott Marlow commented on AS7-6586:
-----------------------------------
[JPA 2.1 specification changes to specify the container requirements are here|http://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2013-...].
> JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern
> -----------------------------------------------------------------------------------------------
>
> Key: AS7-6586
> URL: https://issues.jboss.org/browse/AS7-6586
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 8.0.0.Alpha1
>
>
> For transaction scoped entity managers, the closing the of entity manager is deferred until after the transaction completes.
> It is possible that the transaction manager/service may call the Transaction sync from a non-application thread (tx timeout reaper thread or normal completion in remote propagated tx case). Guards need to be added to make sure that a tx timeout, doesn't interfere with normal application usage of the entity manager.
> I think that there are two main cases to be concerned with that involve the afterCompletion sync being invoked in a non-application thread:
> # TX reaper or other background thread calls afterCompletion while application thread is in (transaction scope) entityManager invocation.
> # TX reaper or other background thread calls afterCompletion while application thread is not in (transaction scope) entityManager invocation.
> Extended persistence contexts do not get closed when the JTA transaction that they are joined to are closed (in case anyone is curious).
> If we are in #1 above, could we delegate the closing of the EntityManager to the in progress EntityManager invocation (to avoid closing the thread unsafe invocation)? Or prevent the background thread from closing the EntityManager until the current EntityManager invocation completes. Or push the requirement up to the top-level EE container (e.g. managed bean, EJB3, web, ...).
> The related classes are org.jboss.as.jpa.container.TransactionScopedEntityManager (or AbstractEntityManager) + org.jboss.as.jpa.transaction.TransactionUtil classes.
--
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, 2 months
[JBoss JIRA] (AS7-6659) Invalid TimeoutException on OSGi web app bundle start
by Thomas Diesler (JIRA)
[ 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
13 years, 2 months
[JBoss JIRA] (AS7-6659) Timeout OSGi web app bundle start
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6659?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6659:
--------------------------------
Attachment: (was: stack_trace_start_timeout.txt)
> Timeout 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
13 years, 2 months
[JBoss JIRA] (AS7-6659) Timeout OSGi web app bundle start
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6659?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6659:
--------------------------------
Description:
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}
was: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.
> Timeout 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
>
> Attachments: stack_trace_start_timeout.txt
>
>
> 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
13 years, 2 months
[JBoss JIRA] (AS7-6659) Timeout OSGi web app bundle start
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6659?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6659:
--------------------------------
Summary: Timeout OSGi web app bundle start (was: Timeout exceptions on OSGified bundle start sometimes occur even if activation works)
> Timeout 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
>
> Attachments: stack_trace_start_timeout.txt
>
>
> 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.
--
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, 2 months