I am sorry to disagree with you: You are right that the connection should have been released in the finally block, but I want to point out that this is not my code, but the Duke's Bank sample application referenced by the JBoss 4.0 Starting Guide.
Unfortunately I did not mark the part of the stack trace I think the real problem was, which is: 2005-01-04 04:00:44,107 ERROR [org.jboss.ejb.plugins.LogInterceptor] EJBException in method: public abstract com.sun.ebank.util.AccountDetails com.sun.ebank.ejb.account.Account.getDetails(): javax.ejb.EJBException: ejbLoad: [interclient] Unsupported feature: Using a JDBC 2 method which is not yet supported. See API reference for exception interbase.interclient.DriverNotCapableException at com.sun.ebank.ejb.account.AccountBean.ejbLoad(AccountBean.java:213) This problem was solved by moving to getLong() from getBigDecimal() in loadAccount() method. I see this was the route cause of the problem, the missing releaseConnection was a side effect of SUN's messy programming style. However, I still don't understand the mechanism how this change of JDBC calls could solve the issue. Regards, Tamas View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860996#3860996 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860996 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
