LMTOOL patch error: SDA to be deployed

Hi All,
During applying patches of LM TOOL through JSPM we are getting error as follows:
It is saying that SDA to be deployed. But I dont know how to do that. I got tclcmdeployer.sda file at given location.
  Info: Finished saving the repository for 210 ms.
  Info: Starting: Initial deployment: Selected development component 'tc/lcm/deployer'/'sap.com'/'MAIN_NW702P05_C'/'3820096'/'10' will be deployed.
  Info: SDA to be deployed: E:\usr.....\SDM\root\origin\sap.com\tc\lcm\deployer\MAIN_NW702P05_C\10\3820096\tclcmdeployer.sda
  Info: Software type of SDA: J2EE
  Info: Begin of SAP J2EE Engine Deployment (J2EE Application)
  Info: Begin of log messages of the target system:
-  Start updating EAR file...
-  start-up mode is lazy
-  EAR file updated successfully for 57ms.
-  Start deploying ...
-  EAR file uploaded to server for 112ms.
ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/tclcmdeployer..
                     Reason: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:575)
                          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:330)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                          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(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:623)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:325)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:309)
                          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:3241)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:560)
                          ... 10 more
                     Caused by: java.lang.NoClassDefFoundError: com/sap/tc/ts/is/spi/ConnectEvent
                          at java.lang.Class.getDeclaredMethods0(Native Method)
                          at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                          at java.lang.Class.getMethod0(Class.java:1901)
                          at java.lang.Class.getMethod(Class.java:984)
                          at com.sap.engine.services.ejb.util.ClassUtils.hasMethod(ClassUtils.java:45)
                          at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:56)
                          at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
                          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:2167)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:608)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
  Info: End of log messages of the target system.
  Info:  End of SAP J2EE Engine Deployment (J2EE Application)
  Error: Aborted: development component 'tc/lcm/deployer'/'sap.com'/'MAIN_NW702P05_C'/'3820096'/'10', grouped by software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tclcmdeployer..
Reason: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)  Info: Starting to save the repository
Info: Finished saving the repository for 156 ms.
  Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P04_C'/'1000.7.02.4.1.20100604135121''/'0'.
Nov 11, 2011 4:26:09 PM  Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2':
Failed deployment of SDAs:
development component 'tc/lcm/deployer'/'sap.com'/'MAIN_NW702P05_C'/'3820096'/'10' : aborted
Please, look at error logs above for more information!
  Info: Starting to save the repository
  Info: Finished saving the repository for 156 ms.
  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
  Error: - At least one of the Deployments failed-
Please help me to solve this issue.
Thanks and Regards,
Ishan

