[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
4:12 a.m.
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
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
7:45 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=all ]
Gavin King updated JBSEAM-760:
------------------------------
Fix Version/s: 1.1.6.GA
Assignee: Gavin King
Priority: Critical (was: Major)
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
8:54 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=all ]
Gavin King closed JBSEAM-760.
-----------------------------
Resolution: Done
Fixed in CVS - please test this for me!
Thanks.
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
9:15 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352195 ]
Alex Kozlenkov commented on JBSEAM-760:
---------------------------------------
Hi Gavin,
Having just recompiled Seam and added the new jcaptcha dependency, I'm
still encountering the same issue.
Cheers,
Alex Kozlenkov
Advanced Technology Group
Office: +44 20 8834 6854
Yahoo! Messenger: alex.kozlenkov
Betfair Limited | Winslow Road | Hammersmith Embankment | London | W6
9HP
Company No. 5140986
ÂÂ
The information in this e-mail and any attachment is confidential and is
intended only for the named recipient(s). The e-mail may not be
disclosed or used by any person other than the addressee, nor may it be
copied in any way. If you are not a named recipient please notify the
sender immediately and delete any copies of this message. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. Any view or opinions presented are solely
those of the author and do not necessarily represent those of the
company.
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
9:18 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352197 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
You didnt get the latest code. Try again (anoncvs is behind).
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
9:22 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352198 ]
Alex Kozlenkov commented on JBSEAM-760:
---------------------------------------
Gavin,
Any chance you could edit my previous post to remove signature?
Ta--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
9:27 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352200 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
I deleted the comment
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
9:27 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=all ]
Gavin King updated JBSEAM-760:
------------------------------
Comment: was deleted
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
9:36 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ 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
9:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352204 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
Thats interesting. Looks like sessionWillPassivate() is called but then
sessionDidActivate() is not. (Which would be a bug in the servlet container clustering,
IMO.)
Can you please put some log messages in those methods and verify that that is what is
going on?
Thanks.
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
10 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352205 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
Thats interesting. Looks like sessionWillPassivate() is called but then
sessionDidActivate() is not. (Which would be a bug in the servlet container
clustering, IMO.)
Can you please put some log messages in those methods and verify that that
is what is going on?
Thanks.
--
Gavin King
gavin.king(a)gmail.com
http://hibernate.org
http://jboss.com/products/seam
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
10:14 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ 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@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
12:12 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352217 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
Definitely breaks the HttpSession contract. But I guess I need to work around that.
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
12:12 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=all ]
Gavin King reopened JBSEAM-760:
-------------------------------
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
2:07 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=all ]
Gavin King closed JBSEAM-760.
-----------------------------
Resolution: Done
OK, I've significantly reworked this code, to workaround the bad lifecycle in Tomcat.
Would you please give this latest change a real hammering? Thanks
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
2:42 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352222 ]
Alex Kozlenkov commented on JBSEAM-760:
---------------------------------------
I've recompiled with the same result, judging by the exception--my log messages were
gone. Seems to be elusive, this one.
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
2:59 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352223 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
It is absolutely not possible that you could get the same exception stack trace.
Are you sure you have the *latest* code.
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
3:03 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352227 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
Excuse me, its totally possible. Silly error. Hold on.
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
3:06 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352229 ]
Gavin King commented on JBSEAM-760:
-----------------------------------
OK, try now. Stupidme.
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
3:22 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise
[ http://jira.jboss.com/jira/browse/JBSEAM-760?page=comments#action_12352232 ]
Alex Kozlenkov commented on JBSEAM-760:
---------------------------------------
====S U C C E S S====
21:13:23,746 INFO [STDOUT] Processing new Request!
21:13:23,746 INFO [STDOUT] before - RESTORE_VIEW(1)
21:13:23,753 INFO [STDOUT] after - RESTORE_VIEW(1)
21:13:23,754 INFO [STDOUT] before - APPLY_REQUEST_VALUES(2)
21:13:23,754 INFO [STDOUT] after - APPLY_REQUEST_VALUES(2)
21:13:23,754 INFO [STDOUT] before - PROCESS_VALIDATIONS(3)
21:13:23,756 INFO [STDOUT] after - PROCESS_VALIDATIONS(3)
21:13:23,756 INFO [STDOUT] before - UPDATE_MODEL_VALUES(4)
21:13:23,760 INFO [STDOUT] after - UPDATE_MODEL_VALUES(4)
21:13:23,760 INFO [STDOUT] before - INVOKE_APPLICATION(5)
21:13:23,763 INFO [STDOUT] Hibernate: select user0_.username as col_0_0_ from User user0_
where user0_.username=?
21:13:23,771 INFO [STDOUT] Hibernate: select userrole0_.roleId as roleId2_,
userrole0_.name as name2_ from UserRole userrole0_ where userrole0_.name=?
21:13:23,813 INFO [STDOUT] Hibernate: insert into User (name, password, username) values
(?, ?, ?)
21:13:23,817 INFO [RegisterActionBean] Registered new user abcde
21:13:23,819 INFO [STDOUT] after - INVOKE_APPLICATION(5)
21:13:23,837 INFO [STDOUT] Hibernate: insert into User_UserRole (User_userId,
roles_roleId) values (?, ?)
21:13:23,891 INFO [STDOUT] Processing new Request!
21:13:23,891 INFO [STDOUT] before - RESTORE_VIEW(1)
21:13:23,892 INFO [STDOUT] after - RESTORE_VIEW(1)
21:13:23,895 INFO [STDOUT] before - RENDER_RESPONSE(6)
21:13:23,948 INFO [STDOUT] after - RENDER_RESPONSE(6)
21:13:23,948 INFO [STDOUT] Done with Request!
Gavin, many thanks for fixing this, really appreciated,
Cheers--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
6920
days inactive
6920
days old
19 comments
2 participants
participants (2)
-
Alex Kozlenkov (JIRA) -
Gavin King (JIRA)