cancel
Showing results for 
Search instead for 
Did you mean: 

Web Application server crashes

Former Member
0 Kudos

Hi,

I have my Webdynpro application deployed on to WAS. The deployment goes successfully. But when i run the application, the server is coming down. I have no clue what is going on.

Earlier the same application used to work perfectly. the only difference is i have pointed my Webdynpro to a different R/3 system, deleted the models and created new models. No build/compilation errors. No errors during deployment.

Please suggest.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Kumar,

It will be good if you could check the work directory of the server

(something like C:\usr\sap\J2E\JC00\work) and have a look at the last modified files searching for crash reason.

Perhaps as a result of your changes you are loading too many jars in the permsize generation or there is some kind of endless cycle that keeps allocating memory and the server crashes with OutOfMemory.

Hope it helps

Peter

JPReyes
Active Contributor
0 Kudos

Yes, as Peter said search and post errors on std_server0.out and std_dispatcher.out in the work directory to have a better idea of what is making the WebAS crash..

Regards

Juan Reyes

Former Member
0 Kudos

Hi,

Thank you very much for the info.

I have checked both the files. There is not indication of OutOfMemory or any such thing.

Find below the last few lines from those files;

<b>std_server0.out</b>

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 110 ms.

Loading: ThreadManager ... 15 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... 203 ms.

Loading: LockingManager ... 63 ms.

Loading: ConfigurationManager ... 1531 ms.

Loading: LicensingManager ... 47 ms.

Loading: ServiceManager ...

0.000: [GC 0.000: [ParNew: 43504K->3560K(65280K), 0.0182775 secs] 43504K->3560K(502528K), 0.0183215 secs]

Loading services.:

Service memory started. (31 ms).

Service runtimeinfo started. (0 ms).

Service timeout started. (63 ms).

Service cross started. (63 ms).

Service file started. (47 ms).

Service trex.service started. (47 ms).

Service p4 started. (250 ms).

Service classpath_resolver started. (47 ms).

Service tcsecwssec~service started. (156 ms).

Service userstore started. (47 ms).

Service jmx_notification started. (78 ms).

4.024: [GC 4.024: [ParNew: 47060K->6591K(65280K), 0.0243041 secs] 47060K->6591K(502528K), 0.0243509 secs]

Service log_configurator started. (4812 ms).

Service locking started. (0 ms).

6.535: [GC 6.535: [ParNew: 50111K->10400K(65280K), 0.0320170 secs] 50111K->10400K(502528K), 0.0320660 secs]

Service naming started. (516 ms).

Service appclient started. (422 ms).

Service failover started. (532 ms).

Service javamail started. (735 ms).

Service jmsconnector started. (812 ms).

Service ts started. (828 ms).

Service licensing started. (62 ms).

Service connector started. (719 ms).

Service http started. (859 ms).

Service webservices started. (2265 ms).

Service deploy started. (7875 ms).

Service configuration started. (47 ms).

Service apptracing started. (187 ms).

10.913: [GC 10.913: [ParNew: 53920K->12571K(65280K), 0.0320241 secs] 53920K->12571K(502528K), 0.0320691 secs]

Service dbpool started. (1578 ms).

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

Service security started. (1719 ms).

15.842: [GC 15.842: [ParNew: 56091K->15916K(65280K), 0.0423570 secs] 56091K->15916K(502528K), 0.0424033 secs]

Service classload started. (828 ms).

Service applocking started. (734 ms).

Service shell started. (766 ms).

Service tceCATTPingservice started. (94 ms).

Service telnet started. (140 ms).

Service ejb started. (2328 ms).

Service webdynpro started. (1141 ms).

Service keystore started. (2266 ms).

Service rfcengine started. (547 ms).

Service tcsecsecurestorage~service started. (156 ms).

Service servlet_jsp started. (3422 ms).

Service ssl started. (94 ms).

Service dsr started. (1609 ms).

Service tcsecdestinations~service started. (515 ms).

Service sld started. (1391 ms).

Service pmi started. (297 ms).

Service jmx started. (2890 ms).

Service tclmctcculculservice_sda started. (0 ms).

Service tcsecvsi~service started. (2250 ms).

23.742: [GC 23.742: [ParNew: 59436K->20450K(65280K), 0.0467592 secs] 59436K->20450K(502528K), 0.0468089 secs]

Service basicadmin started. (2578 ms).

Service adminadapter started. (578 ms).

Service com.sap.portal.pcd.gl started. (31 ms).

25.498: [GC 25.498: [ParNew: 63965K->19245K(65280K), 0.0474574 secs] 63965K->21928K(502528K), 0.0475166 secs]

Service monitor started. (1219 ms).

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

31.309: [GC 31.309: [ParNew: 62765K->19935K(65280K), 0.0383097 secs] 65448K->22618K(502528K), 0.0383602 secs]

Service com.sap.portal.prt.sapj2ee started. (8547 ms).

Service prtbridge started. (13515 ms).

Service tclmctcculservice_sda started. (14500 ms).

Service jms_provider started. (14687 ms).

38.173: [GC 38.173: [ParNew: 63455K->20304K(65280K), 0.0486018 secs] 66138K->25804K(502528K), 0.0486464 secs]

Service DQE started. (3172 ms).

ServiceManager started for 42047 ms.

Framework started for 45188 ms.

SAP J2EE Engine Version 6.40 PatchLevel 98256.313 is running!

PatchLevel 98256.313 September 20, 2005 18:54 GMT

>45.322: [GC 45.322: [ParNew: 63824K->19778K(65280K), 0.0495072 secs] 69324K->28256K(502528K), 0.0495533 secs]

SAP J2EE Engine Version 6.40 PatchLevel 98256.313 is shutting down! PatchLevel 98256.313 September 20, 2005 18:54 GMT

<b>std_dispatcher.out</b>

Loading: PoolManager ... 16 ms.

Loading: ThreadManager ... 188 ms.

Loading: IpVerificationManager ... 15 ms.

Loading: ConnectionsManipulator ... 188 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... 360 ms.

Loading: PortsManager ... 31 ms.

Loading: LockingManager ... 109 ms.

Loading: ConfigurationManager ... 2516 ms.

Loading: LicensingManager ... 94 ms.

Loading: ServiceManager ...

Loading services.:

Service licensing started. (16 ms).

Service memory started. (32 ms).

Service httptunneling started. (15 ms).

Service timeout started. (47 ms).

Service security started. (0 ms).

Service sld started. (63 ms).

Service webservices started. (32 ms).

Service keystore started. (46 ms).

Service jmx_notification started. (32 ms).

Service shell started. (578 ms).

Service jmx started. (375 ms).

Service telnet started. (125 ms).

Service p4 started. (813 ms).

Service classload started. (0 ms).

Service log_configurator started. (2422 ms).

Service configuration started. (0 ms).

Service basicadmin started. (422 ms).

Service http started. (609 ms).

Service adminadapter started. (78 ms).

Service jms_provider started. (656 ms).

Service monitor started. (1187 ms).

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

ServiceManager started for 6812 ms.

Framework started for 12297 ms.

SAP J2EE Engine Version 6.40 PatchLevel 98256.313 is running!

PatchLevel 98256.313 September 20, 2005 18:54 GMT

>

Please suggest

Former Member
0 Kudos

Closing the thread.

Former Member
0 Kudos

Hi

ia m facing the same issue. Pleas elet me know how you fixed the same