[jboss-jira] [JBoss JIRA] Updated: (JBAS-6336) CleanShutdownInterceptor Can Log Container State Incorrectly
Jimmy Wilson (JIRA)
jira-events at lists.jboss.org
Thu Dec 18 16:48:54 EST 2008
[ https://jira.jboss.org/jira/browse/JBAS-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jimmy Wilson updated JBAS-6336:
-------------------------------
> CleanShutdownInterceptor Can Log Container State Incorrectly
> ------------------------------------------------------------
>
> Key: JBAS-6336
> URL: https://jira.jboss.org/jira/browse/JBAS-6336
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: JBossAS-4.2.3.GA
> Reporter: Jimmy Wilson
> Assignee: Jimmy Wilson
> Fix For: JBossAS-4.2.4.GA
>
>
> CleanShutdownInterceptor will report this exception
> Caused by: org.jboss.ha.framework.interfaces.GenericClusteringException: Container is shuting down on this node at org.jboss.ejb.plugins.CleanShutdownInterceptor.invokeHome(CleanShutdownInterceptor.java:234)
> at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:637)
> at org.jboss.ejb.Container.invoke(Container.java:975) at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:359)
> at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:133)
> even when the container in question failed to start as opposed to shutting down.
> The error message needs to be updated to indicate that the container may not have started as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list