Regarding J2EE Server

Hi all,
Set up a system on the Portal J2EE server on which the business package is installed. Assign the alias SAP_WebDynpro_XSS to this system.
What are the details i have to enter for J2EE system to connect portal j2ee server.
Thanks & Regards,
Phanikumar.

talk to the basis personnel for getting some of the details for the system object.
right click on the system object and add the following:
a.     Application host
b.     SAP client
c.     SAP system no
d.     Server port
e.     Gateway host
f.     Gateway service
g.     ITS host name
h.     Logical system name
i.     SAP system no
j.     Session cookie name
k.     Session URL name
l.     WebAs host name
hope it helps!

Similar Messages

Regarding jms implementation that comes with reference j2ee server from sun

I have a message bean that is trying to read message off the queue, do something, and put a message on to other queue.
The problem: I am loosing a message.
I have tried both the container managed as well as bean managed transaction.
Is there any bug with the reference JMS server? I am using the SimpleQueueSender that comes with the jms tutorial from sun to send message in a persisted mode. I am running the J2EE server that comes from SUN.
I will post the code if someone is willing to take a sincere look.
Thanks
Aman

I can tell you one thing about JMS, I have websphere MQ Series, Even the product like MQ from IBM have limitation when using 2 phase commit(), it supports 2 PC only when websphere and MQ Series are installed on the same box, So i would not be surprised if there is a bug in reference JMS implementation and you are losing messages even though in transaction. Are you using distributed transaction.

J2EE Server unable to start

Hi,
first of all, i'm really new to SAP NW. Today I started installing the Sneak Preview of SAP NetWeaver 2004 7.0 SP9
JavaStack on my Virtual Machine (Windows2003Server, J2SE 1.4.2.09) and it worked fine.
After installation I started the SAP Management Console and tried to start my first and only instance J2E.
In J2E i got 3 instances, the DB, Instance 0 and Instance 1.
After start:
DB is working (blue)
Instance 0 is working (green)
Instance 1 failed while starting (turned from yellow to red)
Process List shows:
jcontrol.EXE | J2EE Server | License check failed
igswd.EXE | IGS Watchdog | Running
Problem:
I don't know why the License check failed!
I downloaded the Software about mid of february, its been about 3 month ago and I ran the install for the first time
today. What might be the problem? I searched the SDN-History for similar problems, but i did not find an adequate
answer. I checked dev_jcontrol and the "license check failed" entry is in the file. So I'm wondering why my license
check fails, although I'm installing the software for the first time!
An info i got from the start.htm is:
The license of this Trial Version is for evaluation purposes only and does not allow commercial use.
The license is valid for 90 days and cannot be extended (View license). If the license has expired, the
entry license check failed will appear in the trace file <INST_DRIVE>:\usr\sap\J2E\JC01\work\dev_jcontrol,
if the instance name remains unchanged during the installation process. Please refer to SAP Developer
Network for more information about commercially available editions of SAP Web Application Server and SAP NetWeaver Developer Studio.
May one find some more information in that file?
I realised that a package is missing, but read in the forum, that this is not a obligatory package (?)
JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
node name   : jcontrol
pid         : 2644
system name : J2E
system nr. : 01
started at : Wed May 07 13:28:11 2008
arguments       :
       arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
       arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
