J2EE stack 01

Hi, I am installing EP60 NetWeaver 04 on a W2K platform and have run into a snag. The first step of installing the J2EE engine went ok and now I have a 630 J2EE engine running. The next step calls for upgrading the J2EE engine from SP3 to SP4 following the instructions contained in the 'sap Netweaver 04 support package stack 01 guide'
I have found the guide but on page 29 it says that the sp4 files are included in the 'sap netweaver 04 dvd 51030142_sap_netweaver_04_sap_J2EE_engine_6.30.sp_4'.
I simply can't find this dvd.
Can anyone give me a push in the correct direction?
Thanks
Rich

I have followed the above recomendations on a win2k3/ora platform and have installed the portal sp3. Part of the verification is to signon to the portal, but this seems to just hang.
Were others able to signon, or did you all just put sp9 for EP6 in first and then try and signon.
Lastly talking ep6 to stack 9 requires how many files (sapinst as before, ep6, but do I need the j2ee again-as I am extracting to a different directory?
also is there a specific order to the extracts (as we did for stack 9 for WAS 6.40)?

Similar Messages

Configuration check error: The SMD Agent is not able to connect the Satellite System (J2EE stack)

Hi friends,
Getting the below error in step 10 (configuration check) in managed system configuration.
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this
System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
The SMD log file referred to in the log above gives the same information and not anything much useful.
Any idea what could be the reason for the above error?
Thanks,
Arindam

Hi All,
Thaks for your suggestions. I chcked the note 182020, but the issue described in the note is for error byte code adapter installation whcih is not my case. The byte cde adapter intallation has been successful in our solman system All the steps from 1 to 9 are green. Only in step 10, check cniguration I am getting the above error.
The logon test wth the user id in step 3 "Enter system parameters" is successful. The message server port is also correct.
Hi Khaja,
I went to the links as suggestedby you but there its about a ifferent error message "Invalid Response Code: (401) Unauthorized.". I am not getting any such kind of error.
All I am getting is this -
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Thanks,
Arindam

Monitor J2EE stack like dpmon or msmon on ABAP side

I am attempting to monitor the J2EE stack and want to know if there is a way to get a return code back.
Is there a command much like jcmon that would give me back a status of 1 or 0 to see if it is up. I can go to jcmon and then select a number to get the running status however I cannot interpret that with a single unix command. I know if I see dispatcher server and SDM all running that in all likelyhood the engine is up.
If jcmon is the only tool, how can I in a script get the status of my server0 dispatcher and SDM...it seems cockeyed and messy to do this..
I know to go to DN:50x00 to check and see manually but I nned an SAP command to give me aq return code for engine status.
Does anyone have any idea what I could use. It seems like the ABAP stack has a number of monitors to help with this task but I can't find any on the java side.
Thanks much,
Mikie

Hello Mikie,
If I understand you correctly you are looking for a way to check if the J2EE Engine is running using a script. The easiest way is to use the ps ef | grep jla command. It will return all jlaunch processes, one for every node (server<n>, dispatcher and SDM). The command returns something like that:
sr2adm 7131 6976 0 15:17 ? 00:00:28 /usr/sap/SR2/JC00/exe/jlaunch pf=/usr/sap/SR2/SYS/profile/SR2_JC00_support6 -DSAPINFO=SR2_00_dispatcher -nodeId=0 -file=/usr/sap/SR2/JC00/j2ee/cluster/instance.properties -syncSem=5013577 -nodeName=ID7416300 -jvmOutFile=/usr/sap/SR2/JC00/work/jvm_dispatcher.out -stdOutFile=/usr/sap/SR2/JC00/work/std_dispatcher.out -locOutFile=/usr/sap/SR2/JC00/work/dev_dispatcher -mode=JCONTROL pf=/usr/sap/SR2/SYS/profile/SR2_JC00_support6
As you could see there is a lot of information and you could be more specific when grep and distinguish the jlaunch processes.
One exception when this will not work is if the J2EE Engine is hanging. If you wish to avoid that you could use script that sends telnet request to the http port and checks the result. Something like:
telnet localhost 50000
GET / HTTP/1.0
If everything works fine this should return:
HTTP/1.1 302 Found
If the J2EE Engine is hanging the port will not accept your request.
Regards, Ventsi

Problem with starting j2ee stack

We have Netweaver 2004s ABAP+J2EE (Add-in). ABAP stack starts ok, but j2ee stack not :(.
dev_jcontrol:
[Thr 6040] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 6040] INFO: Invalid property value [javaVMPath=C:\j2sdk1.4.2_09]
[Thr 6040] INFO: Invalid property value [javaVMVersion=1.4.2_09-b05]
[Thr 6040] INFO: Invalid property value [javaVMVendor=Java HotSpot(TM) Server VM (Sun Microsystems Inc.)]
[Thr 6040] INFO: Invalid property value [javaVMCpu=x86]
[Thr 6040] INFO: Invalid property value [javaVMLibPath=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin]
[Thr 6040] INFO: Invalid property value [javaVMExePath=C:\j2sdk1.4.2_09\bin]
[Thr 6040] *** ERROR => Main class not specified [jstartxx.c   2592]
[Thr 6040] *** ERROR => node [bootstrap] not found [jstartxx.c   1593]
[Thr 6040] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = -18)
[Thr 6040] JControlCloseProgram: started (exitcode = -18)
[Thr 6040] JControlCloseProgram: good bye... (exitcode = -18)
instance.properties
#bootstrap. : -
#bootstrap. : generated VM parameters
#bootstrap. : Thu Apr 20 14:36:35 2006
#bootstrap. : -
bootstrap.javaVMPath=C:\j2sdk1.4.2_09
bootstrap.javaVMVersion=1.4.2_09-b05
bootstrap.javaVMVendor=Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
bootstrap.javaVMType=server
bootstrap.javaVMCpu=x86
bootstrap.javaVMLibPath=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin
bootstrap.javaVMExePath=C:\j2sdk1.4.2_09\bin
And I can't understand what can be problem with java props. Any suggestion?
Thanks in advance,
Aliaksandr Kuchar

