There are a few entries on the wiki that describe accessing JBoss datasource remotely via JNDI from external JVMs. They all describe this capability, experimental, not recommended, etc.
e.g. this one: http://wiki.jboss.org/wiki/Wiki.jsp?page=HowCanIAccessADataSourceFromAClient says: anonymous wrote : Note: Exposing a Datasource remotely is NOT recommended. and this one: http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources says: anonymous wrote : JBoss does not recommend using this feature on a production environment. The one specific risk listed is that if the client dies (or fails to close connections), it will cause a connection leak. JBoss is not going to try and detect the client's death and proactively clean up for the client. This makes sense, but are there other risks of using this remote datasource capability? I am talking in terms of JBoss 4.0.5. thanks! - scott View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035989#4035989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035989 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
