That's an interesting problem, and I hope someone offers a response to it. Can I ask, on a different topic, where you were able get access to the bug report? That would be interesting reading, I'm sure. Is it available publicly somewhere?
/charlie -----Original Message----- From: Paap, Keith [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 4:59 PM To: JRun-Talk Subject: AutoCommit bug with Connection pool I posted this in the support forum and am also sending this out to the mailing list in case anyone has any suggestions. There is a problem getting the autocommit status set to false in JRun 3.1 (Bug 27034) After attempting to call a rollback() or commit() on the connection the following exception is thrown: java.lang.UnsupportedOperationException: Operation disallowed on pooled connections;at allaire.ejipt._ejb._Connection.commit(allaire/ejipt/_ejb/_Connection.java:26 5) Digging a little further into the problem report it appears as though the problem lies in the ability to setAutoCommit to false. It remains true at all times. The bug report status shows as closed and the severity is listed as a benign bug with a workaround. However no workaround is provided. Please let me know if anyone is aware of how I could implement a workaround. The response on the bug report states the following: "This is because the ejipt doesn't implement autocommit in allaire/ejipt/_ejb/_Connection.java. However, Jrun does implement the autocommit in allaire\jrun\sql\ConnectionProxy.java. I did a quick modification to _ejb/_connection.java (copied the implementation from ConnectionProxy.java, and ignored the exception msg). The code is messy, and it take long time to execute, but it works. I am putting the code under \\uscamfilp003\rdpublic\Bugs\27034 in case some one want to look at it." There is no mention of this fix being incorporated in any hotfix or future releases of JRun. This creates a problem since there are a number of business needs to be able to control the autocommit status of a connection. Based on the earlier posts in this thread, this was not a problem in JRun 3.0. Our next step will be to attempt to set up a 3.0 server and retest this code to see if we can continue with development. Other options might be to go so a separate pooling process by a 3rd party (JTurbo, others?). If anyone has any other suggestions please share. TIA Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
