OLD FORUM - Use new one: https://www.CaptainCasa.online/forum

Hello!

We have tried to implement a Log Off Button. Like in the Demo Workplace...

Code:

  public void onButtonPressedLogOff( ActionEvent ae )
     {
         getWorkpageContainer().closeAllWorkpages( false, new Runnable()
         {
             public void run()
             {
                 HttpSessionAccess.getCurrentHttpSession().invalidate();
             }
         } );
     }

After pressing this button a error page is shown. Server Side Error

Code:

 java.io.IOException: Server returned HTTP response code: 500 for URL: <a href="http://localhost:8080/antos-1.0/faces/jsp/workplace/surroundingpage.jsp;jsessionid=a159facae14cd3af0c38da63cd9e" target="_blank" rel="nofollow">http://localhost:8080/antos-1.0/faces/jsp/workplace/surroundingpage.jsp;jsessionid=a159facae14cd3af0c38da63cd9e</a>
 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
 	at org.eclnt.client.comm.http.DataTransfer.transferXML(DataTransfer.java:692)
 	at org.eclnt.client.comm.http.DataTransfer.communicateToServerSynchronous(DataTransfer.java:217)
 	at org.eclnt.client.page.Page.transferDataRun(Page.java:1021)

Does someone have an idea what could be wrong?
Kind regards,
Daniel

...will check.

I remeber, that you are using Glassfish. We'll test with the most current version, if you have a specific version that you prefer, pls tell us.

Regards, Björn

current version is fine...

Regards,
Daniel

Hi,

for whatever reason, Glassfish does remove all http-response-header parameters for the response, in which the session was invalidated!!! One of them "eclnt-reload" is indicating to the client to internally re-start with a new session.

This seems to be a Glassfish Bug.
We'll check if we can do a bypass on our side...

Regards, Björn

Hi,

end of analysis: it's not the response header parameters that are missing - it's the whole response that is returned as 500-repsonse.

Björn

Code:

 Glassfish:
 HTTP/1.1 500 Internal Server Error
 eclnt-reload: true
 Content-Encoding: gzip
 Content-Length: 236
 
 Tomcat:
 HTTP/1.1 200 OK
 Server: Apache-Coyote/1.1
 X-Powered-By: JSF/2.0
 Set-Cookie: JSESSIONID=9A7B15EB755C2B4E6A902514F506AB09; Path=/demos; HttpOnly
 eclnt-reload: true
 Content-Encoding: gzip
 Content-Type: text/html;charset=UTF-8

...and the end of the story is: we now check returned header parameters also in the error case ("500") on client side.

Or, in short words: it now works, also with Glassfish... - the change is part of the next regluar update, or earlier on your request.

Thanks for your input +
Regards! Björn

Thanks for the quick solution!
Regards,
Daniel