Thank you Vladimir for your replies, it's very helpful.
Actually we managed to restore properties file on our files system. And now sap mmc shows that j2ee server starts well. But we cann't connect it by http neither deafult page of server nor any other (portal f.e.), but can connect Visual Admin.
std_server0.out
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Loading: LogManager ... 1782 ms.
Loading: PoolManager ... 15 ms.
Loading: ApplicationThreadManager ... 141 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 47 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 453 ms.
Loading: LockingManager ... 110 ms.
Loading: ConfigurationManager ... 8281 ms.
Loading: LicensingManager ... 47 ms.
Loading: CacheManager ... 125 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service runtimeinfo started. (32 ms).
Service memory started. (188 ms).
Service cross started. (172 ms).
Service file started. (250 ms).
Service timeout started. (219 ms).
Service cafeuodi~mnuacc started. (0 ms).
Service trex.service started. (31 ms).
Service p4 started. (969 ms).
Service classpath_resolver started. (78 ms).
Service cafeucc~api started. (2922 ms).
Service jmx_notification started. (93 ms).
Service userstore started. (47 ms).
Service log_configurator started. (8000 ms).
Service locking started. (15 ms).
Service naming started. (1187 ms).
Service failover started. (78 ms).
Service appclient started. (140 ms).
Service javamail started. (641 ms).
Service ts started. (609 ms).
Service http started. (1469 ms).
Service licensing started. (31 ms).
Service jmsconnector started. (562 ms).
Service connector started. (546 ms).
Service iiop started. (656 ms).
Service webservices started. (3625 ms).
Service deploy started. (15578 ms).
Service configuration started. (47 ms).
Service MobileSetupGeneration started. (47 ms).
Service MigrationService started. (79 ms).
Service MobileArchiveContainer started. (63 ms).
Service bimmrdeployer started. (0 ms).
Service dbpool started. (2266 ms).
Service cafeugpmailcf started. (62 ms).
Service com.sap.security.core.ume.service started. (2578 ms).
Service security started. (1296 ms).
Service classload started. (156 ms).
Service applocking started. (344 ms).
Service shell started. (328 ms).
Service tceCATTPingservice started. (78 ms).
Service telnet started. (78 ms).
Service webdynpro started. (859 ms).
Service cafummetadata~imp started. (937 ms).
Service ejb started. (2219 ms).
Service servlet_jsp started. (2937 ms).
Service dsr started. (1500 ms).
Service developmentserver started. (2687 ms).
Service keystore started. (3593 ms).
Service ssl started. (78 ms).
Service tcsecsecurestorage~service started. (562 ms).
Service cafumrelgroups~imp started. (3297 ms).
Service tcsecwssec~service started. (235 ms).
Service tcsecdestinations~service started. (703 ms).
Service pmi started. (500 ms).
Service sld started. (2875 ms).
Service cafruntimeconnectivity~impl started. (28656 ms).
Service cafeugp~model started. (375 ms).
Service tcsecvsi~service started. (1797 ms).
Service tceujwfuiwizsvc started. (16 ms).
service tcdisdic~srv ================= ERROR =================
Service jmx started. (6110 ms).
Service cafeuer~service started. (1781 ms).
Service tc.CBS.Service started. (9578 ms).
Service prtbridge started. (5954 ms).
Service CUL started. (5703 ms).
Service com.adobe~DataManagerService started. (6047 ms).
Jun 7, 2007 3:08:03 PM   ...utilxi.prop.api.PropertySourceFactory [SAPEngine_System_Thread[impl:5]_43] Fatal: XI properties could not be initialized. Check ExchangeProfile (or aii.properties).
Thrown:
java.lang.Throwable: dummy Throwable for stack trace
     at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:55)
     at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:548)
     at com.sap.aii.utilxi.misc.api.AIIProperties.<init>(AIIProperties.java:319)
     at com.sap.aii.utilxi.misc.api.AIIProperties.getInstance(AIIProperties.java:346)
     at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43)
     at com.sap.aii.af.service.cpa.impl.util.SLDReader.run(SLDReader.java:89)
     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)
