J2EE engine does not start correctly

hi,
after the installation of sap was v6.40 abap & j2ee, i cannot logon to the j2ee engine as described in the documentation. when i will access the engine by using a web browser, i get the following error message:
"503: Service Unavailable"
i had a look on the log files and found these messages in the server log file:
java.rmi.RemoteException: Error occurred while starting applications; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container EJBContainer is not active at the moment and it is not possible to startApp sap.com/com.sap.lcrabapapi.
at ...
there are more lines with error messages which seems to belong to the original problem with the ejbcontainer.
can anyone tell me how to fix the errors?
thanks in advance,
michael keller

Hi,
See note: 535532
Mid way through the note it says:
You can then register the SAP J2EE Engine as a windows-service by using the SAP J2EE Engine Config Tool. Open a command prompt and change to the directory <J2EE Engine installation directory>configtool and run configtool.bat or start this tool via your Start-Menu "Tools->Config Tool" of the J2EE Server entry. Select at the left navigation area of this tool the entry "cluster/ server" the checkbox "Enabled" at the tabstrip "NT Service". Apply these settings by clicking on "File->Apply" at the menu. Do the same with the entry "cluster / dispatcher".
After you have finished these steps you can register now the J2EE Engine as a windows service.
Start service.exe, which is also located in the directory
<J2EE Engine installation directory>configtool. It works with three
parameters:
Service.exe u2013install u2013 the service(s) is (are) registered as NT/2000 Service(s). For each specified cluster node, a separate service is generated. All services have startup mode automatic. To start the service(s), open the Control Panel ¨Services folder. Find the service in the list of available services (for example: SAP J2EE Server 1, SAP J2EE Dispatcher 1, SAP J2EE Server 2, and so on). Select it, and choose u201CStartu201D on the right-hand side. No u201CStartup Parametersu201D are needed for the service to run. The system starts the particular J2EE Engine 6.20 node in background mode. It can be used and administered as usual. The only difference is that the server does not run in a console window.
There may be other notes along these lines.
You should also check any notes on the setup of SAP in MSCS cluster, as it will contain instructions for registering the services.
Hope this gives you a pointer in the right direction.

Similar Messages

J2EE Engine does not start

Hi All.
I installed a Dialog instance.
After the installation of the license key on the central instance, the dialog J2EE Engine does not start anymore.
Here it is the std_server0.out log:
stdout/stderr redirect
node name : server0
pid : 1298548
system name : PRP
system nr. : 10
started at : Mon Sep 3 19:07:54 2007
[Thr 1] Mon Sep 3 19:07:55 2007
[Thr 1] MtxInit: -2 0 0
JVMST080: verbosegc is enabled
JVMST082: -verbose:gc output will be written to stderr
^MSAP J2EE Engine Version 7.00 PatchLevel is starting...
^M
Loading: LogManager ... 1887 ms.
Loading: PoolManager ... 3 ms.
Loading: ApplicationThreadManager ... 452 ms.
Loading: ThreadManager ... 428 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 392 ms.
Loading: LockingManager ... 140 ms.
Loading: ConfigurationManager ... 4656 ms.
Loading: LicensingManager ... 28 ms.
Loading: CacheManager ... 311 ms.
Loading: ServiceManager ...
<AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>
<AF[1]: managing allocation failure, action=0 (959472304/1073740288)>
<GC(1): GC cycle started Mon Sep 3 19:08:13 2007
<GC(1): freed 64170704 bytes, 95% free (1023643008/1073740288), in 136 ms>
<GC(1): mark: 123 ms, sweep: 13 ms, compact: 0 ms>
<GC(1): refs: soft 0 (age >= 32), weak 0, final 475, phantom 0>
<AF[1]: completed in 159 ms>
Loading services.:
Service cross started. (72 ms).
Service file started. (156 ms).
Service memory started. (160 ms).
Service userstore started. (24 ms).
Service timeout started. (51 ms).
Service runtimeinfo started. (8 ms).
Service trex.service started. (90 ms).
Service jmx_notification started. (77 ms).
Service p4 started. (182 ms).
Service classpath_resolver started. (99 ms).
Service deploy started. (9491 ms).
Service MigrationService started. (28 ms).
Service bimmrdeployer started. (6 ms).
Service log_configurator started. (21621 ms).
Service locking started. (3 ms).
Service http started. (772 ms).
Service naming started. (1518 ms).
Service failover started. (23 ms).
Service appclient started. (29 ms).
Service javamail started. (87 ms).
Service ts started. (70 ms).
Service jmsconnector started. (80 ms).
Service licensing started. (10 ms).
Service iiop started. (141 ms).
Service connector started. (119 ms).
Service configuration started. (31 ms).
Service webservices started. (463 ms).
Service dbpool started. (8765 ms).
Sep 3, 2007 6:08:47 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME
persistence adapter "PRIVATE_DATASOURCE" failed.
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
 ume.db.connection_pool_type=SAP/BC_UME
 ume.db.connection_pool.j2ee.xatransactions_used=false
 ume.db.connection_pool.j2ee.is_unicode=FALSE
 ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
 at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
 ... 6 more
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
 ume.db.connection_pool_type=SAP/BC_UME
 ume.db.connection_pool.j2ee.xatransactions_used=false
 ume.db.connection_pool.j2ee.is_unicode=FALSE
 ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
 at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
 ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 3, 2007 6:08:47 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was
invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Anyone can help?
Thanks,
Marco

Hi all,
after some corrections, now the problem is changed.
Here you can find the std_server0.out:
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=SAPPRP-DB SYSNR=10 GWHOST=SAPPRP-DB GWSERV=sapgw10 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'SAPPRP-DB:sapgw10' not reached
TIME Fri Sep 7 15:01:11 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 79
ERRNO TEXT A remote host refused an attempted connect operation.
COUNTER 1
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
 ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 7, 2007 2:01:11 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_55] Fatal: Critical shutdown was
invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Thanks all,
Marco

J2ee engine does not start up after system copy

Dear All,
I have done a system copy of BW3.5 (NW04). I installed the BW.3.5 and then replaced the data and control files.
This has ABAP + java.
Now after system copy when i am starting the server, the J2ee instance doesnt start up.
ABAP is running and DB is up too.
I am getting the following error in log_bootstrap file:-
Exception occured:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
 at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
 at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
 at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
==[ Caused by: ]==----
com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID1125100) in the database! Check
database consistency or local Bootstrap properties!
 at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:81)
 at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
 at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
 at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
[Aug 26, 2008 2:00:26 PM ] [Bootstrap module]> Problem occured while performing synchronization.
[Aug 26, 2008 2:00:42 PM ] -
[Aug 26, 2008 2:00:42 PM ] Bootstrap MODE:
[Aug 26, 2008 2:00:42 PM ] <INSTANCE GLOBALS>
[Aug 26, 2008 2:00:42 PM ] determined by parameter [ID0011251].
[Aug 26, 2008 2:00:42 PM ] -
[Aug 26, 2008 2:00:46 PM ] Exception occured:
com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/di
spatcher/ID1125100" does not exist.
 at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(Configura
tionDataCacheAllImpl.java:107)
 at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfi
guration.java:715)
 at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:365)
 at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:78)
 at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
 at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
 at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
What could the problem?. Do I need to do some other settings for system copy of JVA instance?
Kindly help
Thanks
Tajinder

Hi,
I already checked that note. It did not help.
I am pasting mine dev_jcontrol file:--
trc file: "/usr/sap/BD1/DVEBMGS00/work/dev_jcontrol", trc level: 1, release: "640"
node name : jcontrol
pid : 868524
system name : BD1
system nr. : 00
started at : Tue Aug 26 16:27:10 2008
arguments :
 arg[00] : jcontrol
 arg[01] : pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
 arg[02] : -DSAPSTART=1
 arg[03] : -DCONNECT_PORT=64380
 arg[04] : -DLISTEN_PORT=64381
 arg[05] : -DSAPSYSTEM=00
 arg[06] : -DSAPSYSTEMNAME=BD1
 arg[07] : -DSAPMYNAME=BWQAS_BD1_00
 arg[08] : -DSAPPROFILE=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
 arg[09] : -DFRFC_FALLBACK=ON
 arg[10] : -DFRFC_FALLBACK_HOST=localhost
