[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)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352206 ] 
            
Alex Kozlenkov commented on JBSEAM-760:
---------------------------------------

That is exactly as you say:

15:57:11,006 INFO  [STDOUT] Hibernate: select user0_.username as
col_0_0_ from User user0_ where user0_.username=?
15:57:11,054 INFO  [STDOUT] Hibernate: select userrole0_.roleId as
roleId2_, userrole0_.name as name2_ from UserRole userrole0_ where
userrole0_.name=?
15:57:11,145 INFO  [STDOUT] Hibernate: insert into User (name, password,
username) values (?, ?, ?)
15:57:11,153 INFO  [RegisterActionBean] Registered new user zzzzz
15:57:11,166 INFO  [STDOUT] after - INVOKE_APPLICATION(5)
15:57:11,205 INFO  [STDOUT] Hibernate: insert into User_UserRole
(User_userId, roles_roleId) values (?, ?)
15:57:11,252 INFO  [ManagedPersistenceContext] sessionWillPassivate:
javax.servlet.http.HttpSessionEvent[source=org.apache.catalina.session.S
tandardSessionFacade at 1f751c9]
15:57:11,296 INFO  [STDOUT] Processing new  Request!
15:57:11,296 INFO  [STDOUT] before - RESTORE_VIEW(1)
15:57:11,297 INFO  [STDOUT] after - RESTORE_VIEW(1)
15:57:11,304 INFO  [STDOUT] before - RENDER_RESPONSE(6)
15:57:11,407 INFO  [STDOUT] after - RENDER_RESPONSE(6)
15:57:11,410 INFO  [STDOUT] Done with Request!
15:57:11,414 WARN  [Contexts] Could not destroy component: entityManager

Then the stack trace as I sent before.

Alex



> 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