Message propreties in J2EE

hi ,
i would like to know how the message propreties files works in J2ee .
for exp , i have a web based application , which should be in many languages depending on the user ... all the static messages should be picked up from the messagePropreties file .
do you have any idea how does it works ? with J2EE
any tutorial ?
thanks for helping
yacine.

fandi_yacine wrote:
hi ,
i would like to know how the message propreties files works in J2ee .
for exp , i have a web based application , which should be in many languages depending on the user ... all the static messages should be picked up from the messagePropreties file .This is called internationalization and there are many tutorials out there.
Here is the one from Sun.
http://java.sun.com/docs/books/tutorial/i18n/index.html
Bon chance.

Similar Messages

Error message while starting J2EE Server!

Hi!
I get this error message when i try to start J2EE server:
c:\j2ee -verbose
Exception in thread "main" java.lang.NoSuchMethodError
at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImp
l.java:1256)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(Sh
utdownUtilDelegate.java:223)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(Shutdown
UtilDelegate.java:178)
at javax.rmi.CORBA.Util.writeAny(Util.java:80)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.re
bind(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(NamingManag
erImpl.java:192)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManag
erImpl.java:149)
at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.ja
va:473)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
Can someone tell me why?
Thanks

You need jsdk 1.3.1_03 or above to run j2ee 1.3.1 Any other version will give you this error.

Change encoding of input message sent by J2EE Adapter

Hi all,
I get a input message with a wrong encoding (Sender SMTP Adapter). Within XML prolog, there's a declaration of UTF-8. Having a look at the message, it's ISO-8859-1 encoded. That mean's I've to do one of the following options:
a) change encoding declaration in XML prolog to the correct one: ISO-8859-1
b) reencode the entire message from ISO-8859-1 into UTF-8, so that the message encoding matches the XML prolog
I've found two possible solutions, but I don't know if they're working:
1. usage of XMLAnomyzerModule: reading the documentation, it seems to be that I cannot use that module in a sender adapter, right? If I'm wrong: what does the module do? Does it just exchange the encoding declaration in the prolog or does it reencode the message?
2. running that small XSLT mapping before my own mapping: would it change the encoding declaration from UTF-8 to ISO-8859-1 in the XML prolog?
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" encoding="ISO-8859-1"/>
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
BR
Holger

Hi Stefan,
thanks for your reply. Unfortunately it's not my application who's sending the wrong message and it's not possible to change it on sender side. I don't know why but it's like that
So it's exactly like you've mentioned: when using special characters where ISO-8859-1 codepage differs from UTF-8, we've a problem.
When I understand you correct there's a adapter module TextCodepageConversionBean which changes the encoding, right? Then I could use it to encode the inbound ISO-8859-1 message to UTF-8 (which is declaration in XML prolog).
Where can I find more information how to use it? Searching SDN I've just found one other thread where the same module is mentioned, but without further hints.
BR
Holger

"Unsupported platform" error message while installing J2EE ref impl

Hi,
OS of my m/c is windows 2000. I downloaded the windows version of Sun Java System Application Server Platform Edition 8.1 2005Q1. When I tried to install this executable then "Unsupported platform" error messge is reported with a warning that aplication may not behave properly after installation.
Please suggest the remedy.
Thanks,
Hari

What is the SP level of that system? Installer will issue this message if SP2 or higher is not installed on the Windows 2000 system. So, one way to resolve this is to install current SP.
As for the remedy, this is just a warning - you can still choose to proceed with installation when this screen shows up and everything is likely to be fine even if you don't update the system.

Restart of J2EE failed messages

Hello,
is there a job or a process which I can schedule to restart failed messages in the J2EE Adapter. I know the job for the messages on the ABAP Stack before they are handed over to the J2EE Adapter. At the moment we do it by hand but we would like to have an automatic process or job repeat the failed messages.
Has anyone done this?
Thanks
Stefan

Hi Stefan,
Messages in the Adapter Framework are automatically retried 3 times (default). There is a parameter in one of the AF-related services in Visual Admin that determines this count (I think under XI AF Messaging System). Beyond that, I don't think you can do anything automatically
Regards,
Thorsten

J2EE RI: error in creating Oracle XA Datasource

