The way I use middlegen in our build is 1. Create a temporary database user 2. Create tables 3. Run middlegen 4. remove the temporary database user.
This is to ensure that the concurrent builds do not conflict. Whenever middlegen encounters a problem reading the tables, ( if the specified tables donot exist), I get an database error ( user is still connected ) when I try to remove the user. It seems that middlegen does not close the database connection when it encounters an error. I looked at the code MiddlegenTask.java: execute() and it seemed like there could be a case where the connection may not be closed. I agree that this is not a major issue as the problem does not occur for most users and only ocurs when there is an error. Let me know if my analysis is correct, I could submit a patch. Thanks Dinesh ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ middlegen-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/middlegen-user
