[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1681) NPE thrown when tomcat shutsdown

[Michael Youngstrom (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1681?page=all ]

Michael Youngstrom reassigned JBSEAM-1681:
------------------------------------------

    Assignee: Michael Youngstrom

One possible way to fix this is to create a "beginCall" lifecycle method that takes a ServletContext.  Since the HttpSessionEvent passed into passivate contains an instance of the ServletContext.

If nobody has an objection I'd like to whip up a patch that does this?

Mike

> NPE thrown when tomcat shutsdown
> --------------------------------
>
>                 Key: JBSEAM-1681
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1681
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Michael Youngstrom
>         Assigned To: Michael Youngstrom
>             Fix For: 2.0.0.CR1
>
>
> I'm running Seam in tomcat 5.5.23.  When I shutdown I get an NPE.  It appears that contextDestroyed is being called before tomcat does the session passivation.  Any opinions on the best way to deal with this?  It's obviously fairly harmless but the message is semi annoying?
> java.lang.NullPointerException
> 	at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:48)
> 	at org.jboss.seam.Component.forName(Component.java:1709)
> 	at org.jboss.seam.Component.getInstance(Component.java:1757)
> 	at org.jboss.seam.Component.getInstance(Component.java:1752)
> 	at org.jboss.seam.Component.getInstance(Component.java:1729)
> 	at org.jboss.seam.Component.getInstance(Component.java:1724)
> 	at org.jboss.seam.core.Events.instance(Events.java:154)
> 	at org.jboss.seam.core.Events.exists(Events.java:149)
> 	at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:236)
> 	at org.jboss.seam.contexts.Lifecycle.endCall(Lifecycle.java:91)
> 	at org.jboss.seam.persistence.ManagedPersistenceContext.sessionWillPassivate(ManagedPersistenceContext.java:157)
> 	at org.apache.catalina.session.StandardSession.passivate(StandardSession.java:774)
> 	at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:516)
> 	at org.apache.catalina.session.StandardManager.unload(StandardManager.java:463)
> 	at org.apache.catalina.session.StandardManager.stop(StandardManager.java:667)
> 	at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4363)
> 	at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067)
> 	at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067)
> 	at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
> 	at org.apache.catalina.core.StandardService.stop(StandardService.java:510)
> 	at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734)
> 	at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
> 	at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
> 	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:585)
> 	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
> 	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

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