503 You have requested an application that is currently stopped

[Former Member]

Hi All,

We applied SP7 on NW7.01 EHP1 AS Java and we tried restarting the system. The work processes seem like they have started but Dispatcher and Server0 still show as it they are coming up but dont... Looking at the logs in Std_Server0 file the logs are below:

SAP J2EE Engine Version 7.01 PatchLevel 97158. is starting...

Error occurred while preloading classes of security providers from jre/lib/ext folder: java.lang.UnsatisfiedLinkError: com/ibm/net/ssl/www2/protocol/http/NTLMAuthSequence.initFirst()V

file.toString() - /QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit/jre/lib/ext/ibmjsseprovider2.jar

file.getName() - ibmjsseprovider2.jar

file.getPath() - /QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit/jre/lib/ext/ibmjsseprovider2.jar

file.getAbsolutePath() - /QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit/jre/lib/ext/ibmjsseprovider2.jar

ZipFile.toString() - java.util.jar.JarFile@76887688

ZipFile.getName() - /QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit/jre/lib/ext/ibmjsseprovider2.jar

Stack trace:

java.lang.UnsatisfiedLinkError: com/ibm/net/ssl/www2/protocol/http/NTLMAuthSequence.initFirst()V

at com.ibm.net.ssl.www2.protocol.http.NTLMAuthSequence.<clinit>(NTLMAuthSequence.java:9)

at java.lang.J9VMInternals.initializeImpl(Native Method)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)

at java.lang.Class.forNameImpl(Native Method)

at java.lang.Class.forName(Class.java:152)

at com.sap.engine.core.Framework.preloadExtJar(Framework.java:351)

at com.sap.engine.core.Framework.loadExtSecurityProviders(Framework.java:325)

at com.sap.engine.core.Framework.loadManagers(Framework.java:252)

at com.sap.engine.core.Framework.start(Framework.java:190)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)

at java.lang.Thread.run(Thread.java:770)

Loading: LogManager ... 456 ms.

Loading: PoolManager ... 5 ms.

Loading: ApplicationThreadManager ... 701 ms.

Loading: ThreadManager ... 58 ms.

Loading: IpVerificationManager ... 11 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... 876 ms.

Loading: LockingManager ... 48 ms.

Loading: ConfigurationManager ... 1968 ms.

Loading: LicensingManager ... 66 ms.

Loading: CacheManager ... 94 ms.

Loading: ServiceManager ...

Loading services.:

Service runtimeinfo started. (15 ms).

Service cross started. (114 ms).

Service file started. (115 ms).

Service timeout started. (139 ms).

Service memory started. (137 ms).

Service trex.service started. (174 ms).

Service userstore started. (34 ms).

Service jmx_notification started. (66 ms).

Service p4 started. (284 ms).

Service classpath_resolver started. (67 ms).

Service deploy started. (5129 ms).

Service MigrationService started. (45 ms).

Service bi_mmrdeployer started. (10 ms).

Service log_configurator started. (9614 ms).

Service locking started. (9 ms).

Service http started. (250 ms).

Service naming started. (401 ms).

Service licensing started. (45 ms).

Service appclient started. (78 ms).

Service failover started. (81 ms).

Service ts started. (120 ms).

Service javamail started. (155 ms).

Service jmsconnector started. (200 ms).

Service connector started. (189 ms).

Service configuration started. (39 ms).

Service iiop started. (283 ms).

Service dbpool started. (3049 ms).

Service UT started. (12 ms).

Service com.sap.security.core.ume.service started. (1474 ms).

Service tc_disdic~srv started. (920 ms).

Service security started. (1846 ms).

Service classload started. (43 ms).

Service applocking started. (123 ms).

Service shell started. (189 ms).

Service keystore started. (189 ms).

Service telnet started. (52 ms).

Service ssl started. (18 ms).

Service tc_eCATTPingservice started. (300 ms).

Service tc_secsecurestorage~service started. (261 ms).

Service ejb started. (595 ms).

Service caf_ummetadata~imp started. (446 ms).

Service tc_seccertrevoc~service started. (488 ms).

Service dsr started. (578 ms).

Service sld started. (640 ms).

Service jmx started. (1180 ms).

Service servlet_jsp started. (1283 ms).

Service com.adobe~DocumentServicesLicenseSupportService started. (181 ms).

Service com.adobe~FontManagerService started. (308 ms).

Service tc_secwssec~service started. (1139 ms).

Service CUL started. (341 ms).

Service tc_secdestinations~service started. (1222 ms).

Service caf_umrelgroups~imp started. (1517 ms).

Service webdynpro started. (352 ms).

Service com.adobe~DocumentServicesBinaries2 started. (485 ms).

Service com.adobe~DataManagerService started. (698 ms).

Service tc_lmctc_confsservice_sda started. (885 ms).

Service com.adobe~XMLFormService started. (434 ms).

Service com.adobe~PDFManipulation started. (501 ms).

Service com.adobe~DocumentServicesDestProtoService started. (464 ms).

Service tc_secvsi~service started. (632 ms).

Service basicadmin started. (1413 ms).

Service rfcengine started. (772 ms).

Service apptracing started. (309 ms).

Service com.adobe~LicenseService started. (107 ms).

Service pmi started. (60 ms).

Service adminadapter started. (286 ms).

Service com.adobe~DocumentServicesConfiguration started. (269 ms).

