"scottlong" wrote : | This makes sense, but are there other risks of using this remote datasource capability? |
Some risks, but mostly just anti-patterns (even if you ignore the crappy implementation in JBoss4 - e.g. no leasing of connections so faulty clients can leak connections) * Security - this is essentially a JDBC tunnel (remote client --> . --> database) * DOS - Client gets a connection and never returns it (deliberately) eventually leading to connection pool exhaustion * Inefficiency - using a pooled connection remotely is not efficient, co-locate the business logic with the pool (or establish the pool on the remote client) * No transaction enlistment - the remote connection does not take part in any transaction context established on the client - even a UserTransaction * etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036322#4036322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036322 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
