Hi. I believe you are right. Using a HTTP sniffer such as Charles to look at the HTTP headers would tell us exactly what is happening but I think we can assume that you are in the ballpark.

If the server gets a request with no session cookie header, I think it will create a new session and then send a Set-Cookie header on the response with the new session id. It is likely that if both your apps are making their initial requests to the server at roughly the same time that neither of the requests has a session cookie header. In that case the server is probably creating two sessions, one for each request and that is likely causing problems.

While I haven't tested this particular scenario, I have been doing some testing around session cookie handling in BlazeDS recently. I would see if you can workaround this problem by already having a HTTP session established with the server before either of your apps runs. One way to do this would be by having a jsp page redirect to your welcome page. The call to the jsp page would cause a session to get created on the server. The server would return a Set-Cookie header with the new session id. The browser would then request the welcome page sending a session cookie header on the request. Your apps would load. Each app would make its initial request to the server only this time the requests would contain a session cookie header for the same valid HTTP session. . . and you would avoid getting duplicate session detected errors. . . at least that's I hope would happen.

If I have some free time I will try running through this scenario (having two small apps on the same page) and report back.

Hope that helps.

-Alex

Vamshi,

In my situation i had only one flex app in the page.

To avoid getting the error i first did a created a HttpService Request to the server(in my case i requested for the version).

After i got the response for that request i ustarted using RPC using Blaze DS.

Thanks,

Anil

Hi Vamsi,

You are right.

I define a dummy servicve as you did.

Then i made an actual call in creation complete.

In your case it would be:-

photoService.send();

After you get a response ffor the above send you can start RO calls.

That works for me.

Thanks,

Anil

Hi. For anyone who is still interested in the duplicate session detected errors problem I have blogged about it here and proposed some workarounds.

http://www.alexglosband.com/?p=3

-Alex