Solved: Unable to start java engine: dispatcher status is ...

Hello All,

We had for some dag ago upgread XI/PI server form 7.0 to 7.3 and every thing works well.

Now we have problem to start dispatcher will not start :

Message Server connection ok, Dialog Queue time: 0.00 sec, AS Java: Some processes failed.

from dev_disp:

Tue Jul 31 15:22:33 2012

***LOG Q0I=> NiIRead: P=127.0.0.1:50640; L=127.0.0.1:64991: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 16/sock 656

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:50640; L=127.0.0.1:64991) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4244)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Tue Jul 31 15:22:50 2012

J2EE server info

start = TRUE

state = STARTED

pid = 1900

argv[0] = C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE

argv[1] = C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE

argv[2] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64990

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=PID

argv[7] = -DSAPMYNAME=PIMNT10_PID_00

argv[8] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Tue Jul 31 15:22:51 2012

DpJ2eeLogin: j2ee state = CONNECTED

Tue Jul 31 15:22:53 2012

***LOG Q0I=> NiIRead: P=127.0.0.1:50650; L=127.0.0.1:64990: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 57/sock 452

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:50650; L=127.0.0.1:64990) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=1900)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

from dev_jstart :

********************************************************************************

F Process collector started with pid 5036

F ********************************************************************************

F [Thr 5312] *** LOG => Process flightrec started (pid 5036).

F [Thr 5312] *** LOG => Process flightrec stopping (pid 5036).

F [Thr 5748] Tue Jul 31 14:28:40 2012

F [Thr 5748] *** LOG => Signal 13 SIGCHLD.

F [Thr 5312] *** LOG => Process flightrec stopped (pid 5036).

F [Thr 5312] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).

F [Thr 5312] *** LOG => Run level 1 completed.

F [Thr 5312] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

F ********************************************************************************

F *** ERROR => Node 'deployment' failed with exit code -21003.

Any help

Thanks

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hello Reza,

from my point of view it looks like Java server coudn't establish connection to the ABAP sever during startup due to RFC issue. I guess the problem belonss to the ABAP side.

My suggestion:

1. Reboot the entire host if it's possible and see if the prblem still persists

2. If not, you can try to reset gateway cache/host name buffer at gateway monitor (ABAP side: tcd SMGW - > Expert functions)

Best regards,

Ilya

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello IIya,

No there is no conection issue on SM21.

Thanks

Just to be on the safe side:

Is evrything ok with the free disk space?

Regards,

Ilya

Thanks for reply:

Yes there is more then 7GB frre space on disk.

Du you know how can I Reboot the entire host?

Thanks

Hi Reza,

You can do by using the MMC in windows. First you need to shutdown the instances and then database.

Also you can just start the java instance without abap after the database.

Hi Silambharasan,

I did tried that I did restart windows server too, but no help,

Du you know on OS windows 2008r2 after upgrade memory should chenge heap size of Java for OS too?

I have very his is very strang problem.

Thank

Hi Reza,

Found this relevant notes,

Note 88416 - Zero administration memory management for the ABAP server

Note 759669 - java.lang.OutOfMemory - the system is out of resources

Note 1405732 - "OutOfMemoryError: Java heap space" in Web service component

Note 146528 - Configuration of R/3 on hosts with much RAM ( not applicable )

Note 723909 - Java VM settings for J2EE 6.40/7.0

Check this too http://scn.sap.com/thread/2116343

Thanks for reply

I am going to see this Note.

Hi Silambharasan and all of you,

Thanks a lot for help.

At last my server is working now.

The problem was the class com/sap/engine/offline/OfflineToolStart that is part of
the launcher.jar, located in the C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bootstrap folder was missing.

I see that this folder does not exist, there is not bootstrap folder
under cluster directory.

Looking at the traces I could check that the folder existed 2 days ago, for some reason it disappeared, this is the cause of the problem.

I did copy bootstrap folder from C:\usr\sap\PID\SYS\global\bootstrap and server working now.

Thanks

Reza

Hi Reza,

Hope now you are freed from that issue

This forum gives me lot of interesting learning to me

Hi Silambharasan,

Yes I am, I was finsh with this part on mandag, but some how the bootstrap folder was disappeared. Very strange. And the same her i did learned a lot.

Have a nice dag.

Reza

Answers (1)

***LOG Q0I=> NiIRead: P=127.0.0.1:50650; L=127.0.0.1:64990: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]
*** ERROR => NiIRead: SiRecv failed for hdl 57/sock 452
    (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:50650; L=127.0.0.1:64990) [nixxi.cpp    5087]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

This look like a network / firewall issue rather than a problem with the engine itself.

Regards.

Juan

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Juan,

The Firewl is disconnected. I can ping my server form another client and server. Any Idea how can I check it if it is network problem.

I get this error on jstart:

AS Java: Some processes failed.

It is strang The only thing I don yesterdag we incress the memmory from 4GB to 8MG and restert the server.

Any idea

Thanks

We need more info, can you check dev_jcontrol , dev_server0 and dev_dispatcher for errors?

Regards

Juan

Thanks again,

Her is last part og dev_disp:

Tue Jul 31 16:15:11 2012
DpJ2eeLogin: j2ee state = CONNECTED

Tue Jul 31 16:15:12 2012
***LOG Q0I=> NiIRead: P=127.0.0.1:52126; L=127.0.0.1:64833: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]
*** ERROR => NiIRead: SiRecv failed for hdl 22/sock 1668
(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:52126; L=127.0.0.1:64833) [nixxi.cpp 5087]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6436)
*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]
DpIJ2eeShutdown: j2ee state = SHUTDOWN

Tue Jul 31 16:15:30 2012
J2EE server info
start = TRUE
state = STARTED
pid = 6788
argv[0] = C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
argv[1] = C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
argv[2] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64832
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=PID
argv[7] = -DSAPMYNAME=PIMNT10_PID_00
argv[8] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Tue Jul 31 16:15:31 2012
DpJ2eeLogin: j2ee state = CONNECTED

Tue Jul 31 16:15:33 2012
***LOG Q0I=> NiIRead: P=127.0.0.1:52133; L=127.0.0.1:64832: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]
*** ERROR => NiIRead: SiRecv failed for hdl 63/sock 1760
(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:52133; L=127.0.0.1:64832) [nixxi.cpp 5087]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6788)
*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]
DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thanks

And more strange is the last opdate log file from dev_server0 is from yesterdag befor i restert server and not for todag. det same for dev_jcontrol.

her is last part of log file from dev_server0:

J Mon Jul 30 15:45:17 2012

J 17065.132: [GC 17065.133: [ParNew: 366109K->23775K(381696K), 0.1947253 secs] 1540655K->1198321K(2059008K), 0.1950016 secs] [Times: user=0.19 sys=0.05, real=0.19 secs]

M [Thr 6960] Mon Jul 30 15:45:22 2012

M [Thr 6960] CCMS: closeMonitoringSegment(): inside static JMON Lib: nothing to do.

I [Thr 7984] Mon Jul 30 15:45:22 2012

I [Thr 7984] WARNING: MPI Pipe 6 still in use 1 0 0(-1) 0(-1)

F [Thr 7360] Mon Jul 30 15:45:34 2012

F [Thr 7360] *** LOG => State changed from 5 (Stopping) to 6 (Stopped).

F [Thr 7360] *** LOG state real time: 72.611 CPU time: 3.484 sys, 33.640 usr

F [Thr 7360] *** LOG total real time: 17081.544 CPU time: 85.218 sys, 587.750 usr

F [Thr 7360]

J Mon Jul 30 15:45:35 2012

J Heap

J par new generation reserved 419840K, committed 419840K, used 206769K [0x000000007fff0000, 0x00000000999f0000, 0x00000000999f0000)

J eden space 343552K, 53% used [0x000000007fff0000, 0x000000008b2a4558, 0x0000000094f70000)

J from space 38144K, 62% used [0x0000000094f70000, 0x00000000966a7fc8, 0x00000000974b0000)

J to space 38144K, 0% used [0x00000000974b0000, 0x00000000974b0000, 0x00000000999f0000)

J concurrent mark-sweep generation reserved 1677312K, committed 1677312K, used 1175162K [0x00000000999f0000, 0x00000000ffff0000, 0x00000000ffff0000)

J concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 515649K [0x00000000ffff0000, 0x000000013fff0000, 0x000000013fff0000)

F [Thr 7032] Mon Jul 30 15:45:59 2012

F [Thr 7032] *** LOG => SfCJavaVm: exit hook is called. (rc = 0)

F [Thr 7032] *** LOG => exiting (exitcode 0, retcode 0).

M [Thr 7032] CCMS: CCMS Monitoring Cleanup finished successfully.

Thanks again

Yes, that means that the engine has not managed to go by the initial dispatcher error.

Can you open configtool or VA?... beside the Memory Upgrade, have you done anything else?

Regards, Juan

Hi Reza,

Can you paste the jvm_bootstrap error message to analysis the issue better

Hi Reza,

And also check this niping -s -I t=0

If any network error occurring or not.

Hello Juan,

No I am just don memory upgrade and restart server, and yes I can open configtool?

Thanks again

Hi Reza,

Can you do the check with the help of this note,

Note 155147 - WinNT: Connection reset by peer

Which is related to LOG Q0I=> NiIRead: P=127.0.0.1:50640; L=127.0.0.1:64991: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

Hope this helps.

Hello Silambharasan

Thanks for reply: What do you mean I should check this niping -s -I t=0, or where can I check it?

Her is jvm_bootstrap log but it is from yesterdag befor I upgrade memory. I did just restart server bur jvm_jvm_bootstrap not opdatete.:

   INFO: Loading tool launcher...
   INFO: [OS: Windows Server 2008 R2] [VM vendor: SAP AG] [VM version: 1.6.0_33] [VM type: SAP Java Server VM]
   INFO: Main class to start: "com.sap.engine.bootstrap.Bootstrap"
   INFO: Loading 21 JAR files: [C:\usr\sap\PID\SYS\global\security\lib\tools\iaik_smime.jar, C:\usr\sap\PID\SYS\global\security\lib\tools\iaik_ssl.jar, C:\usr\sap\PID\SYS\global\security\lib\tools\iaik_jce.jar, C:\usr\sap\PID\SYS\global\security\lib\tools\iaik_jsse.jar, C:\usr\sap\PID\SYS\global\security\lib\tools\w3c_http.jar, .\bootstrap\jdbc.jar, .\bootstrap\jperflib.jar, .\bootstrap\sap.com~tc~bl~config~impl.jar, .\bootstrap\sap.com~tc~bl~deploy~offline~impl.jar, .\bootstrap\sap.com~tc~bl~iqlib~impl.jar, .\bootstrap\sap.com~tc~bl~jdsr~jdsr.jar, .\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar, .\bootstrap\sap.com~tc~bl~opensql~implStandalone.jar, .\bootstrap\sap.com~tc~exception~impl.jar, .\bootstrap\sap.com~tc~je~bootstrap~impl.jar, .\bootstrap\sap.com~tc~je~cfs~container~standalone_impl.jar, .\bootstrap\sap.com~tc~je~datacollector.jar, .\bootstrap\sap.com~tc~je~extramile.jar, .\bootstrap\sap.com~tc~je~offlineconfiguration~impl.jar, .\bootstrap\sap.com~tc~logging~java~impl.jar, .\bootstrap\sap.com~tc~sec~secstorefs~java~core.jar]
   INFO: Start
Starting to configure the bootstrap
      Bootstrap properties file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bootstrap\bootstrap.properties] found
Bootstrap configured for [89] ms

Memory available to the bootstrap JVM: [2 GiB / 2863333376 bytes]

-----[Bootstrap Module started]--------[Mon Jul 30 11:00:46 CEST 2012]-------

+------------[Bootstrap synchronization activities information]-----------+
| Runtime Binaries: [X] Native files: [X] Instance Properties: [X] |
| Nodes Structure: [X] Cluster File System: [X] Online bootstrap: [ ] |
+-------------------------------------------------------------------------+

None of the startup parameters passed: [-DSAPSTART=1, -DSAPSYSTEM=00, -DSAPSYSTEMNAME=PID, -DSAPMYNAME=PIMNT10_PID_00, -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10, -DFRFC_FALLBACK=ON, -DFRFC_FALLBACK_HOST=localhost] is known to the bootstrap. Activating the default mode - synchronize all [-all]
Properties used for initialization: [element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, log[defaultTrace].pattern=..\..\work\log_bootstrap.log, log[consoleLog].formatter=formatter[ConsoleFormatter], com.sap.engine.bootstrap.severity=Info, formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, com.sap.engine.bootstrap.logs=log[defaultTrace],log[consoleLog], log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}]
Bootstrap initialized for [191] ms

Watchdog [90000] ms checking every [2000] ms started

Starting to initialize database connection
Database connection initialized for [3500] ms

Starting to persist instance profile
   Profile has not been changed
Instance profile persisted for [164] ms
Starting to collect synchronization info [DETECT]
      Local version information read for [146] ms
      Native files will not be synchronized
      Starting to collect instance metadata
         OS properties read for [101] ms
         Cannot read the number of debug nodes
         No debug nodes will be configured
         Global instance properties constructed for [112] ms
         Server processes properties constructed for [151] ms
         Shared memory properties constructed for [280] ms
         Instance [ID99642] will run in [NORMAL] mode; performing action [NONE]
      Instance metadata collected for [543] ms
      Starting to collect runtime binaries metadata
      Runtime binaries will not be synchronized
      Starting to read server processes metadata
         Manager properties loaded for [124] ms
      Server processes metadata collected for [136] ms
      Starting to collect cluster file system metadata
      Cluster file system components will not be synchronized
Finished for [854] ms with [621] operations; [727.17] ops/sec

Starting to synchronize instance file system
      Synchronization of instance metadata in [instance.properties]] finished for [33] ms
      Starting to synchronize manager properties
         Starting the Log Configuration Processor
#1343638851366# : Log-Configuration : Formatter ShortDumpHeaderFormatter without pattern : A property with the name "pattern" could not be found in the PropertySheet "cluster_config/system/instances/current_instance/cfg/kernel/Log/log-configuration.xml/log-formatters/ShortDumpHeaderFormatter/properties".
#1343638851372# : Log-Configuration : Formatter ShortDumpBodyFormatter without pattern : A property with the name "pattern" could not be found in the PropertySheet "cluster_config/system/instances/current_instance/cfg/kernel/Log/log-configuration.xml/log-formatters/ShortDumpBodyFormatter/properties".
#1343638851379# : Log-Configuration : Formatter perf_formatter without pattern : A property with the name "pattern" could not be found in the PropertySheet "cluster_config/system/instances/current_instance/cfg/kernel/Log/log-configuration.xml/log-formatters/perf_formatter/properties".
         Log Configuration Processor finished for [709] ms
         Starting the Cache Configuration Processor
         Cache Configuration Processor finished for [17] ms
         Properties serialized for [64] ms
         Properties stored in [kernelProperties.bin] for [40] ms
      Manager properties synchronized for [836] ms
      Synchronizing folder [server0\dtd]
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\library.provider.dtd] finished. Size: 821 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\data-sources.dtd] finished. Size: 1687 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\data-source-aliases.dtd] finished. Size: 219 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\persistent.dtd] finished. Size: 4 KiB / 4334 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\application-service.dtd] finished. Size: 1128 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\application-client-additional.dtd] finished. Size: 2001 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\jms-destinations.dtd] finished. Size: 385 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\connector-j2ee-engine.dtd] finished. Size: 1415 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\jms-factories.dtd] finished. Size: 1548 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\application-j2ee-engine.dtd] finished. Size: 760 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\appclient-j2ee-engine.dtd] finished. Size: 1864 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\log-configuration.dtd] finished. Size: 2 KiB / 2698 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\db-init.dtd] finished. Size: 233 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\ejb-j2ee-engine.dtd] finished. Size: 3 KiB / 3600 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\web-j2ee-engine.dtd] finished. Size: 2 KiB / 2547 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\interface.provider.dtd] finished. Size: 813 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\service.provider.dtd] finished. Size: 1447 bytes
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\dtd\monitor-configuration.dtd] finished. Size: 13 KiB / 14178 bytes
      Synchronizing folder [server0]
      Skipping file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\filters.txt]
      Synchronization of file [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\components.properties] finished. Size: 643 KiB / 658542 bytes
      No information to save in the version file
Instance synchronization finished for [1094] ms

Synchronization of [683 KiB / 700220 bytes] finished for [2119] ms; [0.32] MiB/s
Total bootstrap time was [5811] ms; [0.11] MiB/s

-----[Bootstrap Module finished]-------[Mon Jul 30 11:00:52 CEST 2012]-------

Thanks for help

Reza

Hi Reza,

Thanks. You can do the ping by using the Note 155147 - WinNT: Connection reset by peer

Hi Silambharasan,

Thanks for reply:)

Her is result of using of niping:''

Do you have idea?

*C:\Users\pidadm>niping -c -H pimnt10 -L 3600 -D 1000*

Tue Jul 31 18:45:05 2012
***LOG Q0I=> NiPConnect2: 10.76.129.79:3298: connect (10061: WSAECONNREFUSED: Co
nnection refused) [nixxi.cpp 3286]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 300
(SI_ECONN_REFUSE/10061; I4; ST; 10.76.129.79:3298) [nixxi.cpp 3286]
*** ERROR => NiTClientLoop: NiHandle (rc=-10) [nixxtst.cpp 2590]

*****************************************************************************
*
* ERROR       partner '10.76.129.79:3298' not reached
*
* TIME        Tue Jul 31 18:45:05 2012
* RELEASE     720
* COMPONENT   NI (network interface)
* VERSION     40
* RC          -10
* MODULE      nixxi.cpp
* LINE        3286
* DETAIL      NiPConnect2: 10.76.129.79:3298
* SYSTEM CALL connect
* ERRNO       10061
* ERRNO TEXT WSAECONNREFUSED: Connection refused
* COUNTER     1
*
*****************************************************************************

sorry:

I should first start niping by using:

C:\Users\pidadm>niping -s -I t=0

Tue Jul 31 18:58:41 2012
ready for connect from client ...

after taht:

niping -c -H pimnt10.dlg.dk -L 3600 -D 1000

C:\Users\pidadm>niping -c -H pimnt10.dlg.dk -L 3600 -D 1000

Tue Jul 31 18:55:44 2012
connect to server o.k.

Thanks

Hi Reza,

The network is very fine. Are you sure no updation in the bootstrap ?

Yes I do, I think it is very staring bootstrap not getting update when I rester SAP server.

Any idea?

I have this log from jstart:

I had take a look on this note: 1316652. But there is no much help.

Her is the last part:

*****************************

F ********************************************************************************

F Starting process: C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE

F arg[ 1] = -nodeId=1000

F arg[ 2] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10

F arg[ 3] = -DSAPINFO=PID_00_flightrec

F arg[ 4] = -hostvm

F arg[ 5] = -nodeName=flightrec

F arg[ 6] = -file=C:\usr\sap\PID\DVEBMGS00\exe\startup.properties

F arg[ 7] = -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm

F arg[ 8] = -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_flightrec

F arg[ 9] = -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_flightrec.out

F arg[10] = -clusterId=deployment

F arg[11] = -exitcode

F arg[12] = -21003

F arg[13] = -DSAPSTART=1

F arg[14] = -DSAPSYSTEM=00

F arg[15] = -DSAPSYSTEMNAME=PID

F arg[16] = -DSAPMYNAME=PIMNT10_PID_00

F arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10

F arg[18] = -DFRFC_FALLBACK=ON

F arg[19] = -DFRFC_FALLBACK_HOST=localhost

F env : NODNSSAPTRANSHOST=1

F exePath : PATH=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64

F libPath : PATH=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64

F stdout : C:\usr\sap\PID\DVEBMGS00\work\std_flightrec.out

F stderr : C:\usr\sap\PID\DVEBMGS00\work\std_flightrec.out

F console : no

F debugger: no

F nice : no

F ********************************************************************************

F Process collector started with pid 2028

F ********************************************************************************

F [Thr 6208] *** LOG => Process flightrec started (pid 2028).

F [Thr 6208] Tue Jul 31 19:21:32 2012

F [Thr 6208] *** LOG => Process flightrec stopping (pid 2028).

F [Thr 6080] Tue Jul 31 19:21:32 2012

F [Thr 6080] *** LOG => Signal 13 SIGCHLD.

F [Thr 6208] *** LOG => Process flightrec stopped (pid 2028).

F [Thr 6208] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).

F [Thr 6208] *** LOG => Run level 1 completed.

F [Thr 6208] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

F ********************************************************************************

F *** ERROR => Node 'deployment' failed with exit code -21003.

F ***

F *** Please see section 'Failures in the 'deploying offline components' phase'

F *** in SAP Note 1316652 for additional information and trouble shooting advice.

