4 Replies Latest reply on Jun 23, 2009 12:43 AM by Bill Evans

    Shutting down JBoss - how long is Seam working?

    Jan Groth Novice

      Hi there,

      consider the following scenario: JBoss is shutting down (controlled), existing web-sessions are destroyed, sessionDestroyed-event is raised, registered SessionListener is called.

      The following problem occurs: The Bijection-mechanism is not working (anymore?) if called from within this app-server-shutting-down scenario.

      15:34:35,053 INFO  [Server] Shutting down the server, blockingShutdown: false
      15:34:35,053 INFO  [Server] Server exit(0) called
      15:34:35,053 INFO  [Server] Runtime shutdown hook called, forceHalt: true
      15:34:35,053 INFO  [Server] JBoss SHUTDOWN: Undeploying all packages
      15:34:35,053 INFO  [TomcatDeployer] undeploy, ctxPath=/saporo-intranet, warUrl=.../deploy/saporo-intranet-ear.ear/saporo-intranet-war.war/
      15:34:35,069 ERROR [[/intranet]] Session event listener threw exception

      Well, that's a bit of a hassle. The session does still exist, the required attributes (the user) is still set, the container just stopped inject the Home / List classes - which i need to persist the logout process.

      Any ideas? Workarounds? Help?

      Many thanks,