I want to use the Oracle XA driver within Sun's J2EE Reference Implementation.
So I put the JDBC driver JAR files to the $J2EE_HOME/lib/system directory and add it to the J2EE_CLASSPATH environment variable.
Then I add the XA Datasource with the following command:
j2eeadmin -addJdbcXADatasource jdbc/MyXADB oracle.jdbc.xa.client.OracleXADataSource
TEST_USER TEST_PWD -props serverName=myserver portNumber=1521 databaseName=work
driverType=thin
When I start the server an error occurs. The log file system.err contains the following error mesage:
Binding DataSource, name = jdbc/MyXADB, url = jdbc/MyXADB__xa
Binding DataSource, name = jdbc/MyXADB__xa, dataSource = oracle.jdbc.xa.client.OracleXADataSource@7b6643
Error in creating data source object: jdbc/MyXADB__xa
The log file error.log contains the following message:
Logging for J2EE Server Version: 1.3_01-b01 started at: Thu Oct 25 19:05:14 CEST 2001..
Using the Java HotSpot(TM) Client VM and the version number 1.3.1_01 from Sun Microsystems Inc..
VM is using the classpath: d:\j2sdkee1.3\lib\system\cloudscape.jar;d:\j2sdkee1.3\lib\system\tools.jar;d:\j2sdkee1.3\lib\cloudscape\RmiJdbc.jar;d:\j2sdkee1.3\lib\cloudscape\cloudclient.jar;d:\j2sdkee1.3\lib\classes;d:\j2sdkee1.3\classes;d:\j2sdkee1.3\lib\j2ee.jar;d:\j2sdkee1.3\lib\locale;d:\j2sdkee1.3\lib\system\classes12.zip;d:\j2sdkee1.3\lib\system\jndi.zip;d:\j2sdkee1.3\lib\system\jta.zip;d:\jdk1.3.1\lib\tools.jar;d:\j2sdkee1.3\lib\jhall.jar .
J2EE Home Directory has been set to: d:\j2sdkee1.3.
javax.naming.CommunicationException: java.rmi.MarshalException: CORBA BAD_PARAM 1398079494 Maybe; nested exception is:
     org.omg.CORBA.BAD_PARAM: minor code: 1398079494 completed: Maybe
     at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:226)
     at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:238)
     at javax.naming.InitialContext.rebind(InitialContext.java:370)
     at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:210)
     at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:169)
     at com.sun.enterprise.resource.ResourceInstaller.installJdbcXADataSources(ResourceInstaller.java:466)
     at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(ResourceInstaller.java:353)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:268)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:913)
Thank you for any help!

Hi Manfed,
I've got exactly the same problem mit j2sdkee 1.3.1. Have yor resolved the problem in the meantime?
If so, please post the solution. Thanks.
Helmut

Message in Message Monitor/ RWB stay forever in status DLNG

Hi,
We have a problem with a Message inside our J2EE Adapter. The message remains in the status DLNG forever.
We use SAP XI 3.0 Service Stack 13.
We have the following scenario:
When sending messages via the Oracle JDBC connection to the Receiver-Service, the
message keeps the delivering status and never fails if the message
fails on the database level. In this particular case, the message failed on the DB level due to a misconfigured trigger and due to unique constraints. The state of the messages can be resolved by cycling the entire J2EE engine.
How can I handle such a message that stay in DLNG status?! And why is it hanging there? I cannot restart the message, I cannot stop it I also cannot cancel it out of the RWB.
regards
Nesimi
Message was edited by: Nesimi Buelbuel

any solution to the problem mentioned here ?
we are also facing the same issue.
have tried all kinds of restarts.
any further help will be appreciated.
thanks,
gaurav

Message Queuing in a single instance: should we use Streams or AQ?

Hi,
We are going over the requirments for a new application, and it needs to have some king of queuing mechanism that table level triggers can add tasks to.
I instantly thought AQ as this is what I last used in the past, however now I see that there is Streams and "Streams AQ".
Has Streams superceded AQ? Is it a simpler concept / technology that does the same thing, or is it intended for a different role?
Thanks!
Kirk Brocas

AQ has appeared in Oracle8. Streams are only avalable in Oracle 9 (limited capabilities) and 10g, and they are build upon AQ.
Although using stright AQ from the trigger will solve your problem, the Streams would give you the following benefits:
1. They are mining redo logs, so there is no trigger perforance degradation within your app transaction.
2. You can declaratively specify the procedure (APPLY process in the stream terms and propagation RULES) to filter, dequeue and process your messages. Oracle will fire your procedure in the background. In AQ you have to program this process by yourself.
On the other hand, streams is a hard artillery more suited to be used as a basis for systems like CDC (change data capture) to provide near real-time update of your Data Warehouse - it is avalable in 10g.
If you need compatability with the earlier versions of Oracle - you have to stay with AQ. Even in Oracle 8 they function as advertized and we did a number of projects which are in production since 2003. Use both Java messaging interface from J2EE appserver and OCI clients - work like a charm!

J2EE Engine is not comming up.