JStartupReadInstanceProperties: read instance properties [/usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.proper
ties:/usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties]
-> ms host : BWQAS
-> ms port : 3601
-> OS libs : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
-> files [01] : /usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties
Instance properties
-> ms host : BWQAS
-> ms port : 3601
-> os libs : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
-> [01] bootstrap_ID1125100 : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
-> [02] bootstrap_ID1125150 : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID1125100 : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
-> [01] ID1125150 : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
-> [02] sdm : /usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties
[Thr 01] Tue Aug 26 16:27:10 2008
[Thr 01] SigISetDefaultAction : default handling for signal 20
[Thr 01] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 258] JControlDPMessageFunc: Thread 258 started as handler thread for R/3 dispatcher messages.
[Thr 01] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) -
using -Xmx512m [jstartxx_mt. 2282]
[Thr 01] [Node: bootstrap] java home is set by profile parameter
 Java Home: /usr/java14_64
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> java path : /usr/java14_64
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20060421 (SR5) (JIT enabl
ed: jitc)
-> java vm vendor : Classic VM (IBM Corporation)
-> java vm type : <default>
-> java vm cpu : ppc64
-> heap size : 512M
-> root path : /usr/sap/BD1/DVEBMGS00/j2ee/cluster
-> class path : ./bootstrap/launcher.jar
-> OS libs path : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jstartup.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0011251
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jlaunch
-> arg[00] = /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jlaunch
-> arg[01] = pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
-> arg[02] = -DSAPINFO=BD1_00_bootstrap
-> arg[03] = -file=/usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
-> arg[04] = -nodeName=bootstrap
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=12582961
-> arg[07] = -jvmOutFile=/usr/sap/BD1/DVEBMGS00/work/jvm_bootstrap.out
-> arg[08] = -stdOutFile=/usr/sap/BD1/DVEBMGS00/work/std_bootstrap.out
-> arg[09] = -locOutFile=/usr/sap/BD1/DVEBMGS00/work/dev_bootstrap
-> arg[08] = -stdOutFile=/usr/sap/BD1/DVEBMGS00/work/std_bootstrap.out
-> arg[09] = -locOutFile=/usr/sap/BD1/DVEBMGS00/work/dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=64382
-> arg[14] = -DLISTEN_PORT=64381
-> arg[15] = -DSAPSYSTEM=00
-> arg[16] = -DSAPSYSTEMNAME=BD1
-> arg[17] = -DSAPMYNAME=BWQAS_BD1_00
-> arg[18] = -DSAPPROFILE=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
-> arg[19] = -DFRFC_FALLBACK=ON
-> arg[20] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = LIBPATH=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/B
D1/DVEBMGS00/j2ee/os_libs:/usr/sap/BD1/SYS/exe/run:/usr/sap/BD1/SYS/exe/runU:/usr/lib:/usr/sap/BD1/DVEBMGS00/
j2ee/os_libs:/usr/sap/BD1/DVEBMGS00/j2ee/os_libs:/usr/lib:/lib:/usr/sap/BD1/SYS/exe/run:/usr/sap/BD1/SYS/exe/
runU
-> exe path = PATH=/usr/java14_64/bin:/usr/sap/BD1/DVEBMGS00/j2ee/os_libs:/oracle/BD1/920_64/bin:/usr/java14_
64/bin:/home/bd1adm:/usr/sap/BD1/SYS/exe/runU:/usr/sap/BD1/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home
/bd1adm/bin:/usr/bin/X11:/sbin:.
[Thr 01] JStartupICreateProcess: fork process (pid 893002)
[Thr 01] Tue Aug 26 16:27:18 2008
[Thr 01] *** ERROR => invalid return code of process [bootstrap] (exitcode=66) [jstartxx_mt. 1433]
[Thr 01] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=66)
[Thr 01] JControlCloseProgram: started (exitcode = 66)
[Thr 01] JControlCloseProgram: good bye... (exitcode=66)
DO i have to change the some settingdsin any file for java instance after system copy.
Thanks
Tajinder

Dispatcher of J2EE Engine does not start

I have the following problem, we restart the j2ee engine and the dispatcher does not come up. The server and SDM works fine
dev_dispatcher:
trc file: "/usr/sap/Q82/JC00/work/dev_dispatcher", trc level: 1, release: "700"
node name : ID2430700
pid : 1192142
system name : Q82
system nr. : 00
started at : Tue Nov 20 10:47:45 2007
arguments :
 arg[00] : /usr/sap/Q82/JC00/exe/jlaunch
 arg[01] : pf=/usr/sap/Q82/SYS/profile/Q82_JC00_sapQ82
 arg[02] : -DSAPINFO=Q82_00_dispatcher
 arg[03] : pf=/usr/sap/Q82/SYS/profile/Q82_JC00_sapQ82
[Thr 1] Tue Nov 20 10:47:45 2007
[Thr 1] *** WARNING => INFO: Unknown property [instance.box.number=Q82JC00sapq82] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.host=sapQ82] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 841]
[Thr 1] *** WARNING => INFO: Unknown property [instance.system.id=00] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/Q82/JC00/j2ee/cluster/instance.properties]
-> ms host : sapQ82
-> ms port : 3901
-> OS libs : /usr/sap/Q82/JC00/j2ee/os_libs
-> Admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
Instance properties
-> ms host : sapQ82
-> ms port : 3901
-> os libs : /usr/sap/Q82/JC00/j2ee/os_libs
-> admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
-> [01] bootstrap_ID2430700 : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
-> [02] bootstrap_ID2430750 : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID2430700 : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
-> [01] ID2430750 : /usr/sap/Q82/JC00/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] 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: dispatcher] java home is set by profile parameter
 Java Home: /usr/java14_64
[Thr 1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/Q82/JC00/exe/jvmx.jar
JStartupIReadSection: read node properties [ID2430700]
-> node name : dispatcher
-> node type : dispatcher
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/java14_64
-> java parameters : -Xj9 -Xgcpolicy.gencon -verbose:gc -Xmn70m -Xdisableexplicitgc -Djava.security.policy=.\java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1
-> java vm version : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142ifx-20070510a (JIT enabled)
-> java vm vendor : IBM J9 VM (IBM Corporation)
-> java vm type : server
-> java vm cpu : ppc64
-> heap size : 202M
-> init heap size : 202M
-> root path : /usr/sap/Q82/JC00/j2ee/cluster/dispatcher
-> class path : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/Q82/JC00/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/Q82/JC00/exe/jstartup.jar:/usr/sap/Q82/JC00/exe/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 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]: -Xj9
-> arg[ 4]: -Xgcpolicy.gencon
-> arg[ 5]: -verbose:gc
-> arg[ 6]: -Xmn70m
-> arg[ 7]: -Xdisableexplicitgc
-> arg[ 8]: -Djava.security.policy=.\java.policy
-> arg[ 9]: -Djava.security.egd=file:/dev/urandom
-> arg[ 10]: -Djco.jarm=1
-> arg[ 11]: -Dsys.global.dir=/usr/sap/Q82/SYS/global
-> arg[ 12]: -Dapplication.home=/usr/sap/Q82/JC00/exe
-> arg[ 13]: -Djava.class.path=/usr/sap/Q82/JC00/exe/jstartup.jar:/usr/sap/Q82/JC00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> arg[ 14]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/sap/Q82/JC00/exe::/usr/lib:/usr/sap/Q82/JC00/j2ee/os_libs:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/JC00/exe:/usr/lib:/lib:/usr/sap/Q82/SYS/exe/run:/oracle/client/10x_64/instantclient
-> arg[ 15]: -Dmemory.manager=202M
-> arg[ 16]: -Xmx202M
-> arg[ 17]: -Xms202M
-> arg[ 18]: -DLoadBalanceRestricted=no
-> arg[ 19]: -Djstartup.mode=JCONTROL
-> arg[ 20]: -Djstartup.ownProcessId=1192142
-> arg[ 21]: -Djstartup.ownHardwareId=R1572408088
-> arg[ 22]: -Djstartup.whoami=dispatcher
-> arg[ 23]: -Djstartup.debuggable=no
-> arg[ 24]: -DSAPINFO=Q82_00_dispatcher
-> arg[ 25]: -DSAPSTARTUP=1
-> arg[ 26]: -DSAPSYSTEM=00
-> arg[ 27]: -DSAPSYSTEMNAME=Q82
-> arg[ 28]: -DSAPMYNAME=sapQ82_Q82_00
-> arg[ 29]: -DSAPDBHOST=sapQ82
-> arg[ 30]: -Dj2ee.dbhost=sapQ82
[Thr 772] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx_mt.c 542]
[Thr 772] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi_mt. 752]
[Thr 772] **********************************************************************
ERROR => Java VM initialization failed.
Please see SAP Note 943602 , section 'Java VM initialization issues'
for additional information and trouble shooting.
[Thr 772] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 772] JLaunchCloseProgram: good bye (exitcode = -1)
Does somebody has any ideas?
Regards Peter

Hi folks,
i solved it by myself. There was a wrong javaparameter in the settings of the dispatcher.
-Xgcpolicy.gencon instead of -Xgcpolicy:gencon, my colleague has found it out.
Regards Peter

J2ee engine does not start - error 503

have a dual stack NetWeaver installation. I can start/connect to the ABAP stack fine, but I cannot connect to the Java stack.
When I do http://<machine name>:50000 or http://<machine name>:50000/irj/portal ... I get a "503 service unavailable. Application stopped" message.
searching through the j2ee logs did not reveal any problems (All j2ee services look like they are started successfully).

Tiberiu,
Check ume service : com.sap.security.core.ume.service started or not?
I think it may be very slow and this may cause a lot of services to time out.
Changed settings in config tool:
1.instance_IDXXX -> server -> managers -> Service manager -> LoadTimeout from 5 to 15.
2.instance_IDXXX -> server -> managers -> ApplicationThreadManager there change InitialThreadCount, MinThreadCount and MaxThreadCount to 350.
3.Restart the server.
Regards,
Karthick Eswaran
*Do not forget to Reward points for helpful answers

J2EE engine does not start and then visual administartor gives error

I am trying to start the SAP J2EE GUI after entering User J2EE_ADMIN and
password it hardly goestill 5% and gives following task error:
"com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
create new RemoteLoginContext".
I have also applied 701654 as suggested by you earlier but I have never
changed the password, However I have updated the Secure storage also
using configuration tool.

I am trying to start the SAP J2EE GUI after entering User J2EE_ADMIN and
password it hardly goestill 5% and gives following task error:
"com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
create new RemoteLoginContext".
I have also applied 701654 as suggested by you earlier but I have never
changed the password, However I have updated the Secure storage also
using configuration tool.

J2EE Engine is not starting

Hi Experts,
our J2EE Engine is not starting. After application restart in SAP MMC's process list for disp+work.exe the status is yellow (Running, Message Server connectionok, ...., J2EE: Some processes running). In the J2EE Process table the server0 is stopped. He tries to start it a couple of times, but after all it stopps with exitcode -11113. So I've checked the dev_trace, the entry was:
[Thr 2376] Wed Nov 17 15:41:35 2010
[Thr 2376] *** WARNING => INFO: Unknown property [instance.box.number=EI3DVEBMGS00chopin] [jstartxx.c   841]
[Thr 2376] *** WARNING => INFO: Unknown property [instance.en.host=chopin] [jstartxx.c   841]
[Thr 2376] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
[Thr 2376] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
[Thr 1128] Wed Nov 17 15:45:06 2010
[Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1128] JLaunchISetClusterId: set cluster id 2121050
[Thr 1128] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1128] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5284] Wed Nov 17 15:45:34 2010
[Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 5900] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 5900] **********************************************************************
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 5900] JLaunchCloseProgram: good bye (exitcode = -11113)
So I searched a little and found this [Thread|Restart of J2EE Engine] and modified the Heapsize. As our Server is a 32-bit machine I used this sizes:
Max heap size: 1024M
-Xms1024M // old size: 512
-XX:PermSize=512M // old size: 128
-XX:MaxPermSize=512M // old size: 128
-XX:NewSize=320M // old size: 86
-XX:MaxNewSize=320M // old size: 86
The result was another error message in dev_trace:
Error occurred during initialization of VM
Could not reserve enough space for object heap
[Thr 2396] JLaunchIAbortJava: abort hook is called
[Thr 2396] **********************************************************************
ERROR => The Java VM aborted unexpectedly.
Please see SAP Note 943602 , section 'Java VM crashes'
for additional information and trouble shooting.
[Thr 2396] JLaunchCloseProgram: good bye (exitcode = -2)
ok, so I changed the sizes again to:
Max heao size: 1024M
-XX:MaxPermSize=128M
-XX:PermSize=512M
-Xms512M
-XX:NewSize=320M
-XX:MaxNewSize=86M
But there's still the same error occurring.
Please, does someone has an idea how to solve this issue?
Thanks in advance,
Tan

