Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ConnectionException: unable to decompress response
#11
Hi Jeff,

>
I suspect the session is lost when the problem happens and therefore it is not getting any correct response from the server.
>

You mean the connection is lost. If the Session is lost then it should be recorded in the logs. Also you could have a HttpSessionListener which can be invoked when the server side session is destroyed.


>
There is one scenario we do know it which is the user close the browser or browser tab when running the application (we launch the app with jnlp).This will cause the session lost.
By the way, we already implemented the ConnectorCommandFailureStrategy which allows user to reconnect if there is connection failure.
>

Did this make it better? That means that there is a temporary network problem which is causing the issue.

>
There is one scenario we do know it which is the user close the browser or browser tab when running the application (we launch the app with jnlp).This will cause the session lost.
>

Closing the browser tab after the app has been started by JWS (jnlp) should not affect the session.

>
Currently we use SSO for authentication and do it through the browser.
Therefore the browser can not be closed when we run the application.
Do you know if there is anyway we can avoid this?
>

Let me understand your scenario:

1. You have a web page with login.
2. The user logs in and the SSO token is obtained.
3. After login a webpage is shown with ulc app's jnlp link
4. The user clicks on this link and the ULC application starts.
5. You close the browser or the browser tab containing the the ULC app's JNLP link
6. You interact with the app but it gives an error saying session is lost or terminated or the URL is wrong because it does not have the SSO token?

Is this understanding correct?

>
Can we run the application independent from the browser ?
Does that mean we have to create the login page within the ULC client and login through it rather than from browser
>

You can run the application independent of the browser. You start the ULC client in standalone mode instead of using JWS-JNLP to start the ULC client.

In case you are doing SSO, then the way to do it would be to login through browser webpage. Once the user is authenticated on the server, on the server side you can generate the jnlp file on the fly and append the SSO token to the url of the ULC application that is specified in the JNLP file.

Thanks

Janak
Reply
#12
Dear Janak

Please ignore the case about closing tab.
I realized that there is a piece of javascript which destroys the session explicitly on our side.
After that code is removed, we can run the application still after the browser is closed.

Thanks,
Jeff
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
Wink Error - Response too large to be displayed namanhem 2 4'565 11-12-2012, 12:17 PM
Last Post: janak.mulani

Forum Jump: