----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
If I understand you correctly, you need a shared class to dole out TCP/IP
connections. This class need not be a servlet, and it can be persistent.
Then you'd just call something like TcpPool.getConnection() in your
doPost. Right? Wrong? Seems too simple.
-- Travis Low
<mailto:[EMAIL PROTECTED]>
<http://dawnstar.org/travis>
Svein Winje wrote:
>
> Hi, I am wondering (and probably, so have many before
> me) where I can find information about creating a
> "persistent" servlet that can talk to other servlets.
>
> My problem, which I may or may not be accurate in
> describing due to an imcomplete understanding of Java
> and Jserv, is that my servlet opens a TCP/IP
> connection. When it dies (I assume Jserv restarts it
> when it sees a more recent version of the class), the
> TCP/IP connection goes with it. On Sun the timeout for
> socket is around 600 seconds, which means have I have
> to wait for 10 minutes to run the servlet again.
>
> Considering what people have done with JDBC connection
> pooling, I figured it should be possible to instead
> make a shared servlet object that other servlets can
> talk to such that I don't have to kill and restart the
> class that creates the TCP/IP socket?
>
> Hoping someone is able to interpret what I am asking
> and I am simply looking for good documentation
> resources, whether on the Web or in books.
>
> Thanks,
> Svein Winje
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