Hi Desiree,
thank you for your posting. It's getting better, but it's still not running. I've set up the same password in client 001 and in the java ume and restarted the cluster. When starting the server0 is J2EE Process Table is starting framework, then starting apps, but after something about 9 minutes its restarting, but it seems not to have errors (in the J2EE Process Table there are restarts displayed but no errors. So its better than before where the server0 restarts after 30 seconds and stopps restarting after 3 errors and 4 restarts.
But nows he's restarting and restarting....
In TA SMICM there is the J2EE server operational TRUE which was not before. When checking the RFC Destination there comes the status "not ready" during Starting framework phase and status "Service unavailable" during starting apps phase.
Here are some parts of the dev_trave:
"VM Thread" prio=5 tid=0x003cec80 nid=0x1028 runnable
"Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x7e0 runnable
[Thr 4136] JLaunchIExitJava: exit hook is called (rc = 666)
[Thr 4136] **********************************************************************
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 4136] JLaunchCloseProgram: good bye (exitcode = 666)
"VM Thread" prio=5 tid=0x003cec80 nid=0xb50 runnable
"VM Periodic Task Thread" prio=10 tid=0x011dcc88 nid=0x9e4 waiting on condition
"Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x748 runnable
[Thr 2896] Thu Nov 18 09:13:33 2010
[Thr 2896] JLaunchIExitJava: exit hook is called (rc = 666)
[Thr 2896] **********************************************************************
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 2896] JLaunchCloseProgram: good bye (exitcode = 666)
... and so on.
I'm not sure whether I should change or add entries in the configtool.bat like in your link recommended. The Engine was running with this settings before.....

Personalization Scheduling Engine does not start -- Bug?

