Bugs item #736611, was opened at 2003-05-12 19:10
Message generated for change (Comment added) made by ejort
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=736611&group_id=22866

Category: JBossCX
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: David Jencks (d_jencks)
>Assigned to: Adrian Brock (ejort)
Summary: 2 cx open at once gets ccm confused

Initial Comment:
I keep forgetting to look into this issue so I'm filing this to remind 

myself.



>From 

http://www.jboss.org/thread.jsp?forum=136&thread=30970



 I have built Jboss 3.0.7 from the latest cvs source and I am getting 

this same problem, with the "Trying to return an unknown 

connection2!" which in turn seems to result in "Successfully closed a 

connection for you. Please close them yourself". It seems like the 

problem occurs when I have more than one connection checked out 

from the pool in a transaction and close them in an unknown order. 

For example, I am able to consistently get the "Trying to return an 

unknown connection2!" stack trace to appear when executing the 

following:



try {

InitialContext ctx = getContext();

DataSource datasource = (DataSource) ctx.lookup(jndiName);

Connection conn = null;

try {

Connection con1 = datasource.getConnection();

Connection con2 = datasource.getConnection();

con2.close(); //prints "Trying to return..."

con1.close(); //works fine



con1 = datasource.getConnection();

con2 = datasource.getConnection();



con1.close(); //prints "Trying to return..."

con2.close(); //prints "Trying to return..."



conn = datasource.getConnection();

conn.close(); //prints "Trying to return..."

} catch (SQLException e) {

e.printStackTrace();

}



} catch (NamingException e) {

e.printStackTrace();

}



Also, I am obtaining/closing all connections from within a framework 

which has been well tested leading me to believe I am closing all my 

connections. When I stepped through 

CachedConnectionManager.closeAll(...) I noticed that the 

WrappedConnections that JBoss was asking me to close had their 

closed member variable set to true before JBoss called it's closed 

method. Also, these were the same connections that I had called 

closed on but had the "Trying to return an unknown connection2!" 

message appear.



Is there possibly a fix for this that has not been checked into the 3.0 

branch? Are their restrictions on getting/returning connections from 

the pool that I may not be taking into consideration?



Brandon

----------------------------------------------------------------------

>Comment By: Adrian Brock (ejort)
Date: 2003-09-15 11:17

Message:
Logged In: YES 
user_id=9459

I cannot reproduce this with jboss-3.0.9RC1

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=736611&group_id=22866


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to