on 06-06-2007 2:03 PM
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
actually it works but on another ports, after changing it in VA it works fine again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aliaksandr,
If you pasted the entire content of instance.properties then it looks like a total nonsense. For example it does not have the main class specified, e.g. bootstrap.MainClass=com.sap.engine.offline.OfflineToolStart and so on and so on...
Please have a look at SAP Note <a href="https://service.sap.com/sap/support/notes/723909">723909</a> for the JVM settings for the J2EE Engine 6.40/7.0.
HTH!
-Vladimir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.