Hi,
I am pasting last part of log file sdmlog<date>  here as file is too big. And Note you mentioned says undeploy that component using SDM. How to do that? I don't know. please help. 
4:26:01 PM  Info: Starting to save the repository
4:26:02 PM  Info: Finished saving the repository for 356 ms.
4:26:02 PM  Info: Starting: No action: Selected development component 'tc/di/cts/import/service/appl'/'sap.com'/'MAIN_NW702P05_C'/'3820207'/'10' will not be redeployed. Only the previous development component 'tc/di/cts/import/service/appl'/'sap.com'/'MAIN_NW702P05_C'/'3820207'/'9' will be updated in the SDM repository.
4:26:02 PM  Info: Finished successfully: development component 'tc/di/cts/import/service/appl'/'sap.com'/'MAIN_NW702P05_C'/'3820207'/'10', grouped by
4:26:02 PM  Info: Starting to save the repository
4:26:02 PM  Info: Finished saving the repository for 223 ms.
4:26:02 PM  Info: Starting: No action: Selected development component 'tc/je/basicadmin/sapcontrol/lib'/'sap.com'/'MAIN_NW702P03_C'/'3520730'/'11' will not be redeployed. Only the previous development component 'tc/je/basicadmin/sapcontrol/lib'/'sap.com'/'MAIN_NW702P03_C'/'3520730'/'10' will be updated in the SDM repository.
4:26:02 PM  Info: Finished successfully: development component 'tc/je/basicadmin/sapcontrol/lib'/'sap.com'/'MAIN_NW702P03_C'/'3520730'/'11', grouped by
4:26:02 PM  Info: Starting to save the repository
4:26:02 PM  Info: Finished saving the repository for 241 ms.
4:26:02 PM  Info: Starting: No action: Selected development component 'tc/je/jmx/wsconnector/app'/'sap.com'/'MAIN_NW702P03_C'/'3520736'/'11' will not be redeployed. Only the previous development component 'tc/je/jmx/wsconnector/app'/'sap.com'/'MAIN_NW702P03_C'/'3520736'/'10' will be updated in the SDM repository.
4:26:02 PM  Info: Finished successfully: development component 'tc/je/jmx/wsconnector/app'/'sap.com'/'MAIN_NW702P03_C'/'3520736'/'11', grouped by software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2'
4:26:02 PM  Info: Starting to save the repository
4:26:03 PM  Info: Finished saving the repository for 365 ms.
4:26:03 PM  Info: Starting: No action: Selected development component 'tc/je/jmx/wsconnector/sp/sda'/'sap.com'/'MAIN_NW702P03_C'/'3520733'/'11' will not be redeployed. Only the previous development component 'tc/je/jmx/wsconnector/sp/sda'/'sap.com'/'MAIN_NW702P03_C'/'3520733'/'10' will be updated in the SDM repository.
4:26:03 PM  Info: Finished successfully: development component 'tc/je/jmx/wsconnector/sp/sda'/'sap.com'/'MAIN_NW702P03_C'/'3520733'/'11', grouped by
4:26:03 PM  Info: Starting to save the repository
4:26:03 PM  Info: Finished saving the repository for 209 ms.
4:26:03 PM  Info: Starting: No action: Selected development component 'tc/je/mbeanviewer/app'/'sap.com'/'MAIN_NW702P03_C'/'3520861'/'11' will not be redeployed. Only the previous development component 'tc/je/mbeanviewer/app'/'sap.com'/'MAIN_NW702P03_C'/'3520861'/'10' will be updated in the SDM repository.
4:26:03 PM  Info: Finished successfully: development component 'tc/je/mbeanviewer/app'/'sap.com'/'MAIN_NW702P03_C'/'3520861'/'11', grouped by software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2'
4:26:03 PM  Info: Starting to save the repository
4:26:03 PM  Info: Finished saving the repository for 239 ms.
4:26:03 PM  Info: Starting: No action: Selected development component 'tc/je/trace/app'/'sap.com'/'MAIN_NW702P03_C'/'3520908'/'11' will not be redeployed. Only the previous development component 'tc/je/trace/app'/'sap.com'/'MAIN_NW702P03_C'/'3520908'/'10' will be updated in the SDM repository.
4:26:03 PM  Info: Finished successfully: development component 'tc/je/trace/app'/'sap.com'/'MAIN_NW702P03_C'/'3520908'/'11', grouped by software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2'
4:26:03 PM  Info: Starting to save the repository
4:26:03 PM  Info: Finished saving the repository for 210 ms.
4:26:03 PM  Info: Starting: Initial deployment: Selected development component 'tc/lcm/deployer'/'sap.com'/'MAIN_NW702P05_C'/'3820096'/'10' will be deployed.
4:26:03 PM  Info: SDA to be deployed: E:\usr\sap\KSA\DVEBMGS00\SDM\root\origin\sap.com\tc\lcm\deployer\MAIN_NW702P05_C\10\3820096\tclcmdeployer.sda
4:26:03 PM  Info: Software type of SDA: J2EE
4:26:04 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
4:26:09 PM  Info: Begin of log messages of the target system:
11/11/11 16:26:04 -  ***********************************************************
11/11/11 16:26:07 -  Start updating EAR file...
11/11/11 16:26:07 -  start-up mode is lazy
11/11/11 16:26:07 -  EAR file updated successfully for 57ms.
11/11/11 16:26:07 -  Start deploying ...
11/11/11 16:26:07 -  EAR file uploaded to server for 112ms.
11/11/11 16:26:09 -  ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/tclcmdeployer..
                     Reason: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:575)
                          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:330)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                          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(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:623)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:325)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:309)
                          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:3241)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:560)
                          ... 10 more
                     Caused by: java.lang.NoClassDefFoundError: com/sap/tc/ts/is/spi/ConnectEvent
                          at java.lang.Class.getDeclaredMethods0(Native Method)
                          at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                          at java.lang.Class.getMethod0(Class.java:1901)
                          at java.lang.Class.getMethod(Class.java:984)
                          at com.sap.engine.services.ejb.util.ClassUtils.hasMethod(ClassUtils.java:45)
                          at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:56)
                          at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
                          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:2167)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:608)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