F ********************************************************************************

F [Thr 6208] *** LOG => exiting (exitcode 22002, retcode 1).

Hi Reza,

Database is running fine rite ? there is no issue in that ?

Hi Silambharasan,

Thanks you helplme on this, Yes DB is working and I logon configtool. I can logon abap by logon gui part.

I have this from

std_deployment

--------------------------------------------------------------------------------

stdout/stderr redirection

--------------------------------------------------------------------------------

node name : Deploy_offline

host name : PIMNT10

system name : PID

system nr. : 00

started at : Tue Jul 31 19:45:30 2012

Hi Reza,

Check this link with other trace files,

http://wiki.sdn.sap.com/wiki/display/JSTSG/%28JSTSG%29%28TG%29Q3025

I already checked too but no help with your given trace files. You may check with other trace files.

Thanks agian:

I have this error fron :dev_development:

---------------------------------------------------
trc file: "dev_deployment", trc level: 1, release: "720"
---------------------------------------------------
sysno      00
sid        PID
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    63
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    \\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
pid        7392

*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*

Tue Jul 31 20:18:51 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*

arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=0
arg[ 3] : pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
arg[ 4] : -hostvm
arg[ 5] : -nodeName=deployment
arg[ 6] : -file=C:\usr\sap\PID\DVEBMGS00\exe\startup.properties
arg[ 7] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 8] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_deployment
arg[ 9] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_deployment.out
arg[10] : -DSAPSTART=1
arg[11] : -DSAPSYSTEM=00
arg[12] : -DSAPSYSTEMNAME=PID
arg[13] : -DSAPMYNAME=PIMNT10_PID_00
arg[14] : -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
arg[15] : -DFRFC_FALLBACK=ON
arg[16] : -DFRFC_FALLBACK_HOST=localhost

F
F Tue Jul 31 20:18:51 2012
F ********************************************************************************
F Java environment properties
F    root directory    : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_33
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.042 1.6-b03
F    jvm library name : jvm.dll
F    library path      : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin
F    executable path   : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin
F    SAP extensions    : available
F ********************************************************************************
I [Thr 7388] MtxInit: 10000 0 2
M [Thr 7388] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 7388] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 7388] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 7388] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 7388] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 7388] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Jul 31 20:18:51 2012
F ********************************************************************************
F SAP Java VM arguments:
F    arg[ 0] = vfprintf
F    arg[ 1] = abort
F    arg[ 2] = exit
F    arg[ 3] = -XmonGcCallback
F    arg[ 4] = -XdebugStateChangeCallback
F    arg[ 5] = -DSAPJStartVersion=720, patch 201, changelist 0, NTAMD64, optU (Mar 20 2012, 14:30:22)
F    arg[ 6] = -verbose:gc
F    arg[ 7] = -XX:+HeapDumpOnOutOfMemoryError
F    arg[ 8] = -DSAPSTARTUP=1
F    arg[ 9] = -DSAPSYSTEM=00
F    arg[10] = -DSAPSYSTEMNAME=PID
F    arg[11] = -DSAPMYNAME=PIMNT10_PID_00
F    arg[12] = -DSAPDBHOST=PIMNT10
F    arg[13] = -DSAPINFO=PID_00_deployment
F    arg[14] = -Dj2ee.dbhost=PIMNT10
F    arg[15] = -Dsun.java.launcher=jstart
F    arg[16] = -Dsun.java.command=com.sap.engine.offline.OfflineToolStart com.sap.engine.services.dc.cm.offline_phase.Runner ./bootstrap -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=PIMNT10_PID_00 -DSAPPROFILE=\\\\PIMNT10\\sapmnt\\PID\\SYS\\profile\\PID_DVEBMGS00_PIMNT10 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F    arg[17] = -Djstartup.mode=JSTART
F    arg[18] = -Djstartup.whoami=bootstrap
F    arg[19] = -Djstartup.ownProcessId=7392
F    arg[20] = -Djstartup.ownHardwareId=G1326133984
F    arg[21] = -Djstartup.debuggable=no
F    arg[22] = -DLoadBalanceRestricted=no
F    arg[23] = -Denv.class.path=
F    arg[24] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F    arg[25] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F    arg[26] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\lib\tools.jar;.\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar;C:\usr\sap\PID\DVEBMGS00\exe\jstartupapi.jar;C:\usr\sap\PID\DVEBMGS00\exe\jstartupimpl.jar
F    arg[27] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
F    arg[28] = -Xmx512m
F    arg[29] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
F [Thr 7384] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method call:
F com/sap/engine/offline/OfflineToolStart.main()
F    arg[ 0] = com.sap.engine.services.dc.cm.offline_phase.Runner
F    arg[ 1] = ./bootstrap
F    arg[ 2] = -DSAPSTART=1
F    arg[ 3] = -DSAPSYSTEM=00
F    arg[ 4] = -DSAPSYSTEMNAME=PID
F    arg[ 5] = -DSAPMYNAME=PIMNT10_PID_00
F    arg[ 6] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
F    arg[ 7] = -DFRFC_FALLBACK=ON
F    arg[ 8] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
F [Thr 7384] *** WARNING => SfCJavaVm::callStatic: Cannot find class: com/sap/engine/offline/OfflineToolStart [sfxxjvm.hpp 665]
F [Thr 7384] *** java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
F [Thr 7384] *** Caused by: java.lang.ClassNotFoundException: com.sap.engine.offline.OfflineToolStart
F [Thr 7384] ***         at java.net.URLClassLoader$1.run(URLClassLoader.java:255)
F [Thr 7384] ***         at java.security.AccessController.doPrivileged(Native Method)
F [Thr 7384] ***         at java.net.URLClassLoader.findClass(URLClassLoader.java:243)
F [Thr 7384] ***         at java.lang.ClassLoader.loadClass(ClassLoader.java:367)
F [Thr 7384] ***         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:344)
F [Thr 7384] ***         at java.lang.ClassLoader.loadClass(ClassLoader.java:308)
F [Thr 7384] *** ERROR => SfEStartupError: SfCSapVm::callMainMethod: : Cannot call method: static void com/sap/engine/offline/OfflineToolStart.main(String[]) [sfxxjvm.hpp 1392]
F [Thr 7384] *** ERROR => Java thread failed: SfEStartupError: : Cannot call method: static void com/sap/engine/offline/OfflineToolStart.main(String[])
[sfxxjvm.hpp 1459]
F
F ********************************************************************************
F *** ERROR => Cannot call main method in com/sap/engine/offline/OfflineToolStart.
F ***
F *** Please see section 'Java VM shared library issues'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
F
F [Thr 7388] *** LOG => exiting (exitcode -21003, retcode 2).
M [Thr 7388] CCMS: CCMS Monitoring Cleanup finished successfully.

Hi Reza,

We will check the Heap dump out of memory by using this documentation

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=33456

Hi reza,

May i know which database you are using ?

I am using sql DB 2008r2.

Thanks

Hi Reza,

As analyzed the above issue, i come across some of the points

1. Eventhough we got some of the Heap dump error in the log when you see that the VM lauches successfully. So it overcomes the error.

