0 Replies Latest reply on Nov 21, 2011 4:34 AM by Koushik C

    Session problems after deploying the Jav/FLEX-BLAZEDS 4.0 application on server.

    Koushik C

      Session problems after deploying the Jav/FLEX-BLAZEDS 4.0 application on server.

       

       

      Problem details

      ****************************************************************************************** *********************************************************

      We are having the swf file embedded in a Java struts web application. There is a link in the web app which launches the swf file and displays a dashboard. When we login to our app, a session (with Jsessionid) is created and we can browse through the app and access other links (except the link that launches the swf). Everything seems fine up till this. Once we click on the link that launches the swf file, we get an error for DuplicateSessionDetected in the log. Also, after this, when we click on any other link in the web app, it logs out the user from the app saying - the user session has expired. WE ONLY GET THIS ISSUE IN THE DEV2 (CLUSTERED ENVIRONMENT). EVERYTHING IS WORKING PERFECTLY IN OUR LOCAL MACHINES!!!

       

      Our deployment environment is:

      ****************************************************************************************** *********************************************************

       

      OS: Windows

      Application Server: Websphere 6.1, Clustered with 2 nodes.

      JRE: 1.4

      Flex: 4.0

      BlazeDS 4.0.1

       

      When the swf loads, there are 2 BlazeDS calls happening. The first call is happening and returning the result. When making the second call, we get "DuplicateSessionDetected" error in the log.

       

       

      We have checked the logs. Something like this happens -

      ****************************************************************************************** *********************************************************

       

      In the clustered environment, BlazeDS is creating a new Flex session of its own and invalidates or overwrites the existing Http session(Which has all the user credentials) and as a result the user is logged out. Again, This doesnot happen in our local machines.

       

      Can you please let us know

      ****************************************************************************************** *********************************************************

       

      1) Is there any way to prevent BlazeDs from creating a new Flexsession and force it to use the existing Httpsession? I tried to pass the jsessionid using flashvars to the swf and then appending the jsession id to endpoint URL. But that is giving an error. If this approach works, can you please let me know how exactly are we supposed to pass the jsession id from mxml so that a new session is not created.

       

      2. Have u ever experienced such problems while deploying flex apps  with BlazeDs?? Also, can u please give us some older versions (preferably BLAZEDS 3.2)so that we can determine if the problem is with the BlazeDS 4.0 JARs??

       

       

      3) Also, do we have to make any specific configuration changes/ settings for using BlazeDS in clustered environment? As this problem is not happening in our local environment, but when we deploy our code in clustered environment.

       

      We are looking forward to your expert advice on this. Thanks in advance!