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
Hi Manoj... appreciate your response. I have an RPC request that
fetches the list from databasebefore 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
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 databasebefore I send back a response, I get
the current session and add my list as
getThreadLocal().getSession().addAttribute(attributeName,
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
I haven't faced an issue on this regard. How do you set the bean in
the session?
On May 22, 10:20 am, DK dmanchikalap...@gmail.com wrote:
I have a session attribute thats set in the session when a user logs
in (ex profile bean). once logged in, I have an RPC call to a remote
service that tries
I have a session attribute thats set in the session when a user logs
in (ex profile bean). once logged in, I have an RPC call to a remote
service that tries to pull information from this session bean and do
additional work. I noticed that a new session id was being generated
when I make the RPC
