can you provide a test case for this? If you can someone will fix it. m
-----Original Message----- From: Joe Germuska [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 11, 2002 10:26 AM To: [EMAIL PROTECTED] Subject: unexpected connection pool destroyObject? I'm using OJB 0.9.5. I have a process where I get an iterator and walk through its items (to make a report). Recently, my reports began coming up short, and on closer inspection, it seems to be because of this: 9127 [main] ERROR accesslayer.ConnectionFactoryConPooledImpl - Destroy object was called, try to close connection: oracle.jdbc.driver.OracleConnection@5749de As a work around, I switched to "getCollectionBySql" instead of "iteratorBySql", and this does give me the complete collection; however, destroyObject is called four times (in a list of 118 items). I'm not blaming OJB here, but I'd really rather use an iterator than a Collection; can anyone suggest things I might look at to understand why this problem has suddenly come up? Is it something to do with network communication between my application machine and the database machine? I've set the logging threshold for OJB all the way down to DEBUG, and I don't see any new messages which seem related to this issue; anyplace else I should go looking for info? Thanks in advance, Joe -- -- * Joe Germuska { [EMAIL PROTECTED] } "It's pitiful, sometimes, if they've got it bad. Their eyes get glazed, they go white, their hands tremble.... As I watch them I often feel that a dope peddler is a gentleman compared with the man who sells records." --Sam Goody, 1956 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
