10 Replies Latest reply: Apr 3, 2013 12:37 PM by h_kumari RSS

    composites becoming unavailable automatically

    Praveen Vaddanam
      We are using soa11.1.1.6 and we observe following behaviour.

      We have SOA BPEL invoking OSB whcih intern invokes Ebiz web services.
      Sometimes we see composites are automatically becoming unavailable.
      When we cllick on composite in em console we see below error

      ERROR
      =====
      The composite <compositename>(1.0) is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this composite.
      Unable to find a WSDL that has a definition for service {target namespace}endpoint and port wsdl_ port. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server

      We could not find any reason why this is happening and there is no way to recover from
      We have to redeploy code.

      soa_log says
      ========

      aused By: javax.management.RuntimeMBeanException: Internal error: Deployment Failed: Composite "default/compositename!1.0*soa_e27e3339-accf-4b88-86e5-47024f8c50f7" does not exist.
      at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:1020)
      at oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java:104)
      at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
      at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalInvoke(AbstractMBeanSecurityInterceptor.java:190)
      at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
      Truncated. see log file for complete stacktrace
      Caused By: oracle.fabric.common.FabricException: Internal error: Deployment Failed: Composite "default/compositename!1.0*soa_e27e3339-accf-4b88-86e5-47024f8c50f7" does not exist.
      at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeStateChange(StandaloneCompositeDeploymentCoordinatorImpl.java:82)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      Truncated. see log file for complete stacktrace
      Caused By: oracle.fabric.common.FabricException: Deployment Failed: Composite "default/compositename!1.0*soa_e27e3339-accf-4b88-86e5-47024f8c50f7" does not exist.
      at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeUpdate(StandaloneCompositeDeploymentCoordinatorImpl.java:127)
      at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeStateChange(StandaloneCompositeDeploymentCoordinatorImpl.java:80)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      Truncated. see log file for complete stacktrace
      Caused By: oracle.fabric.common.FabricDeploymentException: Composite "default/compositename!1.0*soa_e27e3339-accf-4b88-86e5-47024f8c50f7" does not exist. {rootCauses=[]}
      at oracle.integration.platform.blocks.mesh.MeshImpl.prepareConfigChange(MeshImpl.java:692)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      Truncated. see log file for complete stacktrace


      Thanks,
      Praveen
        • 1. Re: composites becoming unavailable automatically
          Praveen Vaddanam
          We also see below chunk of logs

          Error during retrieval of test page or composite resource[[
          oracle.fabric.common.FabricException: Failed to concatanate the following 2 urls: home= "null" and relative="SCA-INF/classes".: no protocol: SCA-INF/classes
          at oracle.fabric.common.metadata.MetadataManagerImpl.resolve(MetadataManagerImpl.java:323)
          at oracle.fabric.composite.model.CompositeModel.getClassLoaderFiles(CompositeModel.java:559)
          at oracle.fabric.composite.model.CompositeModel.getCompositeClassloader(CompositeModel.java:274)
          at oracle.integration.platform.blocks.soap.FabricProviderServlet.doGet(FabricProviderServlet.java:331)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
          at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
          at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
          at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
          at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
          at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
          at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
          at java.security.AccessController.doPrivileged(Native Method)
          at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
          at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
          at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
          at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
          at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
          at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
          at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
          at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
          at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
          at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
          at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:252)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
          Caused by: java.net.MalformedURLException: no protocol: SCA-INF/classes
          at java.net.URL.<init>(URL.java:567)
          at java.net.URL.<init>(URL.java:464)
          • 2. Re: composites becoming unavailable automatically
            Tarak
            Hi,

            Composite "default/compositename!1.0soa_e27e3339-accf-4b88-86e5-47024f8c50f7" does not exist. *

            this is wht i can see in log. Is this related to your composite or you calling above composite from your service.

            Please check any dependent service or child process are up or not or check the code that any unwanted import statement or wsdl are correctly imported in you service

            Regards,
            Tarak
            • 3. Re: composites becoming unavailable automatically
              Praveen Vaddanam
              I have replaced actual composites names with 'compositename'.
              Let's say if dependent services are down then composites becomes unavailable. What I expect here is once dependent services are up then composites should recover automatically.
              my SOA composites invokes OSB services and they are reachable

              Thanks,
              Praveen
              • 4. Re: composites becoming unavailable automatically
                Tarak
                I have replaced actual composites names with 'compositename'.
                Let's say if dependent services are down then composites becomes unavailable. What I expect here is once dependent services are up then composites should recover automatically.
                What i understand is you are trying to call depended service from parent. If dependent is down your parent service should retire, but in fact it is going to unavaliable?

                If this is case , i want to know whether you bounced the service after bring childprocess down? if that is case then your parent process will go to unavailable.

                Please elaborate if i am no where with you

                Regards,
                Tarak.
                .
                • 5. Re: composites becoming unavailable automatically
                  Praveen Vaddanam
                  Hi

                  Actually child processes are never down, but not sure why this is happening.
                  Lets says for some reason child processess(running on another managed server osb_server) are not reachable for SOA composites, then waht is expected behavior of composites?

                  Regards,
                  Praveen
                  • 6. Re: composites becoming unavailable automatically
                    Tarak
                    Then it is difficult to say for this behavior. As i said earlier, composite is trying to load or refer the artifact from server which are not available to the service,this could be high change for a composite to go into unavailable state.
                    But in your scenario it should retry.Can you paste your composite.xml here.

                    Can you bounce your sever and paste the Soa diagnostic log after restart.

                    Also clear the data in log file before you start the server so that we can see the exact issue. If we have luck :-)

                    Regrads,
                    Tarak.
                    • 7. Re: composites becoming unavailable automatically
                      Albin
                      We have faced the same issue and resolved by implementing the Abstract WSDL between the composites.

                      Refer the below URL for more details about implementing Abstract WSDL.

                      http://www.albinsblog.com/2011/11/oracle-soa-suite-10g-to-11g-migration_06.html#.UPAEKKzDiuk


                      Regards
                      Albin I
                      [http://www.albinsblog.com/]
                      • 8. Re: composites becoming unavailable automatically
                        Praveen Vaddanam
                        I feel this is not something to do with abstract vc concrete wsdl.
                        I see concrete wsdl is reachable during soa server startup.
                        • 9. Re: composites becoming unavailable automatically
                          AnuragGSOA
                          I am facing the same issue. I remember the day I deployed the 7 composites. After two days I again checked in and get error message

                          "
                          The composite OrderEBS (1.0) is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this composite.
                          Unable to find a WSDL that has a definition for service {http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2}ProcessOrderUpdateEBF and port CommunicationsSalesOrderEBS_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.

                          "

                          What is the most possible issue I don't know ?
                          • 10. Re: composites becoming unavailable automatically
                            h_kumari
                            I would suggest to move all the reference wsdl artifacts to MDS and referenced from there. We had done it and that resolved the issue.

                            HTH
                            Hruthayah