Upgrade J2ee Engine 1.4.2_06 to 1.4.2_11
Hi,
In our production XI3.0 SP16 server j2ee engine sutting down if we run many jobs at a time. Currently we are using j2ee 1.4.2_06 , this problem happend due to j2ee engine unstability.
SAP note says that need to upgrade j2ee from 1.4.2_06 to 1.4.2_11 . Not sure how to do this at OS level and after that where to change parameters for new java 1.4.2_11 settings.
Before that what files/folders need to take backup.Any idea how to upgrade.
-cheers !
Hi Lisa,
It's known problem in XI. But Apart from SP06, some more reasons are there....
First, Let me know the RAM size... As utilization increases, due to lack of memory, first J2EE engine stops... Because, J2EE engine needs lots of resources.
Normally, For 200 Documents/Hr needs 4GB to 6GB RAM.
Next, There are some standard memory parameter setting which should be set by Basis during installation. That can be changed as per requirement like paging area etc. (I am not sure, which one is required). But this too worked for us.
Regards,
Audy
Similar Messages
-
Problem Connecting to J2ee engine for EP6.o
Hello Gurus,
Help needed..I tried my best in searching several OSS notes but none helped me.
We installed EP6.0 on HPUX 11.1/Oracle 9.2.04
I upgrades J2ee Engine to patchlevel 17.
WHen trying to apply SP2 using SDM, it is erroring out : unable to connect to J2ee with Administrator!!
I launched j2ee admin console and trying to connect(port 50104), user: Administrator, Password none, but in vain.The folowing error is coming:
javax.naming.NamingException:Connection lost
ID003814: !UNSOLICITED! JNDI Exception in getInitialContext of initialCOntextFactoryImpl [Root exception is com.inqmy.services.rmi_p4.P4IOException:Connect
I am able to connect to j2ee engine using telnet to 50108 port with user: Administrator withoout any password.
When I do lsc..it is listing dispatcher (port 50110) and Server (port 50120).
I started the portal (system # 01) and the element joined ...(Element 628068834 joined)
But when I try to connect to the portal using explorer
(http:/myserver:80100 or http:/myserver:80100/irj) , I am getting the following error:
Dispatcher running, but no server connected!
Earlier to applying J2ee ENgine patch 17, I was able to connect to the portal.
Please help me understand what is going on with our EP installation and any experiences/guidance to bring life to EP6.0
thank in advance.
paparaju buddhavarapPaparaju -
1. How are you starting the portal (i.e. go scripts or unixdaemon)?
2. Is the R/3 startup service set to Manual?
If it is not, I'd recommend setting to manual and shutting down all portal processes before restarting.
Regards,
Kyle -
How to Upgrade java version on J2EE Engine Server?
Hi Experts,
We are running the NetWeaver 2004s SP 7 with Java version 1.4.2_08 on the server, but we would like to upgrade the system and be able to upgrade to Java version 1.5. How do we start? We would greatly appreciate your responses.
Thanks,
-Don P.but we would like to upgrade the system and be able to upgrade to Java version 1.5
Can you explain this more accurately? For example the OS version
Are you say about SUN or IBM JDK? I'm think you say about SUN JDK ...when only 1.4.2.XXXX can be installed for
NW 7.0, Do not use
Java version 1.5
In any case Try to check the
Note 709140 - Recommended JDK and VM Settings for the WebAS630/640/7.0
You will see all JDK/OS mixes and link's to recuired notes ....
About how to change java version, for example to newest release ? -->
Note 718901 - How to Change the JDK of the J2EE Engine
Regards. -
How to uninstall J2EE Engine 6.20 from BW 3.1 before starting upgrade BI
Hi all,
We hav BW 3.1 cont installed with J2EE Engine 6.20 and we started upgrade to BI 7.0
6.20 J2EE engine is of no use...so we planned to uninstall it before starting the upgrade and install as ADD in once the upgrade is over.
and we uninstalled also
When i start the SAPup phase its given info like J2EE Engine is running....
but nothing s running....
Pls advice on this
Regards
Karthikthnx
-
J2EE Engine Jcontrol Error :Oracle upgrade 10 to11 :ODBC driver Solution
Hello Every one,
To make a valuable information for Oracle upgrade from Oracle 10 to oracle 11.2.0.2 on Java environment.
Please do the following changes to avoid JDBC driver version error.
Memo : When The upgrade happens the JDBC drivers are overwritten under drive:/oracle/.../JDBC/lib
you will not see classes12.jar and nls_charset12.jar which is a part of Oracle 10 and JDBC driver version. Thereis no such files for Oracle 11. The application is not supported under Oracle 11.
Following steps will make the J2ee Engine work.
1. Upgrade SDK to 1.6. and verify using Java -version. Set Path and Class path.
2. Since the Jdk is changed now do update in this 3 files
a. SID_JC01_hostname
In this file update the parameter "jstartup/vm/home = C:\Program Files\Java\jdk1.6.0_26"
b. Also for SID_SCS00_Hostname
3. Check for j2ee/dbdriver = $(DIR_EXECUTABLE)\ojdbc14.jar which can work with this version at this time or need to change to ojdbc6.jar
in profile parameter, bootstrap properties (:\usr\sap\sid\jc01\j2ee\cluster\bootstrap), and template configuaration file in usr\sap\sid\jc01\j2ee
4. Copy classes12.jar and nls_charset12.jar in \oracle\jdbc\lib from any Oracle 10 installation. and set in classpath.
5. Hope last the password in secure store is correct.
Restart the cluster.
This is exclusively of your oracle is upgraded and J2ee does not come up.
Regards,
Chetan Poojary.I think you'd need to contact Oracle support to get access to older versions of the driver.
Since 8.0.5 isn't supported any longer, however, is it possible for you to update your Oracle client to one of the supported releases-- 8.1.7 or 9i?
Justin -
Exit Code -11114 J2EE Engine doesn't start completely. DESPERATE
XI system - Windows - Oracle - ABAP + Java Stack
We would like to upgrade our J2EE Engine Version however, during the upgrade, there is a phase wherein the J2EE Engine is being started. But, as it is being started, it returns an error and it provides the message Exit Code -11114 and it starts restarts the J2EE Instance automatically over and over again. I've read a forum here that resolved this error. However, the scenario wherein the data source is database_only is not applicable to our case since our data source is already dataSourceConfiguration_r3_roles_db.xml. Furthermore, I've read in one of the logs that indicates that: Critical shutdown was invoked. Reason is: 5 core services have timed out http://adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin. Hope you could help us out! Please help us! This is affecting the business operation since the server 0 doesn't startup completely, thus the java sites are all inaccessible.
Here is one part of the trace.
#1.5#0015C588AED40047000001690000141800044578CA30039C#1202284997468#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/com.sap.aii.af.sdk.rnif.message.listener] application.
The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/com.sap.aii.af.sdk.rnif.message.listener.
Exception id: [0015C588AED40047000001670000141800044578CA300130]#
#1.5#0015C588AED400470000016E0000141800044578CA30A0A8#1202284997515#com.sap.engine.services.servlets_jsp.Deploy##com.sap.engine.services.servlets_jsp.Deploy#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application. The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.servlets_jsp.server.container.StopAction.unBindApp(StopAction.java:92)
at com.sap.engine.services.servlets_jsp.server.container.StopAction.commitStop(StopAction.java:56)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.commitStop(WebContainer.java:419)
at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:262)
at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:305)
at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:296)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:117)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:235)
at com.sap.engine.services.deploy.server.FinishListener.run(FinishListener.java:77)
at com.sap.engine.services.deploy.server.FinishListener.makeOperation(FinishListener.java:57)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startTransactionsLocal(DeployServiceImpl.java:4183)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopMyApplications(DeployCommunicatorImpl.java:214)
at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:235)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
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)
#1.5#0015C588AED40047000001700000141800044578CA30A304#1202284997515#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application.
The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
Exception id: [0015C588AED400470000016E0000141800044578CA30A0A8]#
#1.5#0015C588AED4005D0000004A0000141800044578CA38DF9E#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_5]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: java.lang.Thread | toString: Thread[SAPEngine_EnquReader,5,main]] with classloader [com.sap.engine.boot.CoreClassLoader@a981ca]#
#1.5#0015C588AED4005D0000004B0000141800044578CA38F484#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_51]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.service630.container.ServiceStopper | toString: com.sap.engine.core.service630.container.ServiceStopper@122c960] with classloader [null]#
#1.5#0015C588AED4005D0000004C0000141800044578CA38F5B3#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_71]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]d2e636] with classloader [[email protected]5b6@service:log_configurator]#
#1.5#0015C588AED40047000001780000141800044578CA38F6DB#1202284998062#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Service servlet_jsp error java.lang.ThreadDeath during shutdown.#
#1.5#0015C588AED4005D0000004D0000141800044578CA3DA356#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_2]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.jms.WorkerHandlerImpl | toString: com.sap.aii.af.service.jms.WorkerHandlerImpl@81f25] with classloader [[email protected]b87f@service:com.sap.aii.adapter.jms.svc]#
#1.5#0015C588AED4005D0000004E0000141800044578CA3DA528#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_25]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory | toString: [email protected]2222] with classloader [[email protected]74b@common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore]#
#1.5#0015C588AED4005D0000004F0000141800044578CA3DA681#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_29]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.scheduler.JobBroker$Broker | toString: com.sap.aii.af.service.scheduler.JobBroker$Broker@134d801] with classloader [[email protected]619e@service:com.sap.aii.af.svc]#
#1.5#0015C588AED4005D000000500000141800044578CA3DA79A#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_32]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.adapter.xi.ms.SLDReader | toString: com.sap.aii.adapter.xi.ms.SLDReader@513bb5] with classloader [[email protected]4ab4@service:com.sap.aii.adapter.xi.svc]#
#1.5#0015C588AED4001900000000000034D800044578FAB55C7D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<super()>#
#1.5#0015C588AED4001900000001000034D800044578FAB58D2D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
#1.5#0015C588AED4001900000002000034D800044578FAB597E9#1202285811453#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
#1.5#0015C588AED4001900000003000034D800044578FAC784C7#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
#1.5#0015C588AED4001900000004000034D800044578FAC78D1C#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
#1.5#0015C588AED4000000000016000034D8000445790BF2E967#1202286100703#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Wed Feb 06 16:21:40 CST 2008 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
Service com.sap.aii.af.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service com.sap.aii.adapter.marketplace.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service ejb > hard reference to interface security.
Service com.sap.aii.af.security.service > hard reference to service keystore.
Service ssl > hard reference to service keystore.
Service com.sap.aii.adapter.jms.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service adminadapter > hard reference to service jmx.
Service tcsecsecurestorage~service > hard reference to service keystore.
Service pmi > hard reference to service tcsecdestinations~service.
Service security > hard reference to service com.sap.security.core.ume.service.
Service jms_provider > hard reference to service security.
Service sld > hard reference to service tcsecsecurestorage~service.
Service jmx > hard reference to interface security.
Service rfcengine > hard reference to service ejb.
Service tcsecsaml~service > hard reference to service adminadapter.
Service telnet > hard reference to service shell.
Service com.sap.aii.adapter.jdbc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service tclmctcculculservice_sda > hard reference to service jmx.
Service webdynpro > hard reference to interface shell.
Service tcsecvsiservice > hard reference to service tcsecdestinationsservice.
Service tceCATTPingservice > hard reference to interface shell.
Service com.sap.aii.af.ispeak.svc > hard reference to service applocking.
Service tcsecdestinationsservice > hard reference to service tcsecsecurestorageservice.
Service dsr > hard reference to service security.
Service keystore > hard reference to service security.
Service applocking > hard reference to service security.
Service tclmctcculservice_sda > hard reference to service jmx.
Service monitor > hard reference to service jmx.
Service com.sap.security.core.ume.service > service com.sap.security.core.ume.service start method invoked.
Service com.sap.aii.adapter.bc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service com.sap.aii.adapter.rfc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service tc.monitoring.logviewer > hard reference to service jmx.
Service apptracing > hard reference to service jmx.
Service com.sap.aii.af.ms.svc > hard reference to service com.sap.aii.af.svc.
Service com.sap.aii.af.cpa.svc > hard reference to service sld.
Service shell > hard reference to interface security.
Service tcsecwssecservice > hard reference to service tcsecsecurestorageservice.
Service com.sap.aii.adapter.mail.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service servlet_jsp > hard reference to interface security.
Service com.sap.aii.adapter.file.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service classload > hard reference to service security.
Service basicadmin > hard reference to service jmx.
Service com.sap.aii.adapter.xi.svc > hard reference to service com.sap.aii.af.cpa.svc.
#1.5#0015C588AED4000000000018000034D8000445790BF36AF2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###43 services have timed out.#
#1.5#0015C588AED400000000001A000034D8000445790BF36CBF#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000001C000034D8000445790BF36E70#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.marketplace.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000001E000034D8000445790BF3702D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ejb has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000020000034D8000445790BF371D8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.security.service has timed out > hard reference to service keystore.#
#1.5#0015C588AED4000000000022000034D8000445790BF3737F#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ssl has timed out > hard reference to service keystore.#
#1.5#0015C588AED4000000000024000034D8000445790BF3752A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000026000034D8000445790BF376D2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service adminadapter has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000028000034D8000445790BF3787A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsecurestorage~service has timed out > hard reference to service keystore.#
#1.5#0015C588AED400000000002A000034D8000445790BF37ACC#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service pmi has timed out > hard reference to service tcsecdestinations~service.#
#1.5#0015C588AED400000000002C000034D8000445790BF37D4C#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service security has timed out > hard reference to service com.sap.security.core.ume.service.#
#1.5#0015C588AED400000000002E000034D8000445790BF37EF7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jms_provider has timed out > hard reference to service security.#
#1.5#0015C588AED4000000000030000034D8000445790BF380A1#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service sld has timed out > hard reference to service tcsecsecurestorage~service.#
#1.5#0015C588AED4000000000032000034D8000445790BF3824E#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jmx has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000034000034D8000445790BF383F8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service rfcengine has timed out > hard reference to service ejb.#
#1.5#0015C588AED4000000000036000034D8000445790BF385A7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsaml~service has timed out > hard reference to service adminadapter.#
#1.5#0015C588AED4000000000038000034D8000445790BF38754#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service telnet has timed out > hard reference to service shell.#
#1.5#0015C588AED400000000003A000034D8000445790BF38903#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jdbc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000003C000034D8000445790BF38AB4#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculculservice_sda has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000003E000034D8000445790BF38C5D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service webdynpro has timed out > hard reference to interface shell.#
#1.5#0015C588AED4000000000040000034D8000445790BF38E07#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecvsiservice has timed out > hard reference to service tcsecdestinationsservice.#
#1.5#0015C588AED4000000000042000034D8000445790BF38FD6#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tceCATTPingservice has timed out > hard reference to interface shell.#
#1.5#0015C588AED4000000000044000034D8000445790BF3918B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ispeak.svc has timed out > hard reference to service applocking.#
#1.5#0015C588AED4000000000046000034D8000445790BF3938A#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecdestinationsservice has timed out > hard reference to service tcsecsecurestorageservice.#
#1.5#0015C588AED4000000000048000034D8000445790BF3953F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service dsr has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004A000034D8000445790BF396EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service keystore has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004C000034D8000445790BF398A2#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service applocking has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004E000034D8000445790BF39B53#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculservice_sda has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000050000034D8000445790BF39CFE#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service monitor has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000052000034D8000445790BF39EAB#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.security.core.ume.service has timed out > service com.sap.security.core.ume.service start method invoked.#
#1.5#0015C588AED4000000000054000034D8000445790BF3A068#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.bc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000056000034D8000445790BF3A217#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.rfc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000058000034D8000445790BF3A3CD#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tc.monitoring.logviewer has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000005A000034D8000445790BF3A5EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service apptracing has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000005C000034D8000445790BF3A7B3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ms.svc has timed out > hard reference to service com.sap.aii.af.svc.#
#1.5#0015C588AED400000000005E000034D8000445790BF3A967#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.cpa.svc has timed out > hard reference to service sld.#
#1.5#0015C588AED4000000000060000034D8000445790BF3AB0C#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service shell has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000062000034D8000445790BF3ACBC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecwssecservice has timed out > hard reference to service tcsecsecurestorageservice.#
#1.5#0015C588AED4000000000064000034D8000445790BF3AE81#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.mail.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000066000034D8000445790BF3B03B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service servlet_jsp has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000068000034D8000445790BF3B2D1#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.file.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000006A000034D8000445790BF3B47F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service classload has timed out > hard reference to service security.#
#1.5#0015C588AED400000000006C000034D8000445790BF3B628#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service basicadmin has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000006E000034D8000445790BF3B7D3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.xi.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000070000034D8000445790BF3BA67#1202286100750#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: 5 core services have timed out [adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin].#Hello Sir,
I am also having the similar prblem after upgrading the AIX 5.3 TL 5 to TL6.
I would really like to know what you did to solve you problem, even though our scenario is a little different. -
J2EE ENGINE Takes a lot of time to start
Hi
Whenever we restart the J2EE ENGINE it takes it about and hour and half to start
We upgraded our R/3 to Unicode , but XI Is still non-unicode ( I dont know its connected )
The defaultrace log when it tries to start is :
#1.5#001125A56002001800000000001080B200041C10571A98A0#1156756413257#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupConfigurationService().after<super()>#
#1.5#001125A56002001800000001001080B200041C10571AAF4B#1156756413263#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
#1.5#001125A56002001800000002001080B200041C10571AB8C9#1156756413266#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
#1.5#001125A56002001800000003001080B200041C10571C8F33#1156756413386#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
#1.5#001125A56002001800000004001080B200041C10571C937D#1156756413387#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
#1.5#001125A56002002F00000000001080B200041C1057CBF48D#1156756424881#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_65##0#0#Info#1#/System/Server/CTC#Plain###Starting Configuration util service...#
#1.5#001125A56002003000000000001080B200041C1057CC1A7C#1156756424890#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###entering CulServiceFrame.start#
#1.5#001125A56002003000000001001080B200041C1057CCC060#1156756424933#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###deploymentListener registered#
#1.5#001125A56002002F00000002001080B200041C1057EC01D6#1156756426981#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_65##0#0#Info#1#/System/Server/CTC#Plain###Configuration util service started successfully.#
#1.5#001125A56002003000000002001080B200041C10580B287A#1156756429023#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Enum = com.sap.engine.frame.core.load.res.CompoundEnumeration@21b85f86#
#1.5#001125A56002003000000003001080B200041C10580DB59B#1156756429190#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Inputstream CTC start file java.io.ByteArrayInputStream@b3d5e4e#
#1.5#001125A56002003000000004001080B200041C105811AAC8#1156756429449#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Object = com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup@3105de41#
#1.5#001125A56002003000000005001080B200041C10581C597B#1156756430149#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...ConfigManagerProvider registered#
#1.5#001125A56002003000000007001080B200041C10581C6353#1156756430152#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...TextSourceProvider registered#
#1.5#001125A56002003000000009001080B200041C10581C7EC4#1156756430159#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...JavaServiceProvider registered#
#1.5#001125A5600200300000000B001080B200041C10581D03F2#1156756430193#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...AbapConfigurationProvider registered#
#1.5#001125A5600200300000000D001080B200041C10581F48CA#1156756430342#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###registerApplication2MBeanServer(sc)...#
#1.5#001125A5600200300000000F001080B200041C105820069C#1156756430390#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULExportService registered#
#1.5#001125A56002003000000011001080B200041C105820358F#1156756430402#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULImportService registered#
#1.5#001125A56002003000000013001080B200041C10582078A5#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULAdminService registered#
#1.5#001125A56002003000000015001080B200041C10582079B2#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###CTC System started...#
#1.5#001125A56002003000000017001080B200041C1058207ACA#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###CUL Service started...#
#1.5#001125A56002003B00000000001080B200041C10587E30E2#1156756436562#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_70##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://terudbxid1:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xid.terudbxid1), due to: HTTP 503: Service Unavailable#
#1.5#001125A56002003B00000001001080B200041C10587F353A#1156756436628#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_70##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
#1.5#001125A56002003D00000000001080B200041C105899F3CB#1156756438381#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.getMDTUrl()#######SAPEngine_System_Thread[impl:5]_12##0#0#Error##Plain###HTTP response code: 503 Service Unavailable#
#1.5#001125A56002004600000000001080B200041C1058C7442C#1156756441351#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#1#####File2XI[:MQ_Service:File_Gad_Sender_CONV]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel File_Gad_Sender_CONV: No suitable sender agreement found#
#1.5#001125A56002004800000000001080B200041C105A99226B#1156756471882#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000001001080B200041C105C62E7E3#1156756501882#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000002001080B200041C105E2CC5CB#1156756531889#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000003001080B200041C105FF68EAB#1156756561890#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000004001080B200041C1061C06873#1156756591896#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000005001080B200041C10638A7936#1156756621916#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000006001080B200041C1065543E74#1156756651916#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000007001080B200041C10671E0481#1156756681917#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002000000000015001080B200041C106814AC14#1156756698082#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Mon Aug 28 11:18:18 GMT+02:00 2006 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
Service com.sap.aii.adapter.jms.svc > service com.sap.aii.adapter.jms.svc start method invoked.
#1.5#001125A56002000000000017001080B200041C106814B974#1156756698085#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###1 services have timed out.#
#1.5#001125A56002000000000019001080B200041C106814BB1F#1156756698086#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > service com.sap.aii.adapter.jms.svc start method invoked.#
#1.5#001125A56002004800000008001080B200041C1068E7CA65#1156756711918#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)######2c8f20e0367611db8f53001125a56002#SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000009001080B200041C106AB18FB6#1156756741918#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)######2c8f20e0367611db8f53001125a56002#SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
any Ideas ?
Thx,Shaihi shai,
"but XI Is still non-unicode"
as far as i know XI can be installed only on a unicode Web AS.
plz check that once again
cheers
satish -
J2EE Engine cannot start after applying SP11 on WAS 6.40
Hi SAP
I am upgrading my WAS 6.40 SR1 java instance from SP9 to SP11. At the last stages of the installation the Java instance is stopped & started,at the step where Java instance is started, the 'server' process of the Java instance is not coming up properly. jcmon shows the dispatcher & SDM with status 'running' while server0 is with status 'stopped'.
Since I'm using ABAP as data source to the J2EE, appears to me that the problem is occuring due to password mismatch for user SAPJSF in R/3 client 168 & between user SAPJSF in J2EE though I'm not sure why the password might change in J2EE after applying SP11.
Please advice if my reasoning is correct, if no please advice how to solve this problem.
If yes pls advice how can I change the password for user SAPJSF in J2EE. FYI I already tried changing the password for user SAPJSF using the offline config tool, Under cluster-data-> Instance_ID87066 I select the
services com.sap.security.core.ume.service, then I select the ume.r3.connection.master.passwd, then the problem is inside the value option I'm not able to input the new password, neither I'm able to delete the old password, so the best thing I can do is Click on Set which opens a small window without any description with 2 options OK & Cancel, here I put the password same as R/3 password & save, after this I re-start the J2EE, but the same problem persists. Please advice on solving the problem.
Trace file std_server0.out shows that the foll error message......
Apr 28, 2005 8:09:47 PM com.sap.security.core.persistence
[SAPEngine_System_Thread[impl:5]_23] Fatal: User Management Engine
(com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect. Please re-enter". Connection data (obtained
from properties of UME service in section "ume.r3.connection.master.": "{
snc_qop=
client=168
abap_debug=
snc_myname=
gwserv=
snc_partnername=
ashost=CDBNTD03
group=
r3name=
snc_mode=0
gwhost=
sysnr=00
msserv=
poolmaxsize=10
snc_lib=
passwd=********
poolmaxwait=
trace=
receiverid_guest=master
mshost=
user=SAPJSF
lang=
receiverid=master
Apr 28, 2005 8:09:47 PM com.sap.security.core.persistence
[SAPEngine_System_Thread[impl:5]_23] Fatal: Initialization of UME persistence adapter "R3_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: Name or password is incorrect.
Please re-enter at com.sap.security.core.server.ume.service.UMEServiceFrame.start
(UMEServiceFrame.java:555)
at com.sap.engine.frame.ApplicationFrameAdaptor.start
(ApplicationFrameAdaptor.java:31)
at
com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:
201)
at com.sap.engine.core.service630.container.ServiceRunner.run
(ServiceRunner.java:142)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute
(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run
(SingleThread.java:145)
Caused by:
com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect. Please re-enter
at
com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3Persistenc
eBase.java:1707) at
com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init (R3PersistenceBase.java:1934)
std_server0.out (16%)
Thanks & Rgds,
AbhishekHi,
have a look here.
WebAS - invalid property value -
J2EE engine not getting started
Hi All,
My J2ee engine isnt getting started. When i check the logs, i see the following error,
Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
Loading: LogManager ... 672 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 78 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 218 ms.
Loading: LockingManager ... 94 ms.
Loading: ConfigurationManager ...
Loading: ConfigurationManager returned false!
Kernel not loaded. System halted.
Can anybody help me out with this ??
Thanks in advance,
PranavHi Arun,
ya indeed it looks like a DB connection problem. When i check the logs i see the following error :
#1.5#001321D5DC2000000000001500049EDC0004163FAB8F0C2D#1150362623876#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:360)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at</i></i> com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerFactoryImpl.<init>(ConfigurationHandlerFactoryImpl.java:30)
at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:189)
at com.sap.engine.core.configuration.AbstractConfigurationManagerImpl.init(AbstractConfigurationManagerImpl.java:169)
at com.sap.engine.core.Framework.loadSingleManager(Framework.java:560)
at com.sap.engine.core.Framework.loadManagers(Framework.java:254)
at com.sap.engine.core.Framework.start(Framework.java:188)
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:61)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: [SAP_NWMss][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPBQ3DB'. The user is not associated with a trusted SQL Server connection.
at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
at com.sap.nwmss.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:579)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
Actually i've upgraded my SQL Server2000 DB to SQL Server 2005, i suspect that causes the problem. Would be great if somebody can provide me any further clues..
Regards,
Pranav -
Hi,
I have a strange problem when I try upgrade my Linux TestDrive from SP12 to SP14.
Hostname: NW
The installation is working on SP12. Im able to deploy both from NWDS and SDM.
The sapinst is executed with the remotehost parameter: sapinst SAPINST_USE_HOSTNAME=nw4host
The upgrade goes smooth until Deploy via SDM/JEE where I get a Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002: tetasoft-002
The strange thing is that my laptop is called tetasoft-002.
Any idea how to solve this? Is there a parameter I should use?
callSdmViaSapinst.log:
Nov 1, 2005 1:09:39 PM Info: The deployment prerequisites finished without any errors. All items are correct.
Nov 1, 2005 1:10:00 PM Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002: tetasoft-002
Nov 1, 2005 1:10:00 PM Info: Saved current Engine state.
Nov 1, 2005 1:10:00 PM Info: Error handling strategy: OnErrorStop
Nov 1, 2005 1:10:00 PM Info: Update strategy: UpdateLowerVersions
Nov 1, 2005 1:10:00 PM Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818152214.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050331133103.0000'.
Nov 1, 2005 1:10:00 PM Info: SDA to be deployed: /usr/sap/NW4/DVEBMGS00/SDM/root/origin/sap.com/SQLTrace/SAP AG/6.4014.00.0000.20050818152214.0000/SQLTrace.ear
Nov 1, 2005 1:10:00 PM Info: Software type of SDA: J2EE
Nov 1, 2005 1:10:00 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 1, 2005 1:10:00 PM Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002
Nov 1, 2005 1:10:01 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 1, 2005 1:10:01 PM Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818152214.0000':
CPO data could not be get.
com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Error: Caught the following error or exception: "com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException"
Additional error message is:
Caught exception from deploy service of SAP J2EE Engine. Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [nw4host] with user name: [J2EE_ADMIN]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Additional error message is:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [nw4host] with user name: [J2EE_ADMIN]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).NO_CPO)
Nov 1, 2005 1:10:02 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Nov 1, 2005 1:10:02 PM Info: -
Deployment was successful -
Nov 1, 2005 1:10:02 PM Info: Summarizing the deployment results:
Nov 1, 2005 1:10:02 PM Error: Admitted: /home/hda/SAP Download (Linux)/test/J2EE-RUNT-CD/J2EE-ENG/ONLINE/SAPJTECHS14_0.SCA
Nov 1, 2005 1:10:02 PM Error: Processing error. Return code: 4
Best regards
HenrikGregor,
I have exactly the same symptom in SP9 --> SP13 on clustered Solaris WebAS/EP installation. I am curious as to why you think it's to do with DISPLAY variable - though I wouldnt be at all surprised by some of the imaginings that sapinst has.
In my case, I get the RemoteLoginContext problem, but no 'comapre host' message. Simply that the J2EE administrator credential check failed. At this time, thye J2EE is up and running, all services and apps are in the started/running state; the SDM is stopped (but gets started by the deploy task of sapinst). There is no corruption of the secure store password so far as I can gather.
My installation sounds somewhat similar to Henrik's:
Physical Host : spvcs53prod
Virtual SCS IP (on same host): spscs50prod
Virtuaal CI IP (on same host): spci50prod
..\sapinst SAPINST_USE_HOSTNAME=spci50prod SAPINST_START_GUI=false
The CI is on a virtual host too, for system admin and monitoring reasons, though it is not in a switchable cluster group. I have had some problems for example with the delivered startsap and stopsap scripts. These cannot locate the required hostnames accurately on network adapters as the output of the ping command varies depending on the physical/virtual setup. (start.sopsap parse the ping result to verify hostnames). Maybe sapinst is doing something similar in these installation situations?
Any help appreciated, as we are now stuck delivering a production cluster !
Thanks. -
Error applying SPS9 on J2EE Engine 7.0
Hello,
we are trying to apply SP9 on the Java Stack of Netweaver 2004s, but now we can not start the J2EE engine, that returns the following error:
<b>[SAPEngine_System_Thread[impl:5]_62] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=03
client=200
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=crmds
poolmaxwait=10000
Dec 12, 2006 7:33:00 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "R3_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 initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.</b>
We have verified the userid and password, and they are correct. Changed the values with configtool, but still get this error. What else can be done to get J2EE up and running ?
We are running a ABAP+Java instance.
Thanks in advance for your help.
Ernest Lluis.Hi Daniel,
Thanks for your prompt reply!
Actually we checked out the user SAPJSF and it's password and we are sure they are correct. But we think the SPS9 apply has changed the configtool parameters, might it really be ??
We had a similar situation during installation where the username was bad written in configtool: SAPJFS instead of SAPJFS !
Yesterday we got even the user blocked due to many failed logons... We think that maybe there is some other parameter that we are missing wich can help the Java Stack to determine the user for logging on the Abap Stack.
Anyway, I'll try to Activate the emergency user to be able to finish the upgrade... I'll let you know if it worked.
Please tell me if you have some other idea arround this assuming that user in configtool is well parametrized.
Thanks again ! -
J2ee engine startup error- cant attach shared memory
Hello Experts,
We have upgraded ERP abap+java to EHP4 but J2ee engine is not coming up. It is giving the following errors. There are no issues on the abap side.
Bootstrap logs are fine and are able to syncronize.
Following is the dev_jcontrol log.
JStartupIReadSection: read node properties [ID44702600]
-> node name : dispatcher
-> node type : dispatcher
-> node execute : yes
-> java path : /usr/j2se
-> java parameters : -Djava.security.policy=.\java.policy -Djava.security.egd
=file:/dev/urandom -XX:NewSize=181M -XX:MaxNewSize=181M -XX:+DisableExplicitGC -
verbose:gc -Xloggc:GC.log
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
-> java vm type : server
-> java vm cpu : sparcv9
-> heap size : 544M
-> init heap size : 544M
-> root path : /usr/sap/DV2/DVEBMGS04/j2ee/cluster/dispatcher
-> class path : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/DV2/DVEBMGS04/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/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
xe/run/jvmx.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 1] [Node: server0] java home is set by profile parameter
Java Home: /usr/j2se
[Thr 1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/D
V2/SYS/exe/run/jvmx.jar
JStartupIReadSection: read node properties [ID44702650]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/j2se
-> 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
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jt
s.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -Dsun.io.useCanonCaches=fa
lse -XX:NewSize=341m -XX:MaxNewSize=341m -XX:MaxPermSize=192m -Djava.awt.headles
s=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:Soft
RefLRUPolicyMSPerMB=1 -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX
:PrintGCTimeStamps -XX:UseParNewGC -Drdbms.driverLocation=/oracle/DV2/920_64/j
dbc/lib/classes12.jar -Dsys.global.dir=/sapmnt/DV2/global -Xms2048m
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
-> java vm type : server
-> java vm cpu : sparcv9
-> heap size : 2048M
-> init heap size : 1024M
-> root path : /usr/sap/DV2/DVEBMGS04/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/byt
ecode.jar:.
-> OS libs path : /usr/sap/DV2/DVEBMGS04/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/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
xe/run/jvmx.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50421
-> shutdown timeout : 120000
[Thr 1] [Node: server1] java home is set by profile parameter
Java Home: /usr/j2se
[Thr 1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/D
V2/SYS/exe/run/jvmx.jar
JStartupIReadSection: read node properties [ID44702651]
-> node name : server1
-> node type : server
-> node execute : yes
-> java path : /usr/j2se
-> 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
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jt
s.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -XX:MaxPermSize=192M -XX:P
ermSize=192M -XX:NewSize=170M -XX:MaxNewSize=170M -XX:+DisableExplicitGC -verbos
e:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:PrintGCTimeStamps -Djava.awt.headle
ss=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:Survivor
Ratio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerC
lass=com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
-> java vm type : server
-> java vm cpu : sparcv9
-> heap size : 2048M
-> init heap size : 1024M
-> root path : /usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/byt
ecode.jar:.
-> OS libs path : /usr/sap/DV2/DVEBMGS04/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/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
xe/run/jvmx.jar
-> parameters :
-> debuggable : yes
-> debug mode : no
-> debug port : 50426
-> shutdown timeout : 120000
[Thr 1] INFO: Invalid property value [Debbugable=yes]
[Thr 1] [Node: SDM] java home is set by profile parameter
Java Home: /usr/j2se
[Thr 1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/D
V2/SYS/exe/run/jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : /usr/j2se
-> java parameters :
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
-> java vm type : server
-> java vm cpu : sparcv9
-> heap size : 512M
-> root path : /usr/sap/DV2/DVEBMGS04/SDM/program
-> class path : /usr/sap/DV2/DVEBMGS04/SDM/program/bin/SDM.jar
-> OS libs path : /usr/sap/DV2/DVEBMGS04/j2ee/os_libs
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
xe/run/jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=/usr/sap/DV2/DVEBMGS04/SDM/program
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 1] ***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3803]
[Thr 1] *** ERROR => NiIWrite: SiSendV failed for hdl 2 / sock 13
(SI_ECONN_BROKEN/32; UD; ST; 172.20.40.15:3601) [nixxi.cpp 3803]
[Thr 1] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi_mt.c 24
80]
[Thr 1] *** ERROR => MsIDetach: MsINiWrite (rc=NIECONN_BROKEN) [msxxi_mt.c 11
46]
[Thr 1]
[Thr 1] * ERROR mserrno received (MSEACCESSDENIED)
[Thr 1] *
TIME Wed Oct 6 14:34:06 2010
[Thr 1] * RELEASE 700
[Thr 1] * COMPONENT MS (message handling interface, multithreaded)
[Thr 1] * VERSION 4
[Thr 1] * RC -24
[Thr 1] * MODULE msxxi_mt.c
[Thr 1] * LINE 810
[Thr 1] * COUNTER 2
[Thr 1] *
[Thr 1] *****************************************************************************
[Thr 1] *** WARNING => Can't attach to message server (aeerpdv1/3601) [rc = -20]-> reconnect [jcntrms_mt.c 368]
[Thr 1] Wed Oct 6 14:34:11 2010
[Thr 1] ***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3803]
[Thr 1] *** ERROR => NiIWrite: SiSendV failed for hdl 2 / sock 13
(SI_ECONN_BROKEN/32; UD; ST; 172.20.40.15:3601) [nixxi.cpp 3803]
[Thr 1] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi_mt.c 2480]
[Thr 1] *** ERROR => MsIDetach: MsINiWrite (rc=NIECONN_BROKEN) [msxxi_mt.c 1146]
[Thr 1]
[Thr 1] * ERROR mserrno received (MSEACCESSDENIED)
[Thr 1] *
TIME Wed Oct 6 14:34:11 2010
[Thr 1] * RELEASE 700
[Thr 1] * COMPONENT MS (message handling interface, multithreaded)
[Thr 1] * VERSION 4
[Thr 1] * RC -24
[Thr 1] * MODULE msxxi_mt.c
[Thr 1] * LINE 810
[Thr 1] * COUNTER 4
[Thr 1] *
[Thr 1] *****************************************************************************
[Thr 1] *** WARNING => Can't attach to message server (aeerpdv1/3601) [rc = -20]-> reconnect [jcntrms_mt.c 368]
[Thr 1] Wed Oct 6 14:34:16 2010
[Thr 1]
Please advise and help.
Thanks,
AntarpreetHello Sunny,
Thanks for your help.
All the other relavant logs look fine to me. The default traces of server0, server1 are not being populated. Niether is there any change in dispatcher and bootstrap logs.
Here are the other logs:
aeerpdv1:dv2adm 127% tail -20 dev_bootstrap_ID44702650
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 4] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0 bootstrap]
-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap
-> arg[ 1]: ./bootstrap
-> arg[ 2]: ID044702650
[Thr 4] Thu Oct 7 01:44:54 2010
[Thr 4] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 5] Thu Oct 7 01:44:57 2010
[Thr 5] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 5] SigISetIgnoreAction : SIG_IGN for signal 18
[Thr 5] JLaunchCloseProgram: good bye (exitcode = 0)
aeerpdv1:dv2adm 128%
aeerpdv1:dv2adm 128% tail jvm_bootstrap_ID44702651.out
...Synched ok!
Synchronizing file [/usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1/dtd/application-j2ee-engine.dtd].
...Synched ok!
Synchronizing file [/usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1/dtd/application-client-additional.dtd].
...Synched ok!
Synchronizing file [/usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1/dtd/db-init.dtd].
...Synched ok!
Ok! (46 ms)
Done!
Synch time: 3537 ms
aeerpdv1:dv2adm 131% tail dev_bootstrap_ID44702651
[Thr 4] Thu Oct 7 01:45:00 2010
[Thr 4] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 5] Thu Oct 7 01:45:03 2010
[Thr 5] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 5] SigISetIgnoreAction : SIG_IGN for signal 18
[Thr 5] JLaunchCloseProgram: good bye (exitcode = 0)
tail dev_disp
Thu Oct 7 01:42:40 2010
J2EE server info
start = TRUE
state = STARTED
pid = 3355
argv[0] = /usr/sap/DV2/DVEBMGS04/j2ee/os_libs/jcontrol
argv[1] = jcontrol
argv[2] = pf=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64996
argv[5] = -DSAPSYSTEM=04
argv[6] = -DSAPSYSTEMNAME=DV2
argv[7] = -DSAPMYNAME=aeerpdv1_DV2_04
argv[8] = -DSAPPROFILE=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Thu Oct 7 01:44:09 2010
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Thu Oct 7 01:44:20 2010
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Thu Oct 7 01:44:40 2010
J2EE server info
start = TRUE
state = STARTED
pid = 3417
argv[0] = /usr/sap/DV2/DVEBMGS04/j2ee/os_libs/jcontrol
argv[1] = jcontrol
argv[2] = pf=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64995
argv[5] = -DSAPSYSTEM=04
argv[6] = -DSAPSYSTEMNAME=DV2
argv[7] = -DSAPMYNAME=aeerpdv1_DV2_04
argv[8] = -DSAPPROFILE=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Thu Oct 7 01:46:09 2010
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Thu Oct 7 01:46:20 2010
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Thu Oct 7 01:46:40 2010
DpHdlDeadWp: restart wp (pid=3015) automatically
DpEnvCheckJ2ee: switch off j2ee start flag
Please help, struck in a very bad situation.
Regards,
Antarpreet -
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.KHi 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 -
503 Service Unavailable,SAP J2EE Engine/7.00
Hi Experts,
I have upgraded J2EE Software Components from SP06 to sp22 successfully.
Components
JSPM
BASETABLES
CORE-TOOLS
JLOGVIEW
SAP-JEE
SAP-JEECOR
SAP_JTECHF
SAP_BUILDT
BI_MMR
KM-KW_JIKS
ADSSAP
CAF-UM
SAP_JTECHS
BI_UDI
Now here is the problem...
When I executed the URL: http://hostname:50100/index.html I'm getting the below error:
"503 Service Unavailable"
SAP J2EE Engine/7.00
Application Stopped
Details: you have requested an application that is currently stopped.
Please guide me on this.
Regards,
Sharath
Log :
IM_ERR_FAILED: SAP_SupportPackage.ElementTypeID="01200615321100062316",Name="SAPK-20011INTBYDSP",Vendor="sap.com",Version="0011" referenced by association SAP_SupportPackageSoftwareComponent.Antecedent=ref"SAP_SoftwareComponent.ElementTypeID=
"01200615320200016633
",Name=
"TBYDSP
",Vendor=
"sap.com
",Version=
"200
"",Dependent=ref"SAP_SupportPackage.ElementTypeID=
"01200615321100062316
",Name=
"SAPK-20011INTBYDSP
",Vendor=
"sap.com
",Version=
"0011
"" does not exist.: Instance of SAP_ExportInstCreation.
Embedded instance(s): Target instance = SAP_SupportPackageSoftwareComponent.Antecedent=ref"SAP_SoftwareComponent.ElementTypeID=
"01200615320200016633
",Name=
"TBYDSP
",Vendor=
"sap.com
",Version=
"200
"",Dependent=ref"SAP_SupportPackage.ElementTypeID=
"01200615321100062316
",Name=
"SAPK-20011INTBYDSP
",Vendor=
"sap.com
",Version=
"0011
CIM_ERR_FAILED: Can not create SAP_SupportPackage.ElementTypeID="01200615321100063170",Name="SP072",Vendor="sap.com",Version="072", instance defines an additional property Owner.: Instance of SAP_ExportInstModification.
Embedded instance(s): Target instance = SAP_SupportPackage.ElementTypeID="01200615321100063170",Name="SP072",Vendor="sap.com",Version="072"
CIM_ERR_FAILED: Can not create SAP_SupportPackage.ElementTypeID="01200615321100063169",Name="SP072",Vendor="sap.com",Version="072", instance defines an additional property Owner.: Instance of SAP_ExportInstModification.
Embedded instance(s): Target instance = SAP_SupportPackage.ElementTypeID="01200615321100063169",Name="SP072",Vendor="sap.com",Version="072"
CIM_ERR_FAILED: Can not create SAP_SupportPackage.ElementTypeID="01200615321100063245",Name="SP038",Vendor="sap.com",Version="038", instance defines an additional property Owner.: Instance of SAP_ExportInstModification.
Embedded instance(s): Target instance = SAP_SupportPackage.ElementTypeID="01200615321100063245",Name="SP038",Vendor="sap.com",Version="038"#
Edited by: sharathbabu gundu on Aug 29, 2011 9:42 PMSharath,
Check if your settings in the Visual Adminstrator for SLD are correct and also test the CIM Client Test there.
Secondly, ensure that the SLDDSUSER has all required roles to access SLD and it is not been locked.
Also, you might want to check this SAP NOTE:669669.
Good Luck!
Sandeep Tudumu -
SAP WEBAS 640 J2EE Engine Instalation
Hi All,
This is Clark, We are trying to configure ADS. We already installed ECC 5.0,(oracle database) on windows server. We are trying to install J2EE engine. kindly let me know from where to download and how to install.
Thanks,
ClarkHi Abhishek,
I was trying to install java components in ECC 5.0 IDES Server. it showing an error " This Installation requires an SAP J2EE Engine version 6.30 or higher"
and then i gave NEXT then it gave another error message " No instance found for the central instance. Check your file system. Install Web AS 6.30 and restart this deployment afterwards".
Kindly let me know how to find which version of Web AS now i am using and how to upgrade to higher version.
Thanks,
Clark
Maybe you are looking for
-
Itunes Free Apps Purchase History Deletion
I dont want my purchase history to show up for apps that are free and usually demos. I dont think it is neccessary to keep all the free apps i try or the demos i try. As part of privacy I sometimes dont even want to remeber about an app I tried becau
-
Error connecting to Essbase Server when running business rules
We recently migrated from v9.3 to v11.1.1.3. I have two users with Administrative access who need to run business rules on a native Essbase application, but cannot. They get the message 'Error connecting to Essbase Server'. They get this message when
-
How do I restore audio for yahoo e-mail attachments such as YouTube?
Sound does not activate when playing e-mail attachments or web site tutorials.
-
HI I am using the one bind variable on VO and when i run the application or AM , i am getting the below error as '(java.sql.SQLException) Missing IN or OUT parameter at index:: 1' Vo query as below: SELECT Employees.EMPLOYEE_ID, Employees.FIRST_NAME,
-
Ipod stolen - how do I get itunes to restore to newly purchased one?
My wife's ipod mini 6gb was stolen this week & since she never used more than 2gb and I am broke at the moment, I got her a 4gb to replace it. How do I restore the music? Do I go into her itunes and export all playlists, then plug in the new one and