Service apptracing started. (3125 ms).
Service basicadmin started. (7422 ms).
Service com.adobe~LicenseService started. (531 ms).
Service com.adobe~DocumentServicesConfiguration started. (859 ms).
Service adminadapter started. (3531 ms).
Service com.sap.portal.pcd.gl started. (156 ms).
Service com.adobe~DocumentServicesBinaries2 started. (4156 ms).
Service com.adobe~DocumentServicesDestProtoService started. (4250 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (3391 ms).
Service com.adobe~TrustManagerService started. (2906 ms).
Service jms_provider started. (14734 ms).
Service monitor started. (6047 ms).
Service com.sap.portal.prt.sapj2ee started. (93 ms).
Service com.sap.aii.af.cpa.svc started. (18157 ms).
Service com.sap.aii.af.svc started. (1640 ms).
Service com.sap.aii.af.security.service started. (515 ms).
Service com.sap.aii.af.ms.svc started. (672 ms).
Service com.sap.aii.adapter.marketplace.svc started. (437 ms).
Service com.sap.aii.adapter.jms.svc started. (765 ms).
Service com.sap.aii.adapter.xi.svc started. (734 ms).
Service com.sap.aii.adapter.bc.svc started. (1016 ms).
Service com.sap.aii.adapter.mail.svc started. (610 ms).
Service com.sap.aii.adapter.jdbc.svc started. (640 ms).
Service com.sap.aii.adapter.rfc.svc started. (1063 ms).
Service com.sap.aii.adapter.file.svc started. (766 ms).
Service com.sap.aii.af.ispeak.svc started. (437 ms).
Service com.adobe~FontManagerService started. (19078 ms).
Service com.adobe~PDFManipulation started. (18281 ms).
Service com.adobe~XMLFormService started. (4468 ms).
Service tc.monitoring.logviewer started. (32672 ms).
Service rfcengine started. (43672 ms).
ServiceManager started for 81656 ms.
Framework started for 93172 ms.
SAP J2EE Engine Version 7.00   PatchLevel is running!
PatchLevel October 23, 2006 07:41 GMT
Could it be forced by absence of aii.property or by service tcdisdic~srv ================= ERROR =================? How could I indicate problem in more exact way?

J2EE stack install - ctrun error???

Hello all,
I have done several installations and have never come across an error like this one :-|
The only difference in this case is that I specified to install the J2EE stack only and not the ABAP stack (when installing all of the components only needed the J2EE stack).
When doing the installation, I get an error of :
ERROR: can't change to central Executable-Dir /usr/sap/KDP/SYS/exe/ctrun (No such file or directory)
I saw a /usr/sap/<SID>/SYS/exe/run directory but not a /usr/sap/<SID>/SYS/exe/ctrun directory
I have also seen that the "ctrun" directory seems to be associated with dialog instances (when doing note searches, I have seen this). I have specified that this J2EE server be a central - and not dialog - instance.
Question 1 - Is it possible to have a central system with a J2EE stack only? Or, is the requirement that the central system must have both the J2EE and ABAP stacks?
Any help, hints or advice is greatly desired. Of course, points will be awarded.
TIA
Edited by: Casey Harris on Jan 5, 2009 5:26 PM

Hello all and thanks for the responses
The installation master I am using has the following defined in the CDLABEL.ASC file:
SAP Business Suite 2005
Installation Master for:
SAP NetWeaver 7.0 SR3
SAP ERP 6.0 SR3
SAP SRM 5.0 SR3, SAP SCM 5.0 SR3
SAP CRM 5.0 SR3
Number 51033511
I found the following link:
http://al-infotech.com/news/2006/12/30/use-sapcpe-for-kernel-update-on-netweaver-2004-as-java-by-yu-nong-zhang-sap/
But the one that seems to help the most is this one:
http://help.sap.com/saphelp_nw04/helpdata/EN/4f/37783021fc11d288cd0000e83539c3/frameset.htm
it speaks of "automatic adjustment".
When doing this installation, I specified that this was to be a CENTRAL instance and not an application server. From my understanding above, it seems that this sapcpe is being ran even though it should not be. Not all of the conditions have been met ... One can see that the error files are in the CENTRAL directory:
ex: sapinst_instdir/ERP/SYSTEM/ORA/ *CENTRAL* /AS
Question 1: Why is the sapcpe being ran when this is not a dialog instance but a central instance?
Question 2: Also, am I correct in understanding that there is no way to set up a central instance that is has the J2EE stack only?? No components were chosen that would require the use of a dual-stack. Only the J2EE stack was chosen.
TIA
Edited by: Casey Harris on Jan 5, 2009 11:20 PM

J2EE stack doesn't come up

Our PI 7.1 J2EE stack does not come up anymore. Error message from jvm_bootstrap.out is the following:
Launching external modules...
      Calling the Configuration Manager's persistInstanceProfile()...
Component: [Configuration Manager] of type [external]
Message: [ * Problem occurred while executing the Configuration Manager's persistInstanceProfile()]
com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_config/system/instances/ID1300150" and cid "unknown" do
es not exist.
        at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:943)
        at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:892)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.persistInstanceProfile(ConfigurationManagerBootstrapImpl.java:373)
