[jboss-jira] [JBoss JIRA] (WFLY-1313) IllegalStateException in CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown()

jaikiran pai (JIRA) jira-events at lists.jboss.org
Fri May 3 07:44:53 EDT 2013


     [ https://issues.jboss.org/browse/WFLY-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated WFLY-1313:
-------------------------------

    Summary: IllegalStateException in CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown()  (was: IllegalStateException in achedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown())

    
> IllegalStateException in CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown()
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1313
>                 URL: https://issues.jboss.org/browse/WFLY-1313
>             Project: WildFly
>          Issue Type: Bug
>          Components: EE, JCA
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> The following exception was reported on lightning:
> {code}
> Caused by: java.lang.IllegalStateException
> 	at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> 	at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown(CachedConnectionManagerSetupProcessor.java:105)
> 	at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:62)
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> 	at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
> 	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:329)
> 	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70)
> 	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	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)
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
> The tests involved a EJB deployment and the EJBs were being invoked when the undeployment was in progress (@see SlowUndeploymentRemoteFailoverTestCase).
> It looks like the CachedConnectionManager service isn't being added as a dependency on the components (like EJBs) which rely on it.

--
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


More information about the jboss-jira mailing list