0 Replies Latest reply: Feb 1, 2012 10:46 AM by 872274 RSS

    Soa suite 10.1.3.5 - Migration - ServerException Error - Help Required.

    872274
      Hi

      we are on Oracle soa suite 10.1.3.3 version and we upgraded to 10.1.3.5 last week. We are running on OAS.
      We are facing couple of issues here. the patch is applied properly and we are logging using file based authentication.

      Once we try to access the domains in the BPEL environment. All the domains are loaded properly but we see issues with some orchestrations in one domain only. There are few orchestrations that are not getting loaded properly and throws 'ServerException' Error.

      Following is the error:

      ServerException
      The process handle "Sample_test1" (revision "v2010_12_15__44653") has not been loaded. The process may have failed to load properly. Please use the method "getErrors" for more information.
      An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
      com.oracle.bpel.client.ServerException
      Build Information:
      *****************************************************************************
      Oracle BPEL Server version 10.1.3.5.0
      Build: 0
      Build time: Tue Aug 10 00:59:06 PDT 2010
      Build type: release
      Source tag: PCBPEL_10.1.3.6.0_GENERIC_100810.0003.2425

      Exception Trace:
      com.oracle.bpel.client.BPELProcessHandle.checkIfLoaded BPELProcessHandle.java@671
      com.oracle.bpel.client.BPELProcessHandle.getMetaData BPELProcessHandle.java@234
      displayProcess.jspService _displayProcess.java@96
      com.collaxa.cube.fe.JspPage.service JspPage.java@42
      javax.servlet.http.HttpServlet.service HttpServlet.java@856
      oracle.jsp.runtimev2.JspPageTable.service JspPageTable.java@473
      oracle.jsp.runtimev2.JspServlet.internalService JspServlet.java@594
      oracle.jsp.runtimev2.JspServlet.service JspServlet.java@518
      javax.servlet.http.HttpServlet.service HttpServlet.java@856
      com.evermind.server.http.ResourceFilterChain.doFilter ResourceFilterChain.java@64
      oracle.security.jazn.oc4j.JAZNFilter$1.run JAZNFilter.java@400
      java.security.AccessController.doPrivileged
      javax.security.auth.Subject.doAsPrivileged Subject.java@517
      oracle.security.jazn.oc4j.JAZNFilter.doFilter JAZNFilter.java@414
      com.evermind.server.http.ServletRequestDispatcher.invoke ServletRequestDispatcher.java@644
      com.evermind.server.http.ServletRequestDispatcher.forwardInternal ServletRequestDispatcher.java@391
      com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward ServletRequestDispatcher.java@280
      com.evermind.server.http.ServletRequestDispatcher.access$100 ServletRequestDispatcher.java@68
      com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun ServletRequestDispatcher.java@214
      oracle.oc4j.security.OC4JSecurity.doPrivileged OC4JSecurity.java@284
      com.evermind.server.http.ServletRequestDispatcher.forward ServletRequestDispatcher.java@219
      com.collaxa.cube.fe.DomainFilter.doFilter DomainFilter.java@245
      com.evermind.server.http.EvermindFilterChain.doFilter EvermindFilterChain.java@15
      oracle.security.jazn.oc4j.JAZNFilter$1.run JAZNFilter.java@400
      java.security.AccessController.doPrivileged
      javax.security.auth.Subject.doAsPrivileged Subject.java@517
      oracle.security.jazn.oc4j.JAZNFilter.doFilter JAZNFilter.java@414
      com.evermind.server.http.ServletRequestDispatcher.invoke ServletRequestDispatcher.java@642
      com.evermind.server.http.ServletRequestDispatcher.forwardInternal ServletRequestDispatcher.java@391
      com.evermind.server.http.HttpRequestHandler.doProcessRequest HttpRequestHandler.java@908
      com.evermind.server.http.HttpRequestHandler.processRequest HttpRequestHandler.java@458
      com.evermind.server.http.AJPRequestHandler.run AJPRequestHandler.java@313


      Can someone please suggest what we should do further to eradicate the issue? we tried to delete the 'tmp folder' in the domain path but it did not solve our problem.