[Thr 1352] Wed May 07 13:28:11 2008
[Thr 1352] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.host=sope75] [jstartxx.c   841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01sope75] [jstartxx.c   841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host    : sope75
-> ms port    : 3900
-> OS libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host    : sope75
-> ms port    : 3900
-> os libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap_ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] bootstrap            : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID18439050           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] ID18439000           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] sdm                  : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 1352] [Node: bootstrap] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:28:19 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name          : bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> java path          : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters    : -Djco.jarm=1 -Djco.jarm=1
-> 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\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184390
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 1352] [Node: bootstrap] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name          : bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> java path          : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters    : -Djco.jarm=1 -Djco.jarm=1
-> 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\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184390
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] Wed May 07 13:30:12 2008
[Thr 1352] JControlExecuteBootstrap: read instance values after global bootstrap
[Thr 1352] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01sope75] [jstartxx.c   841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.host=sope75] [jstartxx.c   841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host    : sope75
-> ms port    : 3900
-> OS libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> Admin URL :
-> run mode   : normal
-> run action : NONE
-> enabled    : yes
[Thr 1352] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host    : sope75
-> ms port    : 3900
-> os libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> admin URL :
-> run mode   : normal
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID18439000           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] ID18439050           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] sdm                  : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID18439000]
[Thr 1352] [Node: dispatcher bootstrap] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:30:16 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID18439000]
-> node name          : dispatcher bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters    : -Djco.jarm=1
-> 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          : 256M
-> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID018439000
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=bootstrap_ID18439000
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap_ID18439000.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap_ID18439000.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap_ID18439000
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] Wed May 07 13:31:04 2008
[Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID18439050]
[Thr 1352] [Node: server0 bootstrap] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:31:06 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID18439050]
-> node name          : server0 bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters    : -Djco.jarm=1
-> 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          : 256M
-> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID018439050
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=bootstrap_ID18439050
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap_ID18439050.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap_ID18439050.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap_ID18439050
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] Wed May 07 13:33:15 2008
[Thr 1352] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 1308] JControlRequestFunc: Thread 1308 started as listener thread for np messages.
[Thr 1352] [Node: dispatcher] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:33:17 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID18439000]
-> node name          : dispatcher
-> node type          : dispatcher
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters    : -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 -verbose:gc -verbose:gc -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC
-> 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          : 170M
-> init heap size     : 170M
-> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster\dispatcher
-> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 1352] [Node: server0] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:33:18 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID18439050]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters    : -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 -Djco.jarm=1 -verbose:gc -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -XX:NewSize=145m -XX:MaxNewSize=145m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:+DisableExplicitGC -XX:+UseParNewGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> 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          : 874M
-> init heap size     : 874M
-> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters         :
-> debuggable         : yes
-> debug mode         : yes
-> debug port         : 50121
-> shutdown timeout   : 120000
[Thr 1352] INFO: Invalid property value [Debbugable=yes]
[Thr 1352] [Node: SDM] java home is set by profile parameter
     Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:33:19 2008
[Thr 1352] 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:\Programme\Java\j2sdk1.4.2_09
-> 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          : 256M
-> 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\j2ee\os_libs
-> 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         : 60000
-> shutdown timeout   : 120000
[Thr 1352] JControlMSConnect: attached to message server (sope75/3900)
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=ID18439000
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_dispatcher.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 3376] JControlMSMessageFunc: Thread 3376 started as listener thread for ms messages.
[Thr 1352] JControlICheckProcessList: process dispatcher started (PID:724)
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=ID18439050
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_server0.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_server0.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = -debugMode=yes
-> arg[12] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] JControlICheckProcessList: process server0 started (PID:2276)
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_sdm.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_sdm.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] JControlICheckProcessList: process SDM started (PID:3312)
[Thr 1352] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 3376] Wed May 07 13:33:47 2008
[Thr 3376] JControlIEnableProcesses: disable processes of type (Exclude:0) [SDM Server]
[Thr 3376] JControlIDisableProcess: disable process SDM
[Thr 3376] JControlIProcessSoftKill: soft kill of process SDM (pid:3312)
[Thr 1352] Wed May 07 13:33:52 2008
[Thr 1352] JControlICheckProcessList: process SDM (pid:3312) died (STOPPING)
[Thr 1352] JControlIResetProcess: reset process SDM
[Thr 1352] Wed May 07 14:20:27 2008
[Thr 1352] JControlICheckProcessList: process dispatcher (pid:724) died (RUN-FLAG)
[Thr 1352] JControlIResetProcess: reset process dispatcher
*[Thr 1352] JControlICheckProcessList: license check failed*
*[Thr 1352] JControlMainLoop: license check failed -> shutdown the instance*
[Thr 1352] JControlProcessMessage: received <shutdown without restart> command
[Thr 1352] JControlIStopInstance: shutting down (command: 0)
[Thr 1352] JControlIProcessSoftKill: soft kill of process server0 (pid:2276)
[Thr 1352] Wed May 07 14:22:33 2008
[Thr 1352] *** ERROR => Can't terminate process (pid = 2276,handle = 00000678,err = 5) [jstartnt.c   690]
[Thr 1352] *** ERROR => Critical error, can't terminate process server0 (pid:2276) (rc=-2) [jcntrxxi.c   407]
[Thr 1352] JControlICheckProcessList: process server0 (pid:2276) died (STOPPING)
[Thr 1352] JControlIResetProcess: reset process server0
[Thr 1352] JControlCloseProgram: started (exitcode = 0)
[Thr 3376] JControlMSMessageFunc: shutdown -> terminate message listener
[Thr 3376] JControlMSMessageFunc: leave listener thread
[Thr 1352] Wed May 07 14:22:34 2008
[Thr 1352] JControlCloseProgram: good bye... (exitcode = -11111)
Regards
RandomStudent
Edited by: RandomStudent on May 7, 2008 4:45 PM
Edited by: RandomStudent on May 7, 2008 4:47 PM

