Error in EAR deployment

Hi All,
I am getting when deploying the adapter engine module ear file through SDM.
Can you please help me resolving this error:
ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/AE_SFTP..
                     Reason: Exception during generation of components of application sap.com/AE_SFTP in container EJBContainer.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/AE_SFTP in container EJBContainer.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:569)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(AccessController.java:219)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/AE_SFTP in container EJBContainer.
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3186)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                          ... 10 more
                     Caused by: java.lang.NoClassDefFoundError: com.sap.aii.af.mp.module.Module
Loader Info -
                     ClassLoader name: [Deployment:Runtime:sap.com/AE_SFTP]
                      Parent loader name: [Frame ClassLoader]
                      References:
                        common:service:http;service:servlet_jsp
                        service:ejb
                        common:service:iiop;service:naming;service:p4;service:ts
                        service:jmsconnector
                        library:jsse
                        library:servlet
                        common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
                        library:ejb20
                        library:j2eeca
                        library:jms
                        library:opensql
                        common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
                        interface:resourcecontext_api
                        interface:webservices
                        interface:cross
                        interface:ejbserialization
                      Resources:
                        /usr/sap/BXX/DVEBMGS00/j2ee/cluster/server0/temp/deploy/1226431172027/jsch-0.1.38.jar
                        /usr/sap/BXX/DVEBMGS00/j2ee/cluster/server0/temp/deploy/1226431172027
                        /usr/sap/BXX/DVEBMGS00/j2ee/cluster/server0/temp/deploy/1226431172027/SFTP_AadpterModule.jar
                      Loading model: {parent,references,local}
                     The error occurred while trying to load "SFTPModule.CreateAttachment".
                          at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
                          at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
                          at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
                          at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                          at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
                          at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                          ... 16 more
Thanks
Ankur

Yes i have used :
import com.sap.aii.af.mp.module.Module;
import com.sap.aii.af.mp.module.ModuleContext;
import com.sap.aii.af.mp.module.ModuleData;
import com.sap.aii.af.mp.module.ModuleException;
also in the build Build path; i have the "aii_af_mp.jar". Though in EAR i have removed all added jar file except the one jar file which is not provided by SAP. As mentioned in Adapter module dev guide.
Do you think adding that jar file could solve the issue.
Thanks
Ankur

