Hello
I made several tests on GlassFish 2.1 about the Last Agent Optimization.
First thing, it looks like that this parameter is not taken into account, see
https://glassfish.dev.java.net/issues/show_bug.cgi?id=7262
I have just attached an EAR to reproduce this bug.
This EAR is using 3 datasources, one is an XA datasource, the two others are non-XA ones.
I configured two connection pools : the first one with javax.sql.XADatasource and the second one with javax.sql.Datasource.
I configured three JDBC Resources: the first one pointing to the first pool and the two others pointing to the second pool.
There are three resource references bound with those three JDBC Resources in the web module with the shareable sharing scope.
With that setup, I made the following test:
1) utx.begin()
2) xa.getConnection()
3) nonxa1.getConnection()
4) nonxa2.getConnection()
5) ...
6) xa.close()
7) nonxa1.close()
8) nonxa2.close()
Three cases then:
1) with the setup, I made sure that the connection retrieved from nonxa1 and nonxa2 are eligible to sharing.
But the monitoring shows me that for this test two connections have been created and retrieved.
2) I am wrong about the sharing eligibility and I have a utx with two nonxa resources.
3) The monitoring is wrong and in fact one connection only has been retrieved
Could you reproduce this ?
Or tell me how to modify all this to ensure that there is a bug or that there is none.
Thanks
Bye
[Message sent by forum member 'vkoniecz' (vkoniecz)]
http://forums.java.net/jive/thread.jspa?messageID=341185