Hello Vijith, thanks for your answer.
Installed a Sneak Preview of SAP NetWeaver 7.1 CE on Monday(5th May), but it failed.
Deinstalled the 7.1 CE Software on Tuesday (6th May).
Installed Sneak Preview of SAP Netweaver (2004s) 7.0 SP9 on Wednesday (7th May) and it was installed correctly, but i got the problem with the license check.
So the Options are:
Change the date on OS before starting the Software
or
Deinstalling the Software and installing SAP Netweaver (2004s) 7.0 SP9 SR 3 (which i downloaded this night). But i think i have to get the registry clean then. Are there Tools to clean the registry from all SAP entries?

How to create one more server node for SAP J2EE server?

Hi,
Can any one please suggest how to create one more server node for SAP J2EE server? I am using WAS700.
Thanks and Regards,
Smriti.

Hai,
Login into the Configtool(C:\usr\sap\SID\DVEBMGS<inst no>\j2ee\configtool) if ABAP+JAVA stack or C:\usr\sap\SID\JC<inst no>\j2ee\configtool) if JAVA stack
click on the instance and and select the addserver button on the top to create a servernode for J2EE server.
Thanks and Regards,

Port error while deploying a dictonary project to j2ee server

Hello,
I created a dictonary project in sap netweaver developer studio 7.1.The j2ee server and the database (both on a remote server) are running and configured.
When i try to deploy it i get the following errors
[#3]: DC API is trying to connect to '<server name>:50004' [INFO: Jan 31, 2008 9:28:26 PM /userOut/daView_category (eclipse.UserOutLocation) [Thread[main,6,main]] ]
om.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
The error is guess is the port number.My server is configured on port 50000 and here it is showing 50004.If i am correct then how do i configure my applications port number?
I searched and saw some messages like open \usr\SAP\<SID>\SYS\profile ,edit the port and similar solutions.Where is this "\usr\SAP\<SID>\SYS\profile " location?My server is on a remote machine.How do i configure my client to pick up the correct port ?
Thank you in advance.
Thanks and Regards
Siri

the issue got solved..the error was not about the port..on restarting the server i was able to deploy my project..

JDBC Adapter: J2EE server crashes while sending large messages

We want to use the following scenario to transfer data from a MS SQL Server to SAP BW via XI:
JDBC Sender Adapter XI SAP ABAP Proxy.
All works fine with a small amount of data. But if the select statement delivers too many record sets and the size of the transformed XML payload is greater then 50 MB the J2EE server crashes. A complete restart is necessary. It seems to be am memory problem.
Here are the entries from our log files:
dev_server0
[Thr 6151] Mon Jul 24 12:46:57 2006
[Thr 6151] JLaunchIExitJava: exit hook is called (rc=666)
[Thr 6151] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 940893 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 6151] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 6151] JLaunchCloseProgram: good bye (exitcode=666)
std_server0.out
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError
Is this a general problem of the XI or a specific one of our configuration? Is it possible to transfer such large messages via XI? If not, is there a workaround for such scenarios?
(Memory heap size of the J2EE server is 1024 MB.)