11/11/11 16:26:09 -  ***********************************************************
4:26:09 PM  Info: End of log messages of the target system.
4:26:09 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
4:26:09 PM  Error: Aborted: development component 'tc/lcm/deployer'/'sap.com'/'MAIN_NW702P05_C'/'3820096'/'10', grouped by software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tclcmdeployer..
Reason: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tclcmdeployer in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
4:26:09 PM  Info: Starting to save the repository
4:26:09 PM  Info: Finished saving the repository for 156 ms.
4:26:09 PM  Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P04_C'/'1000.7.02.4.1.20100604135121''/'0'.
4:26:09 PM  Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P06_C'/'1000.7.02.6.10.20110905085221''/'2':
Failed deployment of SDAs:
development component 'tc/lcm/deployer'/'sap.com'/'MAIN_NW702P05_C'/'3820096'/'10' : aborted
Please, look at error logs above for more information!
4:26:09 PM  Info: Starting to save the repository
4:26:09 PM  Info: Finished saving the repository for 156 ms.
4:26:09 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
4:26:09 PM  Error: -
At least one of the Deployments failed -
4:26:10 PM  Info: Delete the files from E:\usr\sap\KSA\DVEBMGS00\SDM\program\temp
4:26:10 PM  Info: Close client connection to <HOSTNAME>.<companyname>.com/<ip-address>, remote port 64891
4:26:13 PM  Info: Opened client connection to <HOSTNAME>.<companyname>.com (IP address <HOSTNAME>.<companyname>.com/<ip-address>, remote port 65012)
4:26:22 PM  Info: Delete the files from E:\usr\sap\KSA\DVEBMGS00\SDM\program\temp
4:26:22 PM  Info: Close client connection to <HOSTNAME>.<companyname>.com/<ip-address>, remote port 65012
4:26:24 PM  Info: Start logging to 'E:\usr\sap\KSA\DVEBMGS00\j2ee\JSPM\log\log_2011_11_11_16_24_07\OperateSDM_01.LOG'
4:26:24 PM  Info:
4:26:24 PM  Info: ==========================================
4:26:24 PM  Info: =   Starting to execute command 'ping'   =
4:26:24 PM  Info: ==========================================
4:26:24 PM  Info: Sending "ping" command to the SDM server...
4:26:24 PM  Info: Opened client connection to 127.0.0.1 (IP address 127.0.0.1/127.0.0.1, remote port 65019)
4:26:25 PM  Info: SDM server is running.
4:26:25 PM  Info: Close client connection to 127.0.0.1/127.0.0.1, remote port 65019
4:26:25 PM  Info: Successfully executed. Return code: 0
6:20:12 PM  Info: ====================================
6:20:12 PM  Info: JControl is shutting SDM Server down
6:20:12 PM  Info: ====================================
6:20:12 PM  Info: Server finished sending back the answer of the ShutdownRequest.
6:20:12 PM  Info: Shutting dispatcher down
6:25:16 PM  Info:
6:25:16 PM  Info: ============================================
6:25:16 PM  Info: =   Starting to execute command 'server'   =
6:25:16 PM  Info: ============================================
6:25:16 PM  Info: Starting SDM - Software Deployment Manager...
6:25:17 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0204.20100323143211.0000
6:25:22 PM  Info: SDM operation mode successfully set to: Integrated
  Info: JStartupFramework is requesting to start the SDM Server.
  Info: Start the SDM Server integrated in the JStartupFramework.
  Info: Initializing Network Manager (50017)
  Info: Starting SDM Server listening on port 50018
  Info: SDM started successfully.