Similar Messages

  • Error in ear deployment weblogic9.2

    Hi..
    When i try to deploy an ear in weblogic9.2 im repeatedly getting these 2 error messages -
    1)Unable to access the selected application
    2)No name parameter specified
    the steps i followed are
    i selected the install option in deployments menu and i selected the ear file and clicked on next.
    i get these error messages here.
    i dont get any error message when deploying in weblogic8.1.
    kindly help me out in this
    Arun

    Yes i have used :
    import com.sap.aii.af.mp.module.Module;
    import com.sap.aii.af.mp.module.ModuleContext;
    import com.sap.aii.af.mp.module.ModuleData;
    import com.sap.aii.af.mp.module.ModuleException;
    also in the build Build path; i have the "aii_af_mp.jar". Though in EAR i have removed all added jar file except the one jar file which is not provided by SAP. As mentioned in Adapter module dev guide.
    Do you think adding that jar file could solve the issue.
    Thanks
    Ankur

  • Error in Ear deployment (Writable directory error)

    I have seen this error before, but I don't remember how it was fixed. The following
    is the error
    that I get when I attempt to deploy my application:
    weblogic.utils.compiler.ToolFailureException: ERROR: The classes which ejbc generated
    from your home and remote interfaces cannot be loaded. Please ensure that you
    have set the -d option to a writeable directory.
    at weblogic.ejb20.ejbc.EJBCompiler.runRmic(EJBCompiler.java:919)
    at weblogic.ejb20.ejbc.EJBCompiler.doRmic(EJBCompiler.java:351)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:483)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1275)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    Any help would be greatly appreciated.
    Thanks,
    Joel

    Another odd thing. When I deploy the ear file to the admin server rather than
    the cluster, that
    deploys without a hitch. However, I still can't deploy to the cluster. Please
    advise.
    Thanks,
    Joel
    "Joel" <[email protected]> wrote:
    >
    Rob, thanks for the reply. I am indeed trying to generate the code on
    the server
    side during
    deployment. Running ejbc on the jar works fine when running outside
    the server.
    I get no
    errors. What would be the reason that the server can't find the files
    it generated.
    Rob Woollen <[email protected]> wrote:
    It looks like you haven't run ejbc/appc on the ejb-jar before deploying
    (or you ran them with a different version) so WLS is generating code
    on
    the server-side. It generated the code but then failed to load the
    classes it generated.
    What happens when your run java weblogic.ejbc (or weblogic.appc if
    you're using 8.1) on your ejb-jar outside of the server?
    -- Rob
    Joel wrote:
    I have seen this error before, but I don't remember how it was fixed.The following
    is the error
    that I get when I attempt to deploy my application:
    weblogic.utils.compiler.ToolFailureException: ERROR: The classes whichejbc generated
    from your home and remote interfaces cannot be loaded. Please ensurethat you
    have set the -d option to a writeable directory.
    at weblogic.ejb20.ejbc.EJBCompiler.runRmic(EJBCompiler.java:919)
    at weblogic.ejb20.ejbc.EJBCompiler.doRmic(EJBCompiler.java:351)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:483)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1275)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    Any help would be greatly appreciated.
    Thanks,
    Joel

  • Error during EAR deployment with EJB and web service

    I created a simple stateless EJB with one method called echo that returns a string.  I created a web service using the wizard, did a build and deployed.  The deployment did not report an error, but the logs in the visual administrator showed the follwoing message, and the web service did NOT deploy.
    Am I missing something related to EJB and web service security?
    PLEASE HELP ME.
    >>> Warning: delete security configuration [apps/com.areva/ear/ejb/security/com.areva~ejb.jar]
    [EXCEPTION]
    java.lang.Exception
         at com.sap.engine.services.security.server.PolicyConfigurations.unregisterPolicyConfiguration(PolicyConfigurations.java:153)
         at com.sap.engine.services.ejb.EJBAdmin.remove(EJBAdmin.java:2538)
         at com.sap.engine.services.deploy.server.application.RemoveTransaction.removeApplication(RemoveTransaction.java:294)
         at com.sap.engine.services.deploy.server.application.RemoveTransaction.prepare(RemoveTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.remove(DeployServiceImpl.java:820)
         at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.remove(DeployRuntimeControlImpl.java:271)
         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:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

    I have the same message. I am running sp11.
    Does anyone have an answer for this?????
    >>> Warning: delete security configuration [apps/avalero.com/rtfa-ear/contextRoot]
    [EXCEPTION]
    java.lang.Exception
         at com.sap.engine.services.security.server.PolicyConfigurations.unregisterPolicyConfiguration(PolicyConfigurations.java:153)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.removeSecurityResources(WebContainerHelper.java:905)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.remove(WebContainerHelper.java:447)
         at com.sap.engine.services.servlets_jsp.server.container.RemoveAction.remove(RemoveAction.java:50)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.remove(WebContainer.java:150)
         at com.sap.engine.services.deploy.server.application.RemoveTransaction.removeApplication(RemoveTransaction.java:294)
         at com.sap.engine.services.deploy.server.application.RemoveTransaction.prepare(RemoveTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.remove(DeployServiceImpl.java:821)
         at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.remove(DeployRuntimeControlImpl.java:271)
         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:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

  • Error in EAR deploy

    Hello, after first deployment without errors now I've obtained this unresolved message:
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/QuickCarRentalApplication. Reason: Application alias "QuickCarRental" for application "sap.com/QuickCarRentalApplication" already exists in the HTTP Provider Service.;
    Thanks in advance for any suggestions.
    Gianfranco

    Hi Gianfranco,
    If you are trying to deploy the same application for the second time, you either have to undeploy it first, or you should use the "redeploy or update" function of the Deploy Service. See http://help.sap.com/saphelp_nw04/helpdata/en/f4/6c9962da317549a05919ce926b5196/content.htm
    Best regards,
    Viliana

  • Error occurred while deploying ear file

    Hello experts,
    I am using NWDS (NW Version: 7.0.18). For a particular java file I am getting this error:
    ERROR: Not deployed. Deploy Service returned ERROR:
    20110728174758 Info   :                     java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/WSPiloto.ear.
    20110728174758 Info   :                     Reason: None of the available containers recognized the components of application sap.com.avn/WSPiloto; it is not possible to make deploy.  Most commonly used containers do not recognize the content of the application. Please contact the application vendor for details.
    Appreciate your help to fix the issue.
    Thanks in advance,
    Guillermo,
    dev

    Hi,
    can you please check if the following note helps?
    #1270242 -- None of the available containers recognized the components
    (http://service.sap.com/sap/support/notes/1270242)
    Best Regards,
    Ervin

  • Error when I deployed the java EAR application in NWDS 7.1

    HI All,
    I got the  error when I deployed the java EAR application in NWDS 7.1 version..help me out...........................................
    com.sap.ide.eclipse.deployer.api.APIException: DeployException,cause=[ERROR CODE DPL.DCAPI.1023] AuthorizationException.
    Reason: , An error occurred during the deployer retrieval. Cause =[ERROR CODE DPL.DC.3151] The user LJ4PJW could not be authorized, because doesn't own the (com.sap.engine.interfaces.security.ServiceAccessPermission dc) permission for deploy controller. at com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
    Thanks
    Costa

    The user LJ4PJW could not be authorized, *because doesn't own the* (com.sap.engine.interfaces.security.ServiceAccessPermission dc) *permission for deploy controller. a*t com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
    The user is not have proper authorizations. Use some other administrators user id which has all admin roles and authorizations assigned and try to deploy.
    Regards,
    Ravi

  • EAR Deployment error!

    I have created a servlet client to test a secured web service.
    When I deploy the EAR,I get error:
    Result
    => deployment aborted : file:/C:/DOCUME~1/uname/LOCALS~1/Temp/temp1530011368822716654CapsWS_EAR.ear
    Aborted: development component 'CapsWS_EAR'/'sap.com'/'localhost'/'2009.08.21.09.06.42'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/CapsWS_EAR.ear. Reason: Cannot make reference between CapsWS_EAR and CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server.
    Deployment exception : The deployment of at least one item abortedAnybody have any idea how to resolve this...
    Thanks
    Srinivas

    BalusC wrote:
    seenuFour wrote:
    Cycle of references is created, which is not allowed for the current version of the server.This is pretty self-explaining I think. Just do not create a cycle of references, or upgrade/change the server version.
    At least this problem is not related to the Servlet API, but to the appserver in question. Try the SAP homepage/forum/mailinglist/whateversupport if you stucks and don't get more help here.I totally agree with you. I am not able to figure out where I am doing "cycle of references". Is this a generic error at all ?
    I am a noob. Thanks for your reply!

  • Error 160078 when deploying WAR file after EAR file

    I am tetsing an application which does automatic deployment to WebLogic 8.1 running on Windows XP using ejbgen tool through Ant.
    The following deployment sequence produces an error. I deploy an EAR file with EJB JAR and WAR file inside. It deploys correctly. I then undeploy the EAR file. This also works. Next I deploy a WAR file using the same deployment name as for the EAR file (the 'name' parameter of weblogic.Deployer command). This deployment fails. If I restart WebLogic server, the same deployment of the WAR file succeeds.
    Any idea what goes wrong?
    Thank you.
    Michael
    Here is the command used for deployment (as reported by Ant):
    [java] 'weblogic.Deployer'
    [java] '-debug'
    [java] '-verbose'
    [java] '-noexit'
    [java] '-remote'
    [java] '-upload'
    [java] '-name'
    [java] 'discoverytestproject'
    [java] '-source'
    [java] 'C:/Projects/Jetson/Toolbox/Tests/Projects/DiscoveryTestProject/build/staging/discoverytestproject-ws.war'
    [java] '-targets'
    [java] 'myserver'
    [java] '-adminurl'
    [java] 't3://10.10.0.123:7001'
    [java] '-user'
    [java] 'system'
    [java] '-password'
    [java] 'password'
    [java] '-deploy'
    This is the error message:
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <J2EE> <BEA-160018> <ComponentMBean: Nam
    e = discoverytestproject-ws, Type = WebAppComponentConfig - Targeted on this ser
    ver but, no corresponding module found in application descriptor. The component
    mbean is being Ignored.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <J2EE> <BEA-160078> <None of the modules o
    f application 'discoverytestproject' in 'META-INF/application.xml' are configure
    d in the 'Application' entry in 'config.xml' to be targetted to 'myserver'.>
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were d
    etected while initiating Deploy task for application discoverytestproject.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <Deployer> <BEA-149201> <Failed to complet
    e the deployment task with ID 6 for the application discoverytestproject.
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createCon
    tainer(SlaveDeployer.java:2556)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: - with nested exception:
    [weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2491)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

    I am tetsing an application which does automatic deployment to WebLogic 8.1 running on Windows XP using ejbgen tool through Ant.
    The following deployment sequence produces an error. I deploy an EAR file with EJB JAR and WAR file inside. It deploys correctly. I then undeploy the EAR file. This also works. Next I deploy a WAR file using the same deployment name as for the EAR file (the 'name' parameter of weblogic.Deployer command). This deployment fails. If I restart WebLogic server, the same deployment of the WAR file succeeds.
    Any idea what goes wrong?
    Thank you.
    Michael
    Here is the command used for deployment (as reported by Ant):
    [java] 'weblogic.Deployer'
    [java] '-debug'
    [java] '-verbose'
    [java] '-noexit'
    [java] '-remote'
    [java] '-upload'
    [java] '-name'
    [java] 'discoverytestproject'
    [java] '-source'
    [java] 'C:/Projects/Jetson/Toolbox/Tests/Projects/DiscoveryTestProject/build/staging/discoverytestproject-ws.war'
    [java] '-targets'
    [java] 'myserver'
    [java] '-adminurl'
    [java] 't3://10.10.0.123:7001'
    [java] '-user'
    [java] 'system'
    [java] '-password'
    [java] 'password'
    [java] '-deploy'
    This is the error message:
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <J2EE> <BEA-160018> <ComponentMBean: Nam
    e = discoverytestproject-ws, Type = WebAppComponentConfig - Targeted on this ser
    ver but, no corresponding module found in application descriptor. The component
    mbean is being Ignored.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <J2EE> <BEA-160078> <None of the modules o
    f application 'discoverytestproject' in 'META-INF/application.xml' are configure
    d in the 'Application' entry in 'config.xml' to be targetted to 'myserver'.>
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were d
    etected while initiating Deploy task for application discoverytestproject.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <Deployer> <BEA-149201> <Failed to complet
    e the deployment task with ID 6 for the application discoverytestproject.
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createCon
    tainer(SlaveDeployer.java:2556)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: - with nested exception:
    [weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2491)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

  • Deployment error in .ear in portal project

    After starting admin server in workshop for weblogic, I am trying to publish the .ear portal project.
    But its giving the following error,
    weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)Unable to deploy EJB: ProxyPagePersistenceManager from netuix.jar:
    Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
    Exception Stack Trace:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1557)
    at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:469)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1329)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:787)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:607)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:503)
    at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
    at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
    at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
    Unable to deploy EJB: ProxyPagePersistenceManager from netuix.jar:
    Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.ejb20.interfaces.PrincipalNotFoundException: Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
    at weblogic.ejb.container.internal.SecurityHelperWLS.deployPolicy(SecurityHelperWLS.java:357)
    at weblogic.ejb.container.internal.SecurityHelper.deployPolicy(SecurityHelper.java:306)
    at weblogic.ejb.container.internal.SecurityHelper.deployPolicy(SecurityHelper.java:294)
    at weblogic.ejb.container.internal.SecurityHelper.deployAllPolicies(SecurityHelper.java:249)
    at weblogic.ejb.container.internal.SecurityHelper.deployAllPolicies(SecurityHelper.java:228)
    at weblogic.ejb.container.internal.RuntimeHelper.deployAllPolicies(RuntimeHelper.java:249)
    at weblogic.ejb.container.deployer.EJBDeployer.deployAllPolicies(EJBDeployer.java:770)
    at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:934)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1188)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)
    FYI, I am using Oracle Weblogic server v10.3 and pointbase DB.

    I was unable to resolve it....!!
    Just found a workaround...I didnt' used a EAR after that....
    But still this SAP note could help u out.....!!
    Deployement error in EAR DC
    Required note is :
    SAP Note Number: 1270242
    "None of the available containers recognized the components"

  • NW 7.2 CE EAR deploy error: Unable to extract ws clients deployment data

    Hi,
        I am attempting to deploy an extremely simple Enterprise application from Developer Studio. I creates a new enterprise app then created a new dynamic web project as associated it with the EAR. I then placed a single JSP containing only static content within the web app. When I attempt to deploy (either through the server view, as a workspace deployable archive in deploy view or after exporting the EAR and deploying as an eternal archive in deploy view) I receive the following error and the deployment fails. I am not trying to do anything with web services or web service clients. After a fresh reinstall deployment works for a short while then the error begins occurring again. Creating a new workspace and recreating the project caused no change.
       Any help, tips or things to try would be greatly appreciated.

    --- Deploying file(s):
         C:\SAP_Workspace_72_b\TestEarB\TestEarB.ear
    --- Status:
         Deploy Exception.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           0
    Failed deployments:                1
    ~~~~~~~~~~~~~~~~~~~
    ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [sap.com_TestEarB].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
    1. File:C:\SAP_Workspace_72_b\TestEarB\TestEarB.ear
         Name:TestEarB
         Vendor:sap.com
         Location:localhost
         Version:2010.08.12.09.23.12
         Deploy status:Aborted
         Version:NEW
         Description:
              1. Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive TestWeb.war, application sap.com/TestEarB.
               -> Unsupported Source object.
              2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.
    Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sap.com_TestEarB].] or thread dumps.
    --- Exception:
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [sap.com_TestEarB].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
         at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:80)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [sap.com_TestEarB].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:244)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:134)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Error while deploying ear file C:\SAP_Workspace_72_b\TestEarB\TestEarB.ear; nested exception is:
         java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive TestWeb.war, application sap.com/TestEarB.
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:249)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.init(WSClientsDeployProcess.java:122)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:320)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWSClients(WebServicesDeployManager.java:1079)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:274)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2198)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:394)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:347)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: javax.xml.transform.TransformerException: Unsupported Source object.
         at com.sap.engine.lib.jaxp.TransformerImpl.invokeDocHandlerMethodsFor(TransformerImpl.java:651)
         at com.sap.engine.lib.jaxp.TransformerImpl.transformSimple(TransformerImpl.java:267)
         at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:237)
         at com.sap.engine.lib.xml.util.legacy.StaxDOMLoader.load(StaxDOMLoader.java:53)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:278)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:231)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:217)
         ... 26 more
         at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4398)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:349)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         ... 11 more
    Caused by: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive TestWeb.war, application sap.com/TestEarB.
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:249)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.init(WSClientsDeployProcess.java:122)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:320)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWSClients(WebServicesDeployManager.java:1079)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:274)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2198)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:394)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:347)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: javax.xml.transform.TransformerException: Unsupported Source object.
         at com.sap.engine.lib.jaxp.TransformerImpl.invokeDocHandlerMethodsFor(TransformerImpl.java:651)
         at com.sap.engine.lib.jaxp.TransformerImpl.transformSimple(TransformerImpl.java:267)
         at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:237)
         at com.sap.engine.lib.xml.util.legacy.StaxDOMLoader.load(StaxDOMLoader.java:53)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:278)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:231)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:217)
         ... 26 more
         at com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:60)

  • Error during application deployment in cluster

    Hi All,
              I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
              Any pointers are greatly appreciated.
              Thanks
              --shashi
              Here is the error log:
              D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
              D:\apps\bea\user_projects\domains\nclusterdomain>echo off
              CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
              jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
              .4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
              intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://[hostname]:[port]/console *
              <Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
              Enter username to boot WebLogic server:weblogic
              Enter password to boot WebLogic server:
              <Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
              Sun Microsystems Inc.>
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
              k if there exists a running admin server at this URL.>
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
              WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
              the initial configuration.>
              <Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
              SR.log is opened. All server side log events will be written to this file.>
              <Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
              <Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
              <Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
              <Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
              Production Mode>
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
              <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
              rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
              rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
              rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
              part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
              javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
                      java.net.ConnectException: Connection refused: connect; No available router to destination]
              at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
              at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
              at javax.naming.InitialContext.init(InitialContext.java:219)
              at javax.naming.InitialContext.<init>(InitialContext.java:175)
              at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
              at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
              at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
              at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
              at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
              at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
              at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
              at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
              at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
              at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
              ... 28 more
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
              [javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
                      java.net.ConnectException: Connection refused: connect; No available router to destination]]
              at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
              at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
              at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
              at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
              at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
              at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
              at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
              at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
              at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
              at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              <Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
              java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
              at javax.naming.InitialContext.init(InitialContext.java:219)
              at javax.naming.InitialContext.<init>(InitialContext.java:175)
              at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
              at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
              at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
              at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
              at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
              at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
              at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
              at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
              at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
              at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              --------------- nested within: ------------------
              weblogic.management.ManagementException: - with nested exception:
              [java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
                      java.net.ConnectException: Connection refused: connect; No available router to destination]
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              >

    I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?

  • EAR Deployment Aborted...

    I am creating a servlet client to test a secured web service (Document Authentication Basic (Username/Password)).
    When I deploy the EAR,I get error:
    Result
    => deployment aborted : file:/C:/DOCUME~1/uname/LOCALS~1/Temp/temp1530011368822716654CapsWS_EAR.ear
    Aborted: development component 'CapsWS_EAR'/'sap.com'/'localhost'/'2009.08.21.09.06.42'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/CapsWS_EAR.ear. Reason: Cannot make reference between sap.com/CapsWS_EAR and sap.com/CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    The version of J2EE engine is 7.00 SP17
    Anybody have any idea how to resolve this...
    Do I need an upgrade for this ?
    Thanks
    Srinivas
    Edited by: srinivas M on Aug 21, 2009 5:55 PM

    Hi Srinivas,
    The reason is clear:
    Reason: Cannot make reference between sap.com/CapsWS_EAR and sap.com/CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server
    You may have created an entry for the same EAR in the application.xml file of your EAR Project. Remove it and redeploy.
    Regards,
    Alka.

  • How to reference sapjco from EAR deployment descriptors

    Hello techies,
    I´ve set up an EJB to use the JCo RFC Provider Service of the J2EE engine. Connection from R3 to EJB works but as soon as the EJB gets invoked, I get the error 'incompatible bean type - no processFunction found' from the RFCDefaultRequestHandler.invokeBean(..., JCO.Function) method.
    The reason is clear to me - the JCO.Function class is loaded by different class loaders and thus the method parameters don´t match.
    I´ve read in earlier postings that it is neccessary to reference the JCO in the module project and the ear deployment descriptor. That´s where my question begins.
    How do I reference the JCO in the module project (what´s that?)? I think it has to do with the EJB jar, doesn´t it?
    In the DeployTool I found a way how to set a reference to a library in the menu deploy-->libraries. But I am not sure what to specify here. I entered 'sapjco', since I saw an entry in the managers/library.txt file. Is that correct?
    Any hints are welcome!
    Regards,
    Jan

    Jan,
    you can set the reference to the EAR project using the reference.txt file that exists in the /managers folder.
    In the library.txt file set a path which is reference to sapjco.jar files..like
    library JCO sapjco.jar
    in the refernce.txt add the JCO referece to the EAR project...like
    reference Project library:JCO
    where Project here is the name of your EAR file..
    Ravi

  • IBFBS failed to deploy in Embedde OC4J but works with EAR deploy.

    Hi
    When i try to deploy IBFBS sample project in JDevloper by Embedde OC4J : its giving
    an error saying "there is no EJB module to deploy".
    But when i deployed through EAR deployment method its working fine.
    PLease kindly help me.
    Sai.

    Hi,
    Can you pls post the Version of JDeveloper and OC4J that you are using?
    I tried to deploy IBFBS using JDeveloper 9.0.3.988 (JDK 1.3.1) on Standalone OC4J server (9.0.3) and it works fine.
    One constraint for not running the application from JDeveloper (by using embedded OC4J) is that, the OC4J where the FBS is deployed needs to have the -userThreads option enabled.
    This option is enabled by starting OC4J with -userThreads option.
    java -jar oc4j.jar -userThreadsRef : Connection to embedded OC4J per FBS Setup Tutorial-Problem.
    Let us know if your problem still persists.
    Thanks
    -- OTN@IDC Team