> Hi Gil,
>
> i had nearly the same problems some times in praxis
> and the mapping was the reason. Just change your
> interface determination temporary, delete the mapping
> and test again to find out if the mapping is the
> reason.
>
> Regards,
> Udo
I have changed my interface determination so that no message mapping is used. The J2EE server still crashes.
> Hi Gil,
> This does sounds like a memory problem especially
> when it comes to 50M message with a minimum XI sys
> requierments...
> To be sure you can check on the RWB for the
> componnent monitoring at the JDBC adapters and look
> for your adapter
> look at the status of the adapter and the trace
> there...
Hi Nimrod
In case of such an error I have no entries in channel monitor. So I can't see anything there. I have also no entries in message monitor of the RWB in this case. So I don't get any information with standard XI tools.
> My reccomendation to you is to set the poll intervall
> to a shorter period,this way you'll make sure you get
> less records...I hope you have remembered to add a
> status/flag column on the table to be set after
> selection so no duplicate records will be taken on
> the second pools.
>
The problem is that the source of my data is not a simple SQL statement but a stored procedure. So I don't know exactly how many records will be delivered. A update command is not possible.

The problem is occurred with J2ee server node which is disabled it from MMC

Dear SAP Consultants,
The problem is occurred with J2ee server node which is disabled J2ee server node from MMS Console and the abap work process is working fine but the dispatcher is yellow status and I can login to the abap system but Iu2019m not able to start the j2ee from Tcode u201CSmicmu201D as well
The system parameters are:
BI 7.0 System as ABAP & JAVA add on, windows 2003 on Oracle database, 24 GB Ram
Paging files: Driveu201D Os system: minimum: 1525, maximum: 3048
Driveu201DEu201D application: minimum: 70855, maximum: 70855
I can see the log files as follow:
From dev_disp:
Sun Jun 21 13:10:28 2009
J2EE server info
start = TRUE
state = STARTED
pid = 2892
argv[0] = E:\usr\sap\BWD\DVEBMGS00\exe\jcontrol.EXE
argv[1] = E:\usr\sap\BWD\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=E:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS00_cai-bwdev
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64990
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=BWD
argv[7] = -DSAPMYNAME=cai-bwdev_BWD_00
argv[8] = -DSAPPROFILE=E:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS00_cai-bwdev
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
Sun Jun 21 13:10:29 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1032
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1362) [nixxi.cpp    4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2892)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Sun Jun 21 13:10:48 2009
DpEnvCheckJ2ee: switch off j2ee start flag
From dev_jcontrol :
[Thr 2124] Sun Jun 21 13:10:29 2009
[Thr 2124] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c   1642]
[Thr 2124] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
[Thr 2124] JControlCloseProgram: started (exitcode = 66)
[Thr 2124] JControlCloseProgram: good bye... (exitcode = 66)
From dev_bootstrap :
JHVM_BuildArgumentList: main method arguments of node [bootstrap]
-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap
-> arg[ 1]: ./bootstrap
-> arg[ 2]: ID0072573
-> arg[ 3]: -XX:NewSize=57M
-> arg[ 4]: -XX:MaxNewSize=57M
-> arg[ 5]: -Xms256M
-> arg[ 6]: -Xmx256M
-> arg[ 7]: -XX:+DisableExplicitGC
-> arg[ 8]: -verbose:gc
-> arg[ 9]: -Djava.security.policy=.java.policy
-> arg[ 10]: -Djava.security.egd=file:/dev/urandom
-> arg[ 11]: -Djco.jarm=1
[Thr 5216] JLaunchIExitJava: exit hook is called (rc = 66)
[Thr 5216] **********************************************************************
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 5216] JLaunchCloseProgram: good bye (exitcode = 66)
From server.0.log :
#1.5 #001E4F208703008A0001C7470000092000046A4414D60A1F#1242740546634#/System/Server##com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#J2EE_GUEST#0##n/a##27772ea0447811deb9bf001e4f208703#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#Plain###ERROR_ACQUIRE_CONNECTION
com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION
     at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92)
     at com.sap.caf.eu.gp.schedule.impl.ScheduleDbImpl.getScheduleToProcess(ScheduleDbImpl.java:1936)
     at com.sap.caf.eu.gp.schedule.impl.ScheduleService.getScheduleToProcess(ScheduleService.java:432)
     at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.work(ScheduleWorker.java:77)
     at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.run(ScheduleWorker.java:63)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should..
     at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)
     at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89)
     ... 8 more
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should..
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:267)
     at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
     ... 9 more
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should..
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:117)
     ... 12 more
