Weblogic problem,weblogic.rmi.extensions.RemoteRuntimeException: Unexpected

Question

hello，everyone.
I have a problem.please help me.
My application is running on weblogic 9.2. My oracle is oracle10g. system:linux redhat4.
my weblogic's log have a problem.
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:109)
at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
at com.goldpalm.sale.team.TeamXml.exeTeamLog(TeamXml.java:762)
at jsp_servlet._ctssale.__teamline_show._jspService(__teamline_show.java:264)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:230)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at filters.AuthFilter.doFilter(AuthFilter.java:95)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3200)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1844)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Answer 1

Hi
Looking at the error stack trace, you are getting this error when trying to close the statement object from your own java code (not weblogic code...) - DBController.releaseConn(...)
at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:109)
at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
at com.goldpalm.sale.team.TeamXml.exeTeamLog(TeamXml.java:762)
Well check the code you have at this location. Usually the way we release/close the db resources are like first close ResultSet, then Statement, then Connection. But if you close connection first, then try to close the Statement object, it throws errors like what you see.
I am giving 2 methods code snippet. One method is caleld like closeAll(..). This method gets called in finally block of all other db methods that does the actual db code to connect and get data etc etc.
// Sample main method that does all db stuff...This is just code snippet only and NOT the full code. Focus on try catch finally block
public static void getCustomerProfile(long custId) throws Exception {
     Connection aConnection = getConnection();
     CallableStatement aCallableStatement = null;
     ResultSet aResultSet = null;
     try {
          aCallableStatement = aConnection.prepareCall("{ call someFunction(?, ?) }");
          aCallableStatement.execute();
          aResultSet = (ResultSet) aCallableStatement.getObject("variable_name_from_sp");
          while(aResultSet.next()) {
               // get all data for each record etc...
     } catch (Exception e) {
          e.printStackTrace();
          throw e;
     } finally {
          closeAll(aConnection, aCallableStatement, aResultSet);
// While closing RS, Statment, Connection, enclose them in their own try/catch block and ofcourse check for nulls first
public static void closeAll(Connection aConn, Statement aStmt, ResultSet aRS) {
     if (aRS != null) {
          try {
               aRS.close();
          } catch (Exception e) {
               System.out.println("Not Able To Close The ResultSet");
               //e.printStackTrace();
     if (aStmt != null) {
          try {
               aStmt.close();
          } catch (Exception e) {
               System.out.println("Not Able To Close The Statement");
               //e.printStackTrace();
     if (aConn != null) {
          try {
               aConn.close();
          } catch (Exception e) {
               System.out.println("Not Able To Close The Connection");
               //e.printStackTrace();
}Thanks
Ravi Jegga