PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2971 *** shadow/2971 Sun Aug 19 00:26:52 2001 --- shadow/2971.tmp.14057 Sun Aug 19 05:39:48 2001 *************** *** 154,157 **** ------- Additional Comments From [EMAIL PROTECTED] 2001-08-19 00:26 ------- I have verified that this will fail with out of memory. It is not due to the ! antcalls since I ran an inlined version which also failed. Investigating. --- 154,167 ---- ------- Additional Comments From [EMAIL PROTECTED] 2001-08-19 00:26 ------- I have verified that this will fail with out of memory. It is not due to the ! antcalls since I ran an inlined version which also failed. Investigating. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-08-19 05:39 ------- ! I have done some further research. The issue appears to be related to the ! loaidng of the driver in the classloader which does not seem to be garbage ! collected. Not easy to figure that one through. ! ! In the meantime, I tried a workaround/optimisation where the drivers are cache ! based on the classpath/drivername. This prevents the out of memory error and ! also makes the creation of the connection, etc much faster. I'll probably ! commit that after 1.4 is released.