Caused by: com.sap.security.core.server.secstorefs.FileMissingException: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should.
     at com.sap.security.core.server.secstorefs.StorageHandler.openExistingStore(StorageHandler.java:372)
     at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1946)
     at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
     at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
     ... 14 more
Please advice with the right solution,
Regards,
Ahmed

thanks

SAP WAS J2EE server installation on Windows Vista

Hi Experts,
Is there anything latest on SAP WAS J2EE server installation on Windows Vista. In SDN download section I see SAP NetWeaver 7.01 ABAP Trial Version available with Vista compatibility.
Is there SAP J2EE server also available with Vista compatibility ?
Regards,
Yomesh

> Is there anything latest on SAP WAS J2EE server installation on Windows Vista. In SDN download section I see SAP NetWeaver 7.01 ABAP Trial Version available with Vista compatibility.
>
> Is there SAP J2EE server also available with Vista compatibility ?
The problem with J2EE is the support status of the used JDK. Sun does not support 1.4.2 under Vista/Windows 2008, technically it works.
Markus

ERROR WHILE STARTING J2EE SERVER IN COMMAND PROMPT

C:\j2sdkee1.3.1\bin>j2ee -verbose
J2EE server listen port: 1050
Naming service started:1050
Exception in thread "main" java.lang.NoSuchMethodError
at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImpl.java:1256)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(ShutdownUtilDelegate.java:223)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(ShutdownUtilDelegate.java:178)
at javax.rmi.CORBA.Util.writeAny(Util.java:80)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:188)
at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:202)
at javax.naming.InitialContext.rebind(InitialContext.java:370)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:192)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:149)
at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.java:473)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
ANY DETAILS POST
REGARDS
VENKAT

I had the same problem overhere.
If you would have taken the time to read some topics on this forum you would have found dozens of others having this problem like
http://forum.java.sun.com/thread.jsp?forum=136&thread=280211
Which gave the answer for me
That was: install the jdk141 and UNDEFINE any classpath and cpath in you environment setting.
HTH
Xiffy

Error while starting NW server and j2ee server is getting stopped.

Hi,
I am working in NW04s. It contains ABAP sp5 and java sp9 versions. The server was working find till ten days back. After the gap of ten days, when i started to work on this SAP system, i was not able to start the j2ee server. During the startup of the server itself, j2ee server is getting stopped and dispatcher also. Following is the error bunch I got in trace. If any one has any idea about this, please reply this soon.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
     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=garden SYSNR=00 GWHOST=garden GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       connection to partner '15.70.176.191:sapgw00' broken
TIME        Mon Nov 13 12:45:30 2006
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -6
MODULE      nixxi.cpp
LINE        4207
DETAIL      NiIRead
SYSTEM CALL recv
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     4
     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:356)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
     ... 6 more
#1.5#000E7FFD8B5D001D00000011000008540004221BAAB8047C#1163402130490#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_54##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

