Does SPNego works on a diferent J2EE engine?

Hi,
We will implement SSO using SPNego and we are wondering if we need the SAP WAS J2EE to instal the SPNego or we can use a diferent J2EE App server?
Thanx in Advanced!!

Gerardo,
You can check requirements on;
http://help.sap.com/saphelp_nw04/helpdata/en/43/4bd58c6c5e5f34e10000000a1553f6/frameset.htm
SAP only supports it on NW2004s SP06.
James

Similar Messages

BPEL Engine: How does it work?

"[BPEL].. Engines will come in a variety of form factors and use different techniques for runtime representation of processes, including:
* interpretative
* code generation
* Obj Oriented models of Activities
* reduction engine based on Pi-Calcolus and related concepts"
[P. Brown& M. Szefler]
How does it work Oracle version of BPEL Engine exactly? Does it make a package (.jar) of Java classes and process them like usual Web Applications?

It is based on a mix of the first 3 techniques. The code gene part is really internal and is more about just in time compilation and performance optimization than generation of a Java application. -Edwin

SAP J2EE Engine : does not work !!!

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

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

Does IC WebClient require a J2EE engine for any of its component

Does IC WebClient requires a J2EE engine for any of its component? What's the need to install j2ee engine on CRM server?
I would appreciate if anybody could give a good answer or any kind of documentation on it.

Prakash,
The answer is yes in terms of the J2EE enginge being required. It primarily handles your multichannel access and broadcast messaging for the call center. If you don't install it, then your IC webclient will not work correctly. We are not using the "telphony" features of the call center, but still installed the java piece so that the standard functionality would work correctly.
Good luck,
Stephen

J2EE engine does not start correctly

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

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

Dispatcher of J2EE Engine does not start

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

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

SAP J2EE Engine has stopped working suddenly

Hi,
I have only SAP J2EE stack in WebAs installed on a machine couple of months ago and all the while it was working fine.But suddenly one day (precisely monday)i see that J2EE Server node is not starting up. But the central instance (which has processes MsgServer.exe,Enserver.exe) has started sucessfully but not the server node instance.
I am getting the following error in the log file
<-- Error log message starts here----
>
[Thr 3108] Tue Nov 15 11:53:06 2005
[Thr 3108] *** ERROR => invalid return code of process [bootstrap] (exitcode=66) [jstartxx.c 1433]
[Thr 3108] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=66)
[Thr 3108] JControlCloseProgram: started (exitcode = 66)
[Thr 3108] JControlCloseProgram: good bye... (exitcode=66)
<-- Error log message starts here----
>
<- Trace error message starts here-->
#1.5#000E0C6021FB00000000001200000614000405862C538277#1131973734265#com.sap.sql.jdbc.NativeConnectionFactory##com.sap.sql.jdbc.NativeConnectionFactory#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Database/sql/jdbc#Java#com.sap.sql_0002##SQL error occurred on connection jdbc:datadirect:sqlserver://blrkecsaptst1:1433;databasename=J2E: code=18,456, state="28000", message="[DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPJ2EDB'.
=> (0,08001,[DataDirect][SQLServer JDBC Driver]An error occurred while attempting to log onto the database.)".#5#18456#28000#[DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPJ2EDB'.
=> (0,08001,[DataDirect][SQLServer JDBC Driver]An error occurred while attempting to log onto the database.)#jdbc:datadirect:sqlserver://blrkecsaptst1:1433;databasename=J2E#<null>#
#1.5#000E0C6021FB00000000001300000614000405862C5392D1#1131973734265#com.sap.sql.jdbc.NativeConnectionFactory##com.sap.sql.jdbc.NativeConnectionFactory#######Thread[Thread-1,5,main]##0#0#Error##Plain###java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPJ2EDB'.
 at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
 at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
 at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
 at com.ddtek.jdbc.base.BaseConnection.connect(Unknown Source)
 at com.ddtek.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
 at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
 at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
 at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:123)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:147)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerFactoryImpl.<init>(ConfigurationHandlerFactoryImpl.java:30)
 at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:180)
 at com.sap.engine.core.configuration.AbstractConfigurationManagerImpl.init(AbstractConfigurationManagerImpl.java:170)
 at com.sap.engine.core.Framework.loadSingleManager(Framework.java:396)
 at com.sap.engine.core.Framework.loadManagers(Framework.java:163)
 at com.sap.engine.core.Framework.start(Framework.java:97)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.boot.FrameThread.run(FrameThread.java:58)
 at java.lang.Thread.run(Thread.java:534)