Hi there. I don't know if it's the correct forum to post my question. If I'm wrong I ask you to redirect to
the correct one.
I've correctly installed Oracle AS 10g release 1 according to the following topology, on the production
environment :
Server 1 --> Here we are three oracle homes : Identity Management , Middle Tier (Portal and Wireless) ,
Personalization.
Server 2 --> MetadataRepository
My problem focuses on Personalization. I advise that in my developing environment I've not got any problem.
So , I've installed Oracle AS Personalization without wornings. I've created RE,MOR and MTR schemas as the
procedure dictates. Problem's that Personalization Scheduling Engine does not start. It should start
automatically but It didn't. So I tried to start it by hand following "Oracle Application Server Hi there.
I don't know if it's the correct forum to post my question. If I'm wrong I ask you to redirect to the
correct one.
I've correctly installed Oracle AS 10g release 1 according to the following topology, on the production
environment :
Server 1 --> Here we are three oracle homes : Identity Management , Middle Tier (Portal and Wireless) ,
Personalization.
Server 2 --> MetadataRepository
My problem focuses on Personalization. I advise that in my developing environment I've not got any problem.
So , I've installed Oracle AS Personalization without wornings. I've created RE,MOR and MTR schemas as the
procedure dictates. Problem's that Personalization Scheduling Engine does not start. It should start
automatically but It didn't. So I tried to start it by hand following "Oracle Application Server
Personalization Administrator's Guide 10g(9.0.4)". Specifically , when I try to start the scheduling engine
with the command "execute OP_START_ENGINE" in the MOR schema I obtain an error linked to DBMS_JOB.run()
method. Digging deep into the Oracle alert log file I found this brief linked to the error executin the
script :
Thu Apr 14 17:57:28 2005
Errors in file E:\MetadataRepositoryHome\admin\asdb\udump\ORA01860.TRC:
ORA-12012: error on auto execute of job 119
ORA-29532: Java call terminated by uncaught Java exception: java.lang.Exception: Scheduler Workflow Error:
9756161113494248343 java.lang.NumberFormatException: 9756161113494248343
at java.lang.Long.parseLong(Long.java)
at java.lang.Long.parseLong(Long.java)
at oracle.dmt.op.util.messagelog.MessageLog.getExecutionContextID(MessageLog.java:857)
at oracle.dmt.op.workflow.SchedulerWorkflowClass.main_method(SchedulerWorkflowClass.java:101)
at oracle.dmt.op.workflow.SchedulerWorkflowClass.SchedulerWorkflowJava(SchedulerWorkflowClass.java:91)
ORA-06512: at "MOR_PORTALE.DMT_CLIENT_IDARWIN_WORKFLOW", line 0
ORA-06512: at line 1
So as the main error is "NumberFormatException" , I executed reverse engineering decompiling two Oracle
classes , just to know the origin of the error :
oracle.dmt.op.util.messagelog.MessageLog and
oracle.dmt.op.workflow.SchedulerWorkflowClass
After simple tracing I think I reached the origin and I shocked myself to see it!! The problem starts in the
main_method of oracle.dmt.op.workflow.SchedulerWorkflowClass, i.e. :
private void main_method()
throws Exception
String event_msg_args[];
traceMsg += "Start";
moduleID = "SchedulerWorkflowClass.main_method";
traceMsg += "-executionContextID";
executionContextID = MessageLog.getExecutionContextID();
The problem resides in the getExectiongContextID() method of oracle.dmt.op.util.messagelog.MessageLog class.
Code of this method is this :
public static long getExecutionContextID()
String hostIP = null;
try
InetAddress host = InetAddress.getLocalHost();
hostIP = host.getHostAddress();
catch(UnknownHostException ex) { }
StringBuffer buf = new StringBuffer(20);
if(hostIP != null)
for(StringTokenizer st = new StringTokenizer(hostIP, "."); st.hasMoreTokens(); buf.append
(st.nextToken()));
buf.append((new Date()).getTime());
String tmpString = buf.toString();
String idString = tmpString.replace('?', ' ');
idString = idString.trim();
int len = idString.length();
if(len > 19)
idString = idString.substring(len - 19);
long id = Long.parseLong(idString);
return id;
Simply , code obtains IP address of the Host , concats it with the current time and if the length of the
result string is longer than 19 it obtains substring of (len -19) length!! I think , Oracle programmer
thought to prevent NumberFormatException with the control "if(len > 19)
idString = idString.substring(len - 19);"
but that's strange , very strange!! In fact , in my case(with my IP Address 160.97.*.*) , method outputs
NumberFormatExceptio 'couse long "id = Long.parseLong(idString);" is not able to convert the String
"9756161113494248343" to java.lang.Long!!! 'couse it exceedes maximum value ( 2EXP(63)-1)!! So , I think
it's bug but I don't know how to solve it!! Problem's in method's semantic. It should control that the
String it creates is lower that the maximum value allowed for a long , not its length lower or equal 19!!!
I mean , I cannot modify Oracle Java Class file.
With kind regards,
Nicola

Fix in OracleAS 10.1.2.0.2 if you file a bug referencing bug 4397235 a backport of the fix can be provided on metalink.

J2EE engine will not start

Hi experts.
J2EE engine will not start. Below is the lower section of the trace. I'd appreciate help with interpretation as I am a NW newby.
I just installed an J2EE key in tcode SLICENSE for our developer's subscription NW 7.0 instance. Another thread implied installing the J2EE key in visual administrator, but how is that possible if the J2EE engine is not running? I cannot establish a connection.
Thanks,
Aron
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1633]
***LOG Q0K=> DpMsAttach, mscon ( S-SAPDEV01) [dpxxdisp.c 11822]
DpStartStopMsg: send start message (myname is >S-SAPDEV01_DS1_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
Tue Jul 08 13:43:35 2008
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 146
Release check o.K.
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:43:37 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 236
 (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4027) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5508)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
MBUF state ACTIVE
Tue Jul 08 13:43:38 2008
DpModState: change server state from STARTING to ACTIVE
Tue Jul 08 13:44:14 2008
J2EE server info
start = TRUE
state = STARTED
pid = 3412
argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64998
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=DS1
argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:17 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 668
 (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4095) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3412)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Jul 08 13:44:34 2008
J2EE server info
start = TRUE
state = STARTED
pid = 5156
argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64997
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=DS1
argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:37 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 208
 (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4105) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5156)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Jul 08 13:44:54 2008
J2EE server info
start = TRUE
state = STARTED
pid = 6072
argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64996
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=DS1
argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:57 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 200
 (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4117) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6072)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN

Actually it was to remove compression, not to allow archiving. Sorry!
We're using Windows Server 2003. Right-click on a folder or file, choose Properties. Click on the Advanced button on the General tab. Remove the check box for Compress to save disk space, click ok. When you click on Apply there will be a prompt to apply just to that folder only or on subfolders and files as well.
When compression is applied, the text for the folder turns blue. When is not applied, the text is black.

J2EE dispatcher does not start !!!

Hi all,
Just got problem, our java dispatcher on XI does not start even if java server starts correctly on one instance, and the other java instance starts correctly either (both dispatcher and server).
We tried to restart java dispatcher, but did not help, then restarted whole system, but did not help, java dispatcher on central instance did not start.
Can somebody help me where to look to solve the problem. May there be a problem with parameter settings? There is suspition that it can be problem with JVM?
Thanx a lot.
Michal