> ceException: Connect to SAP gateway failed
> Connect_PM TYPE=A ASHOST=garden SYSNR=00
> GWHOST=garden GWSERV=sapgw00 PCS=1
>
> LOCATION    CPIC (TCP/IP) on local host with Unicode
> ERROR       connection to partner
> '15.70.176.191:sapgw00' broken
You can ping this machine from your portal-nodes and you can connect to the port "sapgw00" (should be 3300) ?
> ##0#0#Fatal#1#/System/Server#Plain###Critical
> shutdown was invoked. Reason is: Core service
> com.sap.security.core.ume.service failed. J2EE Engine
> cannot be started.#
This is the reason why your j2ee-server stops - the portal can't connect to the ume. What did you configured as the ume - the portal database, a ldap-server or a r3-system ?
Regards
Norman

How to install and configure configure IGS for J2EE server 700

Hi,
Please help me in installing and configuring IGS for J2EE server700 as i need it to run Business Graphics for my Web DynPro application. Earlier i had installed J2EE server 640 and i didnt have to do any separate installation for IGS. I just had to configure the IGS URL from Visual Admin. But i can't find any igswd.exe running on my J2EE700 engine.
Please let me know the procedure for this.
Thanks an Regards,
Smriti.

Hi,
Check the below link,
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/17/86c039c7811f11e10000000a114084/frameset.htm">About IGS Configuration and Adminisatration</a>
Regards,
Suresh.T

J2EE server not running. 503 service unavailable