Service caf_runtimeconnectivity~impl started. (19821 ms).

Service tc.monitoring.logviewer started. (1737 ms).

Feb 2, 2011 8:09:57 AM com.adobe.service.TrustManagerService [SAPEngine_System_Thread[impl:5]_21] Fatal: $$$/TrustManager/Exception: Directory specified for CRLDirectory: "/usr/sap/D19/SYS/global/AdobeDocumentServices/TrustManagerService/trust/CRLs" is not a valid directory.

Service com.adobe~TrustManagerService started. (249 ms).

Service webservices started. (2121 ms).

Service jms_provider started. (2479 ms).

Service monitor started. (2459 ms).

ServiceManager started for 24432 ms.

Framework started for 30682 ms.

SAP J2EE Engine Version 7.01 PatchLevel 97158. is running! PatchLevel 97158. December 17, 2010 11:36 GMT

>

SAP J2EE Engine Version 7.01 PatchLevel 97158. is shutting down! PatchLevel 97158. December 17, 2010 11:36 GMT

Stopping services.

Service servlet_jsp stopped. (135 ms)

Service com.adobe~LicenseService stopped. (3 ms)

Service sld stopped. (4 ms)

Service com.adobe~DataManagerService stopped. (21 ms)

Service tc.monitoring.logviewer stopped. (323 ms)

Service jms_provider stopped. (16 ms)

Service CUL stopped. (1 ms)

Service pmi stopped. (361 ms)

Service apptracing stopped. (173 ms)

Service com.adobe~TrustManagerService stopped. (23 ms)

Service monitor stopped. (37 ms)

Service tc_lmctc_confsservice_sda stopped. (15 ms)

Service com.adobe~FontManagerService stopped. (24 ms)

Service com.adobe~DocumentServicesDestProtoService stopped. (8 ms)

Service com.adobe~DocumentServicesConfiguration stopped. (1 ms)

Service adminadapter stopped. (5 ms)

Service basicadmin stopped. (15 ms)

Service rfcengine stopped. (5 ms)

Service com.adobe~DocumentServicesBinaries2 stopped. (13 ms)

Service com.adobe~DocumentServicesLicenseSupportService stopped. (6 ms)

Service com.adobe~XMLFormService stopped. (13 ms)

Service com.adobe~PDFManipulation stopped. (10 ms)

Service webservices stopped. (51 ms)

Service jmx stopped. (2 ms)

Service appclient stopped. (0 ms)

Service licensing stopped. (1 ms)

Service javamail stopped. (0 ms)

Service tc_secvsi~service stopped. (15 ms)

Service webdynpro stopped. (77 ms)

Service tc_secdestinations~service stopped. (1 ms)

Service tc_secwssec~service stopped. (0 ms)

Service tc_secsecurestorage~service stopped. (0 ms)

Service configuration stopped. (4 ms)

Service tc_eCATTPingservice stopped. (1 ms)

Service jmsconnector stopped. (4 ms)

Service UT stopped. (12 ms)

Service tc_disdic~srv stopped. (1 ms)

Service caf_umrelgroups~imp stopped. (1 ms)

Service caf_ummetadata~imp stopped. (1 ms)

Service applocking stopped. (4 ms)

Service ejb stopped. (10 ms)

Service telnet stopped. (0 ms)

Service classload stopped. (2 ms)

Service shell stopped. (18 ms)

Service dsr stopped. (18 ms)

Service ssl stopped. (1 ms)

Service tc_seccertrevoc~service stopped. (8 ms)

Service keystore stopped. (14 ms)

Service security stopped. (0 ms)

Service com.sap.security.core.ume.service stopped. (1 ms)

Service dbpool stopped. (113 ms)

Service iiop stopped. (22 ms)

Service ts stopped. (1 ms)

Service failover stopped. (0 ms)

Service connector stopped. (6 ms)

Service naming stopped. (2 ms)

Service userstore stopped. (0 ms)

Service memory stopped. (1 ms)

Service MigrationService stopped. (6 ms)

Service file stopped. (0 ms)

Service bi_mmrdeployer stopped. (0 ms)

Service deploy stopped. (2 ms)

Service locking stopped. (0 ms)

Service classpath_resolver stopped. (2 ms)

Service p4 stopped. (0 ms)

Service cross stopped. (1 ms)

Service http stopped. (2 ms)

Service caf_runtimeconnectivity~impl stopped. (0 ms)

Service timeout stopped. (1 ms)

Service trex.service stopped. (0 ms)

Service log_configurator stopped. (1 ms)

Service jmx_notification stopped. (1 ms)

Service runtimeinfo stopped. (0 ms)

Could anyone please let me know what is possibly going wrong.

Thanks,

Shankam

[sunny_pahuja2]

Hi,

Generally after upgrade server0 nodes take a long time to start as they have to sync all binaries and application. Please give a restart again and see if it comes up in sometime.

Thanks

Sunny

[Former Member]

HI Sunny,

After a few seconds of starting the system the Server0 and Dispatcher job seems to disappear... and doesnt start after that.. (Even after giving it ample time to start).

Thanks,

Shankam

Edited by: Praveen Shankam on Feb 2, 2011 6:58 PM

[Former Member]

check the default trace log. paste the recent log update of default trace.

[Former Member]

Check the log dev_server0 and dev_disp and you will find out the cause.

Also check from OS levele whether the processes JCONTROL and JLAUNCH are running once you start your system.