2012-08-13 140 views
0

我們正在開發Vaadin應用程序,在oc4j 10.1.3上運行它。 實現基本認證後,用戶的會話會在超時(默認值)內自動失效。 因此,用戶打開Vaadin應用程序,並且在一點上應該有一些數據集作爲另一個servlet的會話屬性。但是,那時候,我們有一個例外,說這個會議已經失效了。它永遠不會被明確地調用,也許oc4j會這樣嗎? 在驗證執行之前它工作正常。oc4j會話失效

Aug 13, 2012 4:21:27 PM com.vaadin.Application terminalError 
SEVERE: Terminal error: 
com.vaadin.event.ListenerMethod$MethodException: Invocation of method buttonClick in com.mycompany.myapp$1 failed. 
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:530) 
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164) 
at com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219) 
at com.vaadin.ui.Button.fireClick(Button.java:567) 
at com.vaadin.ui.Button.changeVariables(Button.java:223) 
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.changeVariables(AbstractCommunicationManager.java:1460) 
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariableBurst(AbstractCommunicationManager.java:1404) 
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1329) 
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:761) 
at com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:318) 
at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:501) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) 
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64) 
at com.mycompany.myapp.RewriteFilter.doFilter(RewriteFilter.java:44) 
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:644) 
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391) 
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908) 
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458) 
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313) 
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199) 
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) 
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) 
at java.lang.Thread.run(Thread.java:595) 
Caused by: java.lang.IllegalStateException: Session was invalidated 
at com.evermind.server.http.EvermindHttpSession.setAttribute(EvermindHttpSession.java:158) 
at com.evermind.server.http.EvermindHttpSession.setAttribute(EvermindHttpSession.java:137) 
at com.mycompany.myapp$1.buttonClick(MyPage.java:105) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:585) 
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510) 
... 22 more 

回答

0

執行HttpSessionListener後,我發現會話本身是有效的。 Vaadin方面一定是錯誤的,b/c將Session作爲一個變量從HttpServletRequestListener.onRequestStart方法中設置爲一個變量,該會話實例沒問題。