WebAS JAVA 640 - Services Timeout during startup

[Former Member]

Hi,

During the startup of WebAS JAVA, the server just keeps on showing status of Starting Applications in MMC. Looking at the std_server0.out file, it tells that a few services timedout. File dump is hereunder. Can anyone suggest what might be causing this?

Thanks and regards

Shehryar

STD_SERVER0.OUT

-

---

stdout/stderr redirect

-

---

node name : server0

pid : 2092

system name : J2E

system nr. : 00

started at : Thu Apr 19 13:34:53 2007

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 87289.311 is starting...

Loading: LogManager ... 766 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 156 ms.

Loading: ThreadManager ... 63 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... 219 ms.

Loading: LockingManager ... 62 ms.

Loading: ConfigurationManager ... 844 ms.

Loading: LicensingManager ... 31 ms.

Loading: ServiceManager ...

0.000: [GC 0.000: [ParNew: 43517K->2594K(65280K), 0.0299898 secs] 43517K->2594K(502528K), 0.0300233 secs]

Loading services.:

Service memory started. (16 ms).

Service cross started. (78 ms).

Service file started. (32 ms).

Service jmx_notification started. (266 ms).

Service trex.service started. (219 ms).

Service runtimeinfo started. (15 ms).

2.581: [GC 2.581: [ParNew: 46114K->4338K(65280K), 0.0415510 secs] 46114K->4338K(502528K), 0.0415880 secs]

Service userstore started. (0 ms).

Service timeout started. (297 ms).

Service p4 started. (203 ms).

Service classpath_resolver started. (0 ms).

Service tc_secvsi~service started. (797 ms).

Service tc_secwssec~service started. (750 ms).

Service deploy started. (1438 ms).

Service apptracing started. (62 ms).

Timed out services:

Service ssl.

Service connector.

Service tc.monitoring.logviewer.

Service keystore.

Service log_configurator.

Service shell.

Service prtbridge.

Service webdynpro.

Service appclient.

Service com.sap.security.core.ume.service.

Service http.

Service locking.

Service pmi.

Service tc_secsaml~service.

Service sld.

Service com.sap.portal.prt.sapj2ee.

Service jms_provider.

Service basicadmin.

Service classload.

Service iiop.

Service dbpool.

Service licensing.

Service adminadapter.

Service failover.

Service telnet.

Service jmsconnector.

Service servlet_jsp.

Service ejb.

Service dsr.

Service monitor.

Service tc_secdestinations~service.

Service tc_secsecurestorage~service.

Service naming.

Service security.

Service configuration.

Service applocking.

Service jmx.

Service ts.

Service webservices.

Service DQE.

Service tc_eCATTPingservice.

Service javamail.

Service rfcengine.

ServiceManager started for 303829 ms.

Framework started for 306766 ms.

SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is running!

PatchLevel 87289.311 November 18, 2004 20:31 GMT

SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is shutting down! PatchLevel 87289.311 November 18, 2004 20:31 GMT

[praveenkumar_kadi · Accepted solution]

Hi,

Check if you have enough memory allocated. I think it's because of memory issue.

Also, check default params in config tool for the correctness.

for ex:in the configtool.bat check

For the instance_ID:-

Message Server and Bootstrap tab

Java parameters settings

Servers General Tab

Max heap size

-Xms

-XX:NewSize=

-XX:MaxNewSize=64m

-XX:NewRatio=3

-XX:+DisableExplicitGC

The DISPATCHER ID

General TAB

Ensure the max heap size is 64

-Xms64M

Bootstrap TAB

Max heap size 384

(check Java parameters set)

the SERVER ID

General TAB

Max Heap Size 528

Java parameters as below....

-Xms528M

-XX:PermSize=192M

-XX:MaxPermSize=192M

-XX:NewSize=160M

-XX:MaxNewSize=160M

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-verbose:gc

Bootstrap Tab

383MB

check java parameters set

Shut down the Java stack in MMC, pressed the Retry button, and all should become fine.

Hope this helps.reward points if so,

[Former Member · Accepted solution]

Hi,

Thanks for the response. I am trying to change the settings through ConfigTool but it seems to take forever to apply changes to parameters. Its just stuck at message Applying changes....

Any ideas?

Regards

[Former Member · Accepted solution]

btw, the old settings I have used to work just fine until yesterday.

Regards

[Former Member]

The DB log was full.