voyent
Session Timeout - Again  XML
Forum Index -> General Help Go to Page: Previous  1, 2, 3
Author Message
downloadTest

Joined: 01/Oct/2009 00:00:00
Messages: 2
Offline


I have the same problem, any progress?

Thanks.
krokodylowy3

Joined: 01/Feb/2008 00:00:00
Messages: 42
Offline


The problem still exist?

Krashan Brahmanjara
bhuvan

Joined: 19/Aug/2012 23:12:19
Messages: 14
Offline


I am facing the same issue.
[1] session timeout
[2] user do a activity.
[3] error in firebug - empty respose from server
[4] UI hangs forever
[5] user hit F5
[6] redirect to login page
[7] user input credential
[8] redirect to a xml error page
Code:
<partial-response>
 <error>
 <error-name>
 class org.icefaces.application.SessionExpiredException
 </error-name>
 <error-message>
 <![CDATA[ Session has expired ]]>
 </error-message>
 </error>
 <changes>
 <extension aceCallbackParam="validationFailed">{"validationFailed":false}</extension>
 </changes>
 </partial-response>

[9] user hit refresh ..user redirect to a normal application

This use to work fine in 1.8... i am now trying it with 3.3
During the debuging i figured out one major difference between 1.8 and 3.3

in 1.8 when session timeout and user do a activity the response to this request is of the form:
response.status = 200
response.reponseXML = <sessionTimeOut><sessionTimeOut/>

where as in 3.3 when session timeout and user do a activity the response is:
reponse.status = 302 with response.header.location = login page
since status is 302 browser itself make a request for login page.
To icefaces javascript code the response that it got looks like
response.status=200
reponse.responseXML=null
response.reponseHTML=<HTML CODE OF LOGIN PAGE>

and in jsf.js the response handler just logs a error if reponseXML is null.

So thats why icefaces does not redirect or show popup.

The above details is just my observation and might help somebody to figure out the problem and solution.

I am using icefaces 3.3, glassfish 3.1, spring 3.0.1
OuuGiii

Joined: 12/Feb/2019 07:17:23
Messages: 1
Offline


This bug still exist.
ateequr@sg.ibm.com

Joined: 21/Apr/2016 02:41:12
Messages: 1
Offline


Hi All,

We recently migrated to the ICEFaces 3.3.0_P07 version from ICEFaces 1.8 GA.

Our application is running with compatibility mode and We are using the latest configuration which you using and the same issue is persist.

ICEFaces needs to give correct solution for this without workaround.

Configuration :
<context-param>
<param-name>org.icefaces.lazyPush</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>org.icefaces.strictSessionTimeout</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>org.icefaces.sessionTimeoutRedirectURI</param-name>
<param-value>login.jsp</param-value>
</context-param>
<context-param>
<param-name>org.icefaces.sessionExpiredRedirectURI</param-name>
<param-value>login.jsp</param-value>
</context-param>
<context-param>
<param-name>org.icefaces.connectionLostRedirectURI</param-name>
<param-value>login.jsp</param-value>
</context-param>

error showing in browser console like below :
[icefaces] the response does not contain XML data
[icefaces] Error : [status: emptyResponse code:200]: An empty response was received from the server.


Thanks
[Thumb - ICEPushTryingToRedirectOne.png]
 Filename ICEPushTryingToRedirectOne.png [Disk] Download
 Description
 Filesize 98 Kbytes
 Downloaded:  3 time(s)

 
Forum Index -> General Help Go to Page: Previous  1, 2, 3
Go to:   
Powered by JForum 2.1.7ice © JForum Team