Rafi,
To help investigate this, the following would be useful:
1. Versions of software used (Apache SOAP, Tomcat, JVM, etc.) for both LAN
and WAN scenarios. Also, does your WAN connection go through a proxy.
2. Capture (e.g. using TcpTunnelGui) of a pair of messages that you expect
to be in a single session in WAN scenario. If you have not used
TcpTunnelGui before, it is invoked like
java org.apache.soap.util.net.TcpTunnelGui 81 host port
In this case, it would listen on localhost:81 and forward messages to
host:port. You would point your client to localhost:81, e.g. an endpoint
URL of http://localhost:81/soap/servlet/rpcrouter.
Scott Nichol
----- Original Message -----
From: "Rafi M M" <[EMAIL PROTECTED]>
To: "soap developers" <[EMAIL PROTECTED]>
Sent: Monday, August 26, 2002 1:59 AM
Subject: maintaing single db connection over multiple rpc calls
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]>