Maybe you are looking for

  • How to grey out or deactivate the Conditions tab in VA01 and VA02

    Hi gurus, Is there a way I can grey out or deactivate the Conditions tab in VA01 or VA02?  Our objective is to attach the pricing conditons to the customer level and that no sales encoder can edit prices during encoding using t-codes VA01 and VA02? I

  • MacBook Pro Suddenly Very Slow

    Hello all, I own a mid-2012 MacBook Pro with 8gb of RAM and 2.5GHz i5 processor running the latest version of Mavericks. I purchased it back in December 2012, and have only had one issue with it (graphics card failure, which was fixed by Apple). Ever

  • Ipad2 with blacked out screen fix by spanking

    Hi All Just found out from the forum that if your  Apple IPad2 goes into a black out screen mode, you may be able to fix it by spanking it. I had taken it to the Genius Bar and they would have replaced it but was out of warranty. So taking it out of

  • Error in Tcode

    Hello All I have created one Tcode for Table maintanence. when I entered the Tcode, I m getting an message like "Create Data Processing function Module". How can I go about this.

  • APEX4.0 install error

    Hi, I meet a error during the APEX4.0 intallation Thank you for installing Oracle Application Express. Oracle Application Express is installed in the APEX_040000 schema. The structure of the link to the Application Express administration services is