Michal,
Did you check the J2EE startup traces like dev_dispatcher, dev_server etc (I'm not sure about actual names, but they can be found in DVBESMGxx/work subdir) ...
Let us know if you need help
Chris

J2EE 70 does not start - OutOfMemoryError rc=666

We have NTW04s ABAP+J2EE (ut. EP, BI) on Win 32 bit, 2048 RAM installed.
The J2SDk is 1.4.2_17.
We applied the parameters of note 723909 and 1044330 for Win32 (-Xms and -Xmx=1024m, Perm and MaxPerm=256m, new and MaxNew=160m) anyway the J2EE server0 does not come up.
It start and arrive in state 'Starting Apps' in MMC and into the log std_server0.out we see 'Framework started' but after that we see these entries:
730.927: [GC 730.927: [ParNew: 239922K->70400K(245760K), 0.3252431 secs] 293939K->128044K(966656K), 0.3253927 secs]
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
===========================================
getThreadDump : Tue Jun 10 15:42:50 2008
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
===========================================
java.lang.OutOfMemoryError: unable to create new native thread ......."
As note 1044330 says the ut BI Java require more Heap in the Perm area, and we suspect there is not free heap memory to start the J2EE applications, we try to enlarge it to 512m (perm and maxperm) but the J2EE server0 does not come up at all.
Into the std_server0.out we see these entries:
"....Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4876] MtxInit: -2 0 0
Error occurred during initialization of VM
Could not reserve enough space for object heap"
We try also with perm and maxperm equal to 320m, but the result is the same.
We reduced the Abap instance at minimal as number of work process, buffers and Phys_mem_size. We reduced also the Oracle SGA at minimal.
Any advise ?
bye

Thanks for the fedbacks but....
We read these notes, anyway any attempt to increase the Heap size produce the error 'Could not allocate ....'.
This is a 32 bit system.
From the other side if we leave the Xmx=Xms=1024M and the other parameters suggested in the Oss notes for 32bit platform the server0 starts but after a while it give the error "Out of memory...."
It seems the Heap is not enought to start all the applications.
We installed the Sap Adddress Viever and identified the JLAUCH process responsible for the server0.
If we do "List/Rebase" we see 8 dlls: 7 from the J2SDK 1.4.2_17 in use and one from Windows.
Is it possible that the J2SDK 1.4.2_17 compete with the JLAUCH for teh Heap memory ?

Satellite M-series does not start correctly

Hello,
I have the following problem: suddenly (don't know why, nothing changed) Satellite notebook shows black white screen with about the following:
(sorry, translated from german):
windows did not start correctly... due to software or hardware change.. pls choose last functional configuration if mistake was due to power shut down...
But this does not work, also all other options (start windows as normal, start in safe mode...did not work.
No idea what happenend !
Problem:
Actually moved to another country and forgot or lost recovery CD ! already contacted Toshiba for new one but maybe anyway somebody can help?

Hmm. Stupid situation. If possible try to obtain Microsoft WXP installations CD to see if you can start installations procedure properly and if you can use repair option too.
It is not easy to say what is wrong there but I just hope there is no problem with HDD. Try to use original recovery disc.

SAP J2EE Engine : does not work !!!

Hi everyone,
I have installed SAP NW2004s Java SP9 Trial (on Windows XP and Sapdb as database). The installation finished without problems.
But when I start my SAP system, the SAP J2EE engine (process jcontrol) is still stopped
[... I have already searched in the forum, but I have not found a solution to my problem ...]
Here is the contents of files dev_jcontrol & dev_sdm :
File dev_jcontrol : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 1384
system name : J2E
system nr. : 01
started at : Mon Dec 03 15:23:56 2007
arguments :
 arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
 arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
[Thr 2356] Mon Dec 03 15:23:56 2007
[Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c 725]
[Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c 1952]
[Thr 2356] *** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties] (rc = -1) [jstartxx.c 524]
File dev_sdm : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_sdm", trc level: 1, release: "700"
node name : sdm
pid : 1360
system name : J2E
system nr. : 01
started at : Fri Nov 30 10:38:29 2007
arguments :
 arg[00] : D:\usr\sap\J2E\JC01\exe\jlaunch.exe
 arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
 arg[02] : -DSAPINFO=J2E_01_sdm
 arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host : ahassaine
-> ms port : 3900
-> OS libs : D:\usr\sap\J2E\JC01\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : ahassaine
-> ms port : 3900
-> os libs : D:\usr\sap\J2E\JC01\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] sdm : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 3544] Fri Nov 30 10:38:29 2007
[Thr 3544] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 3544] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2240] JLaunchRequestFunc: Thread 2240 started as listener thread for np messages.
[Thr 3352] WaitSyncSemThread: Thread 3352 started as semaphore monitor thread.
[Thr 3544] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 3544] CPIC (version=700.2005.12.02)
[Thr 3544] INFO: Invalid property value [Debbugable=yes]
[Thr 3544] [Node: SDM] java home is set by profile parameter
 Java Home: C:\Java\
