Skip to Content
author's profile photo Former Member
Former Member

WAS 6.40 keeps stopping


I have installed WAS 6.40 (or is that really 6.30 with a bunch of patches 😉 on my laptop (Windows XP) and it keeps stopping for no apparent reason. I have been looking thru the Visual admin and the Config tool but I can't seem to find a stop parameter. I did find a timeout parameter and I changed it from 5 to 45 but that hasn't helped. Does anyone know if there is a timeout paramter and where it may be located and how I should change it?

Cheers and TIA,


Add comment
10|10000 characters needed characters exceeded

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 02, 2004 at 07:50 PM

    Hmmm.... Seems like when I try to work with the SLD it is stopping my J2EE engine. Further investigation is needed

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 03, 2004 at 06:54 AM


    if you use your version for more than 90 days your license has expired and the WAS engine stops every couple of minutes. If so, you have to re-install the sneak preview.

    Best Regards, Astrid

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 04, 2004 at 02:06 PM

    We have a freshly installed 6.40 (well 6.30 with patch 6)that keeps restarting about every 2 minutes as well. This is integrated with a 4.7 R/3 system and was just installed yesterday. BTW-Why are there so many logs in so many different places instead of just one central location?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Logging in 6.40 Web AS is actually quite centralized.




      The SAP J2EE Engine provides a centralized system for logging and tracing. The system consists of the Log Manager, Log Configurator Service, and Log Viewer. All the logs generated are written in the <SAPj2eeEngine_install_dir>/<server or dispatcher>/log/ directory. The basis of the logging system is the SAP Logging API.


      SAP Logging API

      This API provides means for writing structured data into a file, a console, or another output destination. It defines two general routines that a user typically performs: logging and tracing. Logging is generally used for distinguished problematic areas in a productive system. This is why it is usually switched on. Tracing, on the other hand, is mainly used by developers and supporters to find coding problems in the product. It is therefore usually switched off. Log files can be limited to certain severity levels. That is, only data of a defined severity is collected. The order of the constants is, with increasing severity: DEBUG, PATH, INFO, WARNING, ERROR, FATAL.

      The Logging API works with several general terms that provide an abstraction for the different entities involved in the logging and tracing process. For more information about controllers, logs, formatters, and filters, see SAP Logging API.

      Log Configurator Service

      The Log Configurator Service provides a runtime for configuration of logs and traces. For more information, see Log Configuration.

      Log Manager

      This manager is part of the Java Enterprise Runtime and is the first manager to be started at system startup. It configures the logging routines for the kernel by reading the configuration specified in the file log-configuration.xml.

      The Log Manager provides means for storing system critical logs in the database. For more information, see Configuring System Critical Logs.

      This manager also enables you to switch on/off the feature for writing traces to one file and for excluding certain locations from being written to one trace file. This is done using the ForceSingleTraceFile and SingleTraceFile_UnrestrictedLocations properties correspondingly. For more information, see Log Manager properties in the Reference Manual.

      Log Viewer

      Provides a runtime control for displaying log messages. For more information, see Log Viewer.

      The best way to look at the logs is simply to use the logviewer (either inside visual admin or standalone).