#1.5#000E0C6021FB00000000001500000614000405862C53DC14#1131973734281#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Error while connecting to DB.
=======================================================
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:344)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:123)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:147)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerFactoryImpl.<init>(ConfigurationHandlerFactoryImpl.java:30)
 at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:180)
 at com.sap.engine.core.configuration.AbstractConfigurationManagerImpl.init(AbstractConfigurationManagerImpl.java:170)
 at com.sap.engine.core.Framework.loadSingleManager(Framework.java:396)
 at com.sap.engine.core.Framework.loadManagers(Framework.java:163)
 at com.sap.engine.core.Framework.start(Framework.java:97)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.boot.FrameThread.run(FrameThread.java:58)
 at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPJ2EDB'.
 at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
 at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
 at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
 at com.ddtek.jdbc.base.BaseConnection.connect(Unknown Source)
 at com.ddtek.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
 at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
 at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
 at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
 ... 15 more
#1.5#000E0C6021FB00020000000000000614000405862C5494F7#1131973734328#com.sap.engine.core.cluster.impl6.JoinPortListener##com.sap.engine.core.cluster.impl6.JoinPortListener.run()#######SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Plain###java.lang.NullPointerException#
#1.5#000E0C6021FB00020000000100000614000405862C5497CD#1131973734328#com.sap.engine.core.cluster.impl6.JoinPortListener##com.sap.engine.core.cluster.impl6.JoinPortListener.run()#######SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Plain###java.lang.NullPointerException
 at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.getClusterMonitor(ClusterManagerImpl.java:2254)
 at com.sap.engine.core.cluster.impl6.JoinPortListener.waitForThisElementConstruction(JoinPortListener.java:120)
 at com.sap.engine.core.cluster.impl6.JoinPortListener.access$000(JoinPortListener.java:30)
 at com.sap.engine.core.cluster.impl6.JoinPortListener$SocketProcessor.run(JoinPortListener.java:137)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
<--Trace error message ends here--->
I have't not changed any passwords of db users like SAPJ2EDB but i don't know why i am getting this error suddenly.
Can anyone throw light on this issue.
Thanks and Regards,
Satish

Hi Detlev,
The DB (SQL 2000) is started and i have verified through
Window service console and SQL Server Service Manager.
Even the Config tool (i.e offline tool) is throwing the following error message when started.
""PATHHASH" = ?#
#1.5#C000AC19E95B000100000008008420AE0004059711CA16E0#1132046303500#/System/Server##com.sap.engine.core.configuration#######Thread[AWT-EventQueue-0,6,main]##0#0#Error#1#com.sap.engine.core.configuration#Plain###[DataDirect][SQLServer JDBC Driver][SQLServer]Invalid object name 'J2EE_CONFIG'.
=======================================================
java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Invalid object name 'J2EE_CONFIG'.
 at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
 at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRPCNonCursorExecuteRequest.submitPrepare(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRPCExecuteRequest.doPrepExec(Unknown Source)
 at com.ddtek.jdbc.sqlserver.tds.TDSRPCExecuteRequest.execute(Unknown Source)
 at com.ddtek.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
 at com.ddtek.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at com.ddtek.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
 at com.ddtek.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
 at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:97)
 at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:270)
 at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:241)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getConfiguration(DBAccessDefault.java:578)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:102)
 at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:879)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:913)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:783)
 at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:694)
 at com.sap.engine.configtool.batch.Scanner.scan(Scanner.java:44)
 at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:100)
 at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:86)
 at com.sap.engine.configtool.visual.ConfigTool.scanAction(ConfigTool.java:237)
 at com.sap.engine.configtool.visual.ConfigTool.actionPerformed(ConfigTool.java:209)
 at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
 at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
 at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
 at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
 at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1113)
 at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:943)
 at java.awt.Component.processMouseEvent(Component.java:5100)
 at java.awt.Component.processEvent(Component.java:4897)
 at java.awt.Container.processEvent(Container.java:1569)
 at java.awt.Component.dispatchEventImpl(Component.java:3615)
 at java.awt.Container.dispatchEventImpl(Container.java:1627)
 at java.awt.Component.dispatchEvent(Component.java:3477)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
 at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
 at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
 at java.awt.Container.dispatchEventImpl(Container.java:1613)
 at java.awt.Window.dispatchEventImpl(Window.java:1606)
 at java.awt.Component.dispatchEvent(Component.java:3477)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