What should I look for?

The configuration manager has trouble finding your J2EE instance configuration in the database. It might help if you refresh your instance.properties from the database, for this see the following link:
http://help.sap.com/saphelp_nw70/helpdata/en/81/df5641998e061de10000000a155106/content.htm

Problem with XI J2EE Stack

We are getting the following error when the XI stack starts up. It seems to point to a problem in the Exchange Profile. However, I am not sure whether it is complaining because of incorrect parameters or because it is unable to access it. This instance of XI has been running just fine for the last few months and we have had no problems with it. All the J2EE services are shut down as the exception shows. Any insight into what the problem might be is well appreciated.
FYI, We haven't added any patches for the last couple of months. It was working fine during that time.
Included is the output from the log.
stdout/stderr redirect
node name   : server0
pid         : 4500
system name : XID
system nr. : 00
started at : Thu Jan 20 14:57:26 2005
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 6.40   PatchLevel 87037.313 is starting...
Loading: LogManager ... 4687 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 142 ms.
Loading: ThreadManager ... 158 ms.
Loading: IpVerificationManager ... 126 ms.
Loading: ClassLoaderManager ... 78 ms.
Loading: ClusterManager ... 1558 ms.
Loading: LockingManager ... 724 ms.
Loading: ConfigurationManager ... 5647 ms.
Loading: LicensingManager ... 47 ms.
Loading: ServiceManager ...
Loading services.:
Service cross started. (47 ms).
Service memory started. (47 ms).
Service file started. (173 ms).
Service timeout started. (126 ms).
Service userstore started. (31 ms).
Service runtimeinfo started. (31 ms).
Service tcsecvsi~service started. (362 ms).
Service p4 started. (1541 ms).
Service trex.service started. (692 ms).
Service jmx_notification started. (865 ms).
Service classpath_resolver started. (126 ms).
Service tcsecwssec~service started. (661 ms).
Service deploy started. (10662 ms).
Service log_configurator started. (11997 ms).
Service locking started. (16 ms).
Service apptracing started. (424 ms).
Service http started. (533 ms).
Service naming started. (816 ms).
Service ts started. (203 ms).
Service javamail started. (298 ms).
Service failover started. (220 ms).
Service licensing started. (47 ms).
Service appclient started. (282 ms).
Service jmsconnector started. (455 ms).
Service connector started. (204 ms).
Service configuration started. (16 ms).
Service webservices started. (2887 ms).
Service dbpool started. (9428 ms).
Service com.sap.aii.af.svc started. (942 ms).
Service com.sap.security.core.ume.service started. (4048 ms).
Service security started. (5083 ms).
Service applocking started. (486 ms).
Service shell started. (675 ms).
Service tceCATTPingservice started. (189 ms).
Service classload started. (549 ms).
Service telnet started. (220 ms).
Service keystore started. (1789 ms).
Service ssl started. (156 ms).
Service ejb started. (2322 ms).
Service servlet_jsp started. (2400 ms).
Service tcsecsecurestorage~service started. (753 ms).
Service dsr started. (2150 ms).
Service jmx started. (2730 ms).
Service webdynpro started. (2526 ms).
Service tcsecdestinations~service started. (753 ms).
Service pmi started. (392 ms).
Service basicadmin started. (894 ms).
Service adminadapter started. (659 ms).
Service sld started. (2824 ms).
Service rfcengine started. (5098 ms).
Service monitor started. (4032 ms).
Service tc.monitoring.logviewer started. (7608 ms).
Service com.sap.aii.af.ms.svc started. (7640 ms).
Service jms_provider started. (11437 ms).
Service com.sap.aii.af.cpa.svc started. (11718 ms).
Service com.sap.aii.adapter.marketplace.svc started. (188 ms).
Service com.sap.aii.adapter.xi.svc started. (282 ms).
Service com.sap.aii.af.security.service started. (204 ms).
Service com.sap.aii.adapter.bc.svc started. (361 ms).
Service com.sap.aii.adapter.mail.svc started. (94 ms).
Service com.sap.aii.adapter.jms.svc started. (644 ms).
Service com.sap.aii.adapter.jdbc.svc started. (612 ms).
Service com.sap.aii.adapter.file.svc started. (659 ms).
Service com.sap.aii.af.ispeak.svc started. (706 ms).
Service com.sap.aii.adapter.rfc.svc started. (1882 ms).
ServiceManager started for 69917 ms.
Framework started for 84184 ms.
SAP J2EE Engine Version 6.40   PatchLevel 87037.313 is running!
PatchLevel 87037.313 October 19, 2004 19:52 GMT
>### Excluding compile: iaik.security.md.SHA::a
Jan 22, 2005 3:03:51 AM         com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Jan 25, 2005 10:17:28... ...utilxi.prop.api.PropertySourceFactory [SAPEngine_Application_Thread[impl:3]_0] Fatal: XI properties could not be initialized. Check ExchangeProfile (or aii.properties).
Thrown:
java.lang.Throwable: dummy Throwable for stack trace
     at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:55)
     at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:528)
     at com.sap.aii.utilxi.misc.api.AIIProperties.<init>(AIIProperties.java:301)
     at com.sap.aii.utilxi.misc.api.AIIProperties.getInstance(AIIProperties.java:328)
     at com.sap.aii.ib.server.util.perf.TimerFactory.<clinit>(TimerFactory.java:86)
     at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:73)
     at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
     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.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy30.processFunction(Unknown Source)
     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.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
     at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Jan 29, 2005 7:37:28 AM         com.sap.engine.core.configuration [SAPEngine_Application_Thread[impl:3]_23] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Jan 31, 2005 4:11:19 PM ...l.cache.WebResourceCache.startService [Thread[Thread-1140,5,SAPEngine_Application_Thread[impl:3]_Group]] Fatal: Tried to save: ~wd_key0_1107205757104
