First of all - you should be using a nightly snapshot.
Then look into the <validation> element and provide the plugins needed (MySQL), and do <flush-strategy>IdleConnections</flush-strategy>
If you still have errors after that I would need to see TRACE log from org.jboss.jca and your full configuration.
I will test it with the nightly snapshot, but I have been using the validation plugins and the flush strategy. I'll let you know what happens with the snapshot.
I am going to test with 1.0.13.Final, 1.1.0.Beta3, and then if those don't work, I can try the head version (is there a repository with nightly builds or should I just build it myself).
My question is which version of jboss are those built against. When I used 1.0.13.Final, I am getting this error:
Caused by: java.lang.ClassNotFoundException: org.jboss.jca.common.api.metadata.ds.DataSource$Tag from [Module "org.jboss.as.connector:main" from local module loader @538d7ace (roots: /usr/java/jboss/modules)]
so I will update the org.jboss.as.connector module, but I want to make sure I am using the correct version.
Thanks for your help. I really appreciate it.
IronJacamar 1.1 is for EE 7.
AS7/master already contains IJ 1.0.13... so you just need the latest nightly snapshot
I had the same issue with the latest jboss snapshot: jboss-as-7.2.0.Alpha1-SNAPSHOT
The trace is attached.
My datasource config:
<datasource jta="true" jndi-name="java:jboss/datasources/atDS" pool-name="MySqlDS" enabled="true" spy="true" use-ccm="true">
tmp.log.zip 55.2 K
I'm not seeing anything here. If you only have 1 connection available, then requests will timeout.
Thanks for looking into this.
When you say the requests, are you referring to the requests for a connection?
When mysql shows the connection as sleeping, but we still get the error, unable to retrieve managed connection, does that mean something is holding on to the connection?
You have <max-pool-size> at 1 - it doesn't matter how many the connections the database is configured for.
Your log shows that the app gives up after 30 seconds to get a connection, which is default.
Your prefill at true doesn't do anything, since your <min-pool-size> is 0.
Very true, the prefill is left over from other configs -- useless in this test.
I did try increasing the blocking-timeout (default 30), but it just waits longer to timeout.
It seems stable and working with the increased number of connections. I am curious about that one connection, but it's ok for now.
Thanks for your help.