Errors in java SP19 deployment with SDM

hi all
when i deploy the java SP19 with the SDM i get this 2 errors with SAP_jTECHS (xml_das_connector_init) and SAP_JTECHF (XML_DAS_Init):
May 17, 2007 10:15:46... Info: Starting: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4019.00.0000.20051027101045.0000' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041026130543.0000'.
May 17, 2007 10:15:46... Info: ***** Begin of DBSC Deployment *****
May 17, 2007 10:15:46... Info: working with an OpenSQLConnection
May 17, 2007 10:15:46... Info: importmode = deleteonly
May 17, 2007 10:15:46... Info:   allow delete: true
May 17, 2007 10:15:46... Info:   allow insert: false
May 17, 2007 10:15:46... Info:   allow update: false
May 17, 2007 10:15:46... Info: -
May 17, 2007 10:15:46... Info: SAPtrans version 630.8.5
May 17, 2007 10:15:46... Info: @(#) $Id: //sdt/com.sap.sdm/630_REL/src/java/com/sap/sdm/util/dbaccess/SapTransVersion.java#5 $ SAP
May 17, 2007 10:15:46... Info: Start: Thu May 17 10:15:46 ART 2007
May 17, 2007 10:15:46... Info: Input file: /usr/sap/PMI/DVEBMGS02/SDM/root/origin/sap.com/tc/TechSrv/xml_das_connector_init/SAP AG/6.4009.00.0000.20041026130543.0000/ArchivingConnectorInit.sda
May 17, 2007 10:15:46... Info: importmode = deleteonly
May 17, 2007 10:15:46... Info:   allow delete: true
May 17, 2007 10:15:46... Info:   allow insert: false
May 17, 2007 10:15:46... Info:   allow update: false
May 17, 2007 10:15:46... Info: now processing BC_XMLA_ASETS (0_BC_XMLA_ASETS.dat)
May 17, 2007 10:15:46... Info: Success: 0 entries from BC_XMLA_ASETS deleted
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: now processing BC_XMLA_ASETS (1_BC_XMLA_ASETS.dat)
May 17, 2007 10:15:46... Info: Success: 0 entries from BC_XMLA_ASETS deleted
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: now processing BC_XMLA_ASETS (2_BC_XMLA_ASETS.dat)
May 17, 2007 10:15:46... Info: Success: 0 entries from BC_XMLA_ASETS deleted
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: now processing BC_XMLA_ASETS (3_BC_XMLA_ASETS.dat)
May 17, 2007 10:15:46... Info: Success: 0 entries from BC_XMLA_ASETS deleted
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: now processing BC_XMLA_ASETS (4_BC_XMLA_ASETS.dat)
May 17, 2007 10:15:46... Info: Success: 0 entries from BC_XMLA_ASETS deleted
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: now processing BC_XMLA_ASETS (5_BC_XMLA_ASETS.dat)
May 17, 2007 10:15:46... Info: Success: 0 entries from BC_XMLA_ASETS deleted
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: Stop: Thu May 17 10:15:46 ART 2007
May 17, 2007 10:15:46... Info: importmode = default
May 17, 2007 10:15:46... Info:   allow delete: true
May 17, 2007 10:15:46... Info:   allow insert: true
May 17, 2007 10:15:46... Info:   allow update: true
May 17, 2007 10:15:46... Info: -
May 17, 2007 10:15:46... Info: SAPtrans version 630.8.5
May 17, 2007 10:15:46... Info: @(#) $Id: //sdt/com.sap.sdm/630_REL/src/java/com/sap/sdm/util/dbaccess/SapTransVersion.java#5 $ SAP
May 17, 2007 10:15:46... Info: Start: Thu May 17 10:15:46 ART 2007
May 17, 2007 10:15:46... Info: Input file: /usr/sap/PMI/DVEBMGS02/SDM/root/origin/sap.com/tc/TechSrv/xml_das_connector_init/SAP AG/6.4019.00.0000.20051027101045.0000/ArchivingConnectorInit.sda
May 17, 2007 10:15:46... Info: importmode = default
May 17, 2007 10:15:46... Info:   allow delete: true
May 17, 2007 10:15:46... Info:   allow insert: true
May 17, 2007 10:15:46... Info:   allow update: true
May 17, 2007 10:15:46... Info: now processing entry for table BC_XMLA_ASETS (0)
May 17, 2007 10:15:46... Info: DB Error: BC_XMLA_ASETS
May 17, 2007 10:15:46... Info: Message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: SQLState: SAP06
May 17, 2007 10:15:46... Error: Code: 1001104
May 17, 2007 10:15:46... Info: now processing entry for table BC_XMLA_ASETS (1)
May 17, 2007 10:15:46... Info: DB Error: BC_XMLA_ASETS
May 17, 2007 10:15:46... Info: Message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: SQLState: SAP06
May 17, 2007 10:15:46... Error: Code: 1001104
May 17, 2007 10:15:46... Info: now processing entry for table BC_XMLA_ASETS (2)
May 17, 2007 10:15:46... Info: DB Error: BC_XMLA_ASETS
May 17, 2007 10:15:46... Info: Message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: SQLState: SAP06
May 17, 2007 10:15:46... Error: Code: 1001104
May 17, 2007 10:15:46... Info: now processing entry for table BC_XMLA_ASETS (3)
May 17, 2007 10:15:46... Info: DB Error: BC_XMLA_ASETS
May 17, 2007 10:15:46... Info: Message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: SQLState: SAP06
May 17, 2007 10:15:46... Error: Code: 1001104
May 17, 2007 10:15:46... Info: now processing entry for table BC_XMLA_ASETS (4)
May 17, 2007 10:15:46... Info: DB Error: BC_XMLA_ASETS
May 17, 2007 10:15:46... Info: Message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: SQLState: SAP06
May 17, 2007 10:15:46... Error: Code: 1001104
May 17, 2007 10:15:46... Info: now processing entry for table BC_XMLA_ASETS (5)
May 17, 2007 10:15:46... Info: DB Error: BC_XMLA_ASETS
May 17, 2007 10:15:46... Info: Message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: SQLState: SAP06
May 17, 2007 10:15:46... Error: Code: 1001104
May 17, 2007 10:15:46... Info: commit executed
May 17, 2007 10:15:46... Info: 6 SQL error(s) occured
May 17, 2007 10:15:46... Fatal: exception Throwable: com.sap.sql.log.OpenSQLException Throwable message: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Error: Error during import of database content SDA /usr/sap/PMI/DVEBMGS02/SDM/root/origin/sap.com/tc/TechSrv/xml_das_connector_init/SAP AG/6.4019.00.0000.20051027101045.0000/ArchivingConnectorInit.sda: Cannot assign NULL to host variable 1. The corresponding column "ASETNAME" in table "BC_XMLA_ASETS" is defined as NOT NULL. The statement is "INSERT INTO "BC_XMLA_ASETS" ("ASETNAME","ASETPROP","PROPVALUE","INIT","PROPTEXT","PROPPOS") VALUES (?,?,?,?,?,?)".
May 17, 2007 10:15:46... Info: ***** End of DBSC Deployment *****
May 17, 2007 10:15:46... Error: Aborted: development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4019.00.0000.20051027101045.0000':
No further description found.
May 17, 2007 10:15:48... Info: Starting: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.19.0.20061027073538' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.9.0.20041119045630'.
May 17, 2007 10:15:48... Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.19.0.20061027073538':
No further description found.
any idea?
thanks

Hi,
All the deployments which are giving error is online deployment.All the services in the engine should be up n running for this deployment.Check if all the services are up and running.
Some problem is existing with the database also.Chck with database once.
Are you running anything with ATS,like aTS scripts or something.Because,it locks some threads during the execution.If at all u r running those scripts ,stop and rerun the deployments.
reward points if helpful..................

Similar Messages

*** ERROR = The Java VM terminated with a non-zero exit code.

DEAR MASTERS
          after configuring SLD on integerated ABAP+JAVA   server0 not starting
trc file: "D:\usr\sap\W55\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name   : ID9278150
pid         : 4140
system name : W55
system nr. : 00
started at : Sat Mar 21 08:45:23 2009
arguments       :
       arg[00] : D:\usr\sap\W55\DVEBMGS00\exe\jlaunch.exe
       arg[01] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
       arg[02] : -DSAPINFO=W55_00_server
       arg[03] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
       arg[04] : -DSAPSTART=1
       arg[05] : -DCONNECT_PORT=1060
       arg[06] : -DSAPSYSTEM=00
       arg[07] : -DSAPSYSTEMNAME=W55
       arg[08] : -DSAPMYNAME=wipro5_W55_00
       arg[09] : -DSAPPROFILE=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
       arg[10] : -DFRFC_FALLBACK=ON
       arg[11] : -DFRFC_FALLBACK_HOST=localhost
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 4668] Sat Mar 21 08:58:30 2009
[Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4668] JLaunchISetClusterId: set cluster id 9278150
[Thr 4668] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4668] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 4428] Sat Mar 21 08:59:58 2009
[Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 4616] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 4616] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.