#1.5#C000AC19E95B000100000009008420AE0004059711CA16E0#1132046303500#/System/Logging##com.sap.tc.logging.FileLog.[setFormatter()]#######Thread[AWT-EventQueue-0,6,main]##0#0#Warning##Java#SAP_LOGGING_FORMATTER_ERROR##Trying to change a formatter on active log ! The reset() method must be first called!#1#.
system.log#
#1.5#C000AC19E95B00010000000A008420AE0004059711CA5178#1132046303515#/System/Server##com.sap.engine.core.configuration#######Thread[AWT-EventQueue-0,6,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###Properties for connect through secure store not set. Please check your connect properties. Trying to connect via plain user/password.#
#1.5#C000AC19E95B00010000000B008420AE0004059711CA5178#1132046303515#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory#######Thread[AWT-EventQueue-0,6,main]##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0015#com.sap.sql.log.OpenSQLResourceBundle#Value "" is not allowed for parameter .#2#url##
1)is it due to mismatch of the passwords of the user SAPJ2EDB in database and J2EE Engine and Securestore of config tool
2)is there some DB related problem ?
3)i think the problem is similar to this one
Netweaver's WebAS SDM process goes corrupt, exitcode=66
But the solution there is not so clear
4)After i changed the password both in the database as well as in configtool >Secure Tool>/jdbc/pool/J2E/password..but i am getting java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Invalid object name 'J2EE_CONFIG' this error.
Any idea on what needs to be done to fix this problem
Regards,
Satish

Java bean, works in Integration Engine but does not work in Adapter Engine.

In connection to the following thread:
PayloadZipBean - variable filename inside the archive
I am trying to use the same bean.
However I can see, that the bean is working correctly when I use Integration Engine.
But if I am using ICo (AAE) and using the same bean in the receiver, I can see, that the bean gets called but does not work correctly.
The audit log added to my bean shows, that the bean could read the filename correctly from the Dyanic Config in the message, but it cannot write the same into the message.
Could you please help on this?

Your above posted system details show multiple Java Console extensions.
You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.
See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions
See also http://www.java.com/en/download/help/quickstarter.xml - What is Java Quick Starter (JQS)? What is the benefit of running JQS? - 6.0
Disable the Java Quick Starter extension: Tools -> Addons -> Extensions
Control Panel -> Java -> Advanced tab -> Miscellaneous -> Java Quick Starter (disable)
You can try a direct connection: 
Control Panel > Java > General tab > "Network Settings...": "Direct Connection" (enable)

J2EE Engine does not start

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

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

Error CJS-20058 when applying J2EE Engine Patches SP19 and Disp+work.exe

Hello All ,
I am working on SAP XI SP9 (Stand alone J2ee Only). When I am trying to upgrade it SP 19 but it had failed at 17th ( Start J2ee Engine ) step . I am getting following error.
ERROR 2007-04-15 06:52:41
CJS-20058 Java EE Engine DVEBMGS00 of SAP system XI3 did not reach state "Starting Applications" after 1033 seconds: giving up.
and after that Disp+Work process is completely failed to start in SAPMMC.
Operating System :- Windows 2003
Database :- Oracle 9.2.0.4
Please Guide me on this.
Thanks & Regards,
Suresh.K