**************************************************

F arg[ 6] = -verbose:gc

F arg[ 7] = -XX:+HeapDumpOnOutOfMemoryError

F arg[ 8] = -DSAPSTARTUP=1

F arg[ 9] = -DSAPSYSTEM=00

F arg[10] = -DSAPSYSTEMNAME=PID

********************************************************************************

F [Thr 7384] *** LOG => SfCJavaVm: Java VM started.

F ********************************************************************************

So as point is there is no use of chaging the value of Heap value and it may lead to move the performance better instead of startup problem. Check this 1303953 - SAP JVM memory parameters and their names in the Config Tool

2. When you revert back to my earlier query the instance are running in DB. If the database is located in separate host you need to check the Xservice which is neccessary to connect the DB.

3. As your point there is no permission issue in the system to startup since you are able to login the config tool perfectly.

4. You already ping the IP and it is working fine also and it shows that there is no error in networ side.

5. When you see the below error,

********************************************************

F [Thr 7384] *** ERROR => SfEStartupError: SfCSapVm::callMainMethod: : Cannot call method: static void com/sap/engine/offline/OfflineToolStart.main(String[]) [sfxxjvm.hpp 1392]

F [Thr 7384] *** ERROR => Java thread failed: SfEStartupError: : Cannot call method: static void com/sap/engine/offline/OfflineToolStart.main(String[])

[sfxxjvm.hpp 1459]

It shows that there is a problem in the class file. So that is better to delete the *.jvm files in the system and restart the system. No issues it will automatically create the same.

if you are using the license version, it is better you will raise a OSS message underthe componet BC-JAS-SF

If you are using the trail version we will analysis the issue again with the help of below logs,

dev_jstart*

dev_deployment*

std_deployment.*

jvm_deployment.*

Hope this helps.

Hi Silambharasan

The DB is located in the same server ant not on separate host.

You mention it is better to delete the *.jvm files in the system. Where are this files, are they on /usr/sap/<SID>/DVEBMGS<XX>/work?

Thanks for help again,

Hi Reza,

Please find the path,

/usr/sap/<SID>/JC<XX>/workfor Java Central instance (deprecated)
/usr/sap/<SID>/J<XX>/workfor Java Central or Dialog instance
/usr/sap/<SID>/DVEBMGS<XX>/work - for ABAP/DoubleStack Central instance
/usr/sap/<SID>/D<XX>/work - for ABAP/DoubleStack Dialog instance

Hope this helps.

Hi Silambharasan,

I did check the SAP JVM memory parameters and their names in the Config Tool and deleted *jvm file but no help.

Her is the log file you mentioned.

Thanks again for help.

---------------------------------------------------------------------------------------------------------------------------------

jvm_deployment:

nothing is there.

---------------------------------------------------------------------------------------------------------------------------------

std_deplyment:

--------------------------------------------------------------------------------
stdout/stderr redirection
--------------------------------------------------------------------------------
node name : Deploy_offline
host name : PIMNT10
system name : PID
system nr. : 00
started at : Wed Aug 01 09:24:31 2012

---------------------------------------------------------------------------------------------------------------------------------dev_deplyment:

*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*

Wed Aug 01 09:22:32 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*

F
F Wed Aug 01 09:22:32 2012
F ********************************************************************************
F Java environment properties
F    root directory    : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_33
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.042 1.6-b03
F    jvm library name : jvm.dll
F    library path      : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin
F    executable path   : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin
F    SAP extensions    : available
F ********************************************************************************
I [Thr 4548] MtxInit: 10000 0 2
M [Thr 4548] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 4548] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 4548] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 4548] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 4548] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 4548] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Wed Aug 01 09:22:32 2012
F ********************************************************************************
F SAP Java VM arguments:
F    arg[ 0] = vfprintf
F    arg[ 1] = abort
F    arg[ 2] = exit
F    arg[ 3] = -XmonGcCallback
F    arg[ 4] = -XdebugStateChangeCallback
F    arg[ 5] = -DSAPJStartVersion=720, patch 201, changelist 0, NTAMD64, optU (Mar 20 2012, 14:30:22)
F    arg[ 6] = -verbose:gc
F    arg[ 7] = -XX:+HeapDumpOnOutOfMemoryError
F    arg[ 8] = -DSAPSTARTUP=1
F    arg[ 9] = -DSAPSYSTEM=00
F    arg[10] = -DSAPSYSTEMNAME=PID
F    arg[11] = -DSAPMYNAME=PIMNT10_PID_00
F    arg[12] = -DSAPDBHOST=PIMNT10
F    arg[13] = -DSAPINFO=PID_00_deployment
F    arg[14] = -Dj2ee.dbhost=PIMNT10
F    arg[15] = -Dsun.java.launcher=jstart
F    arg[16] = -Dsun.java.command=com.sap.engine.offline.OfflineToolStart com.sap.engine.services.dc.cm.offline_phase.Runner ./bootstrap -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=PIMNT10_PID_00 -DSAPPROFILE=\\\\PIMNT10\\sapmnt\\PID\\SYS\\profile\\PID_DVEBMGS00_PIMNT10 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F    arg[17] = -Djstartup.mode=JSTART
F    arg[18] = -Djstartup.whoami=bootstrap
F    arg[19] = -Djstartup.ownProcessId=5148
F    arg[20] = -Djstartup.ownHardwareId=G1326133984
F    arg[21] = -Djstartup.debuggable=no
F    arg[22] = -DLoadBalanceRestricted=no
F    arg[23] = -Denv.class.path=
F    arg[24] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F    arg[25] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F    arg[26] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\lib\tools.jar;.\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar;C:\usr\sap\PID\DVEBMGS00\exe\jstartupapi.jar;C:\usr\sap\PID\DVEBMGS00\exe\jstartupimpl.jar
F    arg[27] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
F    arg[28] = -Xmx512m
F    arg[29] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
F [Thr 8748] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method call:
F com/sap/engine/offline/OfflineToolStart.main()
F    arg[ 0] = com.sap.engine.services.dc.cm.offline_phase.Runner
F    arg[ 1] = ./bootstrap
F    arg[ 2] = -DSAPSTART=1
F    arg[ 3] = -DSAPSYSTEM=00
F    arg[ 4] = -DSAPSYSTEMNAME=PID
F    arg[ 5] = -DSAPMYNAME=PIMNT10_PID_00
F    arg[ 6] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
F    arg[ 7] = -DFRFC_FALLBACK=ON
F    arg[ 8] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
F [Thr 8748] *** WARNING => SfCJavaVm::callStatic: Cannot find class: com/sap/engine/offline/OfflineToolStart [sfxxjvm.hpp 665]
F [Thr 8748] *** java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
F [Thr 8748] *** Caused by: java.lang.ClassNotFoundException: com.sap.engine.offline.OfflineToolStart
F [Thr 8748] ***         at java.net.URLClassLoader$1.run(URLClassLoader.java:255)
F [Thr 8748] ***         at java.security.AccessController.doPrivileged(Native Method)
F [Thr 8748] ***         at java.net.URLClassLoader.findClass(URLClassLoader.java:243)
F [Thr 8748] ***         at java.lang.ClassLoader.loadClass(ClassLoader.java:367)
F [Thr 8748] ***         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:344)
F [Thr 8748] ***         at java.lang.ClassLoader.loadClass(ClassLoader.java:308)
F [Thr 8748] *** ERROR => SfEStartupError: SfCSapVm::callMainMethod: : Cannot call method: static void com/sap/engine/offline/OfflineToolStart.main(String[]) [sfxxjvm.hpp 1392]
F [Thr 8748] *** ERROR => Java thread failed: SfEStartupError: : Cannot call method: static void com/sap/engine/offline/OfflineToolStart.main(String[])
[sfxxjvm.hpp 1459]
F
F ********************************************************************************
F *** ERROR => Cannot call main method in com/sap/engine/offline/OfflineToolStart.
F ***
F *** Please see section 'Java VM shared library issues'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
F
F [Thr 4548] *** LOG => exiting (exitcode -21003, retcode 2).
M [Thr 4548] CCMS: CCMS Monitoring Cleanup finished successfully.

