Problem in starting the J2EE server0 process.
Hello Experts,
We have EP 7.0 in our landscape, and when we try to start SAP J2EE engine.It shows the server0 process only for some time and later this process stops automatically. Even the WatchDog process stops.
Is there is any configurations we need to do- or parameters or tuning that we need to do to keep the server0 up ?
If there are post installation steps document which talks about these issues, it would be great.
Thanks
Edited by: Mrinalini Das on Jan 11, 2008 10:29 PM
Thank you the quick response.
Here are the logs, also i have mailed you the defaultTrace.0.trc to your sap mail ID.
dev_server0 Complete Log :
trc file: "/usr/sap/PTS/JC68/work/dev_server0", trc level: 1, release: "700"
node name : ID688970850
pid : 89680
system name : PTS
system nr. : 68
started at : Mon Jan 14 10:19:39 2008
arguments :
arg[00] : /usr/sap/PTS/SYS/exe/run/jlaunch
arg[01] : pf=/usr/sap/PTS/SYS/profile/PTS_JC68_i5sap
arg[02] : -DSAPINFO=PTS_68_server
arg[03] : pf=/usr/sap/PTS/SYS/profile/PTS_JC68_i5sap
[Thr 1] Mon Jan 14 10:19:39 2008
[Thr 1] *** WARNING => INFO: Unknown property [instance.box.number=PTSJC68i5sap] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.host=i5sap] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.port=3269] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.system.id=68] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/PTS/JC68/j2ee/cluster/instance.properties]
-> ms host : i5sap
-> ms port : 3969
-> OS libs : /usr/sap/PTS/JC68/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
Instance properties
-> ms host : i5sap
-> ms port : 3969
-> os libs : /usr/sap/PTS/JC68/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
-> [01] bootstrap_ID68897080 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
-> [02] bootstrap_ID68897085 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID688970800 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
-> [01] ID688970850 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
[Thr 1] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 1] JLaunchRequestQueueInit: create pipe listener thread
[Thr 258] JLaunchRequestFunc: Thread 258 started as listener thread for np messages.
[Thr 515] WaitSyncSemThread: Thread 515 started as semaphore monitor thread.
[Thr 1] Mon Jan 14 10:19:40 2008
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_USE_DESCRIPTOR_STDIO=N already set
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_USE_DESCRIPTOR_STDIO=N already set in ILE
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_ALLOW_PREV=1 already set
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_ALLOW_PREV=1 already set in ILE
[Thr 1] JStartupIPaseInitJavaEnvironment: PASE_THREAD_ATTACH=Y already set
[Thr 1] JStartupIPaseInitJavaEnvironment: PASE_THREAD_ATTACH=Y already set in ILE
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_STARTUP=/usr/lib/start64 already set
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_STARTUP=/usr/lib/start64 already set in ILE
[Thr 1] SigISetDefaultAction : default handling for signal 20
[Thr 1] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 1] CPIC (version=700.2006.09.13)
[Thr 1] [Node: server0] java home is set by profile parameter
Java Home: /QIBM/ProdData/Java400/jdk14
JStartupIReadSection: read node properties [ID688970850]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /QIBM/ProdData/Java400/jdk14
-> java parameters : -Djco.jarm=1 -verbose:gc -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 -Djava.ext.dirs=/usr/sap/PTS/SYS/j2ee/ext -Dos400.define.class.cache.file=/usr/sap/PTS/SYS/j2ee/cache/QDefineClassCache.jar -Dos400.define.class.cache.hours=9999 -Dos400.define.class.cache.maxpgms=40000 -Djava.compiler=jitc -Dos400.run.mode=jitc -Dos400.disable.explicit.gc -DJava.compiler=jitc -verbose:gc
-> java vm version : 1.4.2
-> java vm vendor : Classic VM (IBM Corporation)
-> java vm type : server
-> java vm cpu : PowerPC
-> heap size : 4096M
-> init heap size : 4096M
-> root path : /usr/sap/PTS/JC68/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/PTS/JC68/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 : /usr/sap/PTS/SYS/exe/run/jstartup.jar:/usr/sap/PTS/SYS/exe/run/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 56821
-> shutdown timeout : 120000
[Thr 1] JLaunchISetDebugMode: set debug mode [no]
[Thr 1] JStartupIGetILEExecutablePath: original setting of environment variable PATH in ILE: /usr/sap/PTS/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.
[Thr 1] JHVM_SetExecutablePath: Successfully set in ILE: PATH=/QIBM/ProdData/Java400/jdk14/bin:/usr/sap/PTS/JC68/j2ee/os_libs:/usr/sap/PTS/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.
[Thr 1] JStartupIGetJ2EELibrary: Default J2EE library computed as: SAPJ2EE68.
[Thr 1] JStartupIGetILELibraryPath: original setting of environment variable LIBPATH in ILE: /usr/sap/PTS/SYS/exe/run
[Thr 1] JHVM_SetLibraryPath: Successfully set in ILE: LIBPATH=/QIBM/ProdData/Java400/jdk14/PASE64/lib:/QSYS.LIB/SAPJ2EE68.LIB:/usr/sap/PTS/JC68/j2ee/os_libs:/usr/sap/PTS/SYS/exe/run
[Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djco.jarm=1
-> arg[ 4]: -verbose:gc
-> arg[ 5]: -Djava.security.policy=./java.policy
-> arg[ 6]: -Djava.security.egd=file:/dev/urandom
-> arg[ 7]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 8]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 9]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 10]: -Djava.ext.dirs=/usr/sap/PTS/SYS/j2ee/ext
-> arg[ 11]: -Dos400.define.class.cache.file=/usr/sap/PTS/SYS/j2ee/cache/QDefineClassCache.jar
-> arg[ 12]: -Dos400.define.class.cache.hours=9999
-> arg[ 13]: -Dos400.define.class.cache.maxpgms=40000
-> arg[ 14]: -Djava.compiler=jitc
-> arg[ 15]: -Dos400.run.mode=jitc
-> arg[ 16]: -Dos400.disable.explicit.gc
-> arg[ 17]: -DJava.compiler=jitc
-> arg[ 18]: -verbose:gc
-> arg[ 19]: -Dsys.global.dir=/usr/sap/PTS/SYS/global
-> arg[ 20]: -Dapplication.home=/sapmnt/PTS/exe
-> arg[ 21]: -Djava.class.path=/usr/sap/PTS/SYS/exe/run/jstartup.jar:/usr/sap/PTS/SYS/exe/run/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> arg[ 22]: -Djava.library.path=/QIBM/ProdData/Java400/jdk14/PASE64/lib:/QSYS.LIB/SAPJ2EE68.LIB:/usr/sap/PTS/JC68/j2ee/os_libs:/usr/sap/PTS/SYS/exe/run
-> arg[ 23]: -Dmemory.manager=4096M
-> arg[ 24]: -Xmx4096M
-> arg[ 25]: -Xms4096M
-> arg[ 26]: -DLoadBalanceRestricted=no
-> arg[ 27]: -Djstartup.mode=JCONTROL
-> arg[ 28]: -Djstartup.ownProcessId=89680
-> arg[ 29]: -Djstartup.ownHardwareId=I0474946350
-> arg[ 30]: -Djstartup.whoami=server
-> arg[ 31]: -Djstartup.debuggable=no
-> arg[ 32]: -DSAPINFO=PTS_68_server
-> arg[ 33]: -DSAPSTARTUP=1
-> arg[ 34]: -DSAPSYSTEM=68
-> arg[ 35]: -DSAPSYSTEMNAME=PTS
-> arg[ 36]: -DSAPMYNAME=i5sap_PTS_68
-> arg[ 37]: -DSAPDBHOST=i5sap
-> arg[ 38]: -Dj2ee.dbhost=i5sap
Mon Jan 14 10:19:41 2008
GC: initial heap(KB) 4194304; maximum heap(KB) 4195328; virtual machine identifier DBADD35BC7003900; heap identifier DBADD35BC7003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 01/14/08 10:19:41
[Thr 772] JHVM_LoadJavaVM: Java VM created OK.
GC 1: live objects 2696; collected objects 1677; collected(KB) 152.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 7408; current threshold(KB) 4194304.
GC 1: collect (milliseconds) 42.
GC 1: current cycle allocation(KB) 2654; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 01/14/08 10:19:41
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1800] Mon Jan 14 10:19:48 2008
[Thr 1800] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1800] Mon Jan 14 10:19:49 2008
[Thr 1800] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1800] Mon Jan 14 10:19:51 2008
[Thr 1800] JLaunchISetClusterId: set cluster id 688970850
[Thr 1800] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1800] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 23388] Mon Jan 14 10:21:48 2008
[Thr 23388] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 20818] Mon Jan 14 10:21:50 2008
[Thr 20818] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 1800] Mon Jan 14 10:21:57 2008
[Thr 1800] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
Mon Jan 14 10:28:42 2008
GC 2: starting collection, maximum allocation reached.
Mon Jan 14 10:28:43 2008
GC 2: collection starting 01/14/08 10:28:41
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:44 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:45 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:46 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:47 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:48 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:50 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:28:56 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:29:00 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:29:01 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:29:12 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:29:28 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:29:30 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:29:52 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:30:11 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:30:31 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:32:00 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:32:09 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:33:16 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:35:14 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:35:25 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:35:57 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:35:59 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:36:30 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:38:00 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:39:08 2008
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:40:00 2008
GC 3: starting collection, reason stop the world collection.
Mon Jan 14 10:49:00 2008
GC 2: live objects 2510393; collected objects 21929736; collected(KB) 3218537.
Mon Jan 14 10:49:01 2008
GC 2: queued for finalization 0; total soft references 11955; cleared soft references 7727.
GC 2: current heap(KB) 4067680; current threshold(KB) 4194304.
GC 2: collect (milliseconds) 1216837.
GC 2: current cycle allocation(KB) 113; previous cycle allocation(KB) 3648831.
GC 2: total weak references 10190; cleared weak references 677.
GC 2: total final references 70602; cleared final references 67027.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 01/14/08 10:48:58
GC 3: collection starting 01/14/08 10:48:58
[Thr 258] Mon Jan 14 10:51:37 2008
[Thr 258] JLaunchRequestFunc: receive command:17, argument:0 from pid:89653
[Thr 258] JLaunchIShutdownInvoke: set shutdown interval (stop:1200336697/end:1200336817/TO:120)
[Thr 258] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 258] JHVM_FrameworkShutdownDirect: invoke direct shutdown
*stdserver0.out Log :*_
stdout/stderr redirect
node name : server0
pid : 89653
system name : PTS
system nr. : 68
started at : Mon Jan 14 10:19:38 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 4194304; maximum heap(KB) 4195328; virtual machine identifier DBADD35BC7003900; heap identifier DBADD35BC7003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 01/14/08 10:19:41
GC 1: live objects 2696; collected objects 1677; collected(KB) 152.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 7408; current threshold(KB) 4194304.
GC 1: collect (milliseconds) 42.
GC 1: current cycle allocation(KB) 2654; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 01/14/08 10:19:41
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 3708 ms.
Loading: PoolManager ... 43 ms.
Loading: ApplicationThreadManager ... 397 ms.
Loading: ThreadManager ... 98 ms.
Loading: IpVerificationManager ... 104 ms.
Loading: ClassLoaderManager ... 198 ms.
Loading: ClusterManager ... 2478 ms.
Loading: LockingManager ... 1936 ms.
Loading: ConfigurationManager ... 17119 ms.
Loading: LicensingManager ... 220 ms.
Loading: CacheManager ... 1811 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (654 ms).
Service cafeuodi~mnuacc started. (474 ms).
Service timeout started. (809 ms).
Service memory started. (746 ms).
Service runtimeinfo started. (910 ms).
Service cross started. (1109 ms).
Service cafeucc~api started. (1439 ms).
Service file started. (2481 ms).
Service jmx_notification started. (98 ms).
Service userstore started. (140 ms).
Service trex.service started. (2350 ms).
Service p4 started. (2203 ms).
Service classpath_resolver started. (196 ms).
Service log_configurator started. (12159 ms).
Service locking started. (31 ms).
Service naming started. (2849 ms).
Service http started. (2645 ms).
Service failover started. (234 ms).
Service appclient started. (486 ms).
Service jmsconnector started. (612 ms).
Service javamail started. (693 ms).
Service ts started. (654 ms).
Service licensing started. (54 ms).
Service connector started. (1465 ms).
Service iiop started. (2624 ms).
Service webservices started. (8604 ms).
Service deploy started. (24068 ms).
Service MigrationService started. (195 ms).
Service bimmrdeployer started. (298 ms).
Service configuration started. (466 ms).
Service dbpool started. (10511 ms).
Service cafeugpmailcf started. (1516 ms).
Service com.sap.security.core.ume.service started. (10720 ms).
Service security started. (6532 ms).
Service shell started. (210 ms).
Service tceCATTPingservice started. (28 ms).
Service applocking started. (415 ms).
Service telnet started. (243 ms).
Service classload started. (928 ms).
Service webdynpro started. (688 ms).
Service keystore started. (1678 ms).
Service ssl started. (144 ms).
Service cafummetadata~imp started. (2339 ms).
Service jmx started. (2396 ms).
Service tcsecsecurestorage~service started. (2235 ms).
Service dsr started. (4215 ms).
Service basicadmin started. (2652 ms).
Service developmentserver started. (6558 ms).
Service com.adobe~LicenseService started. (347 ms).
Service ejb started. (7742 ms).
Service servlet_jsp started. (8172 ms).
Service tcsecwssec~service started. (1769 ms).
Service com.adobe~DataManagerService started. (3904 ms).
Service cafumrelgroups~imp started. (6937 ms).
Service tcsecdestinations~service started. (4931 ms).
Service cafeugp~model started. (703 ms).
Service tceujwfuiwizsvc started. (10 ms).
Service com.adobe~DocumentServicesBinaries2 started. (453 ms).
Service com.adobe~DocumentServicesConfiguration started. (4902 ms).
Service com.adobe~PDFManipulation started. (581 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (619 ms).
Service com.adobe~FontManagerService started. (1140 ms).
Service com.adobe~DocumentServicesDestProtoService started. (1016 ms).
Service pmi started. (1115 ms).
Service com.adobe~TrustManagerService started. (963 ms).
Service apptracing started. (3598 ms).
Service tc.monitoring.logviewer started. (10414 ms).
Service monitor started. (7459 ms).
Service adminadapter started. (5537 ms).
Service prtbridge started. (9821 ms).
Service com.sap.portal.pcd.gl started. (51 ms).
Service cafeuer~service started. (4123 ms).
Service CUL started. (10769 ms).
Service com.adobe~XMLFormService started. (3796 ms).
Service cafruntimeconnectivity~impl started. (74434 ms).
Service com.sap.portal.prt.sapj2ee started. (918 ms).
Service tcsecvsi~service started. (5263 ms).
Service sld started. (12416 ms).
Service rfcengine started. (10151 ms).
Service jms_provider started. (20929 ms).
ServiceManager started for 104173 ms.
Framework started for 132732 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 2: starting collection, maximum allocation reached.
GC 2: collection starting 01/14/08 10:28:41
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, reason stop the world collection.
GC 2: live objects 2510393; collected objects 21929736; collected(KB) 3218537.
GC 2: queued for finalization 0; total soft references 11955; cleared soft references 7727.
GC 2: current heap(KB) 4067680; current threshold(KB) 4194304.
GC 2: collect (milliseconds) 1216837.
GC 2: current cycle allocation(KB) 113; previous cycle allocation(KB) 3648831.
GC 2: total weak references 10190; cleared weak references 677.
GC 2: total final references 70602; cleared final references 67027.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 01/14/08 10:48:58
GC 3: collection starting 01/14/08 10:48:58
SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel September 11, 2006 16:35 GMT
dev_dispatcher log
trc file: "/usr/sap/PTS/JC68/work/dev_dispatcher", trc level: 1, release: "700"
node name : ID688970800
pid : 89679
system name : PTS
system nr. : 68
started at : Mon Jan 14 10:19:39 2008
arguments :
arg[00] : /usr/sap/PTS/SYS/exe/run/jlaunch
arg[01] : pf=/usr/sap/PTS/SYS/profile/PTS_JC68_i5sap
arg[02] : -DSAPINFO=PTS_68_dispatcher
arg[03] : pf=/usr/sap/PTS/SYS/profile/PTS_JC68_i5sap
[Thr 1] Mon Jan 14 10:19:39 2008
[Thr 1] *** WARNING => INFO: Unknown property [instance.box.number=PTSJC68i5sap] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.host=i5sap] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.port=3269] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.system.id=68] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/PTS/JC68/j2ee/cluster/instance.properties]
-> ms host : i5sap
-> ms port : 3969
-> OS libs : /usr/sap/PTS/JC68/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
Instance properties
-> ms host : i5sap
-> ms port : 3969
-> os libs : /usr/sap/PTS/JC68/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
-> [01] bootstrap_ID68897080 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
-> [02] bootstrap_ID68897085 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID688970800 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
-> [01] ID688970850 : /usr/sap/PTS/JC68/j2ee/cluster/instance.properties
[Thr 1] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 1] JLaunchRequestQueueInit: create pipe listener thread
[Thr 258] JLaunchRequestFunc: Thread 258 started as listener thread for np messages.
[Thr 515] WaitSyncSemThread: Thread 515 started as semaphore monitor thread.
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_USE_DESCRIPTOR_STDIO=N already set
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_USE_DESCRIPTOR_STDIO=N already set in ILE
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_ALLOW_PREV=1 already set
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_ALLOW_PREV=1 already set in ILE
[Thr 1] JStartupIPaseInitJavaEnvironment: PASE_THREAD_ATTACH=Y already set
[Thr 1] JStartupIPaseInitJavaEnvironment: PASE_THREAD_ATTACH=Y already set in ILE
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_STARTUP=/usr/lib/start64 already set
[Thr 1] JStartupIPaseInitJavaEnvironment: QIBM_JAVA_PASE_STARTUP=/usr/lib/start64 already set in ILE
[Thr 1] SigISetDefaultAction : default handling for signal 20
[Thr 1] Mon Jan 14 10:19:40 2008
[Thr 1] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 1] CPIC (version=700.2006.09.13)
[Thr 1] [Node: dispatcher] java home is set by profile parameter
Java Home: /QIBM/ProdData/Java400/jdk14
JStartupIReadSection: read node properties [ID688970800]
-> node name : dispatcher
-> node type : dispatcher
-> node execute : yes
-> jlaunch parameters :
-> java path : /QIBM/ProdData/Java400/jdk14
-> java parameters : -verbose:gc -Djava.security.policy=.\java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -Djava.ext.dirs=/usr/sap/PTS/SYS/j2ee/ext -Dos400.define.class.cache.file=/usr/sap/PTS/SYS/j2ee/cache/QDefineClassCache.jar -Dos400.define.class.cache.hours=9999 -Dos400.define.class.cache.maxpgms=40000 -Djava.compiler=jitc -Dos400.run.mode=jitc -Dos400.disable.explicit.gc -DJava.compiler=jitc
-> java vm version : 1.4.2
-> java vm vendor : Classic VM (IBM Corporation)
-> java vm type : server
-> java vm cpu : PowerPC
-> heap size : 170M
-> init heap size : 170M
-> root path : /usr/sap/PTS/JC68/j2ee/cluster/dispatcher
-> class path : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/PTS/JC68/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 : /usr/sap/PTS/SYS/exe/run/jstartup.jar:/usr/sap/PTS/SYS/exe/run/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50000
-> shutdown timeout : 120000
[Thr 1] JLaunchISetDebugMode: set debug mode [no]
[Thr 1] JStartupIGetILEExecutablePath: original setting of environment variable PATH in ILE: /usr/sap/PTS/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.
[Thr 1] JHVM_SetExecutablePath: Successfully set in ILE: PATH=/QIBM/ProdData/Java400/jdk14/bin:/usr/sap/PTS/JC68/j2ee/os_libs:/usr/sap/PTS/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.
[Thr 1] JStartupIGetJ2EELibrary: Default J2EE library computed as: SAPJ2EE68.
[Thr 1] JStartupIGetILELibraryPath: original setting of environment variable LIBPATH in ILE: /usr/sap/PTS/SYS/exe/run
[Thr 1] JHVM_SetLibraryPath: Successfully set in ILE: LIBPATH=/QIBM/ProdData/Java400/jdk14/PASE64/lib:/QSYS.LIB/SAPJ2EE68.LIB:/usr/sap/PTS/JC68/j2ee/os_libs:/usr/sap/PTS/SYS/exe/run
[Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [dispatcher]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -verbose:gc
-> arg[ 4]: -Djava.security.policy=.\java.policy
-> arg[ 5]: -Djava.security.egd=file:/dev/urandom
-> arg[ 6]: -Djco.jarm=1
-> arg[ 7]: -Djava.ext.dirs=/usr/sap/PTS/SYS/j2ee/ext
-> arg[ 8]: -Dos400.define.class.cache.file=/usr/sap/PTS/SYS/j2ee/cache/QDefineClassCache.jar
-> arg[ 9]: -Dos400.define.class.cache.hours=9999
-> arg[ 10]: -Dos400.define.class.cache.maxpgms=40000
-> arg[ 11]: -Djava.compiler=jitc
-> arg[ 12]: -Dos400.run.mode=jitc
-> arg[ 13]: -Dos400.disable.explicit.gc
-> arg[ 14]: -DJava.compiler=jitc
-> arg[ 15]: -Dsys.global.dir=/usr/sap/PTS/SYS/global
-> arg[ 16]: -Dapplication.home=/sapmnt/PTS/exe
-> arg[ 17]: -Djava.class.path=/usr/sap/PTS/SYS/exe/run/jstartup.jar:/usr/sap/PTS/SYS/exe/run/jvmx.jar:./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> arg[ 18]: -Djava.library.path=/QIBM/ProdData/Java400/jdk14/PASE64/lib:/QSYS.LIB/SAPJ2EE68.LIB:/usr/sap/PTS/JC68/j2ee/os_libs:/usr/sap/PTS/SYS/exe/run
-> arg[ 19]: -Dmemory.manager=170M
-> arg[ 20]: -Xmx170M
-> arg[ 21]: -Xms170M
-> arg[ 22]: -DLoadBalanceRestricted=no
-> arg[ 23]: -Djstartup.mode=JCONTROL
-> arg[ 24]: -Djstartup.ownProcessId=89679
-> arg[ 25]: -Djstartup.ownHardwareId=I0474946350
-> arg[ 26]: -Djstartup.whoami=dispatcher
-> arg[ 27]: -Djstartup.debuggable=no
-> arg[ 28]: -DSAPINFO=PTS_68_dispatcher
-> arg[ 29]: -DSAPSTARTUP=1
-> arg[ 30]: -DSAPSYSTEM=68
-> arg[ 31]: -DSAPSYSTEMNAME=PTS
-> arg[ 32]: -DSAPMYNAME=i5sap_PTS_68
-> arg[ 33]: -DSAPDBHOST=i5sap
-> arg[ 34]: -Dj2ee.dbhost=i5sap
GC: initial heap(KB) 174080; maximum heap(KB) 174080; virtual machine identifier EE89C023D5003900; heap identifier EE89C023D5003900.
GC 1: starting collection, reason external thread attached.
[Thr 772] JHVM_LoadJavaVM: Java VM created OK.
GC 1: collection starting 01/14/08 10:19:40
Mon Jan 14 10:19:41 2008
GC 1: live objects 3156; collected objects 1663; collected(KB) 151.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 7552; current threshold(KB) 174080.
GC 1: collect (milliseconds) 48.
GC 1: current cycle allocation(KB) 2746; previous cycle allocation(KB) 4124.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 01/14/08 10:19:41
JHVM_BuildArgumentList: main method arguments of node [dispatcher]
[Thr 1800] Mon Jan 14 10:19:48 2008
[Thr 1800] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1800] Mon Jan 14 10:19:50 2008
[Thr 1800] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1800] Mon Jan 14 10:19:51 2008
[Thr 1800] JLaunchISetClusterId: set cluster id 688970800
[Thr 1800] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1800] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5912] Mon Jan 14 10:20:22 2008
[Thr 5912] JLaunchISetTelnetPort: set telnet port 56808
[Thr 5912] JLaunchISetTelnetPort: set telnet port 56808
[Thr 3085] JLaunchISetP4Port: set p4 port 56804
Mon Jan 14 10:20:24 2008
GC 2: starting collection, maximum allocation reached.
GC 2: collection starting 01/14/08 10:20:24
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
GC 3: starting collection, maximum allocation reached.
Mon Jan 14 10:20:26 2008
GC 2: live objects 89780; collected objects 743183; collected(KB) 121670.
GC 2: queued for finalization 0; total soft references 201; cleared soft references 167.
GC 2: current heap(KB) 172276; current threshold(KB) 174080.
GC 2: collect (milliseconds) 2562.
GC 2: current cycle allocation(KB) 0; previous cycle allocation(KB) 148111.
GC 2: total weak references 214; cleared weak references 0.
GC 2: total final references 1004; cleared final references 665.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 01/14/08 10:20:26
GC 3: collection starting 01/14/08 10:20:26
GC 3: collected class sun/reflect/GeneratedConstructorAccessor1556976265.
GC 3: collected class sun/reflect/GeneratedConstructorAccessor3962137197.
GC 3: collected class sun/reflect/GeneratedConstructorAccessor1177669627.
GC 3: collected class sun/reflect/GeneratedSerializationConstructorAccessor1244292024.
GC 3: collected class sun/reflect/GeneratedSerializationConstructorAccessor184784663.
GC 3: collected class sun/reflect/GeneratedSerializationConstructorAccessor3292847473.
GC 3: live objects 84631; collected objects 5769; collected(KB) 1090.
GC 3: queued for finalization 0; total soft references 147; cleared soft references 2.
GC 3: current heap(KB) 114492; current threshold(KB) 174080.
GC 3: collect (milliseconds) 118.
GC 3: current cycle allocation(KB) 184; previous cycle allocation(KB) 0.
GC 3: total weak references 214; cleared weak references 0.
GC 3: total final references 343; cleared final references 5.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 01/14/08 10:20:26
[Thr 7197] Mon Jan 14 10:20:30 2008
[Thr 7197] JLaunchISetHttpPort: set http port 56800
[Thr 7197] JLaunchISetHttpsPort: set https port 56801
[Thr 1800] Mon Jan 14 10:20:45 2008
[Thr 1800] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
[Thr 7968] Mon Jan 14 10:21:57 2008
[Thr 7968] JLaunchISetP4Port: set p4 port 56804
Mon Jan 14 10:26:56 2008
GC 4: starting collection, maximum allocation reached.
Mon Jan 14 10:26:57 2008
GC 4: collection starting 01/14/08 10:26:55
Mon Jan 14 10:27:00 2008
GC 5: starting collection, maximum allocation reached.
Mon Jan 14 10:27:11 2008
GC 5: starting collection, maximum allocation reached.
Mon Jan 14 10:27:28 2008
GC 5: starting collection, maximum allocation reached.
Mon Jan 14 10:28:02 2008
GC 4: live objects 169054; collected objects 605112; collected(KB) 103682.
GC 4: queued for finalization 0; total soft references 881; cleared soft references 672.
GC 4: current heap(KB) 156140; current threshold(KB) 174080.
GC 4: collect (milliseconds) 67438.
GC 4: current cycle allocation(KB) 0; previous cycle allocation(KB) 116215.
GC 4: total weak references 707; cleared weak references 10.
GC 4: total final references 1761; cleared final references 1297.
GC 4: total phantom references 0; cleared phantom references 0.
GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
GC 4: collection ending 01/14/08 10:28:02
GC 5: collection starting 01/14/08 10:28:02
Mon Jan 14 10:28:03 2008
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor184784663.
GC 5: collected class sun/reflect/GeneratedMethodAccessor205647375.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1244292024.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2233326064.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor4108601872.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3292847473.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1544539477.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3387531528.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor131936814.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3809350599.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2422572990.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2995163628.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3361052063.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor117167049.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3935118260.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1920751358.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2884326308.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3903475589.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3820744598.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor368371939.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor902021387.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3636210140.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3636210072.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3041006465.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2736528823.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3636210168.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2741816805.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3636210136.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3446856562.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2398015648.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1063262256.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2530410954.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1086686180.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3338641192.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3620979168.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3050581282.
GC 5: collected class sun/reflect/GeneratedMethodAccessor189613539.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3475231319.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2151649844.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2808103358.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1167563472.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3161606295.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor680125725.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2770695927.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2422904334.
GC 5: collected class sun/reflect/GeneratedMethodAccessor393929431.
GC 5: collected class sun/reflect/GeneratedMethodAccessor412390813.
GC 5: collected class sun/reflect/GeneratedMethodAccessor4096661987.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3776713049.
GC 5: collected class sun/reflect/GeneratedMethodAccessor223093694.
GC 5: collected class sun/reflect/GeneratedMethodAccessor289937368.
GC 5: collected class sun/reflect/GeneratedMethodAccessor338446302.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3344517667.
GC 5: collected class sun/reflect/GeneratedMethodAccessor801255704.
GC 5: collected class sun/reflect/GeneratedMethodAccessor420113167.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2423092304.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3448629810.
GC 5: collected class sun/reflect/GeneratedMethodAccessor1976375617.
GC 5: collected class sun/reflect/GeneratedMethodAccessor158587486.
GC 5: collected class sun/reflect/GeneratedMethodAccessor1968915243.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2013173116.
GC 5: collected class sun/reflect/GeneratedMethodAccessor4042187173.
GC 5: collected class sun/reflect/GeneratedMethodAccessor4278228719.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2568173837.
GC 5: collected class sun/reflect/GeneratedMethodAccessor109580843.
GC 5: collected class sun/reflect/GeneratedMethodAccessor3940032716.
GC 5: collected class sun/reflect/GeneratedMethodAccessor4141618346.
GC 5: collected class sun/reflect/GeneratedMethodAccessor4271794301.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2012837666.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1833286043.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor731134905.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1216142229.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3699758718.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor408587165.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor601167037.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1862445261.
GC 5: collected class sun/reflect/GeneratedMethodAccessor820799576.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3873503268.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3575031965.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2979620887.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor4141966511.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1590156282.
GC 5: collected class sun/reflect/GeneratedMethodAccessor2361792333.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2937976439.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3454952673.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1348639602.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3508746310.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2374073616.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2221421956.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor126856405.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3137909645.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3110555419.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2906609244.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor353113607.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2053956510.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2083770132.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3608654748.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor4190943787.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor431358104.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3576950217.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2870426855.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor1330366674.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor4055478671.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor2206527574.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor4046903410.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor3605206134.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor4068021687.
GC 5: collected class sun/reflect/GeneratedSerializationConstructorAccessor416404708.
GC 5: live objects 158510; collected objects 11087; collected(KB) 2034.
GC 5: queued for finalization 0; total soft references 772; cleared soft references 36.
GC 5: current heap(KB) 137272; current threshold(KB) 174080.
GC 5: collect (milliseconds) 371.
GC 5: current cycle allocation(KB) 0; previous cycle allocation(KB) 0.
GC 5: total weak references 707; cleared weak references 0.
GC 5: total final references 467; cleared final references 5.
GC 5: total phantom references 0; cleared phantom references 0.
GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
GC 5: collection ending 01/14/08 10:28:03
[Thr 5912] Mon Jan 14 10:38:56 2008
[Thr 5912] JLaunchISetHttpPort: set http port 56800
[Thr 7711] JLaunchISetHttpPort: set http port 56800
[Thr 6169] JLaunchISetP4Port: set p4 port 56804
[Thr 5912] JLaunchISetHttpsPort: set https port 56801
[Thr 7711] JLaunchISetHttpsPort: set https port 56801
[Thr 8739] Mon Jan 14 10:50:56 2008
[Thr 8739] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
[Thr 8739] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
[Thr 5141] Mon Jan 14 10:51:05 2008
[Thr 5141] JLaunchISetP4Port: set p4 port 56804
[Thr 5141] Mon Jan 14 10:51:08 2008
[Thr 5141] JLaunchISetHttpsPort: set https port 56801
[Thr 5141] JLaunchISetHttpPort: set http port 56800
[Thr 5141] Mon Jan 14 10:51:20 2008
[Thr 5141] JLaunchISetTelnetPort: set telnet port 56808
[Thr 5141] Mon Jan 14 10:51:21 2008
[Thr 5141] JLaunchISetHttpPort: set http port 56800
[Thr 8739] Mon Jan 14 10:51:27 2008
[Thr 8739] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
[Thr 8739] Mon Jan 14 10:51:28 2008
[Thr 8739] JLaunchIExitJava: exit hook is called (rc = -11111)
[Thr 8739] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 8739] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 8739] JLaunchCloseProgram: good bye (exitcode = -11111)
std_dispatcher.out
stdout/stderr redirect
node name : dispatcher
pid : 89653
system name : PTS
system nr. : 68
started at : Mon Jan 14 10:19:38 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 174080; maximum heap(KB) 174080; virtual machine identifier EE89C023D5003900; heap identifier EE89C023D5003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 01/14/08 10:19:40
GC 1: live objects 3156; collected objects 1663; collected(KB) 151.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 7552; current threshold(KB) 174080.
GC 1: collect (milliseconds) 48.
GC 1: current cycle allocation(KB) 2746; previous cycle allocation(KB) 4124.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 01/14/08 10:19:41
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 3699 ms.
Loading: PoolManager ... 17 ms.
Loading: ThreadManager ... 238 ms.
Loading: IpVerificationManager ... 19 ms.
Loading: ConnectionsManipulator ... 417 ms.
Loading: ClassLoaderManager ... 72 ms.
Loading: ClusterManager ... 1228 ms.
Loading: PortsManager ... 261 ms.
Loading: LockingManager ... 1900 ms.
Loading: ConfigurationManager ... 17131 ms.
Loading: LicensingManager ... 227 ms.
Loading: CacheManager ... 1811 ms.
Loading: ServiceManager ...
Loading services.:
Service security started. (256 ms).
Service httptunneling started. (528 ms).
Service licensing started. (565 ms).
Service sld started. (606 ms).
Service jmx_notification started. (573 ms).
Service timeout started. (920 ms).
Service memory started. (937 ms).
Service webservices started. (780 ms).
Service keystore started. (806 ms).
Service shell started. (1636 ms).
Service iiop started. (1549 ms).
S
Similar Messages
-
Problem in Starting the J2EE Server
Hi All,
I am getting the following error message when I start the Server.
[Thr 3820] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642]
[Thr 3820] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
[Thr 3820] JControlCloseProgram: started (exitcode = 66)
[Thr 3820] JControlCloseProgram: good bye... (exitcode = 66)
Expecting any clue to resolve this issue.
Reg/VenkatHi,
This error might be due to the memory heap size. To resolve this:
Stop ur server.
1)Go to My Computer>properties>Advanced.
2)In the performance tab>settings>performance options-->Advanced -->change
3)Change the heap size of the memory to the local drives.
Initial size (1524) and Max size(3048).
<u><b>Alternate Solution</b></u>
Go to services.msc and start all the oracle instances. (Manual Start)
Restart the cluster. The server will start to run.
Hope it helps,
Regards,
Nagarajan. -
Problem with deploying : SDM could not start the J2EE cluster on the host .
Hello, All
I have following problem with deploying the aplication I get this messenger:
16/09/2008 07:59:44 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : 192.168.0.14
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Result
=> deployment aborted : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Aborted: development component 'ZChangeRequestDatabase'/'local'/'LOKAL'/'0.2008.05.03.04.24.17'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated. There is no cluster control instance running on host Jupiter which is described in SecureStorage . The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :|Name:JM_T1221612526745_0_penitus15 |Host:PENITUS15 |State:5|HostAddress:192.168.0.205||Name:JM_T1221612357814_0_Jupiter |Host:pfs |State:5|HostAddress:192.168.0.14||Name:JC_Jupiter_JTP_00 |Host:pfs |State:5|HostAddress:192.168.0.14|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
I dont'n know How do I solver this error?
- I reviewed the virtual memory and I increase the virtual memory
- I restarted the server and the system
- I reviwed the parameter in the config tool --> cluster --> security storage it is OK
Any suggestion for solver this problem
Thanks
Regards
DSI found this messenger in Additional log information., Please si
17/09/2008 03:04:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\JTP\JC00\SDM\program\log\sdmcl20080917200328.log]/>
<!PATTERN[sdmcl20080917200328.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Sep 17, 2008 1:04:40 PM Info: -
Starting deployment -
Sep 17, 2008 1:04:40 PM Info: Error handling strategy: OnErrorStop
Sep 17, 2008 1:04:40 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Sep 17, 2008 1:04:40 PM Info: Update strategy: UpdateAllVersions
Sep 17, 2008 1:04:40 PM Info: Starting deployment prerequisites:
Sep 17, 2008 1:04:40 PM Info: Loading selected archives...
Sep 17, 2008 1:04:40 PM Info: Loading archive 'C:\usr\sap\JTP\JC00\SDM\program\temp\temp62604ZIssueDatabase.ear'
Sep 17, 2008 1:04:41 PM Info: Selected archives successfully loaded.
Sep 17, 2008 1:04:41 PM Info: Actions per selected component:
Sep 17, 2008 1:04:41 PM Info: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:41 PM Info: Ending deployment prerequisites. All items are correct.
Sep 17, 2008 1:04:43 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Saved current Engine state.
Sep 17, 2008 1:04:45 PM Info: Starting: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:45 PM Info: SDA to be deployed: C:\usr\sap\JTP\JC00\SDM\root\origin\local\ZIssueDatabase\LOKAL\0\0.2008.04.17.10.53.03\temp62604ZIssueDatabase.ear
Sep 17, 2008 1:04:45 PM Info: Software type of SDA: J2EE
Sep 17, 2008 1:04:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Starting cluster instance processes.
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: An error occured while starting a cluster instance.
Sep 17, 2008 1:04:45 PM Error: There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
Sep 17, 2008 1:04:45 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Aborted: development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated.
There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Sep 17, 2008 1:04:45 PM Info: Starting to save the repository
Sep 17, 2008 1:04:46 PM Info: Finished saving the repository
Sep 17, 2008 1:04:47 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 17, 2008 1:04:47 PM Error: -
At least one of the Deployments failed -
Any help will be well received about this problema
Thk
Regards
DS -
i am trying to download video that i purchased from itunes, but everytime i want to resume the process after pausing it, it automatically start the whole downloading process again, how can i eliminate this problem?
They don't normally appear in the download screen ... until I attempt to download another movie. Then they just start appearing. If you click edit - a normal movie download has a circle that appears on the left hand side that allows you to select and delete ... these movies don't have that option so you need to find the movie in you list (under movies) and select the download cloud symbol again to stop it downloading ...you may need to do this a number of times before it stops for a while ... or until you try to download a movie then it starts all over again.
i have logged out of my itunes account. restarted the iPad, removed all movies, restarted the iPad, logged back into my iTunes account and restarted my iPad .... but as soon as I tried to download a single movies ... the other movies started appearing in the downloads again. -
Initial Setup Problem - Starting the SLD Registration process
Hi,
we are installing our PI development system. During initial configuration with "NWA --> Configuration Management --> Scenarios --> Configuration Wizard --> Netweaver initial setup" the wizard stands still at Step 68 (of 561) "Starting the SLD Registration process".
We have restarted the system but after starting again the wizard it stands still again.
Same problem on our PI quality assurance system.
PI 7.11 on Windows 2008 R2 with MSSQL 2008 R2.
Steps of installation:
1) Installation of PI 7.11
2) Postworks ABAP (License, TMS, Profiles, rz04, ...)
3) Kernelupdate to 106
4) Updates SPS7 ABAP
5) Updates SPS7 JAVA
6) Run NWA Initial Setup with J2EE_ADMIN
Could someone help?
Thanks
Regards
Thomas MühlThen possibly the password was set wrong somewhere (since the "-" character is not blocked). Its advisable to check all service users passwords, to prevent other issues like this one to occur. Please check the OSS note "999962 - PI 7.10: Change passwords of PI service users" for more information on this.
-
Having trouble starting the J2EE Server... for hours and hours...
Hi:
I am having problem starting the J2EE Server.
I have looked through this page where lots of people had similar problem:
http://forum.java.sun.com/thread.jsp?forum=136&thread=468079
but the solutions provided there could not solve my problem...
My problem, specifically, is that when I try to start the sever, I get:
com.sun.enterprise.admin.servermgmt.DomainException: ...
CLI156 Could not start the domain domain1.
I am using Windows XP Professional on IBM ThinkPad X30.
Does anyone have some idea how to solve the problem?
Thanx!bsankararao,
Thanks for the quick response. I am currently using the latest IE6.0 XPXP2 version and yes I doe have a successful start of the domain1 process. Here is the startup log for verification:
[#|2004-02-02T15:03:04.765-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-02T15:03:12.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-02T15:03:12.436-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-02T15:03:14.649-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-02T15:03:15.470-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-02T15:03:15.491-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-02T15:03:15.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-02T15:03:32.084-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-02T15:03:34.338-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-02T15:03:34.938-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-02T15:03:36.391-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-02T15:03:36.421-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|autoDeployment status dir missing, creating a new one|#]
[#|2004-02-02T15:03:36.451-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.471-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.481-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:38.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:38.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
[#|2004-02-02T15:03:48.818-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:49.549-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12728 msec, Total EJB Compiler Module Time: 10775 msec, Portion spent EJB Compiling: 84%
Breakdown of EJBC Module Time: Total Time for EJBC: 10775 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10605 msec (98%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2004-02-02T15:03:49.750-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-02-02T15:03:50.571-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:51.292-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.029-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.309-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5688 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 83%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 2674 msec (56%), Java Compilation: 1933 msec (40%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-02-02T15:03:56.339-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-02-02T15:03:56.810-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-02T15:03:57.210-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-02T15:03:57.461-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-02T15:03:57.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-02T15:03:57.721-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-02T15:03:59.924-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-02T15:04:00.315-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.355-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.936-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.946-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.966-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:00.986-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:01.266-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075755841276|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-02T15:18:13.512-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T15:18:13.522-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T15:18:39.119-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T15:18:39.119-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:27:40.443-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:41.174-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:27:49.076-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:49.076-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:31:57.022-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:31:57.022-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:32:08.869-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:32:08.869-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T20:00:22.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T20:00:22.424-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-03T08:30:22.556-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T08:30:23.808-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T08:30:23.998-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T08:30:26.422-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T08:30:27.143-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T08:30:27.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T08:30:27.253-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T08:30:31.509-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T08:30:33.462-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T08:30:33.963-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T08:30:34.914-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T08:30:36.036-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T08:30:37.027-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T08:30:37.428-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T08:30:37.618-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T08:30:37.638-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T08:30:37.798-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T08:30:39.901-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T08:30:40.202-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.242-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.402-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.412-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.442-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.452-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.732-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075818640752|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T08:48:32.383-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\domains\domain1\autodeploy\hello.war ] for autodeployment.|#]
[#|2004-02-03T08:48:33.785-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello]|#]
[#|2004-02-03T08:48:33.835-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello]|#]
[#|2004-02-03T08:48:34.606-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1862 msec, Total EJB Compiler Module Time: 50 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 50 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (20%),
|#]
[#|2004-02-03T08:48:34.807-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello]|#]
[#|2004-02-03T08:48:35.007-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T08:48:36.719-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-03T08:48:36.729-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\domains\domain1\autodeploy\hello.war.|#]
[#|2004-02-03T14:53:47.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T14:53:48.718-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T14:53:48.929-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T14:53:51.222-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T14:53:52.003-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T14:53:52.033-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T14:53:52.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T14:53:56.449-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T14:53:58.492-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T14:53:58.983-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T14:53:59.985-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T14:54:01.206-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T14:54:02.188-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T14:54:02.678-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T14:54:02.899-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T14:54:02.919-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T14:54:02.939-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T14:54:03.119-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T14:54:05.563-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T14:54:05.883-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:05.943-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:06.083-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.093-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.123-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.133-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075841646434|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T23:32:20.272-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T23:32:22.004-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T23:32:22.234-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T23:32:24.608-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T23:32:25.629-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T23:32:25.659-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T23:32:25.689-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T23:32:31.237-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T23:32:33.781-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T23:32:34.332-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T23:32:35.453-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T23:32:37.156-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T23:32:38.317-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T23:32:38.948-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T23:32:39.179-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T23:32:39.199-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T23:32:39.229-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T23:32:39.439-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T23:32:42.343-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T23:32:42.724-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.764-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.944-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.954-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.994-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.014-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.315-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075872763335|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-04T08:31:44.681-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02 -
Deployment SDM could not start the J2EE Cluster on the host nw4host
Hello,
I installed the WAS testdrive on Linux SUSE 9.3 and the SNDS on WinXP.
I am trying to deploy the welcome application from the SNDS and get the following error message:
SDM could not start the J2ee Cluster on the host nw4host! The online deployment is terminated. JStartup Framework ist not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine.
I can start the J2EE Start page on port 50000, the system info shows that dispatcher, server0 and SDM are running. I can start the visual admin with go, the SDM with RemoteGui and the DeployTool.
The comand startsap check nw4host shows, everythings running:
nw4host:nw4adm 54> startsap check nw4host
Checking ADA db Database
ABAP Database is running
Checking ADA db Database
J2EE Database is running
See logfile JdbcCon.log
Checking SAP NW4 Instance SCS01
Instance SCS01 is running
Checking SAP NW4 Instance DVEBMGS00
Instance DVEBMGS00 is running
Logging in to SAP with the Java Gui, the ICM says:
ABAP Server operational = TRUE
J2EE Server configured = FALSE
J2EE HTTP port = 50000
J2EE HTTPS port = 50001
J2EE Server operational = TRUE
Default root access handler = ABAP
URL Prefix Table loaded = TRUE
Any idea where the problem could be ?
Thanks, Manfred.changed the ip address for nw4host in etc/hosts to the real ip address of the server where application runs
-
SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host
HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
IHi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet -
Error starting the gateway work process (gwwp)
Hi Gurus,
I have an error in my system when I review the tx sm21, shows me a constant error that says:
Error starting the gateway work process (gwwp)
fork failed, error 002
> \ Gwwp.EXE
This happens after making a copy of the constituents scc9 tx.
Thanks and regards
Tao Gonz.Hi,
Check below SAP notes & thread link.
604437 GW: Checking of started Gateway work processes 1
116051 Checklist: Problems SNA gateways (R/3 ==> R/2)
71251 Gateway : Versions of dplib are different
92104 Gateway does not work after restart
gateway not starting automatically
Hope this helps you.
Thanks,
Sushil -
SDM could not start the J2EE cluster on the host Error on Deployments
Hi,
We are sudenly getting this Error when trying to make a Deployment in the NWDE:
Settings
SDM host : 10.26.26.198
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
Aborted: development component 'WDWFApp'/'local'/'LOKAL'/'0.2007.02.16.15.11.28'/'0':SDM could not start the J2EE cluster on the host vmxtbcsapep01! The online deployment is terminated. There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage . The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :|Name:JM_T1171660289517_0_ALMACARVAJAL |Host:miriamdragustinovis |State:5|HostAddress:10.21.69.164||Name:JM_T1171656308064_0_vmxtbcsapep01 |Host:cvespinosa |State:5|HostAddress:10.26.26.198||Name:JC_vmxtbcsapep01_CPQ_00 |Host:cvespinosa |State:5|HostAddress:10.26.26.198|Please check if there is an appropriate running cluster instances. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
And in the sdm log file we got this kind of errors:
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[miriamdragustinovis] Throwable: java.net.UnknownHostException Throwable message: miriamdragustinovis
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
Feb 16, 2007 2:13:46 PM Error: An error occured while starting a cluster instance.
Feb 16, 2007 2:13:46 PM Error: There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :
Name:JM_T1171656916610_0_ALMACARVAJAL
Host:miriamdragustinovis
State:5
HostAddress:10.21.69.164
Name:JM_T1171656308064_0_vmxtbcsapep01
Host:cvespinosa
State:5
HostAddress:10.26.26.198
Name:JC_vmxtbcsapep01_CPQ_00
Host:cvespinosa
State:5
HostAddress:10.26.26.198
Any Idea what can be wrong? we have even restarted de AIX Server and starting all the services and it is still not working.
Thanx in Advanced!
Gerardo JHi Gerardo,
I encountered exactly the same error, but had a different solution as I was expecting from the error-message.
In my case I was forced by the Visual Administrator to change the administration password, since the time was up on it. But as the password for the Visual Administrator is saved within the database, the password for the SDM is stored within the secure store (file-system) and changing the password just in VA will not automatically change it also in the secure store. But since both passwords for the internal usage need to be equalized, I encountered problems afterwards when trying to deploy something and I got the same error message. However the sense of restriction is meant here, the solution on it was rather simple as follows (Just note that you need to enter a dummy-password first, before setting the correct one similar to your visual administrator):
1. create a telnet session to your J2EE using a command line shell
2. enter "jump 0" to get on the correct node within your J2EE
3. enter "add user" to gain access to user-specific commands
4. enter "password <Administrator> <temporarily new password>"
5. exit
6. create another telnet session to your J2EE using a command line shell
7. after succeeded the login, you will now be forced to enter a new password - so enter "password <Administrator> <origin password of the Visual Administrator>"
8. exit
9. now start the config-tool of the engine
10. apply to the DB-default-question with "yes"
11. select the Secure Store on the left
12. select the entry "admin/password/..." that you can see it in the bottom lines.
13. click "Remove" to delete it from the list
14. set the password similar to the Visual Administrator password within the "Value" line (take care as you can not see the digits).
15. click "Add" to add it back to the list
16. click the disc symbol in the top of the UI to save the new password (if you don't get a dialog afterwards that the data has been stored, something may hasn't worked fine when removing/adding the password-entry, in this case repeat the action on it).
17. After exiting the config-tool, you need to restart the entire J2EE.
18. Your hopefully finished by success ;o))
Best regards
Jochen -
Hi:
I am new to J2EE and I followed the instruction on the J2EE Tutorial setting up the J2EE SDK. When I tried to start the J2EE server by typing in "C:\j2ee -verbose", the server can't seem to start... After it gets to "Starting JMS service..." , it jumps back to the command prompt "C:\>"
If I then try to do a "j2ee -stop", I get an error "javax.naming.CommunicationException: Can't find SerialContextProvider" (which, I think, indicates the server never got started)
I am using Windows 2000 and I am pretty sure I have the environment variables set properly. Does anyone know why this is happening? Thanx!
The following is the trace of me doing "j2ee -verbose"
J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@b301f2
Starting JMS service...
C:\j2sdkee1.3.1\bin>
EugeneI have read some posts and get the answer
change the pc language to English
and reinstall j2ee
all should be ok!
I get message "J2EE server startup complete" now.
luck! -
Trying to start the j2ee to be the JMS provider but why error
Anyone knows why I can't start the j2ee ..which I hope to use it as the JMS provider. I am trying to try the e.g. from JMS tutorial....
But it seems that I can't start the j2ee in the first place 'cos error say that I have another instance running...(but I didn't start anything in the first place). How should I solve this?
How could I stop the j2ee server....I tried the command
j2ee -stop but cannot..
Anyone can help?
AG
G:\jmseg\simple>j2ee -verbose
J2EE server listen port: 1050
java.lang.RuntimeException: Could not initialize j2ee server. Possible cause cou
ld be another instance of the server already running.
at com.sun.enterprise.iiop.POAProtocolMgr.initializeNaming(POAProtocolMg
r.java:134)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:227)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:918)
java.lang.RuntimeException: Could not initialize j2ee server. Possible cause cou
ld be another instance of the server already running.
at com.sun.enterprise.iiop.POAProtocolMgr.initializeNaming(POAProtocolMg
r.java:134)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:227)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:918)
java.lang.RuntimeException: Could not initialize j2ee server. Possible cause cou
ld be another instance of the server already running.
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:355)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:918)
J2EE server reported the following error: Could not initialize j2ee server. Poss
ible cause could be another instance of the server already running.
Error executing J2EE server ...
G:\jmseg\simple>I got exactly the same message when I tried to start j2ee server... It worked fine the second time round though, So I suggest you try it again.
tim.. -
Hi,
We have EP7 SP11 installed on a Win2003 x86 64bit Server. After the windows server reboot the J2EE engine is not started automatically, we have to go to startup framework enter the authentication details and then the J2EE starts.
Is there anyway by which i can automatically start the J2EE engine after the windows server reboot ?
Thanks!!Hi Kiran
You need to set the value of the Autostart parameter to '1' in both the profiles START_<InstanceID>_<host> and
START_<Central instanceID>_<host>
under \usr\sap\<SID>\SYS\profile directory.
After this the J2EE Engine should start automatically when the OS boots.
Cheers.
Please award points for helpful answers. -
PSE 8 problems to start the program
Hello!
Just download the PSE8 today and I can´t get it launched? The edit-program start but the organixer doesn´t. Either I can´t launched the share-programs or the program to make albums.
Someone out there who can help me?
SE-MJAHello!
I got the same result.
The program can´t launch the "read in workspace for Elements Oganizer". It´s try to launch but be freeze and then nothing happens.
It´s bad because I think the program was good. Now I think I will reclaime the produvt and get my money back.
Regards!
Micke
Date: Wed, 7 Apr 2010 04:22:09 -0600
From: [email protected]
To: [email protected]
Subject: PSE 8 problems to start the program
Have you located the program file to ensure it is properly installed?.
If not, click on the start button and type PhotoshopElementsEditor.exe (note caps and no spaces) into the search box.
The program, if available, should appear with a blue PSE icon in the search results.
Right click on it and select send to desktop.
Then try to open the editor from the desktop by clicking on the icon.
> -
ORA-12500 Tns listner failed to start the dedicated server process.
Hi all,
I am getting below error message when i am trying to connect to database through db console.
OS-Windows sever
Database-10GR1
ORA-12500 Tns listner failed to start the dedicated server process.
Kindly help me out..
Thanks in advance
Edited by: rajaryan on Sep 17, 2009 4:46 AMHi all,
I am getting below error message when i am trying to connect to database through db console.
OS-Windows sever
Database-10GR1
ORA-12500 Tns listner failed to start the dedicated server process.
Kindly help me out..
Thanks in advance
Edited by: rajaryan on Sep 17, 2009 4:46 AMYou are running short of resources. Check v$resource_limit. You may also use the orastack utility for minimizing the memory utilized by oracle.
http://hrivera99.blogspot.com/2008/01/orastack.html
Regards,
S.K.
Maybe you are looking for
-
After VO substitution, the "Imported document" doesn't start with "/oracle"
Hello Everyone, I recently tried a VO substitution and while performing the import command in command prompt, the see the following: C:\>C:\p9879989_R12_GENERIC\jdevbin\oaext\bin\JPXIMPORT C:\p9879989_R12_GENERIC\jdevhome\jdev\myclasses\psu.jpx -user
-
What is a pre query and in what circumstances it is used?
Please explain what is a pre query in BW mean,and when is it used...thank you for your answers...
-
Unable to install XL Reporter Add-On
Hi, Getting error message "Application has generated an exception that could not be handled" after giving password for sa user while installation. After clicking on ok it showing like error preparing in meta data repository. can any one help me out i
-
Local bin directory in solaris 10
Hi Which is the local bin directory in solaris 10 /bin or /usr/bin? or else? Ashraf
-
Is it possible to format the appearance of JList components?
Hi! I've looked through the tutorial and browsed through previous messages, but I can't seem to find an answer to my question. Any help would be GREATLY appreciated. The situation: I have a JList in which I want to display a list of objects. I use a