Dear All,
I was trying to run BSP applications on BW to accomplish this I change WORKGROUP to domain to create FQDN.(NW04 is running on Windows 2003 server). My system is dual stack system.
After restart I can login to the ABAP system but & JAVA Engine is down. I can see the message in MMC "J2ee information unavailable". I go through the trace files below are the some part of traces.
dev_jcontrol
[Thr 520] JControlICheckProcessList: process SDM started (PID:5084)
[Thr 520] Thu Aug 21 04:42:20 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:6108) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process server0 (pid:2916) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process SDM (pid:5084) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
dev_dispatcher
[Thr 4560] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4560] JLaunchRequestQueueInit: create pipe listener thread
[Thr 4248] JLaunchRequestFunc: Thread 4248 started as listener thread for np messages.
[Thr 4220] WaitSyncSemThread: Thread 4220 started as semaphore monitor thread.
[Thr 4560] *** ERROR => JLaunchInitAdministration: Can't attach to administration shared memory (rc = 2) [jlnchxx.c    868]
[Thr 4560] *** ERROR => can't initialize JControl Administration [jlnchxx.c    372]
[Thr 4560] JLaunchCloseProgram: good bye (exitcode = 2)
std_server0.out
stdout/stderr redirect
node name   : server0
pid         : 3548
system name : BWT
system nr. : 10
started at : Thu Aug 21 04:42:15 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4424] *** ERROR => ShmCreate: Key=68 Inv.Size: req.=73488, alloc.=41168 [shmnt0.c     615]
Critical Error
Can't initialize JControl Administration
-> Unknown error code (rc = 2)
From above I am getting the error is because of Shared memory. My system is of 4 GB & 40 GB of Virtual memory. This problem occurs after changing from WORKGROUP to DOMAIN. I have given all the rights of local administrator to <SID>adm & SAPService<SID> user.
Please help me to resolve this issue.
Thanks & Regards,
Shambo

-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\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     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID106496700
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=bootstrap_ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_bootstrap_ID106496700.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_bootstrap_ID106496700.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_bootstrap_ID106496700
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] Thu Aug 21 04:41:55 2008
[Thr 520] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID106496750]
[Thr 520] [Node: server0 bootstrap] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID106496750]
-> node name          : server0 bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\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     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID106496750
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=bootstrap_ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_bootstrap_ID106496750.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_bootstrap_ID106496750.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_bootstrap_ID106496750
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] Thu Aug 21 04:41:59 2008
[Thr 520] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5488] JControlRequestFunc: Thread 5488 started as listener thread for np messages.
[Thr 520] [Node: dispatcher] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [ID106496700]
-> node name          : dispatcher
-> node type          : dispatcher
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.sy
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 545M
-> init heap size     : 545M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\dispatcher
-> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\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     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 520] [Node: server0] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [ID106496750]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.sy
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\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     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 51021
-> shutdown timeout   : 120000
[Thr 520] INFO: Invalid property value [Debbugable=yes]
[Thr 520] [Node: SDM] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name          : SDM
-> node type          : sdm
-> node execute       : yes
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    :
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 128M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\SDM\program
-> class path         : E:\usr\sap\BWT\DVEBMGS10\SDM\program\bin\SDM.jar
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs
-> main class         : SDMInternal
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters         : server sdmhome=E:\usr\sap\BWT\DVEBMGS10\SDM\program
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 520] JControlMSConnect: attached to message server (bwtraining/3900)
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
[Thr 4592] JControlMSMessageFunc: Thread 4592 started as listener thread for ms messages.
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:296)
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:5264)
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process SDM started (PID:2860)
[Thr 520] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 520] Thu Aug 21 04:42:04 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:296) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (1)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:4556)
[Thr 520] JControlICheckProcessList: process server0 (pid:5264) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (1)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:5344)
[Thr 520] JControlICheckProcessList: process SDM (pid:2860) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (1)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process SDM started (PID:3900)
[Thr 520] Thu Aug 21 04:42:09 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:4556) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (2)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:3008)
[Thr 520] JControlICheckProcessList: process server0 (pid:5344) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (2)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:5176)
[Thr 520] JControlICheckProcessList: process SDM (pid:3900) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (2)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] Thu Aug 21 04:42:10 2008
[Thr 520] JControlICheckProcessList: process SDM started (PID:2668)
[Thr 520] Thu Aug 21 04:42:15 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:3008) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (3)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:6108)
[Thr 520] JControlICheckProcessList: process server0 (pid:5176) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (3)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:2916)
[Thr 520] JControlICheckProcessList: process SDM (pid:2668) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (3)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process SDM started (PID:5084)
[Thr 520] Thu Aug 21 04:42:20 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:6108) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process server0 (pid:2916) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process SDM (pid:5084) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta

J2ee server problem with details

I 'm working on Win 2000 machine.
While starting the j2ee server from command line
with the command
j2ee -verbose
I am getting error message as follows
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(AnyImp
l.java:1256)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(Sh
utdownUtilDelegate.java:223)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(Shutdown
UtilDelegate.java:178)
at javax.rmi.CORBA.Util.writeAny(Util.java:80)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.re
bind(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(NamingManag
erImpl.java:192)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManag
erImpl.java:149)
at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.ja
va:473)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
Please help

J2EE server listen port: 1050
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Apps\J2SDKE~1.1\bin>j2ee.bat
J2EE server listen port: 1050
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Apps\J2SDKE~1.1\bin>j2ee.bat -verbose
J2EE server listen port: 1050
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Apps\J2SDKE~1.1\bin>j2ee.bat -verbose
J2EE server listen port: 1050
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
how bout this problem?

Com.sap.mw.jco.JCO$Exception starting the J2EE server 620

We are using J2EE 620 pl26, with the latest JCO, but often trying to acces the J2EE services like Mobile Engine Webconsole 21 or the WebEnabled Sapconsole 640 we recive the message:
'Dispatche runningbut no server connected'.
The J2EE dispatcher and server are started at Sap startup. Just after that time the J2EE is working fine, but after some time the J2EE server get down.
We found this message into the J2EE console_logs:
"RFCEngine: Server startup error, stopping "SAPProfile:F:\usr\sap\CAM\SYS\profile\CAM_DVEBMGS00_itmif089" :
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Fri Oct 15 09:58:20 CEST 2004.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 2 seconds.
Could not establish the lcom accepted connection: lcomListenCreate failed with rc 9"
We do not find any Oss notes for that.
Any advise is wellcome.
Regards

Hi Mauro,
normally when you apply a new SAP Kernel a frfclib.sar file is delivered. This frfclib file need to be copied to the J2EE directory /os_libs and need to be extracted there. This frfclib version must always match to the SAP Kernel version.
Ciao
tc

Cannot Find j2ee engine--RSPLAN

I have installed EP in my system.
But when i login to the system with Tcode RSPLAN and click on Start Modeller
I am getting the message "CAnnot find J2ee Engine"
Pls help

Hi Balaji,
Check this thead,
/message/2812976#2812976 [original link is broken]
regards
Juan
please reward with points if helpful

Cannot find J2EE egine

I have already j2ee engine running in the system
But when i execute the transaction rzplan and click on start wizard it is giving the message Cannot find J2EE engine
Pls help me

If somebody didn't realize, Balaji who faced this problem was in 2006 august. Not sure, if his issue is not yet resolved, its been more than 2 years!
Anyways, I checked the above link for another thread for similar error.. that's also unanswered.
For the integrated planning, the following JCo destinations must be created in the Web Dynpro Content administrator of the J2EE engine
BI_MODELDATA
BI_METADATA
WD_ALV_MODELDATA_DEST
WD_ALV_METADATA_DEST
and Note 901022 deals with "J2EE engine not found".
Hope this helps for someone who faces this problem in future.
cheers,
Debasis.

J2ee 1.3.1

I am using durable subscription on j2ee 1.3.1.
It works.
But after receiving serveral hundred JMS messages.
Its perfromance becomes slower.
I notice under directory installation/repository/hostname/db/JMSDB/seg0
create many *.data files.
I believe it stores those JMS messages.
Is there a way to clean up those expired JMS messages?
installation/bin/cleannup program will delete all JMS messages including
those none-expired JMS messages.
Is there any utility can cleanup only expired JMS messages?

The J2EE 1.3.1 RI is not meant to utilized in a deployment environment, it is meant to be used for prototyping.
If you are looking for something more performant, then I would download SJSAS 7.x PE if you must use J2EE 1.3 otherwise I would download SJSAS 8.0 PE or the J2EE 1.4 SDK. These are all allowed to be utilized outside of a development environment

Setting for J2EE server do not exist

Hi,
I have prepared a web service from a FM.
I can't test it from the WSADMIN since this system is not integrated to a J2EE server. So I get the error message "Setting for J2EE server do not exist"
I am able to generate the WSDL file from Tcode WSADMIN
How can I test this web service from a browser with a J2EE server? If browser not possible then how can I test this web service.
Thank you,
Sam

Hi Sam,
I am not sure if you can test the web services without a J2EE server. For
testing in wsadmin, you do not need the system to be integrated with a J2EE server. Only the details of any J2EE server in the landscape can be given in
wsadmin -> Goto -> Administration Settings .
Regards
Srikishan

Message propreties in J2EE

Similar Messages

Maybe you are looking for