We also have _some_ problem with SOAP Sessions, which are terminated a little bit by random. Even if we keep doing a dummy call every now and so often (1min), it happens that a new session is created. This is leading us to not trust Session, and are planning to introduce our own session handling on top of SOAP instead of under SOAP. This will also have the benefit that we control the time out, and can choose to have it to hours and/or days, letting people completely shutdown their system and come back later.
Niclas On Monday 26 August 2002 13:59, Rafi M M wrote: > Hello > I tried to use Apache SOAP rpc call to access the classes(running in a > remote server) which in turn connect to the database and perform the > database operations.I deployed the service in a Apache TomCat Server while > making the scope as "Session".. It was required to maintain a single > database connection for different method invocations for a particular > session..The client classes were running in my machine. When testing the > thing inside a local network,it worked smoothly without any problems and I > could maintain a single database connection variable over different method > invocations for a single session.. But when I run the server in a very > remote machine, for each rpc method call, the constructor of the server > class(which is the deployed service) is called and a new databse connection > is made for the session..Thus for each method call within one single > session, a new database connection is used...I don't know why it > happens..Is it due to session timeout? I would be great if anyone you can > provide a solution to the problem.. > > regards > Rafi -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