Hi Sunil,
im sending following files,
disp+work.exe Developer Traces
trc file: "dev_disp", trc level: 1, release: "640"
Tue Apr 17 08:36:33 2007
kernel runs with dp version 133000(ext=102000) (@(#) DPLIB-INT-VERSION-133000-UC)
length of sys_adm_ext is 524 bytes
sysno 00
sid XI3
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 155
intno 20020600
make: multithreaded, Unicode
pid 3584
***LOG Q00=> DpSapEnvInit, DPStart (00 3584) [dpxxdisp.c 1100]
 shared lib "dw_xml.dll" version 155 successfully loaded
 shared lib "dw_xtc.dll" version 155 successfully loaded
 shared lib "dw_stl.dll" version 155 successfully loaded
 shared lib "dw_gui.dll" version 155 successfully loaded
 shared lib "dw_mdm.dll" version 155 successfully loaded
Tue Apr 17 08:36:38 2007
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3896]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpIPCInit2: start server >dlwsdb10_XI3_00 <
DpShMCreate: sizeof(wp_adm) 10528 (1316)
DpShMCreate: sizeof(tm_adm) 2969176 (14772)
DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpShMCreate: sizeof(comm_adm) 290000 (580)
DpShMCreate: sizeof(vmc_adm) 0 (424)
DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
DpShMCreate: SHM_DP_ADM_KEY (addr: 06AA0040, size: 3381680)
DpShMCreate: allocated sys_adm at 06AA0040
DpShMCreate: allocated wp_adm at 06AA1B88
DpShMCreate: allocated tm_adm_list at 06AA44A8
DpShMCreate: allocated tm_adm at 06AA44D0
DpShMCreate: allocated wp_ca_adm at 06D79328
DpShMCreate: allocated appc_ca_adm at 06D7F0E8
DpShMCreate: allocated comm_adm_list at 06D81028
DpShMCreate: allocated comm_adm at 06D81040
DpShMCreate: allocated vmc_adm_list at 06DC7D10
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 06DC7D38
DpShMCreate: allocated wall_adm at 06DC7D40
MBUF state OFF
Tue Apr 17 08:36:39 2007
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 2207 blocks reserved for free list.
ES initialized.
Tue Apr 17 08:36:41 2007
J2EE server info
start = TRUE
state = STARTED
pid = 3800
argv[0] = D:\usr\sap\XI3\DVEBMGS00/j2ee/os_libs/jcontrol.exe
argv[1] = D:\usr\sap\XI3\DVEBMGS00/j2ee/os_libs/jcontrol.exe
argv[2] = pf=D:\usr\sap\XI3\SYS\profile\XI3_DVEBMGS00_dlwsdb10
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1303
argv[5] = -DLISTEN_PORT=1304
argv[6] = -DSAPSYSTEM=00
argv[7] = -DSAPSYSTEMNAME=XI3
argv[8] = -DSAPMYNAME=dlwsdb10_XI3_00
argv[9] = -DSAPPROFILE=D:\usr\sap\XI3\SYS\profile\XI3_DVEBMGS00_dlwsdb10
argv[10] = -DFRFC_FALLBACK=ON
argv[11] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
Tue Apr 17 08:36:42 2007
rdisp/http_min_wait_dia_wp : 1 -> 1
Tue Apr 17 08:36:43 2007
***LOG CPS=> DpLoopInit, ICU ( 2.6.1 2.6 4.0) [dpxxdisp.c 1468]
***LOG Q0K=> DpMsAttach, mscon ( dlwsdb10) [dpxxdisp.c 10036]
DpStartStopMsg: send start message (myname is >dlwsdb10_XI3_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Tue Apr 17 08:36:44 2007
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 155
Release check o.K.
DpJ2eeLogin: j2ee state = CONNECTED
Tue Apr 17 08:37:24 2007
ERROR => W0 (pid 2888) died [dpxxdisp.c 12562]
ERROR => W1 (pid 2724) died [dpxxdisp.c 12562]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W2 (pid 2324) died [dpxxdisp.c 12562]
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => W3 (pid 2796) died [dpxxdisp.c 12562]
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => W4 (pid 1172) died [dpxxdisp.c 12562]
ERROR => W5 (pid 1272) died [dpxxdisp.c 12562]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W6 (pid 1508) died [dpxxdisp.c 12562]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W7 (pid 1704) died [dpxxdisp.c 12562]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
killing W0-2888 (SIGUSR2)
ERROR => DpWpKill(2888, SIGUSR2) failed [dpxxtool.c 2507]
killing W1-2724 (SIGUSR2)
ERROR => DpWpKill(2724, SIGUSR2) failed [dpxxtool.c 2507]
killing W2-2324 (SIGUSR2)
ERROR => DpWpKill(2324, SIGUSR2) failed [dpxxtool.c 2507]
killing W3-2796 (SIGUSR2)
ERROR => DpWpKill(2796, SIGUSR2) failed [dpxxtool.c 2507]
killing W4-1172 (SIGUSR2)
ERROR => DpWpKill(1172, SIGUSR2) failed [dpxxtool.c 2507]
killing W5-1272 (SIGUSR2)
ERROR => DpWpKill(1272, SIGUSR2) failed [dpxxtool.c 2507]
killing W6-1508 (SIGUSR2)
ERROR => DpWpKill(1508, SIGUSR2) failed [dpxxtool.c 2507]
killing W7-1704 (SIGUSR2)
ERROR => DpWpKill(1704, SIGUSR2) failed [dpxxtool.c 2507]
NiWait: sleep (10000 msecs) ...
NiISelect: timeout 10000 ms
NiISelect: maximum fd=1625
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Dev_w0
trc file: "dev_w0", trc level: 1, release: "640"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
B
B Tue Apr 17 01:31:26 2007
B create_con (con_name=R/3)
B *** ERROR => Invalid profile parameter dbms/type (or environment variable dbms_type) = <undef>, cannot load DB library
[dbcon.c 4484]
M sysno 00
M sid XI3
M systemid 560 (PC with Windows NT)
M relno 6400
M patchlevel 0
M patchno 155
M intno 20020600
M make: multithreaded, Unicode
M pid 524
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 524) [dpxxdisp.c 1160]
I MtxInit: -2 0 0
M DpSysAdmExtCreate: ABAP is active
M
M Tue Apr 17 01:31:27 2007
M DpShMCreate: sizeof(wp_adm) 10528 (1316)
M DpShMCreate: sizeof(tm_adm) 2969176 (14772)
M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
M DpShMCreate: sizeof(comm_adm) 290000 (580)
M DpShMCreate: sizeof(vmc_adm) 0 (424)
M DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
M DpShMCreate: SHM_DP_ADM_KEY (addr: 072A0040, size: 3381680)
M DpShMCreate: allocated sys_adm at 072A0040
M DpShMCreate: allocated wp_adm at 072A1B88
M DpShMCreate: allocated tm_adm_list at 072A44A8
M DpShMCreate: allocated tm_adm at 072A44D0
M DpShMCreate: allocated wp_ca_adm at 07579328
M DpShMCreate: allocated appc_ca_adm at 0757F0E8
M DpShMCreate: allocated comm_adm_list at 07581028
M DpShMCreate: allocated comm_adm at 07581040
M DpShMCreate: allocated vmc_adm_list at 075C7D10
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 075C7D38
M DpShMCreate: allocated wall_adm at 075C7D40
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M calling db_connect ...
B create_con (con_name=R/3)
B *** ERROR => Invalid profile parameter dbms/type (or environment variable dbms_type) = <undef>, cannot load DB library
[dbcon.c 4484]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 008192) [thxxhead.c 1284]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9598]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source = 255
M last_tid = 0
M last_mode = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M
M *****************************************************************************
M *
M * LOCATION SAP-Server dlwsdb10_XI3_00 on host dlwsdb10 (wp 0)
M * ERROR tskh_init: db_connect
M *
M * TIME Tue Apr 17 01:31:27 2007
M * RELEASE 640
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 9783
M * COUNTER 1
M Tue Apr 17 01:31:28 2007
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 730]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 254]
M Entering ThSetStatError
Dev_rd
trc file: "dev_rd", trc level: 1, release: "640"
Tue Apr 17 08:36:40 2007
***LOG S00=> GwInitReader, gateway started ( 384) [gwxxrd.c 1627]
relno 6400
patchlevel 0
patchno 155
intno 20020600
pid 384
unicode active
gateway runs with dp version 133000(ext=102000) (@(#) DPLIB-INT-VERSION-133000-UC)
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
Tue Apr 17 08:36:41 2007
Bind service sapgw00 (datagram) to port 3300
Bind service sapgw00 (datagram) to port 3300
Bind service sapgw00 (socket) to port 3300
GwPrintMyHostAddr: my host addresses are :
1 : [10.20.2.157] dlwsdb10 (HOSTNAME)
2 : [127.0.0.1] dlwsdb10.i2.com (LOCALHOST)
MtxInit: -2 0 0
DpSysAdmExtCreate: ABAP is active
DpShMCreate: sizeof(wp_adm) 10528 (1316)
DpShMCreate: sizeof(tm_adm) 2969176 (14772)
DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpShMCreate: sizeof(comm_adm) 290000 (580)
DpShMCreate: sizeof(vmc_adm) 0 (424)
DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
DpShMCreate: SHM_DP_ADM_KEY (addr: 06DE0040, size: 3381680)
DpShMCreate: allocated sys_adm at 06DE0040
DpShMCreate: allocated wp_adm at 06DE1B88
DpShMCreate: allocated tm_adm_list at 06DE44A8
DpShMCreate: allocated tm_adm at 06DE44D0
DpShMCreate: allocated appc_ca_adm at 070BF0E8
DpShMCreate: allocated comm_adm_list at 070C1028
DpShMCreate: allocated comm_adm at 070C1040
DpShMCreate: allocated vmc_adm_list at 07107D10
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 07107D38
Tue Apr 17 08:37:40 2007
***LOG S30=> GwStopGateway, gateway stopped () [gwxxrd.c 13334]
Dev_Jcmon
trc file: "D:\usr\sap\XI3\DVEBMGS00\work\dev_jcmon", trc level: 1, release: "640"
node name : jcmon
pid : 4896
system name : XI3
system nr. : 00
started at : Mon Apr 16 00:03:28 2007
arguments :
 arg[00] : D:\usr\sap/XI3/DVEBMGS00/j2ee/os_libs/jcmon.exe
 arg[01] : pf=D:\usr\sap\XI3\SYS\profile/XI3_DVEBMGS00_dlwsdb10
[Thr 3668] Mon Apr 16 00:03:28 2007
[Thr 3668] INFO: Unknown property [box.number=XI3DVEBMGS00dlwsdb10]
[Thr 3668] INFO: Unknown property [ms.host=dlwsdb10]
[Thr 3668] INFO: Unknown property [ms.port=3601]
[Thr 3668] INFO: Unknown property [system.id=0]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\instance.properties;D:\usr\sap\XI3\DVEBMGS00\SDM\program\config\sdm_jstartup.properties]
-> ms host : dlwsdb10
-> ms port : 3601
-> OS libs : D:\usr\sap\XI3\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
[Thr 3668] Mon Apr 16 00:03:29 2007
[Thr 3668] *** ERROR => Can't attach to administration shared memory (rc=3) [jcmonxx.c 217]
Please help me,
Regards,
Suresh.K

Does anyone know how travel meta search engines work? (kayak,mobissimo)

Does anyone know how travel meta search engines work? like (mobissimo,kayak,TravelJungle.co.uk)

Thanks for your reply BalusC
i agree with u.
the sites like kayak, mobissimo are using spider tool to get data from other sites(airline site, etc..).
and they are using jquery with php pages. these sites are airline ticket booking sites.
my questions are:-
how can they get flight information without any GDS help?
can a spider program/tool fetch the realtime data?
i had experience in implementation of client side web services for GDS(worldspan,amadeus).
but i am not have any experience with travel meta search engine applications..
thats way a need help from seniors...

Cannot deploy app files to j2ee engine in NWDS

Hi,
I`ve got NWDS ver. 2.0.15 and I am trying to deploy some files to app server but I got message
Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
I am almost 100% it`s because I need to use proxy to connect the server. I set up proxy settings in window->preferences->workbench->proxy but I think this option doesn't affect to j2ee engine connection. Cause for example I can access portal on port 50000 using my browser (with set up proxy), but I cannot deploy PAR file what`s more the settings window->preferences->SAP Enterprise portal are correct and the same which I used to connect portal using web browser.
I was thinking about other way to check the connection and SDM Remote GUI came on my mind. Does anybody know how to set up proxy in this program?

Rich,
I did it and I am absolutley sure that host and message server are correct. I think that the problem is that to connect server the connection should be via proxy. And I think beacuse of it connection desnt work.
Look at my example I can connect portal via web browser with configured proxy, but I cannot deploy PAR file using NWDS with the same port and host as I used in browser.
I have configured proxy in NWDS (window->preferences->workbench->proxy) but I am affraid that this setting doesnt take affect to j2ee engine settings and Enterprise portal deployment settings.
Now I am looking for tool which gives me possibility to connect SDM some other way with proxy. Or maybe there is some soft that allows me to set all outgoing network connections to go via proxy.

Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

Hi,
I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
The following is the part of log file.
#1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[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:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
 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#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##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.#
Please help me to solve the issue.
Thanks,
Ajay.

Hi Tim,
I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps as per below URL
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
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:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
 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
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jun 25, 2010 3:05:24 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
Thanks,
Ajay.

Time out error on deploying to SAP-J2EE engine.

I got a problem while deploying to SAP-J2EE engine using ant. It takes a lot of time and then throws a time out error.
The problem is with the web.xml file pointing to a DTD in the internet, I have pasted some part of the web.xml below,
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
 <display-name>MyPay</display-name>
 <description>MyPay</description>
Once I write down the DTD description in the web.xml itself, it works fine.
I have pasted the error trace below,
j2eedeploy:
 [echo] Deploying to Local environment...
 [echo] C:\Java\Projects/MyPay/dist/MyPay.ear
BUILD FAILED
C:\Java\Projects\MyPay\build.xml:445: java.lang.RuntimeException: ERROR: ID90507: Error occured during getting EARDescriptor : Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
Exception is :
java.io.IOException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
 at com.sap.engine.lib.xml.parser.URLLoaderBase.resolveEntity(URLLoaderBase.java:148)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDTD(XMLParser.java:1271)
 at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2795)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
 at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
 at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
 at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:127)
 at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:120)
 at com.inqmy.services.servlets_jsp.descriptor.jar.WebWar.getWebDescriptor(WebWar.java:98)
 at com.inqmy.deploy.tool.deployer.ExtendedEarReader.loadDescriptorFromFile(ExtendedEarReader.java:175)
 at com.inqmy.deploy.tool.deployer.ExtendedEarReader.getFullEarDescriptor(ExtendedEarReader.java:104)
 at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:355)
 at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:325)
 at com.pg.sap.deploy620.SAPDeploy620Manager.process(SAPDeploy620Manager.java:84)
 at com.pg.ant.tasks.j2ee620.J2ee620EngineDeployTask.execute(J2ee620EngineDeployTask.java:40)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 at org.apache.tools.ant.Task.perform(Task.java:364)
 at org.apache.tools.ant.Target.execute(Target.java:341)
 at org.apache.tools.ant.Target.performTasks(Target.java:369)
 at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
 at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)