Feb 5, 2005 3:07:25 AM          com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 5, 2005 3:02:56 PM          com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_78] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 6, 2005 3:03:13 PM          com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_77] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 19, 2005 3:15:45 AM         com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
SAP J2EE Engine Version 6.40   PatchLevel 87037.313 is shutting down! PatchLevel 87037.313 October 19, 2004 19:52 GMT
Stopping services.
Service com.sap.aii.adapter.rfc.svc stopped. (439 ms)
Service com.sap.aii.af.ispeak.svc stopped. (78 ms)
Service com.sap.aii.adapter.marketplace.svc stopped. (15 ms)
Service com.sap.aii.adapter.jdbc.svc stopped. (79 ms)

Hi Sunit,
Did you figure out what happened? We're seeing the same issue.
Thanks,
Jay

Having multiple J2EE stacks connected to one CRM ABAP instance for CRM IPC

Hello Experts,
The situation we were looking at is this.
We have 3 distinct teams doing Java development for CRM IPC configurators
Team A - IPC/Ecommerce
Team B - UI
Team C - Order Wrapper
They each wanted to do development in their own landscape (Java Stack)
Additionally, two more landscapes are needed:
a landscape for end 2 end testing of the configuration scenarios
another for a Performance Assessment
To get 5 full dual stack CRM instances was deemed unlikely.
Trying to explore if multiple J2EE's, can be connected to one CRM ABAP system.
It seems we can not, as the CRM ABAP to JEE comminucation is via RFC and there is excatly one RFC_Destination defined per CRM (across all clients). Is this correct?
Thanks
Rocky

