Strange JDBC errors? Possible session management issues - any pointers?
Hi,
I'm a technical analyst with a payment processing company, and have been asked to investigate why an application of ours keeps crashing out daily, due to basically too many open connections into an Oracle database. The app gets a lot of traffic, and is hosted in Jrun. Its written in JSP, which I'm not an expert with but I'm learning quickly! I have some concerns about session management within the code between oracle, and our payment gateway (which has its own API), and was wondering what you think my throw the numerous errors we get below (constantly!)
DaonBean hasMoreTransactionData Exception :java.sql.SQLException: ResultSet.next was not called
DaonBean hasMoreCustomerDetails Exception : java.sql.SQLException: Exhausted Resultset
DaoBean could not close: java.sql.SQLException: This Connection has either timed out or been closed, and it has returned to its pool. You must re-acquire the Connection.
DaoBean locateTransUsingUserID Method Exception : java.sql.SQLException: This Connection has either timed out or been closed, and it has returned to its pool. You must re-acquire the Connection.
DaonBean hasMoreCustomerDetails Exception : java.sql.SQLException: Closed Resultset: next
Related to card payment processing:
java.lang.IllegalStateException: Session is invalid
java.lang.IllegalStateException: Session is invalid
java.lang.IllegalStateException: Session is invalid
java.lang.IllegalStateException: Session is invalid
DaonBean hasMoreCustomerDetails Exception : java.sql.SQLException: Exhausted Resultset
DaoBean could not close: java.sql.SQLException: This Connection has either timed out or been closed, and it has returned to its pool. You must re-acquire the Connection.
Do these type of errors suggest initially a fundamental issue, or does nothing immediately stand out? The code base changes frequently, and since some new payment methods were updated, the application have become very unstable.
Hope you can advise any initial thoughts!
Kind regards,
Scott.