[Thr 3544] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\Java\
-> java parameters :
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : D:\usr\sap\J2E\JC01\SDM\program
-> class path : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\J2E\JC01\exe
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 50000
-> shutdown timeout : 120000
[Thr 3544] JLaunchISetDebugMode: set debug mode [no]
[Thr 2480] JLaunchIStartFunc: Thread 2480 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SDM]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
-> arg[ 4]: -Dapplication.home=D:\usr\sap\J2E\JC01\exe
-> arg[ 5]: -Djava.class.path=D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar;D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> arg[ 6]: -Djava.library.path=C:\Java
jre\bin\server;C:\Java
jre\bin;C:\Java
bin;D:\usr\sap\J2E\JC01\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> arg[ 7]: -Dmemory.manager=512M
-> arg[ 8]: -Xmx512M
-> arg[ 9]: -DLoadBalanceRestricted=no
-> arg[ 10]: -Djstartup.mode=JCONTROL
-> arg[ 11]: -Djstartup.ownProcessId=1360
-> arg[ 12]: -Djstartup.ownHardwareId=G1610100576
-> arg[ 13]: -Djstartup.whoami=sdm
-> arg[ 14]: -Djstartup.debuggable=yes
-> arg[ 15]: -DSAPINFO=J2E_01_sdm
-> arg[ 16]: -DSAPSTARTUP=1
-> arg[ 17]: -DSAPSYSTEM=01
-> arg[ 18]: -DSAPSYSTEMNAME=J2E
-> arg[ 19]: -DSAPMYNAME=ahassaine_J2E_01
-> arg[ 20]: -DSAPDBHOST=ahassaine
-> arg[ 21]: -Dj2ee.dbhost=ahassaine
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
[Thr 2480] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SDM]
-> arg[ 0]: server
-> arg[ 1]: sdmhome=D:\usr\sap\J2E\JC01\SDM\program
[Thr 2240] Fri Nov 30 10:38:33 2007
[Thr 2240] JLaunchRequestFunc: receive command:17, argument:0 from pid:2600
[Thr 2240] JLaunchIShutdownInvoke: set shutdown interval (stop:1196419113/end:1196419233/TO:120)
[Thr 2240] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 2240] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 2240] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2240] JLaunchISetState: change state from [Initial (0)] to [Stopping (5)]
[Thr 640] Fri Nov 30 10:38:34 2007
[Thr 640] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 640] JLaunchCloseProgram: good bye (exitcode = 0)
Thank you very much in advance for your help.
Hassan

Hi!
If instance.properties is not there your installation has not finished correctly. This file is the central point of information for the bootstrap, which retrieves the info on how to connect to the database to collect the infos for the system startup (which will then overwrite your instance.properties file with the most recent values from the DB).
Please check if instance.properties has been deleted and can maybe be restored from tape or if there was an error in the installation.
Regards,
Jörg

J2ee service does not start

we are running WAS 6.20 on windows platform. I have problem bringing up the j2ee service.
The parameter for automatic startup is already set and the path to the go.bat is also correct.
I tried execting the go.bat and encountered below error.
C:\usr\sap\CFP\D00\j2ee\cluster\dispatcher>go.bat
SAP J2EE Engine Version 6.20 SP1 is starting...
Loading: LogManager ...
Loading: R3StartupManager ...
[R3StartupManager]: ID000701: Couldn't start r3startup manager. Exception is : Cannot assign
equested address: connect
Loading: R3StartupManager returned false!
Kernel not loaded. System halted.
any suggestions are most welcome
Srinivas

Hi Srinivas,
check out SAP customer note 604080 at http://service.sap.com/notes
Hope this helps
John

J2EE server does not start during installation

Hi,
I am installing WebAS JAVA 640 (NW04 SR1) on a Windows 2003/MSSQL server. I am using JAVA SDK 1.4.2_9. The installation stops at step 24/25 whereby the installer waits for the J2EE engine to start. After making 3 attempts to start the J2EE server, the installation process just hangs and I have to Cancel the installation.
BTW, I am specifying a heap size of 1024 MB and using the "Database Only" option as UME data store during installation.
Having checked the trace and log files, it seems the UME service fails to start, throws an exception and the message "the start of a core service failed, Web AS will not start".
According to the information available <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/20/361941edd5ef23e10000000a155106/content.htm">here</a>, I have checked the settings and it seems that option 2, "User or group data is missing" is causing the problem since database content of UME is missing. I have tried selecting entries from table UME_STRINGS but this table is empty.
Now, the same link says that I should login to UME web application as SAP* but the problem is that without the J2EE engine starting up, I cannot login and create missing users/groups.
Any ideas???
Regards
Shehryar

Thanks to all who replied. I have actually tried all options suggested like waiting for retries until the box appears, trying to manually start the server, and reducing heap size. None worked for me. For your information, I have a 2.4 GHz machine with 4GB RAM so I think heap size should not be an issue. I checked SAP Note regarding heap size issues in Win 2003 but that does not seem to apply in my case since my system does not behave abnormally with JVM settings.
Thanks again and I'll give it another shot.
Regards
Shehryar

J2EE engine does not start correctly

Similar Messages

Maybe you are looking for