May be you can wordsmith your requirement to make it clear what each team is doing. Also, please mention what version of CRM / IPC you are talking about.
From what you have said, I guess IPC/E-Commerce is E-Commerce enhancement. If NWDI is in the picture, you have one track for this enhancement.
The UI - I assume is IPC UI. This is also a Java based web application that shares the same Java stack with the E-Commerce application.
What is Order Wrapper? - If it a custom web application you guys are into, I still don't see why they can't use the same Java "stack".
In the development lifecycle, it is sufficient to have only one IPC environment for each phase. The development team needs only one, unless they have a valid reason to have their own Java stack. I bet they need only one.
If the developers are asking about "Sandbox", they can have their own NetWeaver Developer Workplace in their laptop / desktop.
Easwar Ram
http://www.parxlns.com

Is it possible to run BP ESS/ MSS 60.x on J2EE stack 7.0 (EP 7)?

Hi there,
is it possible to run BP ESS & MSS version 60.x on a J2EE server stack 7.0 (EP7.0) ?
In the contentportfolio area of SDN ([https://www.sdn.sap.com/irj/sdn/contentportfolio]) it is stated, that BP MSS 60.1.2 runs on
---> iView Runtime Technology:
Java / WebDynpro (WAS 6.40 and higher)
(Link: [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/70649942-a46d-2910-be9b-88db98b484f5 [original link is broken]])
Same for BP ESS 60.2.
([https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/d0dfa6ad-9b6d-2910-3d9a-f278ecc80c60 [original link is broken]])
What does "and higher" mean? Do you see any problems ?
I have studied a lot of notes already, but couldn't find a clear statement on this.
Many thanks and kind regards,
Jenny

From what I have "heard", it is possible. I say that because right now, I am on ECC6/EP7 at my current client. But my previous client was on ECC5/EP6 but are now moving to EP7...and have not had problems yet. I would suggest giving it a go in a sandbox system and checking it out...same as you would do for any upgrade. The fallback is that you can upgrade your portal to EP7 but then run a separate server for your XSS apps from ECC5 (that's kinda the point of the WAS anyways....you can run your apps on separate servers than your "main" server). Your JCO connections would point to the "middle" server and those apps would then "talk" back to your ECC5 box. Anyways, I "think" just having them on the EP7 box would work.

Separating ABAP and J2EE stack after an Add-in installation

Hi All,
While I need to migrate an Add-in installation (ABAP + J2EE) to a new machine, there is also a requirement to separate these stacks into two separate instances. Can you please suggest the approach for this? Any suggestions are greatly appreciated.
Regards.

Hi Vincent,
if you want to have a two stack system you better install it that way, meaning two different installation for both.
Unfortunately then you might have some trouble with security after this I cannot foresee.
Regards,
Benny

Removing J2EE stack from dual-stack installation

Hello.
Does anyone know if it's possible to remove the JAVA-stack from a ERP6.0 dual-stack installation ?
We have a ERP 6.0 system running HCM services. The ERP system is installed as dual-stack, but the JAVA-stack is not in use as we also installed a separate NW 7.0 JAVA system hosting portal and java hcm services.
Thank you.
Gerhard.

Hi,
Yes, you can drop Java part from existing dual stack system.
1) Stop cenrtal service instance and all dialog instances of your system.
2) Also, stop J2ee engine of CI from SMICM.
3) Hash out all Java parameters in your default and instance profile (like j2ee, exe/j2ee, exe/jlaunch, jstartup etc.)
4) Delete central service instance.
5) Delete Database schema
6) Delete directories (/usr/sap/<SAPSID>/DVEBMGS<xx>/SDM and /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee)
Thanks
Sunny

Problem starting J2EE stack