Please help me.
Thanks,
Ishan

Similar Messages

  • ERROR: Cannot perform action deploy on component library

    Hi all,
    Some Background on what i did:
    First I created two DCs:
    1)External library DC
    2)J2EE server component library DC
    and followed the procedure given as in
    /people/valery.silaev/blog/2005/09/14/a-bit-of-impractical-scripting-for-web-dynpro
    Then i created a third DC of type Web Module in order to hold all the classes as given in: Using External JARs in a Web Dynpro Project
    But when I deploy the J2EE server library component DC, I am getting the following error:
    Oct 16, 2006 8:38:39 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : teak
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/krunalra/LOCALS1/Temp/temp19352pcbp.com~lib_comp.sda
    Result
    => deployment aborted : file:/C:/DOCUME1/krunalra/LOCALS1/Temp/temp19352pcbp.com~lib_comp.sda
    Aborted: development component 'lib_comp'/'pcbp.com'/'NWX_LIBS_C'/'20061016083638':
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library E:\usr\sap\NWX\DVEBMGS00\SDM\root\origin\pcbp.com\lib_comp\NWX_LIBS_C\20061016083638\temp19352pcbp.comlib_comp.sda. Reason: java.rmi.RemoteException: Error during deployLib of server component ./temp/deploy/work/deploying/temp19352pcbp.comlib_comp.sda.. Reason: com.sap.engine.core.service630.container.ContainerException: java.lang.NullPointerException; nested exception is: com.sap.engine.frame.container.deploy.ComponentDeploymentException: com.sap.engine.core.service630.container.ContainerException: java.lang.NullPointerException
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deployServerComponent(DeployServiceImpl.java:1576)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1434)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
    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(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.frame.container.deploy.ComponentDeploymentException: com.sap.engine.core.service630.container.ContainerException: java.lang.NullPointerException
    at com.sap.engine.core.service630.context.container.deploy.DeployContextImpl.deployLibrary(DeployContextImpl.java:36)
    at com.sap.engine.services.deploy.server.library.DeployLibTransaction.begin(DeployLibTransaction.java:68)
    at com.sap.engine.services.deploy.server.library.LibraryTransaction.makeAllPhases(LibraryTransaction.java:81)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deployServerComponent(DeployServiceImpl.java:1566)
    ... 11 more
    Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library E:\usr\sap\NWX\DVEBMGS00\SDM\root\origin\pcbp.com\lib_comp\NWX_LIBS_C\20061016083638\temp19352pcbp.comlib_comp.sda. Reason: java.rmi.RemoteException: Error during deployLib of server component ./temp/deploy/work/deploying/temp19352pcbp.comlib_comp.sda.. Reason: com.sap.engine.core.service630.container.ContainerException: java.lang.NullPointerException; nested exception is: com.sap.engine.frame.container.deploy.ComponentDeploymentException: com.sap.engine.core.service630.container.ContainerException: java.lang.NullPointerException
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deployServerComponent(DeployServiceImpl.java:1576)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1434)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
    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(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.frame.container.deploy.ComponentDeploymentException: com.sap.engine.core.service630.container.ContainerException: java.lang.NullPointerException
    at com.sap.engine.core.service630.context.container.deploy.DeployContextImpl.deployLibrary(DeployContextImpl.java:36)
    at com.sap.engine.services.deploy.server.library.DeployLibTransaction.begin(DeployLibTransaction.java:68)
    at com.sap.engine.services.deploy.server.library.LibraryTransaction.makeAllPhases(LibraryTransaction.java:81)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deployServerComponent(DeployServiceImpl.java:1566)
    ... 11 more
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    I have being stuck up on this erorr for past few days,
    If anybody can please help me out in this,then it would be highly appreciated.
    Thank You,
    With regards,
    Krunal.

    Do you have permissions to write to the Database/RDMBS?
    James

  • Error while web application deployment in NetBeans5.5

    Error while web application deployment in NetBeans5.5. I am always getting Tomcat deployment error. using Netbeans 5.5.1 with bundeld tomcat. But in some machines its working fine.
    regards
    jossy v jose

    What is the error message you see?
    Are there any stacktraces or other relevant messages in the ide log file? (The ide log file is [userdir]/var/log/messages.log. On userdir: http://blogs.sun.com/karthikr/entry/jse_directories)
    You can also check the server log file to see if there are more detailed messages.
    You can also try setting ant's verbose level to debug or verbose (Tools | Options | Miscellaneous | Ant | Verbosity Level) and check the output.

  • Error while trying to deploy the application (invalid AccountType).

    Hello.
    Error while trying to deploy the planning application (EPMA).
    invalid AccountType
    Rejecting Member PL_Brt_L.2.
    invalid AccountType
    Rejecting Member PL_Brt_L.3.2.
    And not updated outline.
    PL_Brt_L.2 - Account Type = Revenue
    PL_Brt_L.3.2 - Account Type = Revenue
    If a change to the Revenue Expence, the error goes away and the outline changes.
    EPM 11.1.2.1
    1-st server: planning, essbase
    2-nd server: epma
    3-th server: oracle db
    thanks in advance

    Hi,
    I tried using dcmctl but still got the following error.
    Oracle 8i database is running but noone is using it except that this application uses it.
    Pls help
    D:\oraJ2EE\dcm\bin>dcmctl deployapplication -f d:\oraJ2ee\j2ee\elink\applications\advecto.ear -
    a myapp
    ADMN-300075
    D:\oraJ2EE\dcm\bin>dcmctl getError -v -d
    ADMN-300075
    Nested exception
    Base Exception:
    java.rmi.RemoteException:null; nested exception is:
    java.lang.OutOfMemoryError
    Nested exception
    Root Cause: null; nested exception is:
    java.lang.OutOfMemoryError
    java.rmi.RemoteException: null; nested exception is:
    java.lang.OutOfMemoryError
    java.lang.OutOfMemoryError
    <<no stack trace available>>
    Thanks
    Srinath

  • Regarding Error in weblogic 11g deployment

    The following Error occured when i deploy my Application in WEBLOGIC 11G Please can anyone help me for resolving this Urgent Issue..
    Error occurred while processing weblogic-rdbms-bean.xml file: ‘fileName‘. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean).EJB Name:com.foursoft.elog.chargeBasis.ejb.cmp.chargeBasisBean.XML processor:'Weblogic.ejb.container.cmp.rdbms.weblogicCmp20Loader_WLS810'

    The following Error occured when i deploy my Application in WEBLOGIC 11G Please can anyone help me for resolving this Urgent Issue..
    Error occurred while processing weblogic-rdbms-bean.xml file: ‘fileName‘. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean).EJB Name:com.foursoft.elog.chargeBasis.ejb.cmp.chargeBasisBean.XML processor:'Weblogic.ejb.container.cmp.rdbms.weblogicCmp20Loader_WLS810'

  • Error during ear file deployment

    Hi,
    I am getting the error while trying to deploy ear file using SDM.
    The error log is
    Starting Deployment of MyzipBean
    Aborted: development component 'MyzipBean'/'sap.com'/'localhost'/'2008.06.13.17.44.31'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/MyzipBean.. Reason: Incorrect application sap.com/MyzipBean:Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/MyzipBean:Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.
    What could be the reason?
    Thanks,
    Jaishankar

    Hi,
    1. Restart the upgrade
    2. When it shows the error above open callSdmViaSapinst.log and search for the application that can't be deployed
    3. If application is STOPPED start it
    4. Undeploy the application if it is STARTED
    5. Press the "Retry" button in the error message dialog box from the
    upgrade
    6. If it fails again for another application go to 2.
    Please refer SAP NOte 851590. I don't know if it work for u, as i have given this , it seems for Upgrade as you are developing.
    Look into this thread also
    Unable to deploy a module into XI Server
    Regards
    Aashish Sinha
    Edited by: Aashish Sinha on Jun 13, 2008 3:20 PM
    Edited by: Aashish Sinha on Jun 13, 2008 3:28 PM

  • Autoconfig -patch error

    Hai frnds ,
    iam getting the eroor when i run autoconfig
    =========================[AutoConfig Error Report]
    The following report lists errors AutoConfig encountered during each
    phase of its execution. Errors are grouped by directory and phase.
    The report format is:
    <filename> <phase> <return code where appropriate>
    [PROFILE PHASE]
    AutoConfig could not successfully execute the following scripts:
    Directory: /pix/p01/oracle/pixcomn/admin/install/pix_server1
    afcpctx.sh INSTE8_PRF 1
    =======================================================
    i was asked to apply the patch 3377508(got from metalink)when i tried to applied the patch i get the following error.iam a fresher and i dont know wat to do.i got the error when i run the patch
    the error is===========
    *********Writing jobs to run to restart file.
    Reading jobs from FND_INSTALL_PROCESSES table ...
    FAILED: file afmntmds.ldt on worker 1 for product fnd username APPS.
    FAILED: file functype.ldt on worker 2 for product fnd username APPS.
    FAILED: file b2040719.ldt on worker 3 for product fnd username APPS.
    FAILED: file afmntfns.ldt on worker 4 for product fnd username APPS.
    FAILED: file afctxdep.ldt on worker 5 for product fnd username APPS.
    Done reading jobs from FND_INSTALL_PROCESSES table ...
    Telling workers to read 'todo' restart file.
    Done.
    ATTENTION: All workers either have failed or are waiting:
    FAILED: file afmntmds.ldt on worker 1.
    FAILED: file functype.ldt on worker 2.
    FAILED: file b2040719.ldt on worker 3.
    FAILED: file afmntfns.ldt on worker 4.************* Start of AD Worker session *************
    =======================
    so please help me to run the patch correctly and then run the autopatch correctly
    Thanks and Regards
    Parithi.A.

    Hi,
    Search AutoConfig for afcpctx.sh, you should find more details about the error around the filename.
    For the patch error, please search the workers log files for details about the error -- Log files can be found under $APPL_TOP/admin/<SID>/log directory (search for adwork*.log).
    Regards,
    Hussein

  • Error but no error when attempting to deploy to RT target

    OK....I have currently run into a very irritating problem.  Often when I attempt to run an Actor Framework based project on an RT target (PXIe-8135), I run into the problem where a VI seems to throw an error and causes the launch to fail (i.e. I get an error message in the deployment progress window).  It seems that the same VI is not always indicated as the source, but whatever the source, if you hit run on the VI that has a broken run arrow, you inevitably get the error window to pop up with NO errors as shown in the image below.  Anyone have any thoughts or has run into this before?
    Thanks, Matt
    Matt Richardson
    Certified LabVIEW Developer
    MSR Consulting, LLC

    Hi mtat76,
    Since reformatting drive didn’t solve the problem, I would recommend reading these links to see if we might be able to find valuable information, by checking the examples and some community information. On the context help it says that we must ensure that the Caller Actor in has already been launched, because if not, the Nested Actor VI will throw an error.
    http://zone.ni.com/reference/en-XX/help/371361L-01​/lvcomm/af_launch_nested_actor/
    https://decibel.ni.com/content/thread/11299
    https://decibel.ni.com/content/docs/DOC-24187
    https://decibel.ni.com/content/message/44213
    https://decibel.ni.com/content/docs/DOC-24051
    I hope you might be able to find the proper information on that links. You can also try with the example on the community to see if that runs properly on your RT target, and if it does, the problem might be on the program. If you encounter any other issues, it might be a compatibility issue or we need to troubleshoot further.
    Luis C.
    National Instruments

  • What is the required sda files to deploy SSO2?

    what is the required sda files to deploy SSO2?

    Hi Veeraraj,
    You would require
    1. tcsecauthjmxear.sda
    2. tcsecauthsso2wizard.sda
    these files are attached in the SAP Note 1083421 - SSO2 Wizard
    Cheers!
    Sandeep Tudumu

  • Patch error...dammit :)

    I installed the patch and got:
    svrmgrl: error in loading shared libraries: libclntsh.so.8.0: cannot open shared
    object file: No such file or directory
    Applying patch 8.1.5.0.1 .....done
    Applying patch 8.1.5.0.2 .....done
    Did it load? Or is that error serious? Do I need to correct something and then reinstall it?
    Also, I can't run dbassist like many people I see have had problems with. Unable to initialize threads: cannot find class java/lang/Thread
    Could not create Java VM
    Anyway...I decided to try and install the patch..then try again and if that doesn't work...I'm going to try installing a later version of the JVM other than 1.1.6 like Oracle says to use. If anyone knows a way around that error I'd appreciate it!
    THANK YOU THANK YOU THANK YOU...in advance.
    -Julie

    AFAIK, you do not have to rerun the root.sh script.
    I have already upgraded to 8.1.5.0.2.
    That patch error may be related to the relinking script bug that I have posted earlier.
    Basically, what I found out is that if you did not install some/all of the oracle options, the relinking will fail. The relinking script I think assumes that all the options (and related lib file) are installed, which in my initial installations were not.
    If you apply only the 8.1.5.0.1 patch, svrmgrl and sqlplus will still report 8.1.5.0.0. If you apply the .0.2 patch, in my case (when I did not install the options), I cannot run svrmgrl and therefore unable to create a database.
    Check your /tmp/81501.log and /tmp/81502.log.
    Do a grep for "No such file"
    If grep returns:
    /usr/sbin/ld: -lxxxx No such file or directory, the relinking has failed.
    null

  • Production Issue heap space error. Getting ERROR 503 Service not deployed

    Hi,
    I have deployed my web services (VAS services) in tomcat 6.0 in production .I am using axis2 1.4.1 as web service engine and apache 2.2 for httpd service. My problem is that in every 8-10 hrs when no of transactions increase, a problem occurs in my server and I get an “ERROR 503 service not deployed”. I don’t know the exact cause and solution to this problem. Presently every time I face this problem, I restart my httpd services and tomcat. Please help me to rectify this problem as this is hampering our business in a big way. I am sending the log details of catalina.log in tomcat’s log folder
    17-Nov-2008 17:20:56 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:21:36 org.apache.jk.core.MsgContext action
    WARNING: Error sending end packet
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
    at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
    at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
    at org.apache.coyote.Response.action(Response.java:183)
    at org.apache.coyote.Response.finish(Response.java:305)
    at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
    at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:21:36 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action
    WARNING: Error sending end packet
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
    at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
    at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
    at org.apache.coyote.Response.action(Response.java:183)
    at org.apache.coyote.Response.finish(Response.java:305)
    at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
    at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action
    WARNING: Error sending end packet
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
    at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
    at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
    at org.apache.coyote.Response.action(Response.java:183)
    at org.apache.coyote.Response.finish(Response.java:305)
    at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
    at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.IllegalStateException: getOutputStream() has already been called for this response
    at org.apache.catalina.connector.Response.getWriter(Response.java:604)
    at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
    at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
    at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
    at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:186)
    at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118)
    at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77)
    at org.apache.jsp.axis2_002dweb.Error.error500_jsp._jspService(error500_jsp.java:110)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:447)
    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
    at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424)
    at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343)
    at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:287)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
    Regards,
    Paritosh
    Edited by: anshu_299 on Nov 18, 2008 9:39 AM

    Hi,
    503 error comes when the client finds that the target server is not running or accessible.
    Is the java system up and running? Check if the server nodes are up ?
    check for the logs in work dir and if only server node is not coming up then check for default traces.
    Amit.

  • Do I need license to patch agent through grid control deployment wizard

    In grid control, we have license to use database diagnostics pack and database tuning pack.
    I know wihtout license for provision pack, I cannot patch database homes using grid control deployment tab. But I'm wondering if I can patch grid control agent through deployment page without license for the prvision pack.
    thanks

    There is no management pack license needed for patching the agent. You can get clear details what link needs what packs when you click on '+' symbol (Show Management Pack Information) right to the "About Oracle Enterprise Manager" at the extreme down on OEM screen.
    When you click on "Show Management Pack Information", it will show what pack needed next to every link in paranthesis. If there is no pack information mentioned next to link means, there is no license needed for that link.

  • Getting bad host error when trying to deploy simple web sample application

    hi,
    Can someone tell me why I'm getting this error when trying to deploy the simple web application from samples
    This is what it said:
    deploy_common:
    [echo] Deploying ../assemble/war/webapps-simple.war.
    [exec] java.net.MalformedURLException: Bad host: station_1
    thanks

    Hi,
    Another update on this issue.
    To remove the error that we were getting (java.lang.LinkageError: Class javax/xml/transform/Source violates loader constraints), we tried some searching around and found out that the way to fix it is to provide correct versions of xalan.jar, xml-apis.jar and xercesImpl.jar. We downloaded the required version from the apache site and added it to our WEB-INF/lib folder in the WAR file.
    Now, we are getting this error:
    XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: No XPathFctory implementation found for the object model: http://java.sun.com/jaxp/xpath/dom
    What else we might be missing in our libs or do we need to check some other configurations?
    Any help on this would be much appreciated.
    Thanks,
    Gaurav

  • Error in XCM after deploying the customized SCA

    Hi All,
    we are getting error in XCM after deploying the customized SCA in the server for UCES.
    Below is the error message when trying to access the XCM ./bdisu/admin/xcm/init.do
    link     ./bd/admin/xcm/init.do is working fine..
    ISA Framework: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [/usr/sap/EPT/JC04/j2ee/cluster/server0/apps/sap.com/isucesear/servlet_jsp/bdisu/root/admin/xcm/MainConfig.jsp].
      Details:   No details available

    Hi,
    Did you find any solution for this? We face the same problem and we are looking for a good solution.
    Kind Regards
    Daniel Jadeholt

  • A error occured when I deploy a portlet to jetspeed2

    In the portlet I connected MSSQL ,and it can run successfuly in the Pluto which embedded in creator2 .
    But a error occured when I deploy a portlet to jetspeed2.
    I looked for some solutions during the internet,and the problem may be caused by JDBC.
    Then,what should I do next?Can anyone show me a demo?
    Thanks !

    Googling shows that a lockdown folder is only avaialbe for jailbrokem iOS Devices. Jailbreaking voids the Apple warranty and you will not get any help from Apple including from the Apple forum.
    http://www.redmondpie.com/folderlock-password-protects-your-iphone-folders-setti ngs-spotlight-and-multitasking-jailbreak-tweak/

Maybe you are looking for