Hi ,
J2EE Server is not starting. Rest all are running in mmc console.The contents of the file std_server0.out is as below.
stdout/stderr redirect
node name : server0
pid : 584
system name : J2E
system nr. : 00
started at : Tue Feb 15 10:12:46 2005
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
SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...
Loading: LogManager ... 1656 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 282 ms.
Loading: ThreadManager ... 1360 ms.
Loading: IpVerificationManager ... 47 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 1047 ms.
Loading: LockingManager ... 719 ms.
Loading: ConfigurationManager ... 2093 ms.
Loading: LicensingManager ... 125 ms.
Loading: ServiceManager ...
0.000: [GC 0.000: [ParNew: 43517K->2681K(65280K), 0.1899077 secs] 43517K->2681K(502528K), 0.1900163 secs]
Loading services.:
Service memory started. (125 ms).
Service cross started. (125 ms).
Service jmx_notification started. (110 ms).
Service trex.service started. (140 ms).
Service file started. (47 ms).
Service runtimeinfo started. (0 ms).
Service timeout started. (188 ms).
Service userstore started. (16 ms).
7.557: [GC 7.557: [ParNew: 46201K->4641K(65280K), 0.0511883 secs] 46201K->4641K(502528K), 0.0513121 secs]
Service tcsecvsi~service started. (953 ms).
Service tcsecwssec~service started. (1016 ms).
Service p4 started. (578 ms).
Service classpath_resolver started. (32 ms).
Service deploy started. (5922 ms).
14.157: [GC 14.157: [ParNew: 48161K->7636K(65280K), 0.0653829 secs] 48161K->7636K(502528K), 0.0655197 secs]
Service apptracing started. (390 ms).
Service log_configurator started. (11172 ms).
Service locking started. (0 ms).
Service http started. (563 ms).
Service naming started. (765 ms).
Service failover started. (94 ms).
Service appclient started. (250 ms).
Service ts started. (234 ms).
Service javamail started. (282 ms).
Service jmsconnector started. (282 ms).
Service licensing started. (47 ms).
Service connector started. (547 ms).
Service configuration started. (250 ms).
Service webservices started. (1234 ms).
19.873: [GC 19.873: [ParNew: 51143K->8276K(65280K), 0.0746933 secs] 51143K->8276K(502528K), 0.0748063 secs]
25.284: [GC 25.284: [ParNew: 51796K->8763K(65280K), 0.0613457 secs] 51796K->8763K(502528K), 0.0614361 secs]
Service dbpool started. (6796 ms).
Timed out services:
Service ssl.
Service tc.monitoring.logviewer.
Service keystore.
Service shell.
Service prtbridge.
Service webdynpro.
Service com.sap.security.core.ume.service.
Service pmi.
Service tcsecsaml~service.
Service sld.
Service com.sap.portal.prt.sapj2ee.
Service jms_provider.
Service basicadmin.
Service classload.
Service adminadapter.
Service telnet.
Service servlet_jsp.
Service ejb.
Service dsr.
Service monitor.
Service tcsecdestinations~service.
Service tcsecsecurestorage~service.
Service security.
Service applocking.
Service jmx.
Service DQE.
Service tceCATTPingservice.
Service rfcengine.
ServiceManager started for 315217 ms.
Framework started for 323623 ms.
SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is running!
PatchLevel 87289.311 November 18, 2004 20:31 GMT
608.267: [GC 608.268: [ParNew: 52274K->10357K(65280K), 0.1024975 secs] 52274K->10357K(502528K), 0.1026132 secs]
Excluding compile: iaik.security.md.SHA::a
The Developer Trace of J2EE Server is as below.
trc file: "D:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name : ID3718450
pid : 3964
system name : J2E
system nr. : 00
started at : Tue Feb 15 10:12:46 2005
arguments :
arg[00] : D:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC00_igtehydsapweb
arg[02] : -DSAPINFO=J2E_00_server
arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC00_igtehydsapweb
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host : igtehydsapweb
-> ms port : 3601
-> OS libs : D:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host : igtehydsapweb
-> ms port : 3601
-> os libs : D:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3718400 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3718450 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3718400 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID3718450 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 4256] Tue Feb 15 10:12:46 2005
[Thr 4256] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4256] JLaunchRequestQueueInit: create pipe listener thread
[Thr 3328] JLaunchRequestFunc: Thread 3328 started as listener thread for np messages.
[Thr 1800] WaitSyncSemThread: Thread 1800 started as semaphore monitor thread.
[Thr 4256] Tue Feb 15 10:12:47 2005
[Thr 4256] INFO: Invalid property value [JLaunchParameters/]
[Thr 4256] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c 2282]
[Thr 4256] [Node: server0] java home is set by profile parameter
Java Home: D:\j2sdk1.4.2_07
JStartupIReadSection: read node properties [ID3718450]
-> node name : server0
-> node type : server
-> java path : D:\j2sdk1.4.2_07
-> java parameters : -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 -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=D:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=D:/usr/sap/J2E/SYS/global/
-> java vm version : 1.4.2_07-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 512M
-> root path : D:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\J2E\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 : D:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout: 120000
[Thr 4256] JLaunchISetDebugMode: set debug mode [no]
[Thr 1784] JLaunchIStartFunc: Thread 1784 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Denv.class.path=D:\j2sdk1.4.2_07\%JAVA_HOME%\lib;
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -Dsun.io.useCanonCaches=false
-> arg[ 10]: -Djava.awt.headless=true
-> arg[ 11]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 12]: -verbose:gc
-> arg[ 13]: -XX:+PrintGCDetails
-> arg[ 14]: -XX:+PrintGCTimeStamps
-> arg[ 15]: -XX:+UseParNewGC
-> arg[ 16]: -XX:MaxNewSize=85M
-> arg[ 17]: -XX:NewSize=85M
-> arg[ 18]: -XX:+DisableExplicitGC
-> arg[ 19]: -XX:MaxPermSize=192M
-> arg[ 20]: -XX:PermSize=192M
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Drdbms.driverLocation=D:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 24]: -Dsys.global.dir=D:/usr/sap/J2E/SYS/global/
-> arg[ 25]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
-> arg[ 26]: -Dapplication.home=D:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 27]: -Djava.class.path=D:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=D:\j2sdk1.4.2_07\jre\bin\server;D:\j2sdk1.4.2_07\jre\bin;D:\j2sdk1.4.2_07\bin;D:\usr\sap\J2E\JC00\j2ee\os_libs;D:\usr\sap\Python\.;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\j2sdk1.4.2_07\bin;;D:\usr\sap\J2E\SCS01\exe;D:\usr\sap\J2E\JC00\exe;D:\usr\sap\J2E\SYS\exe\run
-> arg[ 29]: -Dmemory.manager=512M
-> arg[ 30]: -Xmx512M
-> arg[ 31]: -Xms512M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=3964
-> arg[ 35]: -Djstartup.ownHardwareId=W0450436801
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=no
-> arg[ 38]: -DSAPINFO=J2E_00_server
-> arg[ 39]: -DSAPSTARTUP=1
-> arg[ 40]: -DSAPSYSTEM=00
-> arg[ 41]: -DSAPSYSTEMNAME=J2E
-> arg[ 42]: -DSAPMYNAME=igtehydsapweb_J2E_00
-> arg[ 43]: -DSAPDBHOST=
-> arg[ 44]: -Dj2ee.dbhost=igtehydsapweb
[Thr 1784] Tue Feb 15 10:12:48 2005
[Thr 1784] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 3104] Tue Feb 15 10:12:56 2005
[Thr 3104] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 3104] JLaunchISetClusterId: set cluster id 3718450
[Thr 3104] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 3104] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 3104] Tue Feb 15 10:18:15 2005
[Thr 3104] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
please do the needful.
regards,
sreeram

