1

The question says it. Does anybody know the answer to this? We're running into problems when 3rd-party cookies are disabled.

Robusto
  • 31,447
  • 8
  • 56
  • 77
  • I don't understand your question. What is the actual description of "Dropping"? – JeffryHouser Jul 20 '11 at 15:51
  • @www.Flextras.com: If 3rd-party cookies are disabled, calls to a RemoteObject fail with the `FaultEvent.fault.faultCode` "Server.Processing.DuplicateSessionDetected". This appears to be because the RemoteObject method call initializing the service drops the JSessionId cookie. – Robusto Jul 20 '11 at 16:43
  • So, then by "drops" do you mean that the cookie is not passed as part of the RemoteObject call? – JeffryHouser Jul 20 '11 at 17:05
  • @Robusto, are you sure it's not a server side issue? Because a 'session' is not the same as a 'cookie'. Session is unique between your BlazeDS and Flex. – J_A_X Jul 20 '11 at 17:58
  • @J_A_X: Apparently this happens from the SWF. See http://stackoverflow.com/q/6764413/271917, which hasn't been answered either. – Robusto Jul 20 '11 at 18:07
  • @Robusto, that link is this question... And even if it appears in the SWF, did you check the server logs? One cannot operate without the other and this error came from the server, hence the `Server.Processing.DuplicateSessionDetected`. I don't think you've debugged enough on both the front end and the server end. – J_A_X Jul 20 '11 at 18:23
  • @J_A_X: The front end has been debugged. I make the initialization call to the service and get a FaultEvent response. There is no code between the two that can be debugged. So it seems like the server side is what needs to be debugged, no? – Robusto Jul 20 '11 at 18:47
  • It helps to have the server side debugged, yes. I'm fairly positive it's a server issue with the session management. It would also be helpful to add the code that tries to call the server. – J_A_X Jul 20 '11 at 19:15

1 Answers1

4

If your browser does not accept cookies the application server should maintain the session using a jsessionid passed in the url. BlazeDS will be aware about that and it will also add the jsessionid to the AMF messages (and on the client it will be read and added to the other requests).

If that's the case you can check this post..there are some links to a couple of articles. If you receive the error even after reading the articles (and applying the suggestions) it would be good to create a running test case (and I can take a look on it).

Community
  • 1
  • 1
Cornel Creanga
  • 5,311
  • 1
  • 22
  • 28