Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8975

Re: An error has occurred during the execution of the START_J2EE_INITIAL phase.

$
0
0

Hi Ashutosh,

 

Thanks a lot for help.

 

The log file dev_disp not getting update,  last update is for some houres ago. that is for some

 

But here is dev_sever0 log

 


---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
sysno      01
sid        PIP
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    63
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    \\PIMNT14\sapmnt\PIP\SYS\profile\PIP_DVEBMGS01_PIMNT14
pid        4816

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

Sat Apr 27 22:31:48 2013
*
*  trace logging activated, max size = 52428800 bytes, 2 versions
*

arguments :
  arg[ 0] : c:\usr\sap\PIP\DVEBMGS01\exe\jstart.EXE
  arg[ 1] : -appTrc
  arg[ 2] : -nodeId=2
  arg[ 3] : pf=\\PIMNT14\sapmnt\PIP\SYS\profile\PIP_DVEBMGS01_PIMNT14
  arg[ 4] : -DSAPINFO=PIP_01_server0
  arg[ 5] : -hostvm
  arg[ 6] : -nodeName=ID15716150
  arg[ 7] : -file=c:\usr\sap\PIP\DVEBMGS01\j2ee\cluster\instance.properties
  arg[ 8] : -jvmFile=c:\usr\sap\PIP\DVEBMGS01\work\jstart.jvm
  arg[ 9] : -traceFile=c:\usr\sap\PIP\DVEBMGS01\work\dev_server0
  arg[10] : -javaOutFile=c:\usr\sap\PIP\DVEBMGS01\work\jvm_server0.out


F Sat Apr 27 22:31:48 2013
F  ********************************************************************************
F  Java environment properties
F    root directory    : C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_45
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.049 23.5-b05
F    jvm library name  : jvm.dll
F    library path      : C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\jre\bin\server;C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\jre\bin
F    executable path   : C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\bin
F    SAP extensions    : available
F  ********************************************************************************
I  [Thr 4192] MtxInit: 10002 0 2
I  [Thr 4192] MPI: dynamic quotas disabled.
I  [Thr 4192] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M  [Thr 4192] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M  [Thr 4192] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M  [Thr 4192] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M  [Thr 4192] CCMS: CCMS Monitoring Initialization finished, rc=0.

