voyent
Messages posted by: thienp  XML
Profile for thienp -> Messages posted by thienp [14]
Author Message
Thank you for your help. I'll give it a try.
Scratch the last part about the same app in the same browser. That was caused by my "concurrentDOMviews" set to 'TRUE'. But the original problem (two different apps in the same browser) remains.

Feel like I'm talking to myself... :)
ICEfaces definitely gets the two sessions mixed up. Just to prove the point, I accessed the same web app from two different tabs within the same browser. From each tab, I logged in as *two** different users, e.g. "John" and "Mary". As soon as I logged "Mary" in as the second user and switched back to the first tab (i.e. "John"'s tab), all John's info that got displayed earlier is now replaced by Mary's. Would this be considered a serious bug?
Further investigation reveals that this problem only occurs if I open both applications in the same browser window (in this instance, two tabs in my IE browser). If I launch two separate instances of IE, they are working fine. Is it possible that somehow ICEfaces gets confused between the two sessions from these two separate webapps?
I have developed two web applications based on ICEfaces 1.7.0. They are bundled into the same EAR file and deployed to my application server (in this case, OC4J). Now, if I access either one of the webapps (but not both), everything works perfectly and is responsive. But as soon as both applications are accessed, they both become very sluggish. I just wonder if anyone has encountered this issue. Any pointer is greatly appreciated.
I'm using ICEfaces 1.7.0 DR2 with WebLogic 9.1 and ran into the exception listed below from the server when I attempted to access my webapp from browser. The ICEfaces immediately displayed "Session Expired" dialog box. Any help is greatly appreciated. Thanks.

java.lang.NullPointerException
at java.util.regex.Matcher.getTextLength(Matcher.java:1127)
at java.util.regex.Matcher.reset(Matcher.java:284)
at java.util.regex.Matcher.<init>(Matcher.java:205)
at java.util.regex.Pattern.matcher(Pattern.java:879)
at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.setHeader(ServletRequestResponse.java:156)
at com.icesoft.faces.webapp.http.common.ResponseProxy.setHeader(ResponseProxy.java:20)
at com.icesoft.faces.webapp.http.core.ServeCSSResource$1.respond(ServeCSSResource.java:32)
at com.icesoft.faces.webapp.http.common.standard.CacheControlledServer$EnhancedRequest$1.respond(CacheControlledServer.java:70)
at com.icesoft.faces.webapp.http.common.standard.CompressingServer$CompressingRequest$1.respond(CompressingServer.java:45)
at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:147)
at com.icesoft.faces.webapp.http.common.standard.CompressingServer$CompressingRequest.respondWith(CompressingServer.java:42)
at com.icesoft.faces.webapp.http.common.standard.CacheControlledServer$EnhancedRequest.respondWith(CacheControlledServer.java:63)
at com.icesoft.faces.webapp.http.core.ServeCSSResource.service(ServeCSSResource.java:30)
at com.icesoft.faces.webapp.http.common.standard.CacheControlledServer.service(CacheControlledServer.java:46)
at com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer$Matcher.serviceOnMatch(PathDispatcherServer.java:50)
at com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service(PathDispatcherServer.java:19)
at com.icesoft.faces.webapp.http.common.standard.CompressingServer.service(CompressingServer.java:26)
at com.icesoft.faces.webapp.http.core.ResourceServer.service(ResourceServer.java:30)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3150)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
I messed up again. I meant "SEMICOLON", not "COLON".
Sorry, the browser does not display my previous message correctly. Basically, all XML entities need to be in the form of "AMPERSAND"xxx"COLON". Replace "AMPERSAND" and "COLON" with the actual characters.
You will need to write a utility routine that converts XML entity characters such as "<", ">", etc. into the form of "<", ">" accordingly. Be sure NOT to encode your "<br/>" string. Hope that helps.
You need to use the escape attribute of the outputText:

<ice:outputText value="blah" escape="false"... />
1.7.0-DR2 appears to work correctly, but not 1.7.0-DR3. Somehow the problem gets reintroduced again.
Don't know if this has been fixed in the past, but I see this very same problem on the latest 1.7.0-DR3a.
Never mind. My bad. I searched thru the forum and someone indicated that it could be my browser's cache issue. I brought up a different copy of IE and the app is happy to be on its way. Sorry for the false alarm.
Hi,

I'm using ICEfaces 1.7.0 DR3a for my webapp. The application works fine on WebSphere 6.1 and Oracle OC4J, but when I tested against WebLogic 9.1, as soon as my login page appears, ICEfaces put out the dialog "User Session Expired" few seconds later. Refresh the page doesn't help, and I saw no error messages in the application server logs. My web.xml defines 120 minutes for the app's session timeout, so I have no clue how to debug this issue. Any help is greatly appreciated. Thanks.
 
Profile for thienp -> Messages posted by thienp [14]
Go to:   
Powered by JForum 2.1.7ice © JForum Team