[JBoss Seam] - Weird random "session was null" exceptions
by IGx89
I've recently started randomly seeing the following exception:
java.lang.IllegalStateException: Could not start transaction
| at org.jboss.seam.jsf.SeamPhaseListener.begin(SeamPhaseListener.java:571)
| at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsBeforePhase(SeamPhaseListener.java:307)
| at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:142)
| at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116)
| at org.ajax4jsf.resource.ResourceLifecycle.send(ResourceLifecycle.java:165)
| at org.ajax4jsf.resource.InternetResourceService.load(InternetResourceService.java:336)
| at org.ajax4jsf.cache.LRUMapCache.load(LRUMapCache.java:116)
| at org.ajax4jsf.cache.LRUMapCache.get(LRUMapCache.java:87)
| at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:198)
| at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:144)
| at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:265)
| at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
| at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
| at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.IllegalStateException: session was null: #{ourDatabase}
| at org.jboss.seam.transaction.HibernateTransaction.initSession(HibernateTransaction.java:71)
| at org.jboss.seam.transaction.HibernateTransaction.begin(HibernateTransaction.java:79)
| at org.jboss.seam.jsf.SeamPhaseListener.begin(SeamPhaseListener.java:566)
| ... 32 more
Anyone know what the cause might be? It doesn't seem to affect the functionality of anything...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089731#4089731
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089731
18 years, 6 months
[JBoss Seam] - Re: Security: Better support for single sign on?!
by bsmithjj
"stephen.friedrich" wrote :
|
| Proposal: Here's a way to make integration into an SSO solution easier:
| Add an attribute to identity that lets me specify a method that is used to try auto-login:
|
| | <security:identity authenticate-method="#{authenticator.authenticate}" auto-login-method="#{authenticator.tryAutoLogin}"/>
| |
|
| Like the authenticate-method the auto-login-method on successful login would set roles at identity and return true.
| That would spare me from configuring a page action for all pages. It would prevent the spurious "Please login. Welcome." messages. Also I would not need to pass user data in a field from the checkLogin method to the authentiocate method like I did above.
|
| What do you think?
|
I like this suggestion most. It's consistent with the JIRA issue I've mentioned earlier in the thread. I wish they would add support for this - I still don't have a working solution / even using your approach posted earlier - sigh....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089729#4089729
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089729
18 years, 6 months