[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
Alex Kozlenkov (JIRA)
jira-events at jboss.com
Fri Feb 2 10:36:19 EST 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352201 ]
Alex Kozlenkov commented on JBSEAM-760:
---------------------------------------
Gavin,
I'm now getting this.
15:24:24,239 WARN [Contexts] Could not destroy component: entityManager
java.lang.NullPointerException
at org.jboss.seam.core.ManagedPersistenceContext.destroy(ManagedPersistenceContext.java:144)
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.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:102)
at org.jboss.seam.Component.callComponentMethod(Component.java:1826)
at org.jboss.seam.Component.callDestroyMethod(Component.java:1782)
at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:230)
at org.jboss.seam.contexts.Lifecycle.flushAndDestroyContexts(Lifecycle.java:397)
at org.jboss.seam.contexts.Lifecycle.endRequest(Lifecycle.java:303)
at org.jboss.seam.jsf.AbstractSeamPhaseListener.afterRender(AbstractSeamPhaseListener.java:223)
at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:95)
at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersAfter(PhaseListenerManager.java:89)
at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:391)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.seam.servlet.SeamMultipartFilter.doFilter(SeamMultipartFilter.java:35)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:87)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)
> Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-760
> URL: http://jira.jboss.com/jira/browse/JBSEAM-760
> Project: JBoss Seam
> Issue Type: Bug
> Components: Security
> Environment: Microsoft Vista with Java 6 SDK, JBoss 4.0.5.GA EJB3 and EJB3 Clustered
> Reporter: Alex Kozlenkov
> Assigned To: Gavin King
> Priority: Critical
> Fix For: 1.1.6.GA
>
>
> A very simple application using the new 1.1.5 level security features produces a java.lang.IllegalStateException when <distributable /> is included in web.xml. The application works perfectly wikthout this setting and even with <distributable /> the exception seems to be non-fatal. The stack trace follows:
> 09:58:11,169 ERROR [[/helloworld]] Session attribute event listener threw exception
> java.lang.IllegalStateException: No application context active
> at org.jboss.seam.Component.forName(Component.java:1586)
> at org.jboss.seam.Component.getInstance(Component.java:1636)
> at org.jboss.seam.Component.getInstance(Component.java:1631)
> at org.jboss.seam.Component.getInstance(Component.java:1608)
> at org.jboss.seam.Component.getInstance(Component.java:1603)
> at org.jboss.seam.persistence.PersistenceProvider.instance(PersistenceProvider.java:45)
> at org.jboss.seam.core.ManagedPersistenceContext.sessionWillPassivate(ManagedPersistenceContext.java:104)
> at org.jboss.web.tomcat.tc5.session.ClusteredSession.passivate(ClusteredSession.java:896)
> at org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:642)
> at org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:49)
> at org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:98)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> at java.lang.Thread.run(Thread.java:619)
> Using a custom phase listener to trace JSF shows that the exception is wedged between a registration page that successfully creates a new account and a login page to which the user is redirected on success. The login page is successfully presented as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list