Actually that's not quite right. Special resources (i.e. those that
shouldn't/can't be used concurrently by multiple threads) need to be managed
to control their usage. Generally a Singleton is used to control access
(either by giving out multiple copies, like Database connections, or by
preventing the requesting thread from executing, like File I/O).
While using a Servlet is a generally accepted way of doing this, its
not the only way, or necessariy the best way depending upon your
application.
Randy
-----Original Message-----
From: William Brogden [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 06, 2001 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: threading issues with tomcat
Byrom Robert-LRB005 wrote:
>
> thanks for the help,
>
> one further question, if I initialise a Database connection within the
init() method of a servlet and use this reference in the doGet() for
example, will each servlet share this connection object? ie if more than one
servlet requests the same connection would this result in a runtime
exception?
>
Resources such as DB connections have to be specially managed
servlets to ensure that only one Thread is using a connection
at one time. Look for recent discussions of connection pools
in this mailing list.
--
WBB - [EMAIL PROTECTED]
Java Cert mock exams http://www.lanw.com/java/javacert/
Author of Java Developer's Guide to Servlets and JSP
ISBN 0-7821-2809-2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
