Hi! I've run into a problem after activating the prepared statement cache for my datasource (to improve performance).
The database entries are modified from an external paplication, too. So I am using "instance per transaction" with commit option B. With prepared statement caching enabled I don't get currently modified data displayed anymore until my connection drops and a new one gets created (this is, because the prepared statements are bound to the connection I think) So is this to enable the prepared statement cache for a datasource which is modified by an external application? Thanks for any help, Sven View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839312#3839312 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839312 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
