Thanks.
A couple notes.
1. I added a try block to your fix. This is the (or at least my)
recommended way to handle db connections, as they will be returned if an
exception occurs.
2. Please submit fixes as a diff.
As has been noted these pages need to be reworked using templates. But I
did not want to leave a nasty bug in the current code.
----- Original Message -----
From: Leon Messerschmidt <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Friday, May 26, 2000 3:33 AM
Subject: Re: Funny Problem
> Hi
>
> > > > After *exactly 3* times the system freezes up.
> > >
> > > How many db connections are in the pool? If it is 3, I think you will
> > have
> > > found a possible answer.
> > >
> >
> > It seems as if one of the admin pages does not return its database
> > connection to the pool. I still trying to figure out which one :-).
> >
>
> The culprit was the EditUser.java screen. Got the answer from
> BasePeer.java - so I think I might have fixed it.
>
> EditUser.java
>
> replace
> QueryDataSet qds = new
> QueryDataSet(DBBroker.getInstance().getConnection().getConnection(),
> "SELECT * FROM Visitor WHERE visitorID = " + loginID );
>
> with
> DBConnection c = DBBroker.getInstance().getConnection();
> QueryDataSet qds = new QueryDataSet(c.getConnection(), "SELECT * FROM
> Visitor WHERE visitorID = " + loginID );
>
> AND
>
> replace
> qds.close();
>
> with
> qds.close();
> DBBroker.getInstance().releaseConnection (c);
>
> Hope this is helpful.
>
> regards
> Leon
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