Hello everybody,
I am running a Netweaver server both Java and ABAP stack on the same system ie an AIX system. The ABAP stack would start up easily but the java stack woudnt. I apply the commands startsap J2EE and it says IGS successfully started but I cannot access http://servername:50000/ and http://servername:8000 says J2EE service not available. I cant figure out the problem even by seeing the logs. I am attaching the logs here. Any help is appreciated.
Regds
Roney
applications.0.log
#1.5#000255533D49001100000017000D10920004297CF317C9BB#1171516537948#/Applications/JMS##com.sap.jms.client.connection.ConnectionFactory.getSocket#J2EE_GUEST#1####8cf9ca70bcb311dbc4d9000255533d49#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.jms.client.connection.ConnectionFactory#Plain###The following hosts (hostname:port) could not be reached: - Please check host names and ports.#
#1.5#000255533D49001C00000019000D10920004297CF31E2FD4#1171516538367#/Applications/JMS##com.sap.jms.client.connection.ConnectionFactory.getSocket#J2EE_GUEST#1####8ca05fd0bcb311db8f40000255533d49#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#com.sap.jms.client.connection.ConnectionFactory#Plain###The following hosts (hostname:port) could not be reached: - Please check host names and ports.#
#1.5#000255533D49001B00000019000D10920004297CF325590B#1171516538837#/Applications/JMS##com.sap.jms.client.connection.ConnectionFactory.getSocket#J2EE_GUEST#1####8c83d720bcb311dbc58b000255533d49#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#com.sap.jms.client.connection.ConnectionFactory#Plain###The following hosts (hostname:port) could not be reached: - Please check host names and ports.#
#1.5#000255533D4900110000001A000D10920004297CF3282763#1171516539021#/Applications/JMS##com.sap.jms.client.connection.ConnectionFactory.getSocket#J2EE_GUEST#1####8cf9ca70bcb311dbc4d9000255533d49#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.jms.client.connection.ConnectionFactory#Plain###The following hosts (hostname:port) could not be reached: - Please check host names and ports.#
#1.5#000255533D49001800000011000D10920004297CF330667F#1171516539561#/Applications/JMS#sap.com/irj#com.sap.jms.client.connection.ConnectionFactory.getSocket#J2EE_GUEST#1####8aebaaf0bcb311dbbd66000255533d49#Thread[Thread-76,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#com.sap.jms.client.connection.ConnectionFactory#Plain###The following hosts (hostname:port) could not be reached: - Please check host names and ports.#
#1.5#000255533D49001B0000001C000D10920004297CF334F46D#1171516539860#/Applications/JMS##com.sap.jms.client.connection.ConnectionFactory.getSocket#J2EE_GUEST#1####8c83d720bcb311dbc58b000255533d49#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#com.sap.jms.client.connection.ConnectionFactory#Plain###The following hosts (hostname:port) could not be reached: - Please check host names and ports.#
#1.5#000255533D49002500000000000D10920004297CF41240EA#1171516554363#/Applications/JMS##com.sap.jms.client.connection.AsyncCloser######9c379da0bcb311dbb806000255533d49#SAPEngine_System_Thread[impl:5]_71##0#0#Warning#1#com.sap.jms.client.connection.AsyncCloser#Plain###A JMS object could not be closed properly from the AsyncCloser Thread. Please see trace file for more details.#
#1.5#000255533D49003400000001000D10920004297CF5290BBE#1171516572634#/Applications/SupportPlatform/SPApplication#sap.com/com.sapportals.supportplatform#com.sapportals.supportplatform.SupportPlatform#SAP*#60####a71b8c90bcb311dbb89c000255533d49#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#com.sapportals.supportplatform.SupportPlatform#Plain###Problem while un-registering MBean
:SAP_J2EECluster="",SAP_J2EEClusterNode="",j2eeType=SAP_AnalyzerModelMBean,name=AnalyzerModelBean
com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null
     at com.sap.engine.services.jmx.JmxFrame.getInnerMBeanServer(JmxFrame.java(Inlined Compiled Code))
     at com.sap.engine.services.jmx.ClusterInterceptor.getInnerMBS(ClusterInterceptor.java(Inlined Compiled Code))
     at com.sap.engine.services.jmx.ClusterInterceptor.getMBSC(ClusterInterceptor.java(Compiled Code))
     at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java(Compiled Code))
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java(Compiled Code))
     at com.sapportals.supportplatform.SupportPlatform.destroy(SupportPlatform.java:222)
     at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:71)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at javax.security.auth.Subject.doAs(Subject.java:555)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:714)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