Thanks for your reply Kalyan,
The problem seems to be with my system, because I had run the same ant script in another system and it deployed successfully.
The problem does not seem to be with the dtd, whereas it seems that the SAP-J2EE engine is not able to open the link to the dtd giving a time out error.
Is it possible to switch off the validation process of the SAP-J2EE engine of an xml with the dtd?

J2EE engine shuts down and restarts....

Hi,
I am doing a scenrio using BPM with multiple parallel process. I am using a inbound file adapter for the incoming message to feed the BPM process. I have set 500 messages/per recordset.The process is stable when the message size is small but when the message size increases may be to 2MB,the J2EE engine collapses and restarts a certain period of time.
When I look at the incoming messages they seem to have failed at the BPM process. I am not sure what is causing the J2EE engine to collapse and restart...It works fine with less than 1MB incoming messages....Does it mean XI cannot support messages greater than 1MB? I know its absurd but this is very interesting..Checking the SMICM, I find the processes are all normal...
-Teresa

Hi :
Did u checked up the java heap parameters in the configtool set for the server
Raise the heap parameters as per the following steps
1) Open up the configtool and increase the heap size and memory size for the server
Cluster Data -> instance_IDXXX -> ServerIDXXXX
Max heap Size 2048MB
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
-Xdebug
-Xms1280m
-Xmx3072m
-XX:MaxPermSize=192m
-XX:NewSize=160m
-XX:MaxNewSize=160m
-XX:NewRatio=3
-XX:+DisableExplicitGC
-verbose:gc
-XX:+PrintCompilation
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-XX:PermSize=192m
-XX:+UseParNewGC
-XX:+PrintGCTimeStamps
-XX:SoftRefLRUPolicyMSPerMB=1
-Djava.awt.headless=true
2) Restart the server using Visual Administrator
3) open up the configtool again to ensure that the settings you have set in the config tool are available
4) Now check whether the problem occurs again or not
regards & cheers
karthik

Does SPNego works on a diferent J2EE engine?

Similar Messages

Maybe you are looking for