11 Replies Latest reply: May 2, 2012 1:31 PM by Arik RSS

    Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.

    Levey_Baskar
      Application Server: OK
      BPEL Process Manager Server: FAILED
      ESB Server: OK


      Verified and tried below steps:

      1. hw_services and orabpel and deploy_services are up and running
      2. Jdeveloper and Oracle SOA Suite Version is 10.1.3.4
      3. Tools->Preferences -> Web Browser and Proxy is disabled.
      4. Restarted hw_services and orabpel via Application server control for OC4J_SOA > hw_services/orabpel
      5. Able to connect the bpel process manager(BPELConsole) from Browser.
      6. But Not able deploy using ant tool as well as with Jdev Deploy option(no domains are displayed under deploy option in Jdev)
      7. Ant deployment throws error,
      A problem occured while connecting to server "testinstance.com" using port "7777": <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      <HTML><HEAD>
      <TITLE>404 Not Found</TITLE>
      </HEAD><BODY>
      <H1>Not Found</H1>
      The requested URL /integration/services/deploy/deployHttpClientProcess.jsp was not found on this server.<P>
      <HR>
      <ADDRESS>Oracle-Application-Server-10g/10.1.3.4.0 Oracle-HTTP-Server Server at testsoa.art.com Port 7777</ADDRESS>
      </BODY></HTML>


      Went thru many threads under soa/bpel forums and couldn't find it worked.

      Appreciate your help
        • 3. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
          Arik
          Can you please stop and start the "hw_services" under OC4J?
          See if it helps please.
          If not, can you post the parameters you've put in the Application Server Connection?

          Thanks
          Arik
          • 4. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
            Levey_Baskar
            Application Server Connection:

            Connection Type: Oracle Application server 10g 10.1.3
            Authentication Username: oc4jadmin
            Connection:
            connect To: Single Instance(radio button)
            Hostname : testinstance.com
            opmn port : 6003
            oc4j instance name:oc4j_soa


            Problem still exists even after the restart of hw_services under oc4j_soa instance via oracle enterprise manager.

            Appreciate your help
            • 5. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
              Arik
              Ok.
              Did you manage to have successful test on 'Application Server' connection?
              When you Test the 'Integration Server' you have a 'Details' button. Press it and see what is the log.

              Arik
              • 6. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
                Levey_Baskar
                Application Server Test     Passed
                BPEL Identity Service     Failed
                BPEL Domains     Not Run
                BPEL Server Mode      Not Run
                BPEL Notification Service     Not Run
                BPEL TaskManager Service     Not Run
                ESB Connection     Passed

                When I select "BPEL Identity Service     Failed" the error displayed as is below. But for the Not Run components it says "Not Executed".


                java.lang.Exception:Exception not handled by the Collaxa Cube system.
                An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-10555

                Identity Service Configuration error.
                Identity Service Configuration file has error.

                     at oracle.tip.pc.services.identity.config.ISConfiguration.load(ISConfiguration.java:277)
                     at oracle.tip.pc.services.identity.config.ISConfiguration.<clinit>(ISConfiguration.java:94)
                     at oracle.bpel.services.workflow.task.impl.WorkflowUtil.setUserNameCaseSensitiveFlagOnServer(WorkflowUtil.java:1193)
                     at oracle.bpel.services.workflow.task.impl.TaskService.<init>(TaskService.java:196)
                     at oracle.bpel.services.workflow.task.impl.TaskService.<clinit>(TaskService.java:153)
                     at oracle.bpel.services.common.InitializeServlet.init(InitializeServlet.java:56)
                     at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2379)
                     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4830)
                     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4754)
                     at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4942)
                     at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1144)
                     at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:741)
                     at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:431)
                     at com.evermind.server.Application.getHttpApplication(Application.java:586)
                     at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1987)
                     at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1906)
                     at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:643)
                     at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
                     at com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
                     at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
                     at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2493)
                     at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1042)
                     at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
                     at java.lang.Thread.run(Thread.java:595)
                Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
                     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
                     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
                     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
                     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291)
                     at oracle.tip.pc.services.identity.config.ISConfiguration.parseDocument(ISConfiguration.java:339)
                     at oracle.tip.pc.services.identity.config.ISConfiguration.load(ISConfiguration.java:259)
                     ... 23 more
                ".
                Exception: ORABPEL-10555

                Identity Service Configuration error.
                Identity Service Configuration file has error.

                Handled As: oracle.tip.pc.infra.exception.PCRuntimeException
                • 7. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
                  Levey_Baskar
                  I guess, I got the issue now. I checked is_config.xml file under SOA_HOME/bpel/system/services/config, the size is 0. Looks like this file got corrupted. let me update later if this file reinstate works or not.

                  Thanks for your support Arik.
                  • 8. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
                    Arik
                    Ok...let me know about your resaults
                    • 9. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
                      NarsingPumandla
                      can you please confirm whether you have oracle application server ? or weblogic server 9.2 or 10 ?

                      generally with soa 10.1.3.4.0, weblogic 9.2 is used..

                      Thanks
                      N
                      • 10. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
                        Levey_Baskar
                        Its Oracle Application server(We are running Oracle SOA10g) 10.1.3.4 version.

                        I got it resolve this issue, it becuase is_config.xml file was corrupted and fixing that file followed by a server bounce resolves my problem. Thanks for your support.

                        -Levey
                        • 11. Re: Jdeveloper 10.1.3.4 Test Connection failed for BPEL Process Manager.
                          Arik
                          Great!
                          please mark this post as answered....