Second, in a managed environment, calling close() on a connection (handle) simply tells the environment you are done with the handle, and if it is not in use by other handles (and, possibly, not in a transaction) it can be put back in the pool.
david jencks On 2002.09.07 07:00:55 -0400 Armin Waibel wrote: > Hi Max, > > First, this was the 'old' stuff. Today or tomorrow I will check in the > 'new' code for the jboss mbean implementation and we will kick out some > unused classes. > > ----- Original Message ----- > From: "Max Rydahl Andersen" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, September 07, 2002 12:22 PM > Subject: Closing connection in J2EE code ? > > > > Hi! > > > > I just "stumbled" across J2EEStatementManager.java and found that here > you > > are calling close on a Connection! > > That is not very healthy in a J2EE environment where the Connections > are > > obtained from a Datasource and could potentially be reused by another > > client/thread, or am missing the point here ? > > I think the 'real' connection was wrapped, so if call close on the given > connection obtained from a datasource, the connection was returned to a > pool. > (Confession makes me happy: I'm not a J2EE expert ;-) ) > > regards, > Armin > > > > > /max > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
