J2EE Process table to visible in SAP MMC
Hi All,
Inside my SAP server MMC i am not getting J2EE process table and ICM also. how ever it was available till yesterday. today morning i restart SAP server and it is not found there. However Java process are running in JCMON, SDM is working with NWDS.
Also MMC is set in expert mode.
Please suggest
Regards
Gyan
I am unable to see J2ee Process in SAP MMC.
There is long running job (OCS_Import_queue) is going on from last 40 hours, i have terminated that job, update the statistics of database and restart SAP server, after that it's not showing the J2ee process and even also my dispatcher is not connecting with message server.
Kernel detail are as follows:
disp+work information
OS = Win2003
Datbase = Oracle 10
kernel release 701
kernel make variant 701_REL
patch number 23
Kindly give me the solution, how to get resolve this issue, as i need to again start the saint import.
Regards
Adil
Similar Messages
-
The "J2EE process table" node not visible in the SAP MMC
For Netweaver 7.0 - The "J2EE process table" node not visible in the SAP MMC.
Details for below
SAP Systems Manager
SAP AG
Version: 7100.109.15.8983
Window Xp
Any suggestions would be apperecited.
Thanks
SriniIt's hard to say without seeing the code for TreeTable. But they probably have something like an addNode mothod for the TreeTableNode which will take care of all the updates for you. If you want to do it youself, you will probably have to get the data Model (tree.getModel()???)behind the TreeTable and use one of the fire... methods on it like fireRowChanged(???) or fireTableChanged(???). I would suspect Sun would do it this way.
-
MMC not showing J2ee process table
Dear Gurus,
I installed ECC 6.0 SR3(ABAP+JAVA) Development and Quality on the same server windows 2003 operating systems.
in MMC it is showing only development system J2ee process table it is not showing the quality system
J2ee process table.
Can any body give the solution for this.
Regards
Rao.Hi,
Please see the below link.
http://help.sap.com/saphelp_nw70/helpdata/EN/63/0f5bcdbc3611d2890d0000e8200722/frameset.htm
Anil -
Hello All,
I just installed Solution Manager 4.0 SR2, Windows SQL 2005.
Install went ok, however I am not able to see the J2EE process table in the MMC. I can see the services running using jcmon.exe, just wanted to know if anyone knows of how to get that view, its convenient.
ThanksHi,
1) Goto <b>usr\sap\SID\SYS\exe\run\sapstartsrv.exe</b>
2) Click on <b>sapstartsrv.exe</b>
Specify SID, Instance number, J2EE profile path and click on ok.
Then you can be able to see java instance details in MMC.
regards,
kanthi -
Hello All,
I just installed Ecc6.0 ABAP+JAVA, Windows SQL 2005.
Install went ok, however I am not able to see the J2EE process table in the MMC, I wanted to know if anyone knows of how to get that view?
Regards
KingHi,
I have seen this before. After installation is succesful, please stop sap via MMC and reboot the server.
After rebooting the server you will see J2EE process table in MMC.
Please try.
Manoj chintawar -
Debug mode of j2ee Process table??
Hello All,
In j2ee Process Table,3 processes are running.
SDM-Debug(Switched off)--SDM Server
Dispatcher-Disable---J2ee Dispatcher
Server0-Swiched off ---J2ee server
Why SDM server & server0 are swiched off & dispacher is disabled in the Debug mode??When we need to enable it??Hi,
Refer these links.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/558e9ae5-0601-0010-40a0-a1d35a13047d?overridelayout=true
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3a83c242-0801-0010-dc95-d496cf6dba9d?overridelayout=true
let us know if u have any issues,
Regards,
Ravi -
System is not visible in SAP MMC
Hellu Guys ,
System is up ad running fine ,but it is not visible in SAP MMC .
Kindly let me know that how to activate in MMC .You cam add snapshot in MMC , check in menu
File --> Add/Remove Snap-in -->Add --> SAP System
Provide detail as required.
Regards, -
ABAP Work process table is not showing in MMC
HI ,
My ABAP ystem is working fine but in MMC ABAP work process table is not showing.
After rebooting the server in MMC console SID is not appaeraing i have to add the entries eevry time after rebooting.
Please help me any one.
Thanks
NekkalapuHi,
I have checked the note :
Use the SAP tool NTSCMGR. EXE to call up the status of an SAP service and to uninstall or install SAP services. Note with service new installations that, before starting, you must assign a corresponding SAP user for the service with whom the service is started ('Control Panel -> Services -> Startup -> Log on As This Account -> <SID>ADM or SAPService<SID>').
a) Status query:
ntscmgr.exe query <service_name>
b) Removing a service:
ntscmgr.exe remove <service_name>
is that the right way or any other way .
Please suggest my system alaready in running state can we do this things while system up or downtime required.
Is their any impact on exsiting system. -
J2EE Process Table Server0 J2EE server status is not started
Dear Experts,
When I open J2EE Enging Visual Administrator and choose default connection as usual, I am getting an error "Unable to lookup connection default
http://<server>:8101/msgserver/text/logon returned empty list of connection parameters"
I have checked in sapmmc and found that server0 status is "stopped" and disp+work.EXE in Process List is showing status "Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE some processes running".
I have checked server0 log file and this is part of error.
"com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.api.UMException: Cannot find first configured anonymous user: J2EE_GUEST: USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!"
This problem has been occurred after I have accidentally changed the computer name.
I found many threads in sap commutinity that posted the problem seemed like my problem, and I followed the steps to solve but I am still getting this problem.
Right now the Basis guy helps me on this, but has not get the answer yet.
Any suggestions and information would be appriciate.
BI ConsultHi,
check the SAPJSF User which is Communication User between Abap and Java Stack and there password must be synchronized between Abap and java.
Open Config Tool and go to cluster-data -> Global Server
Configuration->Sevices->com.sap.security.ume.service.
Select the property ume.r3.connection.master.passwd
and setup the proper password there.
Save the changes.
Regards,
IK -
System copy for ECC 6.0 system no j2ee process under MMC
Dear support,
This has been observed in many of our clients system which are on ECC 6.0 abap+java system, that after we perform system copy from one system to another
whether it is Oracle platform or mssql server platform ( system copy for oracle using controlfile script ) ( system copy for mssql with restoring .BAK file from source )
systems are running fine but j2ee process table showing no processes like
SDM, dispatcher , server0
even configtool and go.bat are unable to connect.
Is there any specific settings we do after system copy for java side
Please let me know at earliest, as it is most strange thing i have seen in almost all my system where system copy is performed.I have already raised a post against this error but at that time i was not aware of this system copy reason behind the same.
Best regards,
AjitRYour main problem is not, that you don't see anything in MMC (the system can be added manually without much hazzle) - but is, that you database content of schema SAP<SID>DB does not match the data found on the filesystem.
If you copy the filesystem structure from production to test/qa, you need to make sure, the database and filesystem are in sync. You will have two problems if you "just copy them":
- They are out of sync because your production was going on running since you copied the backup files
- all configuration (all java property sheets) is/are set to point to the production system instead of the test/qa system
I doubt, that it will work if you copy it over. This also explains, why you can't even start configtool, because it points to the wrong system/schema. You MAY be able to fix all that manually, but you may encounter subsequent errors because not all configuration is documented, you would need to step into the whole j2ee tree and look at each and every propertysheet to find out, whether it's correct or not. Additionally, the database may have other information (see above) and all that may become overwritten during bootstrap.
So - the best way to get your system up and running quickly is to start sapinst on the source system, export your Java instance (not using ABAP but the Java dump) and re-importing that to your test/qa system.
Markus -
J2EE process in SAPMMC do not start automatically after a restart
Hello All,
I have a Netweaver with only J2EE engine set up.
Whenever I restart the server, the services at SAPMMC->Console Root-> SAP Systems-> Instance-> Process List,Current Status, Open Alerts, J2EE Process Table do not start automatically.
I have to start them manually.
Please let me know what configuration I need to make them automatic.
Thanks
RamanHi,
Please confirm that J2ee is failing to start when you restart the server. If yes do post the logs so that we can drill to the max extent.
Rgds
Radhakrishna D S
Edited by: Radhakrishna D S on Sep 8, 2008 8:17 AM
Edited by: Radhakrishna D S on Sep 8, 2008 8:18 AM
Edited by: Radhakrishna D S on Sep 8, 2008 8:19 AM -
Instance Status Yellow on SAP MMC Console
Dear Experts,
We are installing NW 7.0 dialog instance on Windowsx64 bit platform, Central instance is running on Aix64 bit,
NW 7.0 Java add-in has installed on Central instance,
I want to start only abap instance on new windows application server, i set rdisp/j2ee_start parameter to "0",
Now java process do not start but SAP mmc console status is yellow because of it, disp+dowk process message is J2EE status info unavaliable,
How can unistall Java instance from newly instaled application server ?
Best RegardsHi,
Regarding the MMC display "J2EE status info unavailable", as you don't want a dual stack remove the entry icm/HTTP/j2ee_0 from the instance profile and set the parameter 'is/HTTP/default_root_hdl = abap'.
Please reboot your system (bounce OS) to see if this helps.
If this does not help please try this.
1. Stop the SAP service
2. Open a command prompt
3. Go to usr\sap\<SID>\...\exe\run
4. call 'sapstartsrv.exe -t' from the command line
5. Confirm the dialog window
6. Start the service again
Best Regards
Niraj -
Jstart.exe process in sap mmc is not getting started
Hi,
The jstart.exe process of sap mmc (management console/server) is not getting started.
The status for this process is "starting the processes". Need help!
The developer trace is as follows :
trc file: "dev_jstart.7668", trc level: 1, release: "720"
trc file: "dev_jstart.new", trc level: 1, release: "720"
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 7668
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Mon Oct 08 10:03:13 2012
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F Mon Oct 08 10:03:13 2012
F ********************************************************************************
F Java environment properties (C:\usr\sap\SV1\J02\work\jstart.jvm)
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F ********************************************************************************
F SAP extensions : available
F ********************************************************************************
I [Thr 7652] MtxInit: 30002 0 2
trc file: "dev_jstart", trc level: 1, release: "720"
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
F
F [Thr 7652] Mon Oct 08 10:03:14 2012
F [Thr 7652] *** LOG => connected to Enqueue Server.
F [Thr 7652] *** LOG => connected to Message Server.
F [Thr 7652] *** LOG => Starting run level 1.
F ********************************************************************************
F Java process [deployment] properties:
F section name : deployment
F config file : C:\usr\sap\SV1\J02\exe\startup.properties
F node name : Deploy_offline
F home directory : C:\usr\sap\SV1\J02\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Starting nodes: runlevel 1.
F
F Mon Oct 08 10:03:15 2012
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=deployment
F arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_deployment
F arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_deployment.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_deployment.out
F stderr : C:\usr\sap\SV1\J02\work\std_deployment.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process Deploy_offline started with pid 7968
F ********************************************************************************
F [Thr 7652] *** LOG => Process deployment started (pid 7968).
F
F [Thr 7652] Mon Oct 08 10:03:19 2012
F [Thr 7652] *** LOG => Process deployment stopping (pid 7968).
F
F [Thr 6972] Mon Oct 08 10:03:19 2012
F [Thr 6972] *** LOG => Signal 13 SIGCHLD.
F [Thr 7652] *** LOG => Process deployment stopped (pid 7968).
F [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Run level 1 completed.
F [Thr 7652] *** LOG => Starting run level 2.
F ********************************************************************************
F Java process [bootstrap] properties:
F section name : bootstrap
F config file : C:\usr\sap\SV1\J02\exe\startup.properties
F node name : Instance_bootstrap
F home directory : C:\usr\sap\SV1\J02\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Starting nodes: runlevel 2.
F
F Mon Oct 08 10:03:20 2012
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=bootstrap
F arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_bootstrap
F arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_bootstrap.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_bootstrap.out
F stderr : C:\usr\sap\SV1\J02\work\std_bootstrap.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process Instance_bootstrap started with pid 7952
F ********************************************************************************
F [Thr 7652] *** LOG => Process bootstrap started (pid 7952).
F
F [Thr 7652] Mon Oct 08 10:03:47 2012
F [Thr 7652] *** LOG => Process bootstrap running (pid 7952).
F [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).
F
F [Thr 7652] Mon Oct 08 10:04:10 2012
F [Thr 7652] *** LOG => Process bootstrap stopping (pid 7952).
F
F [Thr 4436] Mon Oct 08 10:04:10 2012
F [Thr 4436] *** LOG => Signal 13 SIGCHLD.
F [Thr 7652] *** LOG => Process bootstrap stopped (pid 7952).
F [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Run level 2 completed.
F [Thr 7652] *** LOG => Starting run level 3.
F ********************************************************************************
F Java process [debugproxy] properties:
F section name : debugproxy
F config file : C:\usr\sap\SV1\J02\exe\dproxy.properties
F node name : Debug_Proxy
F home directory : C:\usr\sap\SV1\J02/j2ee/rdbg.proxy
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F ********************************************************************************
F ICM process [icm] properties:
F section name : icm
F config file : C:\usr\sap\SV1\J02\exe\icm.properties
F node name : ICM
F home directory : C:\usr\sap\SV1\J02\work
F shutdown timeout : 122000 ms
F exit timeout : 7000 ms
F ********************************************************************************
F ********************************************************************************
F Java process [server0] properties:
F section name : ID24836450
F config file : C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
F node name : server0
F home directory : .
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : true
F debugger active : false
F ********************************************************************************
F [Thr 7652] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 0.
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\icman.EXE
F arg[ 1] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 2] = -nodeId=1
F arg[ 3] = -f
F arg[ 4] = C:\usr\sap\SV1\J02\work\\dev_icm
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_icm.out
F stderr : C:\usr\sap\SV1\J02\work\std_icm.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process ICM started with pid 7336
F ********************************************************************************
F [Thr 7652] *** LOG => Process icm started (pid 7336).
F
F [Thr 7652] Mon Oct 08 10:04:12 2012
F [Thr 7652] *** LOG => Process icm running (pid 7336).
F [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 1.
F
F Mon Oct 08 10:04:16 2012
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
F arg[ 1] = -nodeId=2
F arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 3] = -DSAPINFO=SV1_02_server0
F arg[ 4] = -hostvm
F arg[ 5] = -nodeName=ID24836450
F arg[ 6] = -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
F arg[ 7] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
F arg[ 8] = -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
F arg[ 9] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_server0.out
F stderr : C:\usr\sap\SV1\J02\work\std_server0.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process server0 started with pid 7616
F ********************************************************************************
F [Thr 7652] *** LOG => Process server0 started (pid 7616).Hi Ravi,
Thanks for your quick response.
Where do I find the default trace for this?
The server0 process status is "Waiting to start". The developer trace for server0 is as follows :
trc file: "dev_server0", trc level: 1, release: "720"
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 7616
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Mon Oct 08 10:04:17 2012
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
arg[ 4] : -DSAPINFO=SV1_02_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID24836450
arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F
F Mon Oct 08 10:04:17 2012
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 7280] MtxInit: 10002 0 2
I [Thr 7280] MPI: dynamic quotas disabled.
I [Thr 7280] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 7280] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 7280] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M [Thr 7280] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M [Thr 7280] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 7280] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Mon Oct 08 10:04:17 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 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
F arg[ 6] = -Xjvmx
F arg[ 7] = -XsapSystem:02
F arg[ 8] = -DSAPSTARTUP=1
F arg[ 9] = -DSAPSYSTEM=02
F arg[10] = -DSAPSYSTEMNAME=SV1
F arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
F arg[12] = -DSAPDBHOST=INLD50787371A
F arg[13] = -DSAPINFO=SV1_02_server0
F arg[14] = -Dj2ee.dbhost=INLD50787371A
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=7616
F arg[20] = -Djstartup.ownHardwareId=Q0723431166
F arg[21] = -Djstartup.debuggable=yes
F arg[22] = -DLoadBalanceRestricted=no
F arg[23] = -XdebugPortRange:50221-50221
F arg[24] = -Denv.class.path=
F arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
F arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
F arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F arg[29] = -XX:PermSize=1024m
F arg[30] = -Xmx2048m
F arg[31] = -XX:MaxNewSize=410m
F arg[32] = -XX:MaxPermSize=1024m
F arg[33] = -Xms2048m
F arg[34] = -XX:NewSize=410m
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:\sapdb\clients\SV1\runtime\jar\sapdbc.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] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
F arg[51] = -XX:+UseConcMarkSweepGC
F arg[52] = -XX:TargetSurvivorRatio=90
F arg[53] = -verbose:gc
F arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[55] = -XX:+PrintGCDetails
F arg[56] = -XX:MaxErrorQueueLength=200
F arg[57] = -XX:+PrintGCTimeStamps
F arg[58] = -XX:+DisableExplicitGC
F arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[60] = -XX:-StringInternTableInPermGen
F arg[61] = -XX:SurvivorRatio=9
F arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F arg[63] = -XX:HeapDumpPath=OOM.hprof
F arg[64] = -XX:-TraceClassUnloading
F arg[65] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 7364] *** LOG => SfCJavaVm: abort hook is called.
F
F [Thr 7280] Mon Oct 08 12:28:13 2012
F [Thr 7280] *** LOG => Command STOP 0 {}.
F [Thr 7280] *** LOG => Result for STOP 0 {}: 0 ok, 00000000.
F
F [Thr 7280] Mon Oct 08 12:28:33 2012
F [Thr 7280] *** LOG => Command DUMP_THREADS 0 {}.
J
J ================================================================================
J Java thread dump : Mon Oct 08 12:28:33 2012
J
J ================================================================================
F [Thr 7280] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.
M
M [Thr 684] Mon Oct 08 12:28:33 2012
M [Thr 684] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "dev_server0", trc level: 1, release: "720"
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 5508
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Mon Oct 08 12:28:34 2012
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
arg[ 4] : -DSAPINFO=SV1_02_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID24836450
arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F
F Mon Oct 08 12:28:34 2012
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 500] MtxInit: 10002 0 2
I [Thr 500] MPI: dynamic quotas disabled.
I [Thr 500] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 500] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 500] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M [Thr 500] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M [Thr 500] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 500] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Mon Oct 08 12:28:34 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 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
F arg[ 6] = -Xjvmx
F arg[ 7] = -XsapSystem:02
F arg[ 8] = -DSAPSTARTUP=1
F arg[ 9] = -DSAPSYSTEM=02
F arg[10] = -DSAPSYSTEMNAME=SV1
F arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
F arg[12] = -DSAPDBHOST=INLD50787371A
F arg[13] = -DSAPINFO=SV1_02_server0
F arg[14] = -Dj2ee.dbhost=INLD50787371A
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=5508
F arg[20] = -Djstartup.ownHardwareId=Q0723431166
F arg[21] = -Djstartup.debuggable=yes
F arg[22] = -DLoadBalanceRestricted=no
F arg[23] = -XdebugPortRange:50221-50221
F arg[24] = -Denv.class.path=
F arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
F arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
F arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F arg[29] = -XX:PermSize=1024m
F arg[30] = -Xmx2048m
F arg[31] = -XX:MaxNewSize=410m
F arg[32] = -XX:MaxPermSize=1024m
F arg[33] = -Xms2048m
F arg[34] = -XX:NewSize=410m
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:\sapdb\clients\SV1\runtime\jar\sapdbc.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] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
F arg[51] = -XX:+UseConcMarkSweepGC
F arg[52] = -XX:TargetSurvivorRatio=90
F arg[53] = -verbose:gc
F arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[55] = -XX:+PrintGCDetails
F arg[56] = -XX:MaxErrorQueueLength=200
F arg[57] = -XX:+PrintGCTimeStamps
F arg[58] = -XX:+DisableExplicitGC
F arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[60] = -XX:-StringInternTableInPermGen
F arg[61] = -XX:SurvivorRatio=9
F arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F arg[63] = -XX:HeapDumpPath=OOM.hprof
F arg[64] = -XX:-TraceClassUnloading
F arg[65] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 4136] *** LOG => SfCJavaVm: abort hook is called.
F
F [Thr 500] Mon Oct 08 12:29:02 2012
F [Thr 500] *** LOG => Command DUMP_THREADS 0 {}.
J
J ================================================================================
J Java thread dump : Mon Oct 08 12:29:02 2012
J
J ================================================================================
F [Thr 500] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.
M
M [Thr 5068] Mon Oct 08 12:29:02 2012
M [Thr 5068] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "dev_server0", trc level: 1, release: "720"
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 7704
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Mon Oct 08 12:29:17 2012
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
arg[ 4] : -DSAPINFO=SV1_02_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID24836450
arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F
F Mon Oct 08 12:29:17 2012
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 4980] MtxInit: 10002 0 2
I [Thr 4980] MPI: dynamic quotas disabled.
I [Thr 4980] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 4980] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 4980] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M [Thr 4980] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M [Thr 4980] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 4980] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Mon Oct 08 12:29:17 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 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
F arg[ 6] = -Xjvmx
F arg[ 7] = -XsapSystem:02
F arg[ 8] = -DSAPSTARTUP=1
F arg[ 9] = -DSAPSYSTEM=02
F arg[10] = -DSAPSYSTEMNAME=SV1
F arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
F arg[12] = -DSAPDBHOST=INLD50787371A
F arg[13] = -DSAPINFO=SV1_02_server0
F arg[14] = -Dj2ee.dbhost=INLD50787371A
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=7704
F arg[20] = -Djstartup.ownHardwareId=Q0723431166
F arg[21] = -Djstartup.debuggable=yes
F arg[22] = -DLoadBalanceRestricted=no
F arg[23] = -XdebugPortRange:50221-50221
F arg[24] = -Denv.class.path=
F arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
F arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
F arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F arg[29] = -XX:PermSize=1024m
F arg[30] = -Xmx2048m
F arg[31] = -XX:MaxNewSize=410m
F arg[32] = -XX:MaxPermSize=1024m
F arg[33] = -Xms2048m
F arg[34] = -XX:NewSize=410m
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:\sapdb\clients\SV1\runtime\jar\sapdbc.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] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
F arg[51] = -XX:+UseConcMarkSweepGC
F arg[52] = -XX:TargetSurvivorRatio=90
F arg[53] = -verbose:gc
F arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[55] = -XX:+PrintGCDetails
F arg[56] = -XX:MaxErrorQueueLength=200
F arg[57] = -XX:+PrintGCTimeStamps
F arg[58] = -XX:+DisableExplicitGC
F arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[60] = -XX:-StringInternTableInPermGen
F arg[61] = -XX:SurvivorRatio=9
F arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F arg[63] = -XX:HeapDumpPath=OOM.hprof
F arg[64] = -XX:-TraceClassUnloading
F arg[65] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 4736] *** LOG => SfCJavaVm: abort hook is called. -
Starting local J2EE engine from SAP MMC
I am trying to start my local J2EE engine using SAP MMC. However, when I select the start option, the DB no longer starts automatically. I can manually start the DB, select start, and the engine will start. Previously, I could select start and everything would just come up.
Can anyone tell me where the disconnect is occuring?Hi,
If you have an add-in installation then you can try to stop the java system by stopping the java dispacther by stopping the j2ee process.You can just try restarting the java system using SMICM.You can check whether the data base services are set to auto start or need a manual start.
Reward points if helpfull.
Regards,
Vamshi. -
Sap J2EE Engine is not visible in NWDS
Hi ,
iam new to Sap iam Builing an Simple Application in Which SAP J2EE engine is not visible under
Window ->Preferences
can any one help me ASAP.MY Sap J2EE Engine is Install in Remote Host and iam not getting the option Of SapJ2EE
Engine in Window->Prefrences.
iam building an Webdynpro Application In Netweaver.
1) When i Click Deploy NewArchive and Run.
2) Sap J2ee engine login Screen Come i logged in.
3) But after deployment is finish.
Iam getting an Error Saying that:
ERROR:
com.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
at com.sap.ide.eclipse.deployer.dc.DCClientImpl.<init>(DCClientImpl.java:70)
at com.sap.ide.eclipse.deployer.dc.DCClientFactoryImpl.createClient(DCClientFactoryImpl.java:142)
at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:201)
at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:359)
at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:149)
at com.sap.ide.webdynpro.archivebuilder.ActionDeployArchive$DeployJob.run(ActionDeployArchive.java:214)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
can you please help me with is error.
Maybe you are looking for
-
A problem while implementing a file to file senario
hi all : There is some problem while implement a file to file senario. the file couldn't be sent or recieved. and as I try to check Check the Sender File Adapter Status via Runtime Workbench -> Component Monitoring -> Communication C
-
I have purchased gems on clash of clans and i haven't received my gems.
I purchased gems on clash of clans, 20$ pack, and at first it was processing it and it wouldn't load or give me gems, so i closed it out and re opened it to see if it worked and it hasn't, so i thought it was my connection possibly lagging. and i end
-
Number of PO with Purchase requisition number not null
Hi Experts, I need to number of PO with Purchase requisition number not null in ECC T-CODE nse16n and table name =EKPO But when I make EKPO-BANFN not equal NULL it doesnt work ? how can do that ? I custom my data source 2LIS_02_SCL with EKET.BANFN I
-
Unable to edit MailBox folder & Rules of other users with PowerShell
Hello, I'm trying to modify the rules of my users inbox folders and rules but I'm not able to do that even though I'm assigned the rights which were supposed to be enough. The account I'm running this command is a domain admin and pretty much has all
-
Audio does not encode when importing MPEGs
Hello, I am working in Flash 8 for the Mac. I am trying to import an MPEG file but it does not give the ability to encode the audio track. The video file does have an audio track and I was able to import this very same file last week with success. As