F Sat Apr 27 22:31:48 2013
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 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)
F    arg[ 6] = -Xjvmx
F    arg[ 7] = -XsapSystem:01
F    arg[ 8] = -DSAPSTARTUP=1
F    arg[ 9] = -DSAPSYSTEM=01
F    arg[10] = -DSAPSYSTEMNAME=PIP
F    arg[11] = -DSAPMYNAME=PIMNT14_PIP_01
F    arg[12] = -DSAPDBHOST=PIMNT14
F    arg[13] = -DSAPINFO=PIP_01_server0
F    arg[14] = -Dj2ee.dbhost=PIMNT14
F    arg[15] = -Dsun.java.launcher=jstart
F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
F    arg[17] = -Djstartup.mode=JSTART
F    arg[18] = -Djstartup.whoami=server
F    arg[19] = -Djstartup.ownProcessId=4816
F    arg[20] = -Djstartup.ownHardwareId=U0314089341
F    arg[21] = -Djstartup.debuggable=yes
F    arg[22] = -DLoadBalanceRestricted=no
F    arg[23] = -XdebugPortRange:50121-50121
F    arg[24] = -Denv.class.path=
F    arg[25] = -Dsys.global.dir=c:\usr\sap\PIP\SYS\global
F    arg[26] = -Dapplication.home=c:\usr\sap\PIP\DVEBMGS01\exe
F    arg[27] = -Djava.class.path=c:\usr\sap\PIP\DVEBMGS01\exe\jstart71.jar;C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\lib\jvmx.jar;C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\lib\jvmx_tools.jar;c:\usr\sap\PIP\DVEBMGS01\exe\jre\lib\iqlib.jar;C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\lib\tools.jar;c:\usr\sap\PIP\DVEBMGS01\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;c:\usr\sap\PIP\DVEBMGS01\j2ee\cluster\bin\boot\jaas.jar;c:\usr\sap\PIP\DVEBMGS01\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;c:\usr\sap\PIP\DVEBMGS01\j2ee\cluster\bin\boot\memoryanalyzer.jar
F    arg[28] = -Djava.library.path=C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\jre\bin\server;C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\jre\bin;c:\usr\sap\PIP\DVEBMGS01\j2ee\os_libs;C:\usr\sap\PIP\SYS\exe\jvm\NTAMD64\sapjvm_6.1.049\sapjvm_6\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;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 Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\usr\sap\PIP\DVEBMGS04\exe;C:\usr\sap\PIP\DVEBMGS01\exe;C:\usr\sap\PIP\SYS\exe\uc\NTAMD64
F    arg[29] = -XX:PermSize=1024m
F    arg[30] = -Xmx2024m
F    arg[31] = -XX:MaxNewSize=675m
F    arg[32] = -XX:MaxPermSize=1024m
F    arg[33] = -Xms2024m
F    arg[34] = -XX:NewSize=675m
F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
F    arg[37] = -Djmx.invoke.getters=true
F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
F    arg[39] = -Djava.security.egd=file:/dev/urandom
F    arg[40] = -Djava.awt.headless=true
F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F    arg[42] = -Drdbms.driverLocation=c:/usr/sap/PIP/DVEBMGS01/exe/mssjdbc/jdbc4/sqljdbc4.jar
F    arg[43] = -Djava.io.tmpdir=./temp
F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
F    arg[46] = -Dnetworkaddress.cache.ttl=10
F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F    arg[48] = -Djco.jarm=1
F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F    arg[50] = -XX:+UseConcMarkSweepGC
F    arg[51] = -XX:TargetSurvivorRatio=90
F    arg[52] = -verbose:gc
F    arg[53] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F    arg[54] = -XX:+PrintGCDetails
F    arg[55] = -XX:MaxErrorQueueLength=200
F    arg[56] = -XX:+PrintGCTimeStamps
F    arg[57] = -XX:+DisableExplicitGC
F    arg[58] = -XX:SoftRefLRUPolicyMSPerMB=1
F    arg[59] = -XX:-StringInternTableInPermGen
F    arg[60] = -XX:SurvivorRatio=6
F    arg[61] = -Xss2m
F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F    arg[63] = -XX:HeapDumpPath=OOM.hprof
F    arg[64] = -XX:-TraceClassUnloading
F  ignore unrecognized options : no
F  ********************************************************************************
J  JVMX version - Apr 19 2013 00:36:21 - 61_REL - optU - windows amd64 - 6 - bas2:194331 (mixed mode)
J  Error occurred during initialization of VM
J  Could not reserve enough space for object heap
J  [Last 4000 events in the event buffer]
J    <thread>                      <time>  <id>          <description>
J   4248                             0.01  0x00000001    Creating red and yellow zone [0x00000000072a0000,0x00000000072a3000]
F  [Thr 4248] *** LOG => SfCJavaVm: abort hook is called.

F [Thr 4604] Sat Apr 27 22:36:46 2013
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.

F [Thr 4604] Sat Apr 27 22:36:47 2013
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.

F [Thr 4604] Sat Apr 27 22:37:07 2013
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.

F [Thr 4604] Sat Apr 27 22:41:47 2013
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.

F [Thr 4604] Sat Apr 27 22:46:47 2013
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.
F  [Thr 4604] *** LOG => Signal 18 SIGINFO.

F [Thr 4192] Sat Apr 27 22:48:17 2013
F  [Thr 4192] *** LOG => Command STOP 0 {instance,internal}.
F  [Thr 4192] *** LOG => Result for STOP 0 {instance,internal}: 0 ok, 00000000.

F [Thr 4192] Sat Apr 27 22:50:17 2013
F  [Thr 4192] *** LOG => Timer expired (120000 ms).

F [Thr 4192] Sat Apr 27 22:50:22 2013
F  [Thr 4192] *** LOG => Timer expired (5000 ms).

F [Thr 4192] Sat Apr 27 22:50:27 2013
F  [Thr 4192] *** LOG => Timer expired (5000 ms).

F  ********************************************************************************
F  *** ERROR => Shutdown timer expired.
F  ***
F  *** Please see section 'Java shutdown failures'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************

F  [Thr 4192] *** LOG => exiting (exitcode 22001, retcode 1).
M  [Thr 4192] CCMS: CCMS Monitoring Cleanup finished successfully.


Viewing all articles
Browse latest Browse all 8975

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>