---------------------------------------------------------------------------------------------------------------------------------

dev_jstart:

---------------------------------------------------
trc file: "dev_jstart.7800", trc level: 1, release: "720"
---------------------------------------------------

---------------------------------------------------
trc file: "dev_jstart.new", trc level: 1, release: "720"
---------------------------------------------------
sysno      00
sid        PID
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    63
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    \\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
pid        7800

*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*

Wed Aug 01 09:21:11 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*

arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
arg[ 2] : -DSAPSTART=1
arg[ 3] : -DCONNECT_PORT=64897
arg[ 4] : -DSAPSYSTEM=00
arg[ 5] : -DSAPSYSTEMNAME=PID
arg[ 6] : -DSAPMYNAME=PIMNT10_PID_00
arg[ 7] : -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
arg[ 8] : -DFRFC_FALLBACK=ON
arg[ 9] : -DFRFC_FALLBACK_HOST=localhost

F
F Wed Aug 01 09:21:11 2012
F ********************************************************************************
F Java environment properties (C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm)
F    root directory    : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_33
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.042 1.6-b03
F    jvm library name : jvm.dll
F    library path      : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin
F    executable path   : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin
F ********************************************************************************
F    SAP extensions    : available
F ********************************************************************************
I [Thr 3888] MtxInit: 30002 0 2

---------------------------------------------------
trc file: "dev_jstart", trc level: 1, release: "720"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL           1
* ACTIVE TRACE COMPONENTS      All, egi
*
F [Thr 3888] *** LOG => connected to Enqueue Server.
F [Thr 3888] *** LOG => connected to Message Server.
F [Thr 3888] *** LOG => Starting run level 1.
F ********************************************************************************
F Java process [deployment] properties:
F    section name     : deployment
F    config file      : C:\usr\sap\PID\DVEBMGS00\exe\startup.properties
F    node name        : Deploy_offline
F    home directory   : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster
F    shutdown timeout : 136000 ms
F    exit timeout     : 7000 ms
F    debuggable       : false
F    debugger active : false
F ********************************************************************************
F [Thr 3888] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
F [Thr 3888] *** LOG => Starting nodes: runlevel 1.
F ********************************************************************************
F Starting process: C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
F    arg[ 1] = -nodeId=0
F    arg[ 2] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
F    arg[ 3] = -hostvm
F    arg[ 4] = -nodeName=deployment
F    arg[ 5] = -file=C:\usr\sap\PID\DVEBMGS00\exe\startup.properties
F    arg[ 6] = -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
F    arg[ 7] = -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_deployment
F    arg[ 8] = -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_deployment.out
F    arg[ 9] = -DSAPSTART=1
F    arg[10] = -DSAPSYSTEM=00
F    arg[11] = -DSAPSYSTEMNAME=PID
F    arg[12] = -DSAPMYNAME=PIMNT10_PID_00
F    arg[13] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
F    arg[14] = -DFRFC_FALLBACK=ON
F    arg[15] = -DFRFC_FALLBACK_HOST=localhost
F    env   : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
F libPath : PATH=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
F stdout : C:\usr\sap\PID\DVEBMGS00\work\std_deployment.out
F stderr : C:\usr\sap\PID\DVEBMGS00\work\std_deployment.out
F console : no
F debugger: no
F nice    : no
F ********************************************************************************
F Process Deploy_offline started with pid 5728
F ********************************************************************************
F [Thr 3888] *** LOG => Process deployment started (pid 5728).
F
F [Thr 3888] Wed Aug 01 09:21:12 2012
F [Thr 3888] *** LOG => Process deployment stopping (pid 5728).
F
F [Thr 8560] Wed Aug 01 09:21:12 2012
F [Thr 8560] *** LOG => Signal 13 SIGCHLD.
F [Thr 3888] *** LOG => Process deployment stopped (pid 5728).
F [Thr 3888] *** WARNING => Node deployment failed: result 2, exit code -21003. [sfxxnode.hpp 1024]
F ********************************************************************************
F Java process [flightrec] properties:
F    section name     : flightrec
F    config file      : C:\usr\sap\PID\DVEBMGS00\exe\startup.properties
F    node name        : collector
F    home directory   : C:\usr\sap\PID\DVEBMGS00/j2ee
F    shutdown timeout : 136000 ms
F    exit timeout     : 7000 ms
F    debuggable       : false
F    debugger active : false
F ********************************************************************************
F ********************************************************************************
F Starting process: C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
F    arg[ 1] = -nodeId=1000
F    arg[ 2] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
F    arg[ 3] = -DSAPINFO=PID_00_flightrec
F    arg[ 4] = -hostvm
F    arg[ 5] = -nodeName=flightrec
F    arg[ 6] = -file=C:\usr\sap\PID\DVEBMGS00\exe\startup.properties
F    arg[ 7] = -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
F    arg[ 8] = -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_flightrec
F    arg[ 9] = -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_flightrec.out
F    arg[10] = -clusterId=deployment
F    arg[11] = -exitcode
F    arg[12] = -21003
F    arg[13] = -DSAPSTART=1
F    arg[14] = -DSAPSYSTEM=00
F    arg[15] = -DSAPSYSTEMNAME=PID
F    arg[16] = -DSAPMYNAME=PIMNT10_PID_00
F    arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
F    arg[18] = -DFRFC_FALLBACK=ON
F    arg[19] = -DFRFC_FALLBACK_HOST=localhost
F    env   : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
F libPath : PATH=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_6\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;c:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PID\DVEBMGS02\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
F stdout : C:\usr\sap\PID\DVEBMGS00\work\std_flightrec.out
F stderr : C:\usr\sap\PID\DVEBMGS00\work\std_flightrec.out
F console : no
F debugger: no
F nice    : no
F ********************************************************************************
F Process collector started with pid 5920
F ********************************************************************************
F [Thr 3888] *** LOG => Process flightrec started (pid 5920).
F
F [Thr 3888] Wed Aug 01 09:21:13 2012
F [Thr 3888] *** LOG => Process flightrec stopping (pid 5920).
F
F [Thr 1708] Wed Aug 01 09:21:13 2012
F [Thr 1708] *** LOG => Signal 13 SIGCHLD.
F [Thr 3888] *** LOG => Process flightrec stopped (pid 5920).
F [Thr 3888] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
F [Thr 3888] *** LOG => Run level 1 completed.
F [Thr 3888] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).
F
F ********************************************************************************
F *** ERROR => Node 'deployment' failed with exit code -21003.
F ***
F *** Please see section 'Failures in the 'deploying offline components' phase'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
F
F [Thr 3888] *** LOG => exiting (exitcode 22002, retcode 1).

