-
1. Re: JBoss 2.4.8 datasource pool size problem
davidjencks Sep 5, 2002 9:11 PM (in response to kenneth)Are you sure that you copied that right? it looks to me as if you have mixed two mbeans together.
I rewrote a lot of the pooling code and some of XADataSourceImpl in 2.4.8 so it was somewhat thread safe and the pool hands out connections in order. I don't know why the behavior you are seeing would have changed. Does the mvcsoft code use autocommit??
I thought the jdbcdatasourceloader mbean took a driver class as an attribute and don't know how it would work if given an XADataSource implementation.
Are the connections being closed? -
2. Re: JBoss 2.4.8 datasource pool size problem
kenneth Sep 6, 2002 5:14 AM (in response to kenneth)David
Which part of the descriptor seems wrong to you? Could you post an example of what you would consider a correct setup for a JDBCDatasource please? I based my config on the MVCSoft documentation, viewable here:
http://www.mvcsoft.com/documentation/PersistenceManager11.pdf
Specifically, page 77.
Looking at the MVCSoft code, it doesn't change the autocommit setting. It just gets a connection from the datasource, uses it, and closes it in a finally block (it doesn't explicitly call conn.commit() though).
Thanks
Kenneth -
3. Re: JBoss 2.4.8 datasource pool size problem
psjoe Oct 4, 2002 11:15 AM (in response to kenneth)All,
I'm getting the "No Managed Connections" error a well. My DataSource is geting bound properly. It is bound to the name my ejbs are looking for. Any clues anyone? I'm using 2.4.9.
[INFO,org.jboss.jdbc.JDBCDataSourceLoader] Starting
[DEBUG,org.jboss.pool.jdbc.JDBCConnectionFactory] Starting
[DEBUG,org.jboss.pool.ObjectPool] Adding pool: ALCDataSource, GC enabled: false
[INFO,org.jboss.jdbc.JDBCDataSourceLoader] JDBC Connection pool ALCDataSource bound to java:/ALCDataSource