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

Similar Messages

  • Install error : Please make sure TEMP is set to a valid writable directory

    Hello all.
    When i run ./runInstaller on the command prompt.. i get the error below.
    # ./runInstaller
    Error in writing to directory /tmp. Oracle Universal Installer needs you to have permission in this area to install. Installation cannot continue. Please make sure TEMP is set to a valid writable directory.
    : Permission denied
    Yes i ran the command using oracle user.
    Permissions checked on the partition.
    # ls -ld /tmp
    drwxr-xr-x 3 root root 4096 Dec 11 20:11 /tmp
    Please help, do i need to change the permission for the /tmp partition? if that is the case, what exactly command should i use to change the permission?

    Hi
    Try to do that
    export TEMP=/tmp
    export TMPDIR=/tmp
    export TMP=/tmp
    just to be sure
    Control after that the value is present with env | grep -i temp
    please change also the value to 777 as root.
    Read that for more information : http://download.oracle.com/docs/cd/B19306_01/install.102/b15667/pre_install.htm#CIHFICFD
    especially 2.14 Configuring the oracle User's Environment section 11 and 12.
    Let us know if it helps.
    Thanks.
    Regards,
    Hub

  • 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

  • WLS 11 Policy migration during EAR deployment

    We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
    Can anyone explain this behavior and verify if this is expected?
    Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
    /opt/oracle/admin/snidomain/aserver
    /opt/oracle/admin/snidomain/mserver
    The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
    Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

    We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
    Can anyone explain this behavior and verify if this is expected?
    Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
    /opt/oracle/admin/snidomain/aserver
    /opt/oracle/admin/snidomain/mserver
    The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
    Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

  • Ear deploy problems if dir contains '.' in the name

    Is there a fix that will allow Weblogic 8.1 SP for RedHat to deploy an ear that contains directory structure containing '.' in the name?
    We currently have to extract the ear and modify the application.xml to deploy the app in question due to this limitation.

    "Don Maxwell" <[email protected]> wrote in message news:27286804.1095364176807.JavaMail.root@jserv5...
    Is there a fix that will allow Weblogic 8.1 SP for RedHat to deploy an ear that contains directory structure containing '.' in thename?
    >
    We currently have to extract the ear and modify the application.xml to deploy the app in question due to this limitation.What is the problem? Can you show a stacktrace?
    óÌÁ×Á

  • WebLogic Server EAR Deployment Queries!

    Hi All,
    I have few queries with respect to EAR deployment in BEA WebLogic Server
    a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
    b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
    c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
    Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
    d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
    Any pointers to info source will be REALLY appreciated.
    Wiating for your reply.
    Many Thanks in Advance,
    C R Baradwaj

    Hi,
    Can anyone from BEA team help me in these queries?
    This is very urgent!
    have few queries with respect to EAR deployment in BEA WebLogic Server
    a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
    b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
    c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
    Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
    d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
    Thanks and Regards,
    C R Baradwaj

  • Exploded EAR deployment supported?

    Hi,
    I am currently developing with the MyEclipse IDE. Does Sun Java Studio Enterprise 8.1 support exploded deployment of EARs, and can it 'hot deploy' changes into the running Application Server?
    Thank You

    Hi.
    SJSE 8.1 doesn't support exploded deployment of EAR projects. It currently supports exploded deployment of WAR projects.
    I know that folks have extended NetBeans to support exploded EAR deployment in NB 6.0...
    You can find out more about that in this blog entry and screencast:
    http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_directory
    http://serverplugins.netbeans.org/screencasts/pfsc1.html
    Can you clarify what you mean by 'hot deploy'? Different folks have different definitions of this phrase... I think SJSE 8.1 does 'hot deploy' as I understand it... but my understanding may not match your vision of this feature...
    vbk

  • NWDI - How to control EAR deployment order

    We are developing a custom application in NWDI. We have created a software component for the this and have created all required DCs under this software component.
    All the J2EE DCs are deployed through separate EAR DCs and there are references from one to another ear DC where ever required.
    Deployment of a EAR DC fails if the dependent EARs are missing at that time as it looks for some classes at the time of deployment. We could resolve this in development env as we have the control over individual EAR deployment.
    But for deployment in QA through NWDI, where the whole software component is deployed as one SCA file, deployment is failing due to wrong order of deployment for the EARs. We are not able to figure out how to control the order of EAR deployments contained in a single SCA.
    Please let me know for any further info.
    Points will be awarded for helpful answers
    Regards, Chandra

    Hi  Chandra,
    It defines runtime-reference. And should automatically add references to application-j2ee-engine.xml
    But as far as I remember it is done only in NW7.1
    Regards,
    Andrei.

  • 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!

  • Weblogic EAR deployment - "error in opening zip file"

    Dear All,
    we build EAR using MAVEN 3.0.4 on Unix and are trying to deploy the application. The weblogic version is 10.3.4.
    We get the following error.
    <Mar 12, 2012 5:31:41 PM CET> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "ServletContext@1306153[app:sma-1 module:afis/sma path:/afis/sma spec-version:2.5]" to "/AFIS_DOMAIN/AFIS/servers/production/tmp/_WL_user/sma-1/bmzpi3/sma.web-1.1.0.war".>
    <Mar 12, 2012 5:31:42 PM CET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1331569832008' for task '13'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'afis/sma''
    weblogic.application.ModuleException: Failed to load webapp: 'afis/sma'
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    Truncated. see log file for complete stacktrace
    Caused By: java.util.zip.ZipException: error in opening zip file
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.<init>(ZipFile.java:114)
    at java.util.zip.ZipFile.<init>(ZipFile.java:131)
    at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
    at weblogic.servlet.internal.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:298)
    Truncated. see log file for complete stacktrace
    >
    Obviously, the WAR file cannot be opened by Weblogic, but why and how to solve it ... have no clue. We went through almost everything in Internet, regarding this issue, but we couldn't find a solution.
    Every idea or suggestion is more than welcome because I'm running out of ideas :(

    Did you perhaps do something like FTP the EAR file to the RedHat box in text mode or something? Can you check that the file size of the file on RedHat is the same as it was on Windows?

  • 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

    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

  • 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)

  • 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)

Maybe you are looking for