J2EE startup framework

Hai all,
is the startup Framework supported on SP2 Patch3 with J2EE PL 19?? And where can I find these files for installation on marketplace
Wolfgang

Hello Roth,
Startup framework 6.0 for 6.2 should work with all patches. Though I used it in P3 + PL22 combination and not with PL19.
Please upgrade to PL23, specially if you are planning cluster......
Regards
Ashutosh

Similar Messages

  • How to determine 640/J2EE Startup Framework Binary Patch Level?

    Hi All,
    We are running BI ABAP with Java Add-in on WAS 640/SUSE/Oracle.
    In the ABAP world, there are many options for determining the current kernel patch level.  Disp+work -v, SYSTEM->STATUS, etc..
    How do I determine the patch level of the J2EE startup framework (ie: jlaunch, jcontrol, etc..)?  If I run these commands with '-version', I get a patch level of 0. From System Information, the Cluster Kernel Version is 6.40 PatchLevel 105424.313. 
    What I am trying to determine is if I have the binaries that map to the latest applied SP (18).  Do I need to download J2EERTOS18.SAR and apply the bits or has that already been done?  Or is the current patch level for the bits fro the J2EERTOS14.SAR file?  Etc...
    Any tips/suggestions?
    Thanks much,
    Greg

    Hi
    You can check the patch number like this;
    D:\usr\sap\FT0\SYS\exe\uc\NTI386>jlaunch -version
    Failed to reserve 1610612736 (0x60000000) bytes before loading DLLs (error 8).
    jlaunch information
    kernel release                700
    kernel make variant           700_REL
    compiled on                   NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
    compilation mode              UNICODE
    compile time                  Jan 23 2008 20:42:28
    update level                  0
    patch number                  128                         <<< Here is the patch number>>
    source id                     0.144
    While regarding which file(s) to apply, please notice that the files you are not talking like
    J2EERTOS16_1, is part of the J2EE support package stack, which can be applied with JSPM.
    Regarding the kernel, you can alway refer to note 19466, and downlaod the lastest kernel from:
    http://service.sap.com/swdc
       Support Packages and Patches ->
       Entry by Application Group "
       SAP NetWeaver and complementary products"
       SAP NETWEAVER" SAP NETWEAVER 7.0"
       Entry by Component"
       Application Server Java
       ===> SAP KERNEL 7.00 64-BIT UNICODE
    Regards,
    Thunder

  • J2EE startup framework and J2EE

    I have changed some Java VM parameters.
    To make above change effective, I have to re-start the J2EE instance.
    But my co-worker  (who left my company)  wrote in his document
    " For the SAP J2EE startup framework, it's NOT sufficient to re-satrt the J2EE
    instance"  to activate above change.
    I did some research on J2EE startup framework. I think it is no longer used in NW7.0
    Could you help me
    -- how do I know a system has SAP J2EE startup framework (I believe it is a concept  prior to 7.0 version).
        Our system is NW7.0.
    --  If it is a J2EE stratup framework, how do I activate above change?
    Thanks a million!

    Hello Christy
    SAP Netweaver 7.0 still has J2EE Startup and Control framework.
    When you change a property normally the tool prompts that a restart is required. Normally you get a description of what kind of restart is needed. "A cluster restart is needed" for example meaning you have to stop/start your J2EE cluster.
    If you are working on a dual stack you can stop/start through transaction SMICM under menu item Administration --> J2EE Cluster --> Send Hard Shutdown --> With Restart. That will hard restart your J2EE cluster and your parameter change (done in configtool I assume) will be activated once the J2EE cluster has restarted.
    If you are working on a single stack SAP system you can stop/start using command prompt stopsap JC<instance number> or through the SAP Management Console.
    You can check the activate VM parameters through the http://<hostname>:<j2ee port>:/index.html page under system information --> VM parameters for the node for which you have made a change.
    Kind regards
    Tom

  • Startup Framework and dbpool

    Hello,
    we are facing some problems installing the startup Framework for our EP (EP 6.0 SP2 Patch 35 on Win/MSSQL).
    We can start the services via MMC and after 1-2 minutes everything is "green". The J2EE is running and we can connect, but the portal doesn't.
    The browser says:
    Service Unavailable 503!
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
    And the jvm_server.out:
    Loading services:
    Loading service: com.sap.portal.license.runtime|license
    May 5, 2006 11:34:31 AM # System_Thread_61 Fatal PcdGlService: cannot get pool factory
    java.security.PrivilegedActionException: java.sql.SQLException: Pool is closed!
    at com.inqmy.services.dbpool.CPool.lazyInit(CPool.java:93)
    at com.inqmy.services.dbpool.CPool.getConnection(CPool.java:139)
    ........Enterprise Portal is shutting down ........
    ...................Successful....................
    I found some postings here regarding those problems and we tried everything (e.g. carriage return at the end of the profiles, Instancenmae: JC00 and so on) - but the portal won't run.
    I found also something regarding the dbpool-service and the strange thing is, that it isn't running and I can't start it (Visual Admin -> Server -> Services -> dbpool). It always says "Pool sapep can't be changed". This message pops up after pressing the start-button. The change-button is disabled and thus I can't change the pool-settings.
    Any Ideas?
    Cheers,
    Kai

    Is the sapep dbpool started when you start the J2EE engine. I would also check that the connection settings for the dbpool are correct, and that you can actually access the database server from the J2EE server. One thing you might also want to check is that the user name that the startup framework starts with has access to the network resources of the other machines you are trying to access, i.e. DB, file system (if any), etc.
    I hope this helps
    Darrell

  • Error running startup framework

    Hi,
    We are running EP 6 Sp2 p4 hf 8 on hp-ux 11.11 operating system, and
    We installed startup framework according to document "Installing and
    Configuring the 6.40 Startup Framework to Use with SAP J2EE Engine 6.20
    (Last update: 23.09.2004)", we installed patch PHCO_30544 for the os.
    We used the latest version of SCSCLIENTEP.SAR.
    The problem is that for a heap size more than 1G the startup framework
    doesn't work.
    The following error is in the file ../os_libs/work/dev_server:
    [Thr 4] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-1)
    [jhvmxx_mt.c 480]
    [Thr 4] *** ERROR => Cannot load Java VM (client) (rc=-1)
    [jlnchxxi_mt. 590]
    [Thr 4] SigISetIgnoreAction : SIG_IGN for signal 18
    [Thr 4] JLaunchCloseProgram: good bye (exitcode=-1)
    Best regards,
    Bogdan<b></b>

    I doubt it is the heap size itself. Have you checked all your java startup params (flags). Having an improper flag, such as -XXNewSize=192 (missing a ":" between XX and NewSize) will give you such an error.

  • Webdynpro application automatic start after j2ee startup

    Hi ,
    Is there a way to automatically start any specific webdynpro applications after j2ee startup
    Oren

    I guess you can write batch file for that.
    Example
    suppose you have a bat file which starts J2EE engine, startJ2EE.
    You can write a new bat file with following commands.
    startJ2EE.bat
    explorer http://<server>:<port>/webdynpro/<URL as application>
    Let me know if you need more help
    Ashutosh

  • URGENT SUGGESTIONS- j2ee WEB FRAMEWORK

    Hi All,
    As a part of our part time project me and my friends are exploring on development of a j2ee web framework. For this we are exploring the behaviours of some famous frameworks such as STRUTS.
    We are looking at the normal Controller model, The automatic httprequest to Java bean bindings and other such features.
    We would like to hear more suggestions as to what
    1. What all should be the salient features of a j2ee Web Framework.
    2. Any feature that isnt present in the existing web frameworks but wud be a real value add if present.
    Any other general suggestion about design of such frameworks etc are also welcome.
    It would be great if all you guys give us your genuis feedbacks..
    Thanks
    Karthik

    Sorry, I used up all my genuis feedback advice for the week. However, here are some ideas.
    Struts framework is/was very popular but is rapidly being replaced by the Spring framework.
    I dont believe you can just read some on-line articles on these frameworks because there is a lot of information to learn.
    I suggest you buy a book on either framework and go through it cover to cover. Similiarly I suggest you read a JSP book first (you can look through them at the bookstore, then buy them on amazon.com cheaper).
    I few quick suggestions about building your own framework before messing with a framework:
    Ideally, you should have a separation of concerns between the layers (Model View Controller):
    View = this is the JSP pages. Those pages should read all the information necessary to populate itself from objects placed in request scope. They should not contain business logic (such as instansiating java objects) or database logic (such as sql statements to fetch data from the database).
    Control= this usually is a single servlet responsible for taking in all url browser requests (say, a JSP button update click), verifying the user is logged in, then calling up business logic to obtain data to populate the JSP page. It puts the data provided by the business logic in request scope for the JSP page to read, then dispatches to the correct JSP page. The control does not genereate html tags to put on the JSP page. The user should never directly call up a JSP page. All requests should go through the servlet to ensure you have a single class that verifies the user's login (security).
    Model: The model consists of business logic and database logic. Often, these are separated into thier own layers as follows:
    1) business logic: The control calls the business logic and passes all the data from the JSP page to it. It then determines what data to pass back to the control so it can pass it back to the JSP page. The business logic does not deal with the request scope (request is a presentation object), it does not call sql statements to talk to the database. Instead it calls database logic to actually get the data.
    2) database logic: fetches data from the database for the business logic to use. It has sql. It has no business logic or presentation logic.
    Lastly, I normally create a form object to hold all the data I read from the JSP page. Example: You have a JSP page called MyJspPage..jsp:
    class MyJspPageForm{
    public MyJspPageForm(HttpRequest request){
    //get all data from the request scope that the JSP page put there
    //have a bunch of get/set functions for the business logic to access the data.
    I suggest creating a project based on the above ideas before you mess with a framework such as struts or spring. a lot of work has gone into creating those frameworks and they abstract away a lot of the low level code that I discussed above.

  • Shine J2EE Appplication Framework - A New MVC -JWMS-Ajax Framework

    Hi Dears
    Shine is a Java-J2EE Application Framework/JWMS(Java Web Model Service)Framework/MVC Framework/Service Oriented Framework. Shine Includes Ajax Libs/Server API/J2EE Architecture. Shine Supported JSF/Spring/AspectJ/Struts/Hibernate/...
    You can use Shine Framework for Implement ERP Web Based Application, Web Based Operating System, WFM Web Based Application, CRM Web Based Application, HRM Web Based Application, BPR Web Based Application, Or ... Web Based Application, Shine Registered in Source Forge.
    This Framework is a Java Service Oriented Framework for Web Based Project. This Framework include:
    * MVC (Model View Controller)
    * Ajax
    * Service Oriented Scope
    * JWMS (Java Web Model Service)
    Shine Framework is a Java Web Model Service Framework.
    Shine Framework is very easy, stable. You can use other Framework by Shine Framework:
    *Hibernate
    *Struts
    *Spring
    *And Other Framework
    JWMS And Shine J2EE Framework ?
    JWMS is a J2EE Architecture for implement Service Oriented Web-Based Appliction you can get more information about this and Shine J2EE Application Framework by -> J2EE And Service Oriented Programming :
    http://j2sos.googlegroups.com/web/J2EE_And_Service_Oriented_Programming+(English).doc?gda=VCp-YWkAAABaK1bFJn7XMhSpdkjvrT6Pd5MA3H6uh5taxEUxR6gwSUWwa05VcrqgHRSC0l_xcf_5FoxLEBXNbyq4-bBifvraWOZGQE6LgzeTU5Q6eFny4M-fIZvKNC5H8bRWhAn1psCECKgQbmraGdxlZulaYnsh
    Or
    http://j2sos.googlegroups.com
    Report: http://sourceforge.net/tracker/?group_id=244136
    Forum: http://sourceforge.net/forum/?group_id=244136
    News: http://sourceforge.net/news/?group_id=244136
    Wiki: http://shine-app.wiki.sourceforge.net/space/pagelist
    Rank: http://sourceforge.net/project/stats/rank_history.php?group_id=244136&ugn=shine-app
    Shine J2EE Framework Rank in Sourceforge is 14!
    Shine J2EE Framework: http://sourceforge.net/projects/shine-app/
    Site: www.J2SOS.org
    Special Thanks Oracle! For this Part! Your Site is very Active about J2EE - Java!
    This paper is no image paper !!!!!!!!!!!!!!!!!!!
    J2EE and Service Oriented Programming
    Authored by: AmirSam Bahador
    Level:
    Advanced
    Contents:
    Introduction
    - The purpose of compilation this essay
    Chapter 1: Basic concepts of J2EE
    - Servlet and JSP
    - MVC
    - MVC or JWMS? That is the problem? Perhaps both!
    Chapter 2: Basic concepts of Shine Framework
    - What is "Shine Framework�?
    - The components of Shine Framework
    - Implimentation of an application by Shine Framework
    Chapter 3: The objects of Shine Framework
    - The types of objects in Shine Framework
    Chapter 4: Engineering & Communication items
    - The communication of Shine Framework with the other
    existing Frameworks
    - The major purpose of Shine Framework
    Introduction
    The purpose of compilation of the this paper
    A few years ago, when I was the software architect of a big project with J2EE, I advised some of the modern tools of that time to the project manager. He acknowledged it. Therefore, we began deploying our Enterprise on Java platform. However, we encounterd with many problems, as we got ahead the project. Our tools were included Struts Framework, Spring Framework & Hibernate.
    I convinced that MVC architecture is the best option to develop macro projects! However, I believe it now, as well. Couldn't it be more completed? In developed Enterprise projects, an advanced architecture is required to divide the project, technically. The project was successfully finished after one year, but my mind was busy with it for a long time!
    Then, I began implementing an Application Framework and registered it in Sourceforge.net as an Open Source Framework. I developed some Enterprise projects & some other J2EE frameworks, as well. I achieved a good result! The velocity of implemention & developing projects increased up to 50%. Subsequently, by cooperation of my elected students who had worked with Application Framework, I established an organization, named J2SOS, to protect & develop this Application Framework.
    Fortunately, my students were so skilled that each took a chief task in big J2EE projects.
    Their experiences had a practical affect on development of Application Framework as well as the organization.
    Therefore, it is required to write down my & my yesterday students (my today co-workers) experiences. This was the outset to write the present paper!
    Chapter 1
    The basic concepts of J2EE
    Purposes
    In this chapter, we do our best to introduce J2EE basic concepts.
    Servlet & JSP
    If you ahve ever worked with JSP & Servlet, you know that Servlet is so proper for processing functions but there are particular problems with it in displaying functions.
    JSP is applied reverse to Servlet. Thus, what is the solution? To apply both JSP and Servlet together!
    What is MVC?
    MVC is an easy way to use JSP & Servlet together. In MVC architecture, the request will be processed by a Class (Servlet) and the appropriate response will be showen by JSP.
    n the above Servlet Class, the validation operation, etc will be done.
    Nowadays, there are numerous Frameworks which will assist you to use MVC Framework architecture. Struts Framework is the most well-known one.
    MVC or JWMS ? That is the problem! Perhaps both!
    MVC is a powerful architecture, but it is required an advanced architecture to implement developed projects.
    Today, web applications are well developed which complicatethe work for programmers & developers.
    To clarify it, see Google site! Google Web Application enjoys numerous services, each have a special service for the users.
    For Instance, Gmail service, E-Mail or by SearchEngine, the users can search for websites, pictures, etc.
    These services have certaily close communication with each other.
    If the services do not use a particular architecture, the Google will encounter with various problems.
    In Service Oriented architecture, each part of the program is a service programme. For example, E-Mail service, SearchEngine service, etc.
    for get full this paper plz goto : J2EE And Service Oriented Programming
    in :
    http://groups.google.com/group/j2sos
    Or
    http://j2sos.googlegroups.com/web/J2EE_And_Service_Oriented_Programming+(English).doc?gda=-C13JmkAAABaK1bFJn7XMhSpdkjvrT6PLb1WFhhPKkBftsH3LvtvGEWwa05VcrqgHRSC0l_xcf_5FoxLEBXNbyq4-bBifvraWOZGQE6LgzeTU5Q6eFny4M-fIZvKNC5H8bRWhAn1psCECKgQbmraGdxlZulaYnsh

    iabstudio have been engaged in a persistent Usenet and webboard spamming and astroturfing operation since the beginning of this month. Google has the scoop at http://groups.google.com/groups?q=www.iabstudio.com&hl=en&lr=&c2coff=1&scoring=d&start=0&sa=N&filter=0 note in particular the same IP address is used to post both their spam from iabstudio themselves and from people who claim to be satisfied users. If you do not like spamming and dishonest, don't use the product.

  • Startup Framework for EP6 SP2 - Windows 2003 - registry key error

    Hi,
    I've installed the Startup Framework and it all works from the MMC but if I try to start the SAP<SID>_00 NT Service, the portal server/dispatcher/state controller do not start up and I get the following message in the Event Viewer:
    The description for Event ID ( 0 ) in Source ( SAPCCD_00 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Cannot open Registry key HKEY_LOCAL_MACHINE\Software\SAP\CCD\Environment (Error 2 ENOENT*: No such file or directory OR: The system cannot find the file specified.  ) [ntservmgr.cpp 264].
    The registry key it refers to doesn't exist. I followed the pdf guide & have noticed that it says Windows 2000/XP - I'm trying to install it on Windows 2003, could this be the problem and is there a workaround?
    It's a problem because when the server gets restarted, the portal doesn't come up.
    Many thanks in advance.
    Best regards,
    Jane

    OK, manually added registry key - which got rid of registry error message but still wasn't starting portal.
    Then set Autostart=1 in start_<##>.pfl - now works.
    Thanks,
    Jane

  • The Java startup framework must be updated - SAP JVM 4

    Dear All,
    While execution of switch from JDK to SAP JVM 4.1 on java instance we get the message "The Java startup framework must be updated in order to use SAP JVM 4"
    Please help or guide for further steps
    Regards,
    Ajay

    Hi Ajay,
    Hope you are doing good.
    If the issue persists, kindly update the kernel to the latest level as this will update the native libraries which the JVM needs. This is the next step in these kind of cases.
    The below links will help you if there are any queries with the
    kernel update procedure.
    If you wish to do a Manual Kernel Upgrade:
    <http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70d8838d-cb8f-2c10-7ab8-d1504670fbb8>
    Kernel upgrade using JSPM:
    <http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11219>
    and
    SAP Note No. 19466: Downloading SAP kernel patches
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth
    SAP AGS

  • Kernel startup failure and timeout error during J2EE startup

    We are working on getting a DR (Disaster recovery) instance of EP6.0 started up after a restore from an offline backup of our Production Portal. This is on a separate piece of hardware. This is the J2EE version 6.2 and Ep 6.0 Sp2 Patch 37. This version is working fine on the Production Portal. When we start up the J2EE (using go.bat or the framework) we get the following error-
    [OS: SunOS] [VM vendor: Sun Microsystems Inc.] [VM version: 1.3.1_11-b02] [VM type: Java HotSpot(TM) Client VM]
    SAP J2EE Engine Version 6.20 PatchLevel 78993.20 is starting...
    Loading: LogManager ...
    Loading: SystemThreadManager ...
    Loading: ThreadManager ...
    Loading: TimeoutManager ...
    Loading: MemoryManager ...
    Loading: PoolManager ...
    Loading: PolicyManager ...
    Loading: IpVerificationManager ...
    Loading: ClusterManager ...
    Loading: ClassLoaderManager ...
    Loading: SwapManager ...
    Loading: LockManager ...
    Loading: R3StartupManager ...
    Loading: ServiceManager ...
    Loading core services:
      Starting core service monitor ... done. (215 ms)
      Starting core service p4 ... done. (310 ms)
      Starting core service log ... done. (447 ms)
      Starting core service dbms ... done. (1145 ms)
      Starting core service security ... done. (3008 ms)
      Starting core service naming ... done. (5369 ms)
      Starting core service admin ... done. (5616 ms)
    Timeout starting core services. Kernel not started.
    [ServiceManager]: * Timeout starting core services. Kernel not started.
      Timeout starting core services.
      Not started services:
      deploy
      file
    [ServiceManager]:
      Timeout starting core services.
      Not started services:
      deploy
      file
    Loading: ServiceManager returned false!
    Kernel not loaded. System halted.
    [Framework -> criticalShutdown] Kernel startup failed.
    We need assistance as soon as possible.
    Any pointers would help and will be greatly appreciated!
    S. Rao

    We resolved this error. It was a timeout setting that we needed to change on the J2EE that allowed it to bypass the timeout error.

  • J2ee startup problems

    Hi all!
    we tried to configure a connection between EP 6.0 SP13 and our CRM - System after the configuration in the portal we restartet the engine and following errors occure:
    jcontrol.exe - some processes running
    Developer Trace:
    Thr 4352] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5552] Mon Sep 05 16:27:03 2005
    [Thr 5552] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5552] JLaunchISetClusterId: set cluster id 1165550
    [Thr 5552] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5552] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 4288] Mon Sep 05 16:27:17 2005
    [Thr 4288] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 2208] JLaunchIExitJava: exit hook is called (rc=-11113)
    [Thr 2208] JLaunchCloseProgram: good bye (exitcode=-11113)
    dev_jcontrol:
    trc file: "F:\usr\sap\UEP\JC00\work\dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:25:47 2005
    arguments   :
        arg[00] : F:\usr\sap\UEP\JC00\j2ee\os_libs\jcontrol.exe
        arg[01] : pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    [Thr 4104] Mon Sep 05 16:25:47 2005
    [Thr 4104] INFO: Unknown property [box.number=UEPJC00uep]
    [Thr 4104] INFO: Unknown property [system.id=0]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties;F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : uep
    -> ms port    : 3601
    -> OS libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> files [01] : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : uep
    -> ms port    : 3601
    -> os libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID1165500  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID1165550  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID1165500            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] ID1165550            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 4104] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 4104] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0011655
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_bootstrap
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] Mon Sep 05 16:25:50 2005
    [Thr 4104] JControlExecuteBootstrap: read instance values after global bootstrap
    [Thr 4104] INFO: Unknown property [box.number=UEPJC00uep]
    [Thr 4104] INFO: Unknown property [system.id=0]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties;F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : uep
    -> ms port    : 3601
    -> OS libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 4104] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> files [01] : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : uep
    -> ms port    : 3601
    -> os libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID1165500  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID1165550  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID1165500            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] ID1165550            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 4104] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID1165500]
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 4104] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [bootstrap_ID1165500]
    -> node name       : dispatcher bootstrap
    -> node type       : bootstrap
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID001165500
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_bootstrap
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID1165500
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_bootstrap_ID1165500.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_bootstrap_ID1165500.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_bootstrap_ID1165500
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] Mon Sep 05 16:25:53 2005
    [Thr 4104] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID1165550]
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 4104] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [bootstrap_ID1165550]
    -> node name       : server0 bootstrap
    -> node type       : bootstrap
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 1024M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID001165550
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_bootstrap
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID1165550
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_bootstrap_ID1165550.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_bootstrap_ID1165550.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_bootstrap_ID1165550
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] Mon Sep 05 16:25:56 2005
    [Thr 4104] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 3900] JControlRequestFunc: Thread 3900 started as listener thread for np messages.
    [Thr 4104] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [ID1165500]
    -> node name       : dispatcher
    -> node type       : dispatcher
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC -Drdbms.driverLocation=F:/oracle/uep/920/jdbc/lib/classes12.jar -Dsys.global.dir=F:/usr/sap/UEP/SYS/global/
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster\dispatcher
    -> class path      : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 4104] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c   2300]
    [Thr 4104] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [ID1165550]
    -> node name       : server0
    -> node type       : server
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=F:/oracle/uep/920/jdbc/lib/classes12.jar -Dsys.global.dir=F:/usr/sap/UEP/SYS/global/
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 4104] [Node: SDM] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [sdm]
    -> node name       : SDM
    -> node type       : sdm
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters :
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : F:\usr\sap\UEP\JC00\SDM\program
    -> class path      : F:\usr\sap\UEP\JC00\SDM\program\bin\SDM.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : SDMInternal
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters      : server sdmhome=F:\usr\sap/UEP/JC00/SDM/program
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 4104] JControlMSConnect: attached to message server (uep/3601)
    [Thr 2896] JControlMSMessageFunc: Thread 2896 started as listener thread for ms messages.
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_dispatcher
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165500
    -> arg[05] = -nodeId=0
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_dispatcher.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process dispatcher started (PID:5596)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:4700)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_sdm
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    -> arg[04] = -nodeName=sdm
    -> arg[05] = -nodeId=2
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_sdm.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process SDM started (PID:5272)
    [Thr 4104] Mon Sep 05 16:26:21 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:4700) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (1)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:3440)
    [Thr 4104] Mon Sep 05 16:26:41 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:3440) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (2)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:3280)
    [Thr 4104] Mon Sep 05 16:27:01 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:3280) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (3)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:3436)
    [Thr 4104] Mon Sep 05 16:27:21 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:3436) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (4)
    std_server0.out
    stdout/stderr redirect
    node name   : server0
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:25:56 2005
    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 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 95420.313 is starting...
    Loading: LogManager ... 516 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 15 ms.
    Loading: ClusterManager ... 657 ms.
    Loading: LockingManager ... 109 ms.
    Loading: ConfigurationManager ... 2000 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43519K->3351K(65280K), 0.0312769 secs] 43519K->3351K(502528K), 0.0313265 secs]
    Loading services.:
      Service memory started. (16 ms).
      Service cross started. (15 ms).
      Service jmx_notification started. (234 ms).
      Service trex.service started. (156 ms).
      Service runtimeinfo started. (15 ms).
      Service file started. (31 ms).
      Service tcsecwssec~service started. (625 ms).
      Service timeout started. (672 ms).
      Service userstore started. (0 ms).
      Service p4 started. (937 ms).
      Service classpath_resolver started. (0 ms).
    5.469: [GC 5.469: [ParNew: 46871K->7055K(65280K), 0.0510631 secs] 46871K->7055K(502528K), 0.0511160 secs]
      Service log_configurator started. (4078 ms).
      Service locking started. (16 ms).
      Service http started. (375 ms).
      Service naming started. (437 ms).
      Service failover started. (266 ms).
      Service appclient started. (281 ms).
      Service jmsconnector started. (297 ms).
      Service javamail started. (438 ms).
      Service ts started. (359 ms).
      Service licensing started. (16 ms).
      Service connector started. (375 ms).
    9.002: [GC 9.002: [ParNew: 50575K->8716K(65280K), 0.1193652 secs] 50575K->8716K(502528K), 0.1194184 secs]
      Service webservices started. (1469 ms).
      Service deploy started. (7484 ms).
      Service configuration started. (63 ms).
      Service apptracing started. (94 ms).
    12.418: [GC 12.418: [ParNew: 52236K->11128K(65280K), 0.0434016 secs] 52236K->11128K(502528K), 0.0434532 secs]
      Service dbpool started. (1484 ms).
    Sep 5, 2005 4:26:20 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_25] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'mshost' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      TimeZoneMapping=
      snc_qop=
      client=300
      abap_debug=
      snc_myname=
      gwserv=
      snc_partnername=
      ashost=194.127.167.74
      group=
      r3name=UME
      snc_mode=0
      gwhost=
      sysnr=00
      msserv=
      poolmaxsize=10
      snc_lib=
      passwd=********
      poolmaxwait=
      trace=
      receiverid_guest=master
      mshost=
      user=SAPJSF_UEP
      lang=EN
      receiverid=master
    Sep 5, 2005 4:26:20 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_25] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 5, 2005 4:26:20 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_25] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:26:21 2005
    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 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 95420.313 is starting...
    Loading: LogManager ... 516 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 31 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 234 ms.
    Loading: LockingManager ... 63 ms.
    Loading: ConfigurationManager ... 1375 ms.
    Loading: LicensingManager ... 32 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43520K->2968K(65280K), 0.0208138 secs] 43520K->2968K(502528K), 0.0208688 secs]
    Loading services.:
      Service memory started. (94 ms).
      Service cross started. (172 ms).
      Service runtimeinfo started. (94 ms).
      Service file started. (172 ms).
      Service trex.service started. (172 ms).
      Service timeout started. (218 ms).
      Service userstore started. (125 ms).
      Service jmx_notification started. (156 ms).
      Service tcsecwssec~service started. (407 ms).
      Service p4 started. (172 ms).
      Service classpath_resolver started. (0 ms).
    3.397: [GC 3.397: [ParNew: 46488K->6596K(65280K), 0.0343611 secs] 46488K->6596K(502528K), 0.0344101 secs]
      Service log_configurator started. (3390 ms).
      Service locking started. (0 ms).
      Service naming started. (312 ms).
      Service failover started. (93 ms).
      Service appclient started. (172 ms).
      Service jmsconnector started. (203 ms).
      Service http started. (656 ms).
      Service javamail started. (344 ms).
      Service ts started. (281 ms).
      Service licensing started. (0 ms).
      Service connector started. (312 ms).
    6.312: [GC 6.312: [ParNew: 50113K->8624K(65280K), 0.0386024 secs] 50113K->8624K(502528K), 0.0386580 secs]
      Service webservices started. (813 ms).
      Service deploy started. (6532 ms).
      Service configuration started. (47 ms).
      Service apptracing started. (79 ms).
    9.241: [GC 9.241: [ParNew: 52143K->11000K(65280K), 0.0363859 secs] 52143K->11000K(502528K), 0.0364380 secs]
      Service dbpool started. (1359 ms).
    Sep 5, 2005 4:26:37 PM          com.sap.security.core.persistence [Session Reader for cluster node 1165500] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'mshost' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      TimeZoneMapping=
      snc_qop=
      client=300
      abap_debug=
      snc_myname=
      gwserv=
      snc_partnername=
      ashost=194.127.167.74
      group=
      r3name=UME
      snc_mode=0
      gwhost=
      sysnr=00
      msserv=
      poolmaxsize=10
      snc_lib=
      passwd=********
      poolmaxwait=
      trace=
      receiverid_guest=master
      mshost=
      user=SAPJSF_UEP
      lang=EN
      receiverid=master
    Sep 5, 2005 4:26:37 PM          com.sap.security.core.persistence [Session Reader for cluster node 1165500] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 5, 2005 4:26:37 PM              com.sap.engine.core.Framework [Session Reader for cluster node 1165500] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:26:41 2005
    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 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 95420.313 is starting...
    Loading: LogManager ... 531 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 235 ms.
    Loading: LockingManager ... 125 ms.
    Loading: ConfigurationManager ... 1171 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43505K->3079K(65280K), 0.0218877 secs] 43505K->3079K(502528K), 0.0219387 secs]
    Loading services.:
      Service memory started. (31 ms).
      Service jmx_notification started. (47 ms).
      Service cross started. (47 ms).
      Service runtimeinfo started. (31 ms).
      Service trex.service started. (125 ms).
      Service userstore started. (15 ms).
      Service file started. (109 ms).
      Service timeout started. (141 ms).
      Service p4 started. (250 ms).
      Service classpath_resolver started. (31 ms).
      Service tcsecwssec~service started. (343 ms).
    3.557: [GC 3.557: [ParNew: 46599K->6971K(65280K), 0.0362422 secs] 46599K->6971K(502528K), 0.0362937 secs]
      Service log_configurator started. (3297 ms).
      Service locking started. (0 ms).
      Service http started. (344 ms).
      Service naming started. (391 ms).
      Service appclient started. (218 ms).
      Service jmsconnector started. (250 ms).
      Service javamail started. (297 ms).
      Service ts started. (219 ms).
      Service failover started. (297 ms).
      Service licensing started. (15 ms).
      Service connector started. (422 ms).
      Service webservices started. (640 ms).
    6.372: [GC 6.372: [ParNew: 50462K->8734K(65280K), 0.0393979 secs] 50462K->8734K(502528K), 0.0394531 secs]
      Service deploy started. (7015 ms).
      Service configuration started. (32 ms).
      Service apptracing started. (125 ms).
    9.659: [GC 9.659: [ParNew: 52254K->11326K(65280K), 0.0405210 secs] 52254K->11326K(502528K), 0.0405719 secs]
      Service dbpool started. (1469 ms).
    Sep 5, 2005 4:26:58 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_11] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'mshost' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      TimeZoneMapping=
      snc_qop=
      client=300
      abap_debug=
      snc_myname=
      gwserv=
      snc_partnername=
      ashost=194.127.167.74
      group=
      r3name=UME
      snc_mode=0
      gwhost=
      sysnr=00
      msserv=
      poolmaxsize=10
      snc_lib=
      passwd=********
      poolmaxwait=
      trace=
      receiverid_guest=master
      mshost=
      user=SAPJSF_UEP
      lang=EN
      receiverid=master
    Sep 5, 2005 4:26:58 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_11] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleT

    Here's a list of all the parameters but I think you need this one ume.r3.connection.master.msserv=
    ume.r3.connection.master.abap_debug=
    ume.r3.connection.master.ashost=
    ume.r3.connection.master.client=
    ume.r3.connection.master.group=
    ume.r3.connection.master.gwhost=
    ume.r3.connection.master.gwserv=
    ume.r3.connection.master.lang=
    ume.r3.connection.master.msghost=
    ume.r3.connection.master.msserv=
    ume.r3.connection.master.poolmaxsize=10
    ume.r3.connection.master.poolmaxwait=
    ume.r3.connection.master.r3name=
    ume.r3.connection.master.receiverid=master
    ume.r3.connection.master.receiverid_guest=master
    ume.r3.connection.master.snc_lib=
    ume.r3.connection.master.snc_mode=
    ume.r3.connection.master.snc_myname=
    ume.r3.connection.master.snc_partnername=
    ume.r3.connection.master.snc_qop=
    ume.r3.connection.master.sysnr=
    ume.r3.connection.master.trace=
    ume.r3.connection.master.user=
    ume.r3.connection.master.TimeZoneMapping=
    ume.r3.connection.master.abap_debug=
    ume.r3.connection.master.ashost=
    ume.r3.connection.master.client=
    ume.r3.connection.master.group=
    ume.r3.connection.master.gwhost=
    ume.r3.connection.master.gwserv=
    ume.r3.connection.master.lang=
    ume.r3.connection.master.msghost=
    ume.r3.connection.master.msserv=
    ume.r3.connection.master.poolmaxsize=10
    ume.r3.connection.master.poolmaxwait=
    ume.r3.connection.master.r3name=
    ume.r3.connection.master.receiverid=master
    ume.r3.connection.master.receiverid_guest=master
    ume.r3.connection.master.snc_lib=
    ume.r3.connection.master.snc_mode=
    ume.r3.connection.master.snc_myname=
    ume.r3.connection.master.snc_partnername=
    ume.r3.connection.master.snc_qop=
    ume.r3.connection.master.sysnr=
    ume.r3.connection.master.trace=
    ume.r3.connection.master.user=

  • J2E startup problem

    I just installed the J2E full trial on a laptop that already has a NSP instance installed.I get a Half Green/ Half Yellow icon in the MMC when I start the J2E server.The 01 instance is always yellow and never progresses onto green. I have a process status of 'starting framework'.
    Also,I get a "page not found" when I try http://localhost:50100 (could be because the server is not yet started).I have not installed the Adobe forms credential yet .
    The NSP starts well and I can sign on.
    Has anyone got a pointer for me?  Am I missing a license or something ?

    Hi,
    1.Check in all the nodes of instance,if
    message server,enqeue server and jcontrol are up and running.
    2.In the process list,right click on server node and open the developer trace and look for the error messages it is showing.
    3.Try connecting to DB .if you able to conect,look if logs are full.remove old logs which are not necessary.
    4.check if environment variables JAVA_HOME and path set properly.
    5.look for other logs in
    c:/usr/sap/SID/JCxx/j2ee/server0/log/default.trace
    and /usr/sap/SID/JCxx/work----->dev_log*(all logs with server node).
    You will definitely get an hint of error.
    after doing teh changes ,restart the instance,it will work.
    reward points if helpful........

  • J2ee startup but nothing happens then

    Hi all,
    I'm new to j2ee and having the following problem. When I startup j2ee the following happens and then i doesnt let me type anything else in the command line.
    this is what i get after starting j2ee:
    J2EE server listen port: 1000
    Naming service started:1000
    Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
    DB;create=true
    Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
    te=true
    Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
    eDB;create=true
    Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB
    ;create=true
    Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
    te=true
    Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
    Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
    re.RemoteXaDataSource@358f03
    Starting JMS service...
    Initialization complete - waiting for client requests
    Binding: < JMS Destination : jms/Topic , javax.jms.Topic >
    Binding: < JMS Destination : jms/Queue , javax.jms.Queue >
    Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , No properties >
    Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No properties
    >
    Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No properties
    >
    Binding: < JMS Cnx Factory : TopicConnectionFactory , Topic , No properties >
    Starting web service at port: 8000
    Starting secure web service at port: 7000
    J2EE SDK/1.3.1
    Starting web service at port: 9191
    J2EE SDK/1.3.1
    J2EE server startup complete.

    Hello,
    Your j2ee server seems to be just fine and you need to open another window to work in it. Afterall there is the message
    J2EE server startup complete.
    nothing can be done on the server window till you stop the server. To stop the server, u need to open another window and issue the commandj2ee -stop saem case for all other command u need to send to the server..
    after starting the server , if the link
    http://localhost:8000
    works, then the j2ee server is just fine..
    Please refer
    http://forum.java.sun.com/thread.jsp?forum=136&thread=292049
    for answers on exactly the same question..
    Cheers,
    -Jer

  • J2ee startup problem

    hi,
    After installation of NW2004's I restarted the system for post installation then I found server0 is not working...see the logs
    dev_server0:
    Thr 4256] Thu May  8 17:53:04 2008
    [Thr 4256] ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2460]
    [Thr 4256] *** ERROR => NiPConnect: SiConnect failed for hdl 6 / sock 9
        (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3300) [nixxi.cpp    2460]
    [Thr 4256] *** ERROR => GwIConnect: GwConnect to localhost / sapgw00 failed (rc=NIECONN_REFUSED) [gwxx_mt.c    296]
    [Thr 4256] ***LOG S0T=> GwIConnect, GwConnect (-0010) [gwxx_mt.c    297]
    [Thr 4256] ***LOG S0R=> GwIConnect, GwConnect () [gwxx_mt.c    299]
    [Thr 4256] ***LOG S0S=> GwIConnect, GwConnect (sapgw00) [gwxx_mt.c    301]
    [Thr 4256] ***LOG S90=> SAP_STINIT3, GwIConnect ( 236) [r3cpic_mt.c  2006]
    [Thr 4256]
    [Thr 4256] *  LOCATION    CPIC (TCP/IP) on local host with Unicode
    [Thr 4256] *  ERROR       partner '127.0.0.1:sapgw00' not reached
    [Thr 4256] *
    TIME        Thu May  8 17:53:04 2008
    [Thr 4256] *  RELEASE     700
    [Thr 4256] *  COMPONENT   NI (network interface)
    [Thr 4256] *  VERSION     38
    [Thr 4256] *  RC          -10
    [Thr 4256] *  MODULE      nixxi.cpp
    [Thr 4256] *  LINE        2460
    [Thr 4256] *  DETAIL      NiPConnect
    [Thr 4256] *  SYSTEM CALL connect
    [Thr 4256] *  ERRNO       79
    [Thr 4256] *  ERRNO TEXT  Connection refused
    [Thr 4256] *  COUNTER     84
    [Thr 4256] *
    [Thr 4256] *****************************************************************************
    dev_jcontrol:
    [Thr  1] Sat May 10 13:40:35 2008
    [Thr  1] ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2460]
    [Thr  1] *** ERROR => NiPConnect: SiConnect failed for hdl 2 / sock 11
        (SI_ECONN_REFUSE/79; I4; ST; :3901) [nixxi.cpp    2460]
    [Thr  1] *** ERROR => MsIAttachEx: NiBufConnect to GGBDV/3901 failed (rc=NIECONN_REFUSED) [msxxi_mt.c   652]
    [Thr  1] *** ERROR => Can't attach to message server (hostname/3901) [rc = -100]-> terminate [jcntrms_mt.c 374]
    [Thr  1] JControlCloseProgram: started (exitcode = -100)
    [Thr  1] *** ERROR => MsIModState: not_attached [msxxi_mt.c   3838]
    [Thr  1] *** ERROR => Can't modify message server state (state = 7, rc = -3) [jcntrms_mt.c 841]
    [Thr  1] JControlCloseProgram: good bye... (exitcode = -100)
    dev_ms:
    trc file: "dev_ms", trc level: 1, release: "700"
    [Thr  1] Sat May 10 13:16:54 2008
    [Thr  1] MsSOsPrivInit: Run priority adjusted to 12
    [Thr  1] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
    systemid   324 (IBM iSeries with OS400)
    relno      7000
    patchlevel 0
    patchno    116
    intno      20050900
    make:      multithreaded, Unicode, 64 bit, optimized
    pid        475
    [Thr  1] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 475) [msxxserv_mt. 1824]
    [Thr  1] SigISetDefaultAction : default handling for signal 20
    [Thr  1] load acl file = /usr/sap/GBI/SYS/global/ms_acl_info
    [Thr  1] MsGetOwnIpAddr: my host addresses are :
    [Thr  1]   1 :  (HOSTNAME)
    [Thr  1]   2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    [Thr  1] MsHttpInit: full qualified hostname
    [Thr  1] HTTP logging is switch off
    [Thr  1] set HTTP state to LISTEN
    [Thr  1] MsHttpOwnDomain: own domain[1]
    [Thr  1] ms/icf_info_server : deleted
    [Thr  1] *** I listen to port sapmsSID(3600) ***
    [Thr  1] *** I listen to internal port 3900 (3900) ***
    [Thr  1] *** HTTP port 8100 state LISTEN ***
    [Thr  1] CUSTOMER KEY: >Y0799187842<
    [Thr  1] Sat May 10 13:18:17 2008
    [Thr  1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403 Forbidden)
    [Thr  1] Sat May 10 13:18:23 2008
    [Thr  1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/urlprefix (403 Forbidden)
    [Thr  1] Sat May 10 13:47:18 2008
    [Thr  1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403 Forbidden)
    give me your suggestion

    HI,
    STD_SERVEO:
    stdout/stderr redirect
    node name   : server0
    pid         : 7753
    system name : SID
    system nr.  : 00
    started at  : Thu May  8 08:01:48 2008
    [Thr  1] Thu May  8 08:01:51 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier CC9D260C1B003900;  heap identifier CC9D260C1B003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/08/08 08:01:55
    GC 1: live objects 3550; collected objects 1654; collected(KB) 145.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 5556; current threshold(KB) 1048576.
    GC 1: collect (milliseconds) 57.
    GC 1: current cycle allocation(KB) 864; previous cycle allocation(KB) 4185.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/08/08 08:01:56
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 2339 ms.
    Loading: PoolManager ... 15 ms.
    Loading: ApplicationThreadManager ... 338 ms.
    Loading: ThreadManager ... 87 ms.
    Loading: IpVerificationManager ... 53 ms.
    Loading: ClassLoaderManager ... 116 ms.
    Loading: ClusterManager ... 1461 ms.
    Loading: LockingManager ... 744 ms.
    Loading: ConfigurationManager ... 11296 ms.
    Loading: LicensingManager ... 82 ms.
    Loading: CacheManager ... 805 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service cafeuodi~mnuacc started. (87 ms).
      Service DQE started. (440 ms).
      Service runtimeinfo started. (137 ms).
      Service cross started. (351 ms).
      Service timeout started. (333 ms).
      Service cafeucc~api started. (480 ms).
      Service memory started. (427 ms).
      Service userstore started. (4 ms).
      Service jmx_notification started. (196 ms).
      Service trex.service started. (1513 ms).
      Service file started. (1756 ms).
      Service p4 started. (1453 ms).
      Service classpath_resolver started. (62 ms).
      Service log_configurator started. (19040 ms).
      Service locking started. (7 ms).
      Service http started. (820 ms).
      Service naming started. (1393 ms).
      Service failover started. (151 ms).
      Service javamail started. (350 ms).
      Service appclient started. (304 ms).
      Service jmsconnector started. (464 ms).
      Service ts started. (457 ms).
      Service licensing started. (33 ms).
      Service connector started. (1071 ms).
      Service iiop started. (1319 ms).
      Service webservices started. (3808 ms).
      Service deploy started. (29721 ms).
      Service MigrationService started. (163 ms).
      Service bimmrdeployer started. (79 ms).
      Service configuration started. (175 ms).
      Service dbpool started. (8671 ms).
      Service cafeugpmailcf started. (500 ms).
      Service com.sap.security.core.ume.service started. (7927 ms).
      Service security started. (3006 ms).
      Service shell started. (236 ms).
      Service applocking started. (455 ms).
      Service tceCATTPingservice started. (37 ms).
      Service telnet started. (259 ms).
      Service classload started. (1208 ms).
      Service webdynpro started. (511 ms).
      Service dsr started. (1009 ms).
      Service keystore started. (2174 ms).
      Service developmentserver started. (1797 ms).
      Service ssl started. (52 ms).
      Service jmx started. (1357 ms).
      Service cafummetadata~imp started. (2227 ms).
      Service ejb started. (3294 ms).
      Service tcsecsecurestorage~service started. (830 ms).
      Service rfcengine started. (832 ms).
      Service cafeugp~model started. (197 ms).
      Service CUL started. (1771 ms).
      Service tceujwfuiwizsvc started. (14 ms).
      Service cafumrelgroups~imp started. (2829 ms).
      Service cafeuer~service started. (415 ms).
      Service basicadmin started. (2980 ms).
      Service servlet_jsp started. (6096 ms).
      Service prtbridge started. (2911 ms).
      Service com.adobe~DataManagerService started. (3094 ms).
      Service com.adobe~LicenseService started. (493 ms).
      Service tcsecwssec~service started. (3116 ms).
      Service com.adobe~DocumentServicesBinaries2 started. (620 ms).
      Service apptracing started. (2852 ms).
      Service com.adobe~FontManagerService started. (498 ms).
      Service com.adobe~DocumentServicesLicenseSupportService started. (387 ms).
      Service com.adobe~PDFManipulation started. (284 ms).
      Service adminadapter started. (980 ms).
      Service com.sap.portal.pcd.gl started. (39 ms).
      Service com.adobe~DocumentServicesConfiguration started. (2104 ms).
      Service tcsecdestinations~service started. (5500 ms).
      Service tc.monitoring.logviewer started. (6134 ms).
      Service com.adobe~XMLFormService started. (819 ms).
      Service pmi started. (165 ms).
      Service com.adobe~TrustManagerService started. (317 ms).
      Service com.adobe~DocumentServicesDestProtoService started. (231 ms).
      Service cafruntimeconnectivity~impl started. (62893 ms).
      Service tcsecvsi~service started. (976 ms).
      Service sld started. (6967 ms).
      Service monitor started. (2806 ms).
      Service com.sap.portal.prt.sapj2ee started. (147 ms).
      Service jms_provider started. (9062 ms).
    ServiceManager started for 79016 ms.
    Framework started for 96848 ms.
    GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/08/08 08:03:51
    GC 2: live objects 745472; collected objects 5156091; collected(KB) 928487.
    GC 2: queued for finalization 0; total soft references 8468; cleared soft references 0.
    GC 2: current heap(KB) 1142708; current threshold(KB) 1048576.
    GC 2: collect (milliseconds) 3028.
    GC 2: current cycle allocation(KB) 7441; previous cycle allocation(KB) 1048599.
    GC 2: total weak references 2607; cleared weak references 4.
    GC 2: total final references 19258; cleared final references 17233.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/08/08 08:03:54
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/08/08 08:06:15
    GC 3: collected class [Lcom/sap/engine/core/configuration/impl/utilities/ConfigurationPath;.
    GC 3: collected class sun/reflect/GeneratedMethodAccessor3630385287.
    GC 3: live objects 1665790; collected objects 7135030; collected(KB) 951876.
    GC 3: queued for finalization 0; total soft references 11565; cleared soft references 0.
    GC 3: current heap(KB) 1534552; current threshold(KB) 1048576.
    GC 3: collect (milliseconds) 3812.
    GC 3: current cycle allocation(KB) 21947; previous cycle allocation(KB) 1048593.
    GC 3: total weak references 11335; cleared weak references 76.
    GC 3: total final references 22258; cleared final references 19091.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/08/08 08:06:18
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/08/08 08:08:59
    GC 4: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
    GC 4: live objects 2586327; collected objects 6257242; collected(KB) 965514.
    GC 4: queued for finalization 0; total soft references 12760; cleared soft references 0.
    GC 4: current heap(KB) 1701500; current threshold(KB) 1048576.
    GC 4: collect (milliseconds) 5253.
    GC 4: current cycle allocation(KB) 14367; previous cycle allocation(KB) 1048589.
    GC 4: total weak references 15920; cleared weak references 177.
    GC 4: total final references 19978; cleared final references 16017.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/08/08 08:09:05
    GC 5: starting collection, threshold allocation reached.
    GC 5: collection starting 05/08/08 08:11:03
    GC 5: live objects 3284648; collected objects 7007268; collected(KB) 917356.
    GC 5: queued for finalization 0; total soft references 16766; cleared soft references 0.
    GC 5: current heap(KB) 1899328; current threshold(KB) 1048576.
    GC 5: collect (milliseconds) 4109.
    GC 5: current cycle allocation(KB) 30464; previous cycle allocation(KB) 1048598.
    GC 5: total weak references 17038; cleared weak references 132.
    GC 5: total final references 42750; cleared final references 38720.
    GC 5: total phantom references 0; cleared phantom references 0.
    GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 5: collection ending 05/08/08 08:11:07
    GC 6: starting collection, threshold allocation reached.
    GC 6: collection starting 05/08/08 08:14:03
    GC 6: live objects 4470495; collected objects 6575918; collected(KB) 979951.
    GC 6: queued for finalization 0; total soft references 34096; cleared soft references 0.
    GC 6: current heap(KB) 2095156; current threshold(KB) 1048576.
    GC 6: collect (milliseconds) 7546.
    GC 6: current cycle allocation(KB) 110101; previous cycle allocation(KB) 1048623.
    GC 6: total weak references 42891; cleared weak references 48.
    GC 6: total final references 35776; cleared final references 26485.
    GC 6: total phantom references 0; cleared phantom references 0.
    GC 6: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 6: collection ending 05/08/08 08:14:11
    GC 7: starting collection, threshold allocation reached.
    GC 7: collection starting 05/08/08 08:15:43
    GC 7: live objects 4922324; collected objects 7424152; collected(KB) 1034175.
    GC 7: queued for finalization 0; total soft references 36030; cleared soft references 0.
    GC 7: current heap(KB) 2196632; current threshold(KB) 1048576.
    GC 7: collect (milliseconds) 6246.
    GC 7: current cycle allocation(KB) 43733; previous cycle allocation(KB) 1048605.
    GC 7: total weak references 43181; cleared weak references 20.
    GC 7: total final references 17977; cleared final references 8153.
    GC 7: total phantom references 0; cleared phantom references 0.
    GC 7: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 7: collection ending 05/08/08 08:15:50
    GC 8: starting collection, threshold allocation reached.
    GC 8: collection starting 05/08/08 09:12:27
    GC 8: live objects 5349555; collected objects 8155508; collected(KB) 994872.
    GC 8: queued for finalization 0; total soft references 38217; cleared soft references 0.
    GC 8: current heap(KB) 2274232; current threshold(KB) 1048576.
    GC 8: collect (milliseconds) 7318.
    GC 8: current cycle allocation(KB) 220; previous cycle allocation(KB) 1048585.
    GC 8: total weak references 43778; cleared weak references 744.
    GC 8: total final references 31202; cleared final references 21696.
    GC 8: total phantom references 0; cleared phantom references 0.
    GC 8: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 8: collection ending 05/08/08 09:12:34
    GC 9: starting collection, threshold allocation reached.
    GC 9: collection starting 05/08/08 12:38:34
    GC 9: live objects 5680591; collected objects 11334758; collected(KB) 1014649.
    GC 9: queued for finalization 0; total soft references 39096; cleared soft references 3371.
    GC 9: current heap(KB) 2580764; current threshold(KB) 1048576.
    GC 9: collect (milliseconds) 50888.
    GC 9: current cycle allocation(KB) 5858; previous cycle allocation(KB) 1048591.
    GC 9: total weak references 43169; cleared weak references 5333.
    GC 9: total final references 61932; cleared final references 56885.
    GC 9: total phantom references 0; cleared phantom references 0.
    GC 9: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 9: collection ending 05/08/08 12:39:25
    GC 10: starting collection, threshold allocation reached.
    GC 10: collection starting 05/08/08 16:04:37
    GC 10: collected class sun/reflect/GeneratedConstructorAccessor3962137197.
    GC 10: collected class sun/reflect/GeneratedConstructorAccessor1177669627.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor1221400578.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor1175886476.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor842495978.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2995163628.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3935118260.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3903475589.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3820744598.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor902021387.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3636210140.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3041006465.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2736528823.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2741816805.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3446856562.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor1063262256.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2292015554.
    GC 10: collected class sun/reflect/GeneratedMethodAccessor3099279424.
    GC 10: live objects 5604892; collected objects 11760953; collected(KB) 1053812.
    GC 10: queued for finalization 0; total soft references 36473; cleared soft references 535.
    GC 10: current heap(KB) 2589776; current threshold(KB) 1048576.
    GC 10: collect (milliseconds) 11701.
    GC 10: current cycle allocation(KB) 2425; previous cycle allocation(KB) 1048581.
    GC 10: total weak references 38374; cleared weak references 910.
    GC 10: total final references 57639; cleared final references 53234.
    GC 10: total phantom references 0; cleared phantom references 0.
    GC 10: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 10: collection ending 05/08/08 16:04:49
    SAP J2EE Engine Version 7.00   PatchLevel is shutting down!  PatchLevel September 11, 2006 16:35 GMT
    Stopping services.
      Service com.sap.portal.prt.sapj2ee stopped. (287 ms)
      Service com.adobe~DocumentServicesLicenseSupportService stopped. (1567 ms)
      Service com.adobe~LicenseService stopped. (37 ms)
      Service com.adobe~XMLFormService stopped. (77 ms)
      Service com.adobe~FontManagerService stopped. (162 ms)
      Service com.adobe~PDFManipulation stopped. (165 ms)
      Service com.adobe~TrustManagerService stopped. (73 ms)
      Service com.adobe~DocumentServicesDestProtoService stopped. (52 ms)
      Service com.adobe~DocumentServicesBinaries2 stopped. (66 ms)
      Service com.adobe~DataManagerService stopped. (99 ms)
      Service iiop stopped. (1313 ms)
      Service cafumrelgroups~imp stopped. (27 ms)
      Service cafummetadata~imp stopped. (25 ms)
      Service cafeuer~service stopped. (4 ms)
      Service applocking stopped. (112 ms)
      Service licensing stopped. (10 ms)
      Service ts stopped. (57 ms)
      Service telnet stopped. (6 ms)
      Service com.adobe~DocumentServicesConfiguration stopped. (3 ms)
      Service tcsecwssec~service stopped. (50 ms)
      Service sld stopped. (29 ms)
      Service tcsecvsi~service stopped. (118 ms)
      Service pmi stopped. (176 ms)
      Service tcsecdestinations~service stopped. (4 ms)
      Service tceujwfuiwizsvc stopped. (10 ms)
      Service cafeugp~model stopped. (628 ms)
      Service tcsecsecurestorage~service stopped. (0 ms)
      Service ssl stopped. (6 ms)
      Service keystore stopped. (120 ms)
      Service classload stopped. (12 ms)
      Service jms_provider stopped. (161 ms)
      Service developmentserver stopped. (29 ms)
    GC 11: starting collection, threshold allocation reached.
    GC 11: collection starting 05/08/08 17:52:55

Maybe you are looking for