Hi Reza,

Can you paste the log file for log_deployment..log*

Hi Silambharasan

Her is log_deployment

Jul 12, 2012 2:22:01 PM [Info] [offline] :Log was reinitialized [Common(offline):c:\usr\sap\PID\DVEBMGS00\work].

Thanks

Hi Reza,

Also provide the version of JVM.

Hi Reza,

You wrongly attached the file i think so. Check the below and reattach the same

The logs can be found in these locations:

/usr/sap/<SID>/JC<XX>/work for Java Central instance (deprecated)
/usr/sap/<SID>/J<XX>/work for Java Central or Dialog instance
/usr/sap/<SID>/DVEBMGS<XX>/work - for ABAP/DoubleStack Central instance
/usr/sap/<SID>/D<XX>/work - for ABAP/DoubleStack Dialog instance

Log files

dev_deployment
Log file containing Startup Framework flow entries
log_deployment..log*
Log files of the offline deploy process
std_deployment.out
The file contains the redirected output of Java's System.out
jvm_deployment.out
The file contains the redirected output of the JVM

Hi Silambharasan

The JVM version is sapjvm_6.1.042.

Hi Reza,

Thanks for the reply.

The very important filed for the monitoring the java system is DEV_JCONTROL but as your earlier post you said nothing update in that post. Can you check and post the same.

Hi,

The last update from dev_jcontrol is from 12-07-2012:

Her is last update:

---------------------------------------------------
trc file: "dev_jcontrol", trc level: 1, release: "720"
---------------------------------------------------
node name   : jcontrol
pid         : 7472
system name : PID
system nr. : 00
started at : Tue Jul 10 16:01:40 2012
arguments   :
   arg[00] : C:\usr\sap\PID\DVEBMGS00\exe\jcontrol.EXE
   arg[01] : pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
   arg[02] : -DSAPSTART=1
   arg[03] : -DCONNECT_PORT=65000
   arg[04] : -DSAPSYSTEM=00
   arg[05] : -DSAPSYSTEMNAME=PID
   arg[06] : -DSAPMYNAME=PIMNT10_PID_00
   arg[07] : -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
   arg[08] : -DFRFC_FALLBACK=ON
   arg[09] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************
Used property files
-> files [00] : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> files [01] : C:\usr\sap\PID\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
**********************************************************************

**********************************************************************
Bootstrap nodes
-> [00] bootstrap : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9964200 : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9964250 : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Worker nodes
-> [00] ID9964200            : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID9964250            : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] sdm                  : C:\usr\sap\PID\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
**********************************************************************

**********************************************************************
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties;C:\usr\sap\PID\DVEBMGS00\SDM\program\config\sdm_jstartup.properties]
-> ms host    : PIMNT10
-> ms port    : 3901
-> OS libs    : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode   : normal
-> run action : NONE
-> enabled    : yes
**********************************************************************

[Thr 9652] [Node: bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 4500] JControlDPMessageProxy: Thread 4500 started as handler thread for R/3 dispatcher messages.

[Thr 9652] Tue Jul 10 16:01:42 2012
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [bootstrap]
-> node name          : bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> java path          : C:\j2sdk1.4.2_17-x64
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_17-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 512M
-> root path          : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0099642
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 9652] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 9652] [Node: bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_bootstrap.out
-> arg[09] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=62081
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=PID
-> arg[16] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 9652] Tue Jul 10 16:01:51 2012
[Thr 9652] JControlExecuteBootstrap: read instance values after global bootstrap

[Thr 9652] JControlExecuteBootstrap: enumerate the nodes after global bootstrap

[Thr 9652] [Node: dispatcher bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [bootstrap_ID9964200]
-> node name          : dispatcher bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_17-x64
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_17-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 256M
-> root path          : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009964200
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 9652] [Node: server0 bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [bootstrap_ID9964250]
-> node name          : server0 bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_17-x64
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_17-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 256M
-> root path          : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009964250
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 9652] [Node: bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

[Thr 9652] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9964200]
[Thr 9652] [Node: dispatcher bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=bootstrap_ID9964200
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_bootstrap_ID9964200.out
-> arg[08] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_bootstrap_ID9964200.out
-> arg[09] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_bootstrap_ID9964200
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=62081
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=PID
-> arg[16] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 9652] Tue Jul 10 16:01:53 2012
[Thr 9652] [Node: server0 bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

[Thr 9652] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9964250]
[Thr 9652] [Node: server0 bootstrap] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=bootstrap_ID9964250
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_bootstrap_ID9964250.out
-> arg[08] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_bootstrap_ID9964250.out
-> arg[09] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_bootstrap_ID9964250
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=62081
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=PID
-> arg[16] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 7020] Tue Jul 10 16:01:55 2012
[Thr 7020] JControlRequestFunc: Thread 7020 started as listener thread for np messages.
[Thr 9652] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 9652] [Node: dispatcher] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [ID9964200]
-> node name          : dispatcher
-> node type          : dispatcher
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_17-x64
-> java parameters    : -XX:NewSize=57M -XX:MaxNewSize=57M -XX:+DisableExplicitGC -verbose:gc -Djava.security.policy=.java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1
-> java vm version    : 1.4.2_17-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 170M
-> init heap size     : 170M
-> root path          : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\dispatcher
-> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 9652] [Node: server0] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [ID9964250]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_17-x64
-> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:+DisableExplicitGC -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> java vm version    : 1.4.2_17-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50021
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 9652] INFO: Invalid property value [Debbugable=yes]
[Thr 9652] [Node: SDM] java home is set by profile parameter
[Thr 9652] Java Home: C:\j2sdk1.4.2_17-x64
[Thr 9652] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [sdm]
-> node name          : SDM
-> node type          : sdm
-> node execute       : yes
-> java path          : C:\j2sdk1.4.2_17-x64
-> java parameters    :
-> java vm version    : 1.4.2_17-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 512M
-> root path          : C:\usr\sap\PID\DVEBMGS00\SDM\program
-> class path         : C:\usr\sap\PID\DVEBMGS00\SDM\program\bin\SDM.jar
-> OS libs path       : C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs
-> main class         : SDMInternal
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar
-> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters         : server sdmhome=C:\usr\sap\PID\DVEBMGS00\SDM\program
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 7092] JControlSocketServerFunc: Thread 7092 started as handler thread for control socket.
[Thr 9652] JControlMSConnect: attached to message server (PIMNT10/3901)

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=ID9964200
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_dispatcher.out
-> arg[09] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=62081
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=PID
-> arg[16] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 9652] JControlICheckProcessList: process dispatcher started (PID:6332)

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=ID9964250
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
-> arg[08] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_server0.out
-> arg[09] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=62081
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=PID
-> arg[16] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 7112] JControlMSMessageFunc: Thread 7112 started as listener thread for ms messages.
[Thr 9652] JControlICheckProcessList: process server0 started (PID:2144)

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_sdm.out
-> arg[08] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_sdm.out
-> arg[09] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=62081
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=PID
-> arg[16] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[17] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 9652] JControlICheckProcessList: process SDM started (PID:3808)
[Thr 9652] JControlMSSendLogon: delete SDM logon information (rc=0)

