By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 985 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

OC4j and abnormal exit of stm.executeQuery

P: n/a
Good Morning,
I've a Servlet with inside the doPost() method a connection to a dB,
the problem is that is a long query that work ok if launched on the dB
with something like TOAD and also works well on (JbuilderX + Tomcat)
environment but when deployed on OC4j it happens that during the
execution of
rs = stm.executeQuery(sSQL);
something appens and the result is that the execution go out of the
doPost() without passing for the catch() or the finally(), after this
the servlet is recharged again.
I can't not figure what is happening, could you help me ???

Antonio D'Ottavio
P.S. : Here's the code :
ResultSet rs = null;
Statement stm = null;
Connection connR = null;
try {
sSQL = getSQLSelect();
connR = DriverManager.getConnection();
stm = connR.createStatement();
rs = stm.executeQuery(sSQL);
System.out.println("WebStampaRERO - after executeQuery" );
catch (Exception ex) {
System.out.println("WebStampaRERO - inside exception" );
finally {
System.out.println("WebStampaRERO - dentro finally" );
if (rs != null) {
try {rs.close();} catch (Exception ex) {}
if (stm != null) {
try {stm.close();} catch (Exception ex) {}
if (connR != null) {
try { connR.close();} catch (Exception ex) {}
System.out.println("WebStampaRERO - dopo sendTemplate" );
Jul 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.