This is why the dispatcher coudnt start
[Thr 1] JLaunchISetDebugMode: set debug mode [no]
[Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [dispatcher]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Denv.class.path=:/db2/db2pod/sqllib/java/db2java.zip:/db2/db2pod/sqllib/java/runtime.zip:.
-> arg[ 3]: -Djava.security.policy=.\java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Djco.jarm=1
-> arg[ 6]: -verbose:gc
-> arg[ 7]: -XX:+UseParNewGC
-> arg[ 8]: -XX:+PrintGCTimeStamps
-> arg[ 9]: -Drdbms.driverLocation=/usr/opt/db2_08_01/java/db2jcc.jar:/usr/opt/db2_08_01/java/db2jcc_license_cu.jar
-> arg[ 10]: -Dsys.global.dir=/usr/sap/POD/SYS/global/
-> arg[ 11]: -Dsys.global.dir=/usr/sap/POD/SYS/global
-> arg[ 12]: -Dapplication.home=/usr/sap/POD/DVEBMGS00/j2ee/os_libs
-> arg[ 13]: -Djava.class.path=/usr/sap/POD/DVEBMGS00/j2ee/os_libs/jstartup.jar:./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> arg[ 14]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/POD/DVEBMGS00/j2ee/os_libs:/usr/sap/POD/SYS/exe/run:/usr/sap/POD/SYS/exe/runU:/db2/db2pod/sqllib/lib:/usr/lib:/usr/sap/POD/DVEBMGS00/j2ee/os_libs:/usr/sap/POD/DVEBMGS00/j2ee/os_libs:/usr/lib:/lib:/usr/sap/POD/SYS/exe/run:/usr/sap/POD/SYS/exe/runU:/db2/db2pod/sqllib/lib
-> arg[ 15]: -Dmemory.manager=170M
-> arg[ 16]: -Xmx170M
-> arg[ 17]: -Xms170M
-> arg[ 18]: -DLoadBalanceRestricted=no
-> arg[ 19]: -Djstartup.mode=JCONTROL
-> arg[ 20]: -Djstartup.ownProcessId=893004
-> arg[ 21]: -Djstartup.ownHardwareId=N2046619315
-> arg[ 22]: -Djstartup.whoami=dispatcher
-> arg[ 23]: -Djstartup.debuggable=no
-> arg[ 24]: -DSAPINFO=POD_00_dispatcher
-> arg[ 25]: -DSAPSTART=1
-> arg[ 26]: -DCONNECT_PORT=33792
-> arg[ 27]: -DLISTEN_PORT=33791
-> arg[ 28]: -DSAPSYSTEM=00
-> arg[ 29]: -DSAPSYSTEMNAME=POD
-> arg[ 30]: -DSAPMYNAME=pordev_POD_00
-> arg[ 31]: -DSAPPROFILE=/usr/sap/POD/SYS/profile/POD_DVEBMGS00_pordev
-> arg[ 32]: -DFRFC_FALLBACK=ON
-> arg[ 33]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 34]: -DSAPSTARTUP=1
-> arg[ 35]: -DSAPSYSTEM=00
-> arg[ 36]: -DSAPSYSTEMNAME=POD
-> arg[ 37]: -DSAPMYNAME=pordev_POD_00
-> arg[ 38]: -DSAPDBHOST=pordev
-> arg[ 39]: -Dj2ee.dbhost=PORDEV
[Thr 772] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx_mt.c 500]
[Thr 772] *** ERROR => Cannot load Java VM (<default>) (rc=-1) [jlnchxxi_mt. 591]
[Thr 772] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 772] JLaunchCloseProgram: good bye (exitcode=-1)
Any ideas why?

Identify OSS Notes Applied to J2EE Stack

We are running CRM 5.0 Netweaver CRM 5.0 2004s. We have applied several OSS Notes to the Java stack in DEV, QA, and PRD. Is there any way to determine which notes have been applied, short of re-applying the notes? Some of you may remember life before transaction SNOTE on the ABAP stack. The J2EE engine seems to be at that same stage, with no easy way to determine patches applied. Am I missing something?
Best regards,
Mike

Thanks Timo,
I realize there is no equivalent to SNOTE on the Java side, but is there any way to determine which notes have been applied, short of re-applying?
Take care,
Mike

ABAP and J2EE-Stacks in SAP WEB AS

Hi,
I have two questions about the technical architecture of SAP WebAS, particularly about the ABAP- and J2EE-Server.
Can someone recommend detailed papers/guides (besides help.sap.com)describing:
1) the management of processes and resources in two parts (ABAP and Java)
and
2) The communication mechanisms between J2EE- and ABAP-server.
What are the problems with JCo?
Is there other possibilities to communicate between 2EE- and ABAP-server.(besides JCO), what is the performance in this case compares with JCO?
Thank you!
Peter Hneke

Hi
please have a look in to this Pdf Doc . might be of soem help to you .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b52456bd-0a01-0010-6d9b-f153bf15a82f
Apart from JCO communication between JAVA and ABAP can also be handled using ESA services .
please have a llok at these blogs
/people/scott.campbell/blog/2005/05/16/the-esa-is-coming-the-esa-is-coming
/people/kevin.liu/blog/2005/10/17/esa-soa-es
/people/harsh.chauhan/blog/2005/08/27/building-esa-and-delivering-it-through-caf
/people/sap.user72/blog/2005/10/28/the-fundamental-problem-solved-by-esa
Hope this helps . pelase do not forget to reward points , if helpful
regards
rajeshkr

J2EE STACK

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,Shai

Hi,
Plz check the configuration of the Server where u have installed. At least one GB RAM is minimum recommended.
Secondly during the restart ask all users to logout of the J2EE Server. This will minimize the time taken for restart.
Cheers!!!
Sukanta Rudra

J2EE stack 01

Similar Messages

Maybe you are looking for