Hi,
Please find the link below for J2EE start up problem.
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d]
Please refer to following note for VM settings.
[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=723909]
Please also check the license validity on this server.
Hope this helps.
Manoj Chintawar

A simple question about deployment with SDM

I've deployted an EAR onto thte server with SDM. Now want to redeploy it. Should I undeploy the old one first, or can I simply depoy it again?

Hi Thomas
You can redeploy the Ear file through SDM by selecting the option:
"<b>update deployed SCAs/SDAs that have the same or lower component versions than the selected SCAs/SDAs</b>" after adding Ear file to deploy in deployment tab under "<b>Deployment Configuration</b>"
Cheers !!!
Best Regards
Satish Kumar.

Problems deploying with SDM on SAP Netweaver Testdrive on Linux

Hello,
I tried to deploy the System Analyzer (see SAP-Note 770702) for NW 04 on the SAP Netweaver Testdrive on Linux (Technology Preview SAP NetWeaver 04 - SAP Web Application Server on Linux and MaxDB).
When I try to deploy it with the RemoteGui, the GUI hangs after the step 2 ('show deployment proposals for SCAs/SDA's to be deployed'). There is no error in the logfiles.
When I try to deploy it on the command line (standalone modus), I get the following error:
>>>
Caught Exception: java.lang.NullPointerException
java.lang.NullPointerException
        at com.sap.sdm.serverext.sdmprovided.DeplParamVarSubstProcessorImpl.doSubstitution(DeplParamVarSubstProcessorImpl.java:238)
        at com.sap.sdm.serverext.sdmprovided.DeplParamVarSubstProcessorImpl.findSubstitution(DeplParamVarSubstProcessorImpl.java:75)
        at com.sap.sdm.serverext.servertype.fs.cpo.CPOFSJavaFileSet.<init>(CPOFSJavaFileSet.java:58)
        at com.sap.sdm.serverext.servertype.fs.cpo.CPOFSJavaFileSets.<init>(CPOFSJavaFileSets.java:41)
        at com.sap.sdm.serverext.servertype.fs.cpo.CPOFSJavaFactory.createNewFileSets(CPOFSJavaFactory.java:24)
        at com.sap.sdm.serverext.servertype.fs.FSJavaDeploymentActionProcessor.<init>(FSJavaDeploymentActionProcessor.java:87)
        at com.sap.sdm.serverext.servertype.fs.FSJavaDeploymentActionHandler.createDeploymentActionProcessor(FSJavaDeploymentActionHandler.java:25)
        at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.createDeploymentActionProcessor(PhysicalDeploymentActionExecutor.java:104)
        at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.createDeploymentActionProcessor(DeploymentActionImpl.java:102)
        at com.sap.sdm.app.proc.deployment.states.StateRequestTargets.processEvent(StateRequestTargets.java:69)
        at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
        at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.processStartInstallation(DeployerImpl.java:168)
        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:80)
        at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:182)
        at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
        at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
        at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
        at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
        at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
        at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
        at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
        at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
        at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
        at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
        at com.sap.sdm.control.command.Command.exec(Command.java:42)
        at SDM.main(SDM.java:21)
Severe (internal) error. Return code: 16
<<<
Any ideas?
Thank's a lot
Peter

Hi Peter,
Testdrive is a manipulated version that may miss some parts. It is definitely not intended for installing any additional SAP software nor tools on it.
Regards,
Benny

Online deployment with SDM

Hallo,
I have folloving problem with deploying SAPXITOOL SP14 L9.
When I started deploying there is a message that SAP WEB AS JAVA is currently stopped, but J2EE (dispatcher, server0 and SDM) is started. If SDM deploying part com.sap.aii.security.ws.proxy the SDM using online deploying.
Now there is a bad message:
Feb 24, 2006 8:23:49 AM Info: Software type of SDA: J2EE
Feb 24, 2006 8:23:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 24, 2006 8:23:49 AM Info: Starting cluster instance processes.
Feb 24, 2006 8:23:49 AM Error: An error occured while starting a cluster instance.
Feb 24, 2006 8:23:49 AM Error: There is no control instance running in the cluster:
Name:JM_T1140765829632_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Feb 24, 2006 8:23:49 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 24, 2006 8:23:49 AM Error: Aborted: development component 'com.sap.aii.security.ws.proxy'/'sap.com'/'SAP AG'/'3.0.1420060214105340.0000':
SDM could not start the J2EE cluster on the host smbxi2db! The online deployment is terminated.
There is no control instance running in the cluster:
Name:JM_T1140765829632_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Feb 24, 2006 8:23:52 AM Error: An error occured while restoring the cluster instances states
Feb 24, 2006 8:23:52 AM Error: There is no control instance running in the cluster:
Name:JM_T1140765832130_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Feb 24, 2006 8:23:52 AM Error: Received exception when restoring Engine state: There is no control instance running in the cluster:
Name:JM_T1140765832130_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Can you somebody help me to resolve this problem?
Thanks
Martin Capek

Please check if "smbxi2db" is the JAVA CI host . If not maintain correct host in secstore.
Configtool-> Secure Store -> admin/host/<SID> (JAVA CI host, Not DB host)

Error during Java Stack upgrade with SAPINST Tool for Netweaver 04

Hi,
I have updated all the ABAP stack support packages fine. But when i try to upgrade the Java Stack for the BW server using the SAPINST tool, i received an error in the 17th step "Starting J2EE Engine".
The error log says:
CJS-20057 Starting Java engine DVEBMGS05 of SAP system <SID> failed:
after 165 seconds the state of the engine changed from "Starting" to "Stopped".
Please help.
Thanks
Vijay

Hi Vijay,
Please check the link for some initial troubleshooting:
http://help.sap.com/saphelp_nw70/helpdata/en/69/430841a6e1ef6fe10000000a1550b0/frameset.htm
Regards,
Siddhesh

Error starting java in RedHat Enterprise ES v3

Hello all. I'm posting hoping someone has run into this before and might be able to help me.
We've set up a number of boxes with Redhat Enterprise ES v3, and upgraded the kernel from the stock RedHat 2.4.21 to 2.4.26 because we required reiserfs support (no idea why it isn't bundled from RedHat).
We are using j2sdk1.4.2_02.
Once the kernel was upgraded, I tried to run java and we get a strange error. Java runs fine with the stock kernel, but not with the new one.
At this point in time, I'm inclined to think I neglected to enable an option in the kernel configuration, but I went back and wasn't able to find anything.
Any idea what could be causing this issue? The complete error is below.
Thank you in advance
-Paul
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x0
Function=[Unknown.]
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
Dynamic libraries:
08048000-0804e000 r-xp 00000000 03:03 7962746 /usr/java/j2sdk1.4.2_02/bin/jav
a
0804e000-0804f000 rw-p 00005000 03:03 7962746 /usr/java/j2sdk1.4.2_02/bin/jav
a
40000000-40015000 r-xp 00000000 03:03 524292 /lib/ld-2.3.2.so
40015000-40016000 rw-p 00014000 03:03 524292 /lib/ld-2.3.2.so
40017000-4001f000 r-xp 00000000 03:03 8274108 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/native_threads/libhpi.so
4001f000-40020000 rw-p 00007000 03:03 8274108 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/native_threads/libhpi.so
40020000-4002d000 r-xp 00000000 03:03 2408456 /lib/tls/libpthread-0.60.so
4002d000-4002e000 rw-p 0000c000 03:03 2408456 /lib/tls/libpthread-0.60.so
40030000-40032000 r-xp 00000000 03:03 524305 /lib/libdl-2.3.2.so
40032000-40033000 rw-p 00001000 03:03 524305 /lib/libdl-2.3.2.so
40033000-40165000 r-xp 00000000 03:03 2408452 /lib/tls/libc-2.3.2.so
40165000-40168000 rw-p 00131000 03:03 2408452 /lib/tls/libc-2.3.2.so
4016c000-40566000 r-xp 00000000 03:03 7667771 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/client/libjvm.so
40566000-40582000 rw-p 003f9000 03:03 7667771 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/client/libjvm.so
40594000-405a6000 r-xp 00000000 03:03 524309 /lib/libnsl-2.3.2.so
405a6000-405a7000 rw-p 00011000 03:03 524309 /lib/libnsl-2.3.2.so
405a9000-405ca000 r-xp 00000000 03:03 2408454 /lib/tls/libm-2.3.2.so
405ca000-405cb000 rw-p 00020000 03:03 2408454 /lib/tls/libm-2.3.2.so
405cb000-405cf000 rw-s 00000000 03:03 5292244 /tmp/hsperfdata_root/7828
405d4000-405df000 r-xp 00000000 03:03 524325 /lib/libnss_files-2.3.2.so
405df000-405e0000 rw-p 0000a000 03:03 524325 /lib/libnss_files-2.3.2.so
405e0000-405f0000 r-xp 00000000 03:03 7045311 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/libverify.so
405f0000-405f2000 rw-p 0000f000 03:03 7045311 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/libverify.so
405f2000-40612000 r-xp 00000000 03:03 7045297 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/libjava.so
40612000-40614000 rw-p 0001f000 03:03 7045297 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/libjava.so
40614000-40628000 r-xp 00000000 03:03 7045312 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/libzip.so
40628000-4062b000 rw-p 00013000 03:03 7045312 /usr/java/j2sdk1.4.2_02/jre/lib
/i386/libzip.so
4062b000-41fc3000 r--s 00000000 03:03 3768491 /usr/java/j2sdk1.4.2_02/jre/lib
/rt.jar
4200d000-42023000 r--s 00000000 03:03 3768490 /usr/java/j2sdk1.4.2_02/jre/lib
/sunrsasign.jar
42023000-420fe000 r--s 00000000 03:03 3768489 /usr/java/j2sdk1.4.2_02/jre/lib
/jsse.jar
420fe000-4210f000 r--s 00000000 03:03 3768481 /usr/java/j2sdk1.4.2_02/jre/lib
/jce.jar
4210f000-42668000 r--s 00000000 03:03 3768482 /usr/java/j2sdk1.4.2_02/jre/lib
/charsets.jar
Heap at VM Abort:
Heap
def new generation total 576K, used 0K [0x44710000, 0x447b0000, 0x44bf0000)
eden space 512K, 0% used [0x44710000, 0x44710048, 0x44790000)
from space 64K, 0% used [0x44790000, 0x44790000, 0x447a0000)
to space 64K, 0% used [0x447a0000, 0x447a0000, 0x447b0000)
tenured generation total 1408K, used 0K [0x44bf0000, 0x44d50000, 0x48710000)
the space 1408K, 0% used [0x44bf0000, 0x44bf0000, 0x44bf0200, 0x44d50000)
compacting perm gen total 4096K, used 276K [0x48710000, 0x48b10000, 0x4c710000
the space 4096K, 6% used [0x48710000, 0x48755070, 0x48755200, 0x48b10000)
Local Time = Sat Jun 26 13:20:19 2004
Elapsed Time = 0
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.2_02-b03 mixed mode)

Hi ditg.
I have no idea what was causing the problem on 2.4.26, but at this point in time, I'm almost 100% sure it's a kernel-specific issue.
The workaround I came up with was rebuild the 2.4.21 kernel using the RedHat sources, disabling all the non-necessary modules and basically make it as slim as possible.
Once we successfully recompiled 2.4.21, j2sdk1.4.2.02/3/4 runs fine.
Hope this helps....
-Paul

Java VM terminated with a non-zero exit code (rc = -337)

Hi,
It seems that our portal (7.0) was unavailable for five minutes (all users experienced problems which after a few minutes solved itself). We had a look at the logs, and dev_server0 shows that the server node did shut down and start again:
[Thr 6688] Wed Aug 13 10:19:36 2014
[Thr 6688] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 6688] **********************************************************************
[Thr 6688] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 6688] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 6688] *** for additional information and trouble shooting.
[Thr 6688] **********************************************************************
[Thr 6688] JLaunchCloseProgram: good bye (exitcode = -337)
The referenced note doesn't offer much help. I've tried to find more info about rc -337, and the only info I've found is that rc -337 is: "Exiting listener loop - restart the node (MSLib)."
Do you guys know what exiting listener loop means, or what the rc -377 is?
Thanks!
M.

Hi Moye,
Hope you are doing good.
Such issues can also be caused due to a network failure. Can you check the below notes along with the network administrator to ascertain that there are no network related issues presently:
#124562     Hostname resolution problems (DNS timeouts)
#500235     Network Diagnosis with NIPING
#413330     Network timeout
If you run the niping tool at the time the issue occurred, it should check the whole network and report the error.
It is also possible to optimize the j2ee server in the manner it interacts with the message server for better performance. As Divyanshu mentioned, the note 1658385 - J2EE System fails with "exitcode = -334" explains, you need to optimize the manner in which the message server reconnects with the Java instances.
This can happen sometimes if you have quite a few nodes in cluster. To make sure the issue does not happen again, you need to increase for each server node the timeout it waits for the confirmation,
that is the value of 'ms.confirmation.timeout' property of ClusterManager along with the other parameters mentioned in the note. Also add the below parameters to the SCS instance file:
<sid>_SCS01_<host> in folder /usr/sap/<sid>/SYS/profile
ms/max_clients = 600
ms/max_open_requests = 2000
ms/audit=1
and
jstartup/keep_old_logfiles=3
The latter 2 parameters will prevent overwritting log files in case of restart. Once the values are increased, the time for the timeout should increase enabling the server to connect to the message server.
Thank you!
Kind Regards,
Hemanth
SAP AGS

The Java VM terminated with a non-zero exit code.

Hi,expert,
I have got this error when I am trying to restart the sap Instance use
command STARTSAP,
The error log as below:
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 940893 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
trc file: "/usr/sap/J2E/JC00/work/dev_jcontrol", trc level: 1,
release: "640"
ERROR => can't retrieve client list (rc=24) [jcntrms_mt.c960]
May 21, 2010 12:53:14... com.sap.engine.core.Framework [SAP
J2EE Engi
ne|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is:
Exiting
Listener Loop. This requires a restart of the node. Possible reason is
an interr
upted reconnect session to the message server.
Thanks and Best regards,
Michael

Hi Michael,
I am also facing the same issue, can you please let me know where to find the ms.hostname and enqu.hostname...It's very urgent.
Thanks in advance..
Regards,
Krishna.M

Java VM terminated with a non-zero exit code (-337)

We are running a J2EE application on NW7.0 and IBM i5 V5R4.
The application server restarts itself after the server0 proces terminates with the following messages in the dev_server0.log
[Thr 2057] Sat Jun 20 09:34:12 2009
[Thr 2057] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 2057]
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 2057] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 2057] JLaunchCloseProgram: good bye (exitcode = -337)
The mentioned Sapnote 943602 refers to Note 940893, which suggest to send the logfiles to Support (which we did).
But can anyone shed a light on this? What can we learn from the mentioned exit codes?
Thanks
Anita

Hi Sunny,
Here's the last part of the dev_server0 log:
Sat Jun 20 09:17:38 2009
GC 12352: live objects 6177736; collected objects 7188118; collected(KB) 775717.
GC 12352: queued for finalization 0; total soft references 8982; cleared soft references 0.
GC 12352: current heap(KB) 2416964; current threshold(KB) 786432.
GC 12352: collect (milliseconds) 3423.
GC 12352: current cycle allocation(KB) 317872; previous cycle allocation(KB) 786457.
GC 12352: total weak references 15151; cleared weak references 0.
GC 12352: total final references 11901; cleared final references 7466.
GC 12352: total phantom references 0; cleared phantom references 0.
GC 12352: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12352: collection ending 20/06/09 09:17:38
Sat Jun 20 09:17:41 2009
GC 12353: starting collection, threshold allocation reached.
GC 12353: collection starting 20/06/09 09:17:41
Sat Jun 20 09:17:44 2009
GC 12353: live objects 6220831; collected objects 7043383; collected(KB) 785764.
GC 12353: queued for finalization 0; total soft references 8974; cleared soft references 0.
GC 12353: current heap(KB) 2415944; current threshold(KB) 786432.
GC 12353: collect (milliseconds) 3003.
GC 12353: current cycle allocation(KB) 294375; previous cycle allocation(KB) 786464.
GC 12353: total weak references 15151; cleared weak references 0.
GC 12353: total final references 10853; cleared final references 6411.
GC 12353: total phantom references 0; cleared phantom references 0.
GC 12353: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12353: collection ending 20/06/09 09:17:44
Sat Jun 20 09:17:47 2009
GC 12354: starting collection, threshold allocation reached.
GC 12354: collection starting 20/06/09 09:17:47
Sat Jun 20 09:17:54 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:18:23 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:20:10 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:20:23 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:20:30 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:31 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:32 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:34 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:35 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:36 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:38 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:39 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:45 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:46 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:50 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:58 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:21:00 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:21:21 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:21:50 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:22:40 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:22:42 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:22:50 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:24:46 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:24:47 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:24:50 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:25:06 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:25:51 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:27:04 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:28:28 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:28:42 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:29:19 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:30:46 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:31:08 2009
GC 12354: live objects 6994240; collected objects 6961336; collected(KB) 789682.
GC 12354: queued for finalization 0; total soft references 8976; cleared soft references 3.
GC 12354: current heap(KB) 4194292; current threshold(KB) 786432.
GC 12354: collect (milliseconds) 801210.
GC 12354: current cycle allocation(KB) 0; previous cycle allocation(KB) 4242195.
GC 12354: total weak references 15151; cleared weak references 0.
GC 12354: total final references 10905; cleared final references 6451.
GC 12354: total phantom references 0; cleared phantom references 0.
GC 12354: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12354: collection ending 20/06/09 09:31:08
GC 12355: collection starting 20/06/09 09:31:08
Sat Jun 20 09:31:18 2009
GC 12356: starting collection, maximum allocation reached.
Sat Jun 20 09:32:38 2009
GC 12356: starting collection, maximum allocation reached.
Sat Jun 20 09:33:48 2009
GC 12355: collected class sun/reflect/GeneratedMethodAccessor3620979168.
Sat Jun 20 09:33:59 2009
GC 12355: live objects 6717156; collected objects 29066552; collected(KB) 3256489.
GC 12355: queued for finalization 0; total soft references 8973; cleared soft references 89.
GC 12355: current heap(KB) 4193652; current threshold(KB) 786432.
GC 12355: collect (milliseconds) 170434.
GC 12355: current cycle allocation(KB) 75; previous cycle allocation(KB) 0.
GC 12355: total weak references 15164; cleared weak references 0.
GC 12355: total final references 32619; cleared final references 28210.
GC 12355: total phantom references 0; cleared phantom references 0.
GC 12355: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12355: collection ending 20/06/09 09:33:59
GC 12356: collection starting 20/06/09 09:33:59
Sat Jun 20 09:34:01 2009
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor746382538.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3780712466.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor168496322.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor980237086.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1886738503.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1251676621.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1433437257.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1328663959.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3914321935.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor333360639.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3292847473.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor752085389.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor416310187.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor3620979168.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor2138604126.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor2058455930.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor599442064.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor853421746.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1143931263.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor379179616.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1925696964.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor57815531.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor843740711.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor2093346596.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1446511408.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1446703216.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1522492322.
Sat Jun 20 09:34:02 2009
GC 12356: collected class sun/reflect/GeneratedMethodAccessor1786850049.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor515968301.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor1786794657.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor516161133.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor2753180717.
GC 12356: live objects 4366863; collected objects 2655706; collected(KB) 255573.
GC 12356: queued for finalization 0; total soft references 8976; cleared soft references 0.
GC 12356: current heap(KB) 3147644; current threshold(KB) 786432.
GC 12356: collect (milliseconds) 3478.
GC 12356: current cycle allocation(KB) 25809; previous cycle allocation(KB) 0.
GC 12356: total weak references 15164; cleared weak references 0.
GC 12356: total final references 4422; cleared final references 11.
GC 12356: total phantom references 0; cleared phantom references 0.
GC 12356: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12356: collection ending 20/06/09 09:34:02
[Thr 2057] Sat Jun 20 09:34:12 2009
[Thr 2057] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 2057] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 2057] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 2057] JLaunchCloseProgram: good bye (exitcode = -337)
trc file: "/usr/sap/P01/DVEBMGS01/work/dev_server0", trc level: 1, release: "700"

The error when I deploy ess application with SDM

SOS!!!when I deploy ess application with SDM(ESS05P_1-10002965.sca), It failed.please help me.
The trace file:
#1.5#00145ED221BE00F7000000B90011A07C0004421B32EEBBA8#1198584492898#com.sap.engine.services.webdynpro.WebDynproContainer##com.sap.engine.services.webdynpro.WebDynproContainer#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/UserInterface#Java###Failed to deploy application '''' for deployment state listener ''''.
[EXCEPTION]
#3#sap.com/essauaddr#com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook#com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file '/usr/sap/EP1/DVEBMGS02/j2ee/cluster/server0/./temp/webdynpro/public/sap.com/essauaddr/webdynpro/Applications/com.sap.xss.hr.per.au.address.Per_Address_AU/Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     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:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     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:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00145ED221BE00F7000000BB0011A07C0004421B32EF7CEE#1198584492948#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation deploy with application sap.com/essauaddr.#2#deploy#sap.com/essauaddr#
#1.5#00145ED221BE00F7000000BC0011A07C0004421B32EF7F24#1198584492949#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation deploy with application sap.com/essauaddr.
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:294)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     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:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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:215)
     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.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application sap.com/essauaddr.
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
     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)
     ... 13 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     ... 15 more

Check these below links
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4611860
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4562067
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4258751
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4474525
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4543091
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4368694
reward points if helpful

SP09- SP14 deployment error: caf~bw~ear fails with NoClassDefFoundError

Hi,
The following error occurs when upgrading a portal from NW2004s (Java AS 7.00) SP09 to SP14. A similar portal has been upgraded from SP11 to SP14 without problems, so we're thinking of first patching the CAF application from SP09 to SP11 before proceeding to SP14.
The key errors are:
Exception in operation update with application sap.com/cafbwear..
                     Reason: com/sap/caf/bw/api/IBWProcessorLocal; nested exception is:
                    java.lang.NoClassDefFoundError: com/sap/caf/bw/api/IBWProcessorLocal
The error occurred while trying to load "com.sap.caf.bw.services.bwprocessor.BWProcessorLocal".
Anyone experienced the same problem?
Jan 17, 2008 8:31:20 AM Info: Starting: Update: Selected development component 'caf/bw/ear'/'sap.com'/'MAIN_APL70VAL_C'/'1497856'/'2' updates currently deployed development component 'caf/bw/ear'/'sap.com'/'MAIN_APL70VAL_C'/'946553'/'1'.
Jan 17, 2008 8:31:20 AM Info: SDA to be deployed: /usr/sap/ES3/JC87/SDM/root/origin/sap.com/caf/bw/ear/MAIN_APL70VAL_C/2/1497856/cafbwear.sda
Jan 17, 2008 8:31:20 AM Info: Software type of SDA: J2EE
Jan 17, 2008 8:31:20 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 17, 2008 8:31:27 AM Info: Begin of log messages of the target system:
08/01/17 08:31:20 - ***********************************************************
08/01/17 08:31:21 - Start updating EAR file...
08/01/17 08:31:21 - start-up mode is lazy
08/01/17 08:31:21 - EAR file updated successfully for 413ms.
08/01/17 08:31:21 - Start updating...
08/01/17 08:31:22 - EAR file uploaded to server for 541ms.
08/01/17 08:31:27 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Exception in operation update with application sap.com/cafbwear..
                     Reason: com/sap/caf/bw/api/IBWProcessorLocal; nested exception is:
                          java.lang.NoClassDefFoundError: com/sap/caf/bw/api/IBWProcessorLocal
Loader Info -
                     ClassLoader name: [sap.com/cafbwear]
                      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
                        library:com.sap.mw.jco
                        common:library:bimmrcore;library:bimmrdb
                        library:bimmrjmi
                        library:com.sap.tc.Logging
                        library:bimmrcwm_1.0_library
                        service:applocking
                        sap.com/cafruntimeear
                        sap.com/com.sap.jdo
                        library:com.sap.ip.bi.sdk
                        library:tcddicddicruntime
                        library:tcconnconnectorframework
                        library:tc~cmi
                        library:tcddicddicservices
                        service:webdynpro
                        library:cafruntimeapi~lib
                        library:cafruntimeuicouplingapilib
                      Resources:
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/EJBContainer/applicationjars/sap.comcafbw~services.jar
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/servlet_jsp/bwtest/work
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/EJBContainer/clientjars/clientsap.comcafbw~services.jar
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/servlet_jsp/bwtest/root/WEB-INF/classes
                      Loading model: {parent,references,local}
                     The error occurred while trying to load "com.sap.caf.bw.services.bwprocessor.BWProcessorLocal".
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                          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(Native Method)
                          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: java.lang.NoClassDefFoundError: com/sap/caf/bw/api/IBWProcessorLocal
Loader Info -
                     ClassLoader name: [sap.com/cafbwear]
                      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
                        library:com.sap.mw.jco
                        common:library:bimmrcore;library:bimmrdb
                        library:bimmrjmi
                        library:com.sap.tc.Logging
                        library:bimmrcwm_1.0_library
                        service:applocking
                        sap.com/cafruntimeear
                        sap.com/com.sap.jdo
                        library:com.sap.ip.bi.sdk
                        library:tcddicddicruntime
                        library:tcconnconnectorframework
                        library:tc~cmi
                        library:tcddicddicservices
                        service:webdynpro
                        library:cafruntimeapi~lib
                        library:cafruntimeuicouplingapilib
                      Resources:
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/EJBContainer/applicationjars/sap.comcafbw~services.jar
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/servlet_jsp/bwtest/work
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/EJBContainer/clientjars/clientsap.comcafbw~services.jar
                        /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/servlet_jsp/bwtest/root/WEB-INF/classes
                      Loading model: {parent,references,local}
                     The error occurred while trying to load "com.sap.caf.bw.services.bwprocessor.BWProcessorLocal".
                          at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
                          at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:91)
                          at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
                          at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
                          at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
                          at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
                          at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:298)
                          at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
                          at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                          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:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
                          ... 10 more
                     For detailed information see the log file of the Deploy Service.
08/01/17 08:31:27 - ***********************************************************
Jan 17, 2008 8:31:27 AM Info: End of log messages of the target system.
Jan 17, 2008 8:31:27 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 17, 2008 8:31:27 AM Error: Aborted: development component 'caf/bw/ear'/'sap.com'/'MAIN_APL70VAL_C'/'1497856'/'2', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Exception in operation update with application sap.com/cafbwear..
Reason: com/sap/caf/bw/api/IBWProcessorLocal; nested exception is:
     java.lang.NoClassDefFoundError: com/sap/caf/bw/api/IBWProcessorLocal
Loader Info -
ClassLoader name: [sap.com/cafbwear]
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
   library:com.sap.mw.jco
   common:library:bimmrcore;library:bimmrdb
   library:bimmrjmi
   library:com.sap.tc.Logging
   library:bimmrcwm_1.0_library
   service:applocking
   sap.com/cafruntimeear
   sap.com/com.sap.jdo
   library:com.sap.ip.bi.sdk
   library:tcddicddicruntime
   library:tcconnconnectorframework
   library:tc~cmi
   library:tcddicddicservices
   service:webdynpro
   library:cafruntimeapi~lib
   library:cafruntimeuicouplingapilib
Resources:
   /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/EJBContainer/applicationjars/sap.comcafbw~services.jar
   /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/servlet_jsp/bwtest/work
   /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/EJBContainer/clientjars/clientsap.comcafbw~services.jar
   /usr/sap/ES3/JC87/j2ee/cluster/server0/apps/sap.com/cafbwear/servlet_jsp/bwtest/root/WEB-INF/classes
Loading model: {parent,references,local}
The error occurred while trying to load "com.sap.caf.bw.services.bwprocessor.BWProcessorLocal".
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jan 17, 2008 8:31:27 AM Info: Starting to save the repository
Jan 17, 2008 8:31:54 AM Info: Finished saving the repository
Jan 17, 2008 8:31:54 AM Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062838''/'2' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.9.0.20060825071023''/'2'.
Jan 17, 2008 8:31:54 AM Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062838''/'2':
Failed deployment of SDAs:
development component 'caf/bw/ear'/'sap.com'/'MAIN_APL70VAL_C'/'1497856'/'2' : aborted
Please, look at error logs above for more information!

It seems the root cause is the failure of cafruntimeear to startup after it has been upgraded.
It receives a java.lang.StackOverflowError without any more explanation.
Jan 16, 2008 10:05:36... Warning: Finished with warnings: development component 'caf/runtime/ear'/'sap.com'/'MAIN_APL70VAL_C'/'1534014'/'1', grouped by :
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/caf/runtime/ear and wait.
Reason: Clusterwide exception: server ID 871120050:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while preparing start of application sap.com/cafruntimeear.
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:233)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
     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(Native Method)
     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: java.lang.StackOverflowError

Java DC not deployed with WebDynPro DC

Hi,
I've been testing the DC functionality and I'm trying to create the following:
1) WebDynPro DC (DCA)
2) Java DC (DCB)
DCB has code for reading data from a database table (three classes, one is set as a public part). This code is functioning ok in another WebDynpro project where I've used it as an external jar file located in the lib directory and added to classpath.
DCA has a small table in the view that I'm filling (or trying to) with data from the database.
DCB has one java class as a Public Part. DCA has this PP defined in the Used DC's (DC Metadata --> DC definition --> Used DC's). I can see the DCB code fine from the DCA's view (I can use the methods from the class).
I see no code errors and everything compiles ok. I've built the DCA and DCB separately (Development Component --> Build) before doing the project build and deployment.
When I deploy, I'm getting java.lang.NoClassDefFoundError for the DCB class (User.class) when the program starts. So it seems that the DCB is not deployed with the DCA. I've tried to look at the properties and java classpath but nothing I've done has helped.
Purpose is set to compilation, and there is a
<at-build-time/>
tag in the .dcdef file.
Deployment of normal (no DC) Webdynpro projects works fine and the jars in the lib directory are deployed to the server OK.
Seems like I've tried everything but have found no solution yet. Refreshed every part, re-created everything, re-built, re-deployed etc...
Shortly: how to get DCB to deploy ?
Any help is appreciated here
Kind Regards,
Jari Pakarinen

Hi,
What is the Java DC for then ? If it cannot be used as a part of another DC (deployable unit) then how should it be used ? What is the use if it does not end up at the server with Webdynpro code ?
The scenario I'm looking for is to include Java classes in a Webdynpro project as a part of the project (not jars done somewhere else, I can do that already) deployed to the server with the Webdynpro.
Thank you for your help, I'm not blaming you or anything
Regards,
Jari

Netweaver 7.3 AS Java Installation Error in Java Deploy (30th step) of 33.

Hi Experts,
I'm installing Netweaver Application Java 7.3 with the following system credentials.
1) Windows 7.0 - 64 bit
2) 6 GB RAM, 150 GB HDD
Software folders downloaded -
1) 510415560_16 (NW730_WPL_IM_WIN_X86_64_ADA) - SAPINST.exe file (started this first)
2) 51039309 Java Part 1 to Java Part 6.- Given the path of this for the java request from 51039309 java Part1.exe
3) 51038550_10 for MAX DB
4) JCE_POLICY -6.zip
and I was unfortunately stuck in Java deployment step that is 30 of 33.
undefinedStatus:AlreadyDeployedDescription:1. Already deployed component has version:1000.7.30.0.0.20101020230400. SOLUTION: Check 'undefined' and '' for more information
Saw similar issue in the threads but no response, I would be very happy if you can provide me any clue in resolving this.
Thanks,
Raj.

Thanks Naveen and Prander,
I think it is just Netweaver 7.3 Web AppServer Java (I have searched the market place it did not say anything about the version EHP),
so as said by Naveen try to start the server manually, it says some processes running (safe mode) and also the
developer trace says
Warning => Node Server0 failed : result 1, exit code 666.
and restarted the installation got the latest error as below:
An error occurred while processing option SAP NetWeaver 7.3 Developer Edition > Install > Typical Server Installation( Last error reported by the step: Execution of Deploy Controller Runner tool '
C:\Program Files\sapinst_instdir\NW73\INSTALL\SERVER\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/ProgramFiles/sapinst_instdir/NW73/INSTALL/SERVER/install/lib;
C:/usr/sap/CE7/SYS/global/security/lib/tools/iaik_jce.jar;
C:/usr/sap/CE7/SYS/global/security/lib/tools/iaik_jsse.jar;
C:/usr/sap/CE7/SYS/global/security/lib/tools/iaik_smime.jar;
C:/usr/sap/CE7/SYS/global/security/lib/tools/iaik_ssl.jar;
C:/usr/sap/CE7/SYS/global/security/lib/tools/w3c_http.jar;
C:/usr/sap/CE7/J00/j2ee/j2eeclient/sap.comtcexception~impl.jar;
C:/usr/sap/CE7/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;
C:/usr/sap/CE7/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;
C:/Program Files/sapinst_instdir/NW73/INSTALL/SERVER/install/lib/tcjecl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW73/INSTALL/SERVER/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host <host> --port 50004'
aborts with return code 1. Error message is 'undefined. SOLUTION: Check 'undefined' and '' for more information.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/NW73/INSTALL/SERVER.

NWDS 7.0 deployement error with SDM

Hello,
It seems that my SDM host is not correctly configured, when I try to deploy, the SDM host ip is not correct, I am thus getting this error:
02-juil.-2008 14:41:38 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Settings
SDM host : *WrongIP*
SDM port : 50018
URL to deploy : file.ear
Deployment exception : Server *WrongIP* did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server *WrongIP* at port 50018: Connection timed out: connect
Inner exception was :
Server *WrongIP* did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server *WrongIP* at port 50018: Connection timed out: connect
Where can I change this configuration?
I've checked the sdmrepository.sdc, the defined host is correct (it's not a ip but a hostname).
We have user IPs and admin IPs thus two networks for the machine hosting those servers.
I don't know at which level to look: Message Server, Dispatcher or Network Config.
Thx for your help,
Tanguy

Hi,
Did you add server IP and hostname in HOSTS file under C:\WINDOWS\system32\drivers\etc ?
If you did that then....
Deployment error occurs when deploying from IDE, the following message is displayed:
Server XXX did not accept login request as admin on port 50018
Details: ERROR: Could not establish connection to server XXX at port
50018: XXX
If you use the SDM remote GUI with the same SDM host and port, you can deploy successfully.
Solution
This problem can be fixed without any code changes just by adding a corresponding record to the file %WINDIR%/system32/drivers/etc/hosts on the IDE host, so that the remote host short name is known to the local host.
For more information, see SAP Note 783965.
from http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm
regards,
Pradeep

Errors in java SP19 deployment with SDM

Similar Messages

Maybe you are looking for