1 2 Previous Next 15 Replies Latest reply: Aug 31, 2013 12:53 PM by Timo Hahn RSS

    Deploying adf application on weblogic server with soa patch

    967398

      Hi ,

       

      Web logic version : 10.3.6. With SOA server installaed on it.

       

       

      There is one admin node and two managed nodes.

       

      Jdeveloper version 11.1.6.0.

       

      I developed a war file and deployed it on the server but the application is not up in the server. so as suggested by certain blogs , I constructed an EAR and deployed.

       

       

      But the issue is that :

       

      1. I can able to deploy only on admin node .

      2. When I tried to deploy it on the all nodes it is showing the below error.

       

      Message icon - Error jzentry == 0, jzfile = 184071968, total = 843, name = /apps/pqbprd/admin/pqbprd_domain/mserver/pqbprd_domain/servers/Managed_soa_server02/tmp/_WL_user/CompWizard/h1sxxx/war/WEB-INF/lib/axis.jar, i = 1, message = null




        • 1. Re: Deploying adf application on weblogic server with soa patch
          967398

          Please help me with your valuable suggestions.

          • 2. Re: Deploying adf application on weblogic server with soa patch
            Timo Hahn

            There must be more information to the error than you disclosed here. Does it tell you that the jar is missing? Anything else in the log?

            What kind of application do you try to deploy? Pure ADF application? Soa Application with some add on?

             

            Have you checked that the managed servers are setup correctly? Are the soa libs you need targeted to the managed servers?

             

            Timo

            • 3. Re: Deploying adf application on weblogic server with soa patch
              967398

              It's a pure ADF application. All libraries are there.

               

              when I deploy it only on Admin node it's working fine.

              • 4. Re: Deploying adf application on weblogic server with soa patch
                Timo Hahn

                It's not enough that you see the libraries, you have to check if they are targeted to the managed servers. To check this you open the admin console of the managed server select deployments and make sure you see the libraries and the applications. Then select the adf.oracle.domain and click on it which will get you to another page where you open the "Targets" tab. There you should see all your servers. The checkbox for the managed servers has to be marked. If not you can't delpoy an adf application to the server.

                If you don't see the check mark, you need to extend the managed server with the adf run time libraries (the one you just checked is not enough, there are others too).

                 

                Timo

                • 5. Re: Deploying adf application on weblogic server with soa patch
                  kdario

                   

                  There is one admin node and two managed nodes.

                  I suppose: SOA managed server and BAM managed server ?

                  2. When I tried to deploy it on the all nodes it is showing the below error.

                  Maybe you need to instruct WL server to pick up your axis classes instead of built in.

                  You can do this with prefer-web-inf-classes parameter in weblogic.xml deployment descriptor.

                   

                  Dario

                  • 6. Re: Deploying adf application on weblogic server with soa patch
                    967398

                    option selected as all servers in the cluster.

                    • 7. Re: Deploying adf application on weblogic server with soa patch
                      967398

                      Stack trace for message 149004 java.lang.InternalError: jzentry == 0, jzfile = 170026832, total = 843, name = /apps/pqbprd/admin/pqbprd_domain/mserver/pqbprd_domain/servers/Managed_soa_server01/tmp/_WL_user/CompWizard/sigimu/war/WEB-INF/lib/axis.jar, i = 1, message = null at java.util.zip.ZipFile$2.nextElement(ZipFile.java:322) at java.util.zip.ZipFile$2.nextElement(ZipFile.java:304) at java.util.jar.JarFile$1.nextElement(JarFile.java:225) at java.util.jar.JarFile$1.nextElement(JarFile.java:220) at weblogic.utils.classloaders.ZipClassFinder$1.nextElement(ZipClassFinder.java:58) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.application.utils.ClassFinderMetaDataEnumaration.hasMoreElements(ClassFinderMetaDataEnumaration.java:31) at weblogic.servlet.internal.WebAnnotationProcessorImpl.getAnnotatedClasses(WebAnnotationProcessorImpl.java:139) at weblogic.servlet.internal.War.getAnnotatedClasses(War.java:1038) at weblogic.servlet.internal.WebAppServletContext$ServletContextWebAppHelper.getAnnotatedClasses(WebAppServletContext.java:3848) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:84) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1370) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:452) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:497) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused By: java.lang.InternalError: jzentry == 0, jzfile = 170026832, total = 843, name = /apps/pqbprd/admin/pqbprd_domain/mserver/pqbprd_domain/servers/Managed_soa_server01/tmp/_WL_user/CompWizard/sigimu/war/WEB-INF/lib/axis.jar, i = 1, message = null at java.util.zip.ZipFile$2.nextElement(ZipFile.java:322) at java.util.zip.ZipFile$2.nextElement(ZipFile.java:304) at java.util.jar.JarFile$1.nextElement(JarFile.java:225) at java.util.jar.JarFile$1.nextElement(JarFile.java:220) at weblogic.utils.classloaders.ZipClassFinder$1.nextElement(ZipClassFinder.java:58) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at weblogic.application.utils.ClassFinderMetaDataEnumaration.hasMoreElements(ClassFinderMetaDataEnumaration.java:31) at weblogic.servlet.internal.WebAnnotationProcessorImpl.getAnnotatedClasses(WebAnnotationProcessorImpl.java:139) at weblogic.servlet.internal.War.getAnnotatedClasses(War.java:1038) at weblogic.servlet.internal.WebAppServletContext$ServletContextWebAppHelper.getAnnotatedClasses(WebAppServletContext.java:3848) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:84) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1370) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:452) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:497) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

                      • 8. Re: Deploying adf application on weblogic server with soa patch
                        967398

                        @kadario will try with your suggestion

                        • 9. Re: Deploying adf application on weblogic server with soa patch
                          967398

                          I tried modifying with that but it's not working.

                          • 10. Re: Deploying adf application on weblogic server with soa patch
                            kdario

                            weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused By: java.lang.InternalError: jzentry == 0, jzfile = 170026832, total = 843, name = /apps/pqbprd/admin/pqbprd_domain/mserver/pqbprd_domain/servers/Managed_soa_server01/tmp/_WL_user/CompWizard/sigimu/war/WEB-INF/lib/axis.jar, i = 1, message = null at java.util.zip.ZipFile$2.nextElement(ZipFile.java:322) at java.util.zip.ZipFile$2.nextElement(ZipFile.java:304) at java.util.jar.JarFile$1.nextElement(JarFile.java:225) at java.util.jar.JarFile$1.nextElement(JarFile.java:220) at weblogic.utils.classloaders.ZipClassFinder$1.nextElement(ZipClassFinder.java:58) at weblogic.utils.enumerations.SequencingEnumerator.nextElement(SequencingEnumerator.java:65) at

                            Check free space and access rights to given path(maybe you started managed server as different OS user, etc.).

                             

                            Dario

                            • 11. Re: Deploying adf application on weblogic server with soa patch
                              967398

                              @Dario available space is 19 gb. but still it's not working.

                              • 12. Re: Deploying adf application on weblogic server with soa patch
                                kdario

                                If this works on Admin Server and you don't have issues with free space and filesystem access rights, this is probably some issue with class loading order.

                                It can be tricky to setup proper class loading order of third party jars in WL server(especially for xml parsing libraries), so maybe is easier to change your code to use builtin ws suport(jax-ws) instead of axis?

                                 

                                Dario

                                • 13. Re: Deploying adf application on weblogic server with soa patch
                                  967398

                                  hi When I deploy it as war it is getting deployed . But when I load the application it is showing the blank page.

                                  • 14. Re: Deploying adf application on weblogic server with soa patch
                                    967398

                                    I have gone through this thread , but it is not helpful.

                                    Adf blank page problem

                                     

                                    I gone through blogs they are giving suggestions to deploy the application as ear so tried to deploying as ear in weblogic + soa env .

                                     

                                    We have two environemnts. 1. stage 2. production

                                     

                                    In both of these environments web logic server is there . soa libraries installed soa version 11.1.1.6.

                                     

                                    Weblogic version 10.3.6.

                                     

                                    but same ear is working in STAGE but not working in Production.

                                    1 2 Previous Next