[jboss-dev-forums] [Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

[adrian@jboss.org]

"weston.price at jboss.com" wrote : 
  | Tricky because we would effectively be asserting that we *know* how to handle this situation better than the RDBMS. Again, perhaps a config option? 
  | 

In the old transaction manager this type of thing was an optional plugin
see org.jboss.tm.integrity.*
except here we doing the integrity check for the resource usage
rather than transaction thread association.

But this is really a 1% usecase. You do still see people that
put a connection in a HTTP Session and then end up using it concurrently
when the client opens mulitple browser windows.

Obviously, this is probably broken if the servlet does setAutoCommit(false)
and it is something we could detect in the resource adapter.

Maybe this is a debug feature we could leave to the new JCA implementation?
Since it will be easier to plugin as an optional interceptor to do the extra tracking
(it requires tracking all connection, statement, result set invocations not just executeXXX).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025529#4025529

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025529