Hi,
On Mon, 28 Jun 1999, Steven J. Owens wrote:
...........
>
> > -Are we really sure a servlet could not hang the JVM that in its turn would
> > hand the OS?
>
> I'm not sure at all :-). Java's design mandates a very clean
> handling of memory, but I'm well aware of memory leak possibilities.
> God knows what else is out there; "I am but an egg" in the java
> programming world.
I found such problems but they werent servlet or jvm specific - rather
JDBC problem:
When I use several database connections through pool (let it be "Pool1")
in some applications, and try to open a new pool at a new datasource,
(Pool2) in other application, when this last one (Pool2) cant open
connection (for any reasons - e.g. the server is down), the whole
JDBC stuff (including already opened connections) seem to be frozen,
until the Pool2 connection either succeeds or times out.
Could not figure yet if the problem was in JDBC code,
the JDBC drivers I use or the connection broker.
Makes me feel many JDBC driver writers or even JDBC itself does not
allways handle well multi-user/tasking, with potential many parallel
connections - as a servlet environment might require.
Cezar.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
