Originally posted by Graeme Brown:
The normal way to do this would be by using Websphere's in-built facilities. Why are you having to hard code your own way of doing this?
It looks likely that you are getting synchronization problems with Websphere trying to do it's own thing.
yes i know but the automatic session saving doesnt work for my case.
it saves the session AFTER the service method but in may happen that the servers switch BEFORE that and the session values are useless.
thats why i need a manual hard coded saving procedure.
the automatic saving has been switched off.
Vijaya