Thanks for your reply Michael. I could buy into that argument if I had
multiple resin servers on the server side. We only have one. It should
not cause multiple sessions to be created. Also ... I do see the
following code in the resin.conf file for session management :
<!--
Renamed from JESSESSIONID to avoid issues with Dynamo.
-->
<session-cookie>RJESSESSIONID</session-cookie>
Could this be the issue ?
--DK.
On May 24, 5:05 pm, Michael W <mwang_2...@yahoo.com> wrote:
> Cookie session is set when the page is finished rendering/parsing.
>
> In your case, the second RPC is executed before you get full page, so
> session cookie is not set. Your load balancer will route your request
> to another resin server.
>
> It works locally because you may have only one instance in your
> local.
>
> On May 24, 12:15 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
>
> > On 24 mai, 17:21, DK <dmanchikalap...@gmail.com> wrote:
>
> > > Hi Manoj... appreciate your response. I have an RPC request that
> > > fetches the list from database....before I send back a response, I get
> > > the current session and add my list as
> > > getThreadLocal().getSession().addAttribute("attributeName",
> > > activityList); .... inside the onSuccess() method, I am making another
> > > RPC call that does some more processing on the server side,...I am
> > > relying on the session attribute previously set. However, I am getting
> > > a new session when I try to get the session attribute using --
> > > getThreadLocal().getSession().getAttribute("attributeName").... I did
> > > notice that it does not happen locally when I deploy it on a resin
> > > server .... I feel that some session config on the server could be the
> > > reason for not counting the jsessionid that comes back with RPC
> > > payload.
>
> > Try making your second call from outside the onSuccess (just use a
> > DeferredCommand or the Scheduler), it might be that the browser has
> > yet put the cookies sent by the server in its cookie store so it
> > doesn't send them back with your second RPC (that wouldn't explain why
> > it works with your local resin server though).
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to google-web-tool...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-toolkit+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group
> athttp://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
