Hi, just one followup on my posting regarding the modifications I made to allow the use of JDBCPool connection pooling. the solution is up and running but still has one ugly spot. when the JDBCPool connection manager reaps idle connections, this might conflict with EJBs accessing the connection. after a slight modification of the jdbcpool code this becomes very unlikely but not impossible, so I can only recommend that approach to people like myself who just need a quick solution, that prevents things like the "morning bug" when the database connection goes down for some reason and JOnAS is not restarted. in my tests I have not been able to produce any conflicts even with absurd settings (database connections are checked once a second if they are idle for more than two seconds, if they are, they are reopened) but your mileage may vary. I implemented this on top of JOnAS 1.4.1 for jdk1.1 (because that's what we currently use in production) but the (few) code changes should really apply to all current versions of JOnAS. Interested people can contact me for the code. my guess is that there are one or two people out there, who might find this useful but it will not influence where JOnAS connection pooling is heading as I agree with Philippe that this should really be implemented within JOnAS (by smarter people than myself) because a clean implementation must be tighly coupled with the transaction management. robert -- (-) Robert Kr�ger (-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH (-) Br�der-Knau�-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de
