-
15. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:30 PM (in response to adrian.brock)CachedConnectionManager
Added methods to view unclosed/inuse connections in the management console. -
16. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:32 PM (in response to adrian.brock)JDBC Resource Adapter
Don't log the password when debugging. -
17. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:33 PM (in response to adrian.brock)JMS Resource Adapter
Backport improved JmsRA from head.
The fixes include:
1) No need to explicity close sessions/receivers/producers
they are tracked by the connection
2) Implemented methods that were previously disallowed
Most importantly start() should be invoked when you are receving
messages.
3) Disallowed methods that shouldn't be allowed on the server
This includes disallowing more than one session for a connection
on the server.
4) Allow a configured client id
Use JmsManagedConnectionFactoryNonStrict in the ra.xml
of jms-ra.rar if you want the old behaviour. But this is really intended
for application client usage.
The backport does not include support for JMS1.1 -
18. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:35 PM (in response to adrian.brock)JDBC Resource Adapter
Wrap results sets so we can trap
ResultSet.getStatement()
Also, track unclosed ResultSets in the statements when <track-statement> is true.
This helps point out a common error when using prepared statement pooling. -
19. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:36 PM (in response to adrian.brock)Move track-connection-by-tx inside the pool. This avoids
it overridding other pooling considerations.
Fixes bug 648442
http://sourceforge.net/tracker/?group_id=22866&atid=376685&func=detail&aid=648442 -
20. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:40 PM (in response to adrian.brock)Bug Fix:
Moving the track-connection-by-tx to the pool caused a bug where the connection
was getting suspended, fixed. -
21. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:41 PM (in response to adrian.brock)Bug FIx:
Remove the local transaction checks from the TxConnectionManager they are not correct. -
22. Re: Change Notes: 3.2.4
adrian.brock Apr 13, 2004 4:42 PM (in response to adrian.brock)Bug Fix:
We need to register a synchronization even when not doing track-connection-by-tx.
For user transactions we must "delist" the connection as the connection may not
have been closed and could be used again after the commit. -
23. Re: Change Notes: 3.2.4
adrian.brock Apr 19, 2004 8:09 AM (in response to adrian.brock)Bug Fix:
DTD fixes to <track-connection-by-tx/>, <track-statements/> and <set-tx-query-timeout/>
which take no text node and corresponding fixes to the example configs. -
24. Re: Change Notes: 3.2.4
adrian.brock Apr 19, 2004 3:24 PM (in response to adrian.brock)Add additional TRACE logging to the pooling
-
25. Re: Change Notes: 3.2.4
adrian.brock Apr 19, 2004 3:25 PM (in response to adrian.brock)Bug Fix:
Shutdown the flushed/discarded internal managed connection pool, otherwise the
pool filler could refill it with connections that are unreachable - a connection leak
See Bug#938010
http://sourceforge.net/tracker/?group_id=22866&atid=376685&func=detail&aid=938010 -
26. Re: Change Notes: 3.2.4
adrian.brock Apr 19, 2004 3:26 PM (in response to adrian.brock)Workaround:
Use a SynchronizedBoolean rather than a volatile for the shutdown state,
some VMs do not implement volatile correctly. -
27. Re: Change Notes: 3.2.4
adrian.brock Apr 21, 2004 12:42 PM (in response to adrian.brock)Bug Fix:
Show 0 for stats rather than NullPointerException when the pool is not in the
started state. -
28. Re: Change Notes: 3.2.4
adrian.brock Apr 23, 2004 12:26 PM (in response to adrian.brock)Regression:
Allow the transaction isolation to overridden inside a manged transaction.
Leave it to the db to decide whether this is legal. -
29. Re: Change Notes: 3.2.4
adrian.brock Apr 26, 2004 4:22 PM (in response to adrian.brock)JMSRA:
Use the application's connection request info rather than the values on the underlying XASession.
Report IllegalStateExceptions when wrapping XASession to avoid implementation specific exceptions leaking to the application.
Remove the NonStrict version of the JMS ManagedConnectionFactory and replace it with an MCF property.
The first two modifications coupled with a change to JBossMQ
make the connection factory java:/JmsXA useable
outside a JTA transaction. It behaves like Auto_Acknowledge