-
1. Re: connection.close()
juhalindfors Jul 29, 2003 4:36 PM (in response to sysuser1)Does it help if you close the statement before you close the connection?
-- Juha -
2. Re: connection.close()
sysuser1 Jul 31, 2003 12:01 PM (in response to sysuser1)No idea. The connection is passed on to another api that actually does the statement thing and that is out of my control.
-
3. Re: connection.close()
darranl Aug 1, 2003 7:25 AM (in response to sysuser1)Which JBoss version are you using?
-
4. Re: connection.close()
frito Aug 1, 2003 8:44 AM (in response to sysuser1)Perhaps it could help to toggle the spec-compliant flag in your transaction-service.xml .
Greetings,
Frito -
5. Re: connection.close()
jefferykim Aug 6, 2003 7:35 PM (in response to sysuser1)no, I tried to set it as true, it does not help. Any other idea? Or is there any patch for download?
thanks -
6. Re: connection.close()
darranl Aug 7, 2003 2:26 AM (in response to sysuser1)Which JBoss version are you using?
-
7. Re: connection.close()
sbahal Aug 18, 2003 7:50 AM (in response to sysuser1)I have the similar problem. I use DB2/AS-400 on JBoss- 3.0.7.
I have a BMP. If I call a method in my EJB this methos gets its own Connection. But if this method calls a 2nd method that gets its own Connection and then if the 2nd method tries to close() the Connection- I get this error '... trying to return a unkown connection to JBoss... blah blah blah ...... try to close your own connection.....blah blah blah.
But if I pass the Connection (as obtained in the 1st method) to the 2nd method (so it does not have to get its own)- all works well.
Is this some kind of known behavior?
Thanks
Sanjay -
8. Re: connection.close()
darranl Aug 19, 2003 4:03 AM (in response to sysuser1)I had the same issue with JBoss 3.0.7, from what I can remember it was raised as a bug on sf.net and fixed for 3.0.8.