Hi Sreeram,
The reasons for this issue can be numerous and most of them will be present in the default trace in
/usr/sap/<SID>/JC<instance-nr>/j2ee/cluster/server<0..N>/log
It would be best to report an OSS message and let the support find the problem for you.
Best Regards: Iavor

Java DC wrapped in J2EE Server Comp Library DC

Hi Experts
I have jxl.jar file, I imported this jar file in a Java DC and declared jxl.jar as public part. I created a Webdynpro DC and used the public part in it. I have created an application, component and a view in it using some classes of jxl.jar. I created a new J2EE Server Component Library DC and used the public part of jxl.jar in it again. Built the J2EE Server Component Library DC. Once done I got a .sda file. I deployed it in server. Once this is done, I have added the J2EE Server Component Library DC in my Webdynpro DC's Library Reference. Once I added this, i built it and deployed it. I got deployment finished with Warnings. Please see the exception below and Please advice.
Exception from NWDS Deployment Screen
"java.rmi.RemoteException: Error occurred while starting application wrigley.com/signauth/ui and wait. Reason: Clusterwide exception: server ID 6840450:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application wrigley.com/signauthui for startup. Reason=Clusterwide exception: Failed to start dependent library ''signauth/libraryimpl'' of application ''wrigley.com/signauthui''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine?"
Names of the DCs used
Webdynpro DC - signauth/ui
J2EE Server Component DC - signauth/libraryimpl
Java External Library DC - signauth/library
FYI. I have created J2EE Server Component DC's name with more number of characters. Hope this shouldn't create issue. If this is also an issue, please let me know. I will reduce it and try.
Thank you
Best Regards
Ramamoorthy D

Hi Experts
Kindly help me out in getting a solution for this problem.
Thank you.
Best Regards
Ramamoorthy D

How to view the dispatched mails in J2EE server???

Hi All,
I want to view how many mails have been sent from the J2EE server. May I know how we can see this in NetWeaver AS JAVA? As we can view in ABAP stack using SOST tcode, this will show the list of user who have been sent mails from SAP system for a particular criterion. However, I dont find any such option in J2EE server. I see a challenge here to confirm to the buusiness that how many mails have been sent from J2EE server.
Please help me finding out a way to this.
Regards,
Fisal

Hi Mr!
If you want to generate the e-file feature 40ACK, do it in our Customization client box (Golden box) & save the request & move to Quality & production.
Still if you need to workout only in Production, than with the help of Basis people you can get the Production change mode for 5 to 10 min time & can generate it. But mostly Basis people wont give us change mode for Production box ... with ur request they can do..try it.
Did u collected 4 quarter TAN no's for 2008 Quarter...if not collect it & generate it at a time.
All the best:-)
Kind Regards,
Saisree.S

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, <b>"User or group data is missing"</b> 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

Regarding J2EE Server

Similar Messages

Maybe you are looking for