[Thr 9652] Tue Jul 10 16:02:00 2012
[Thr 9652] JControlMSSendLogon: insert SDM logon information (port=50018; rc=0)

[Thr 7112] Wed Jul 11 11:54:49 2012
[Thr 7112] JControlMSMessageFunc: received command:12, argument:4 from Message Server
[Thr 7112] JControlProcessMessage: received <disable processes 4> command
[Thr 7112] JControlIEnableProcesses: disable processes of type (Exclude:0) [SDM Server]
[Thr 7112] JControlIDisableProcess: disable process SDM
[Thr 7112] JControlIProcessSoftKill: soft kill of process SDM (pid:3808)

[Thr 9652] Wed Jul 11 11:54:55 2012
[Thr 9652] JControlICheckProcessList: process SDM (pid:3808) died (STOPPING)
[Thr 9652] JControlIResetProcess: reset process SDM

[Thr 7112] Wed Jul 11 11:55:24 2012
[Thr 7112] JControlMSMessageFunc: received command:11, argument:4 from Message Server
[Thr 7112] JControlProcessMessage: received <enable processes 4> command
[Thr 7112] JControlIEnableProcesses: enable processes of type (Exclude:0) [SDM Server]
[Thr 7112] JControlIEnableProcess: enable process SDM

**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\PID\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[02] = -DSAPINFO=PID_00_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=C:\usr\sap\PID\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_7472
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=C:\usr\sap\PID\DVEBMGS00\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=C:\usr\sap\PID\DVEBMGS00\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=62081
-> arg[17] = -DSAPSYSTEM=00
-> arg[18] = -DSAPSYSTEMNAME=PID
-> arg[19] = -DSAPMYNAME=PIMNT10_PID_00
-> arg[20] = -DSAPPROFILE=\\PIMNT10\sapmnt\PID\SYS\profile\PID_DVEBMGS00_PIMNT10
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\PID\DVEBMGS00\exe;C:\usr\sap\PID\SYS\exe\uc\NTAMD64
**********************************************************************

[Thr 9652] Wed Jul 11 11:55:25 2012
[Thr 9652] JControlICheckProcessList: process SDM started (PID:10372)

[Thr 4500] Thu Jul 12 13:22:55 2012
[Thr 4500] JControlDPMessageProxy: Thread 4500 terminated as handler thread for R/3 dispatcher messages.

[Thr 4368] Thu Jul 12 13:22:57 2012
[Thr 4368] JControlSigInt: signal = 3
[Thr 4368] JControlIStopInstance: shutting down (command: 0)
[Thr 4368] JControlIProcessSoftKill: soft kill of process dispatcher (pid:6332)
[Thr 4368] JControlIProcessSoftKill: soft kill of process server0 (pid:2144)
[Thr 4368] JControlIProcessSoftKill: soft kill of process SDM (pid:10372)

[Thr 9652] Thu Jul 12 13:23:04 2012
[Thr 9652] JControlICheckProcessList: process SDM (pid:10372) died (STOPPING)
[Thr 9652] JControlIResetProcess: reset process SDM

[Thr 9652] Thu Jul 12 13:23:25 2012
[Thr 9652] JControlICheckProcessList: process dispatcher (pid:6332) died (STOPPING)
[Thr 9652] JControlIResetProcess: reset process dispatcher

[Thr 4368] Thu Jul 12 13:24:01 2012
[Thr 4368] JControlSigInt: signal = 2
[Thr 4368] *** WARNING => shutdown is active [jcntrxx.c 2502]

Hi Reza,

Hope we found the error there is a problem in the file jvmx.Jar.

JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

Can you check this file is avail or not in that path

Hi,

No there is no jvmx.jar on C:\usr\sap\PID\DVEBMGS00\exe\

Thanks

Hi Reza,

The heap size is very low, can you change this to the below,

( the below is my recommendation and increasing the heap size in 64bit will not cause any issues)

Xss2m

-Xms1024m

-Xmx1024m

-XX:NewSize=256m

-XX:MaxNewSize=256m

-XX:+DisableExplicitGC

-XX:PermSize=256m

-XX:MaxPermSize=256m

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

After that restart the server

Hi Silambharasan,

I did add a file with my parameter from configtool.

Some of this parameter is not there. Should I add them?

And what about jvamx.jar file should it added it?

-XX:TargetSurvivorRatio 90 true

-XX:SurvivorRatio 9 true

-XX:SoftRefLRUPolicyMSPerMB 1 true

-XX:MaxErrorQueueLength 200 true

-XX:HeapDumpPath OOM.hprof true

-XX:+DisableExplicitGC true

globalArea 1 false

maxHeapSize 2048 true

maxNewSize 410 true

newRatio 6 false

maxPermSize 1024 true

newSize 410 true

permSize 1024 true

There is no :

Xss2m

-Xms1024m

-Xmx1024m

Hi Reza,

That is a typo error set the parameter and restart the same.

-XX:NewSize=256m

-XX:MaxNewSize=256m

-XX:+DisableExplicitGC

-XX:PermSize=256m

-XX:MaxPermSize=256m

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

Hi,

I did set the parameter and rester the server still the same

Did tried se on MSGW there was no Active connections and I did Expert functions -> Host Name Buffer and rester server but stil no Active connections there

Thanks

Hi Reza,

This may be a error in JVM and also you raise a oss message to the SAP under the component BC-JAS-SF also try to install the latest JVM4.1 to the server and restart.

Thanks again. I will try that.

Reza,

can you have a look at ABAP srever system log (tcd SM21) in regard to any traces of the connection issue?

Regards,

Ilya

Hi Reza,

In our case this was caused by wily parameters.

Please proceed as follows:

Logon to configtool->template->Instance(please don't drop down only select or high light )->click on view->expert mode->click VM Parameters->System and Additional(both system and additional tabs)

select any parameters that have "Wily" then click disable button below them.

save and restart your AS Java Node.

Best Regards

Sipho Mathye

Ask a Question

Top Q&A Solution Author

User

Count

Unable to start java engine: dispatcher status is "yellow" in windows2008r2

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)

Log files

Re: Auto close/update all open Notifications work ...

Re: Auto close/update all open Notifications work ...

Re: SAP AI Core: proxy deployment: url not found

Re: Digital Signature on PDF

systemVars in SAP BUILD apps