IBM BS029ML Self Help Guide - Page 134
Application server startup, WMM startup
View all IBM BS029ML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 134 highlights
to the JVM runtime log files to show the correlations of the events by matching their timestamps. Application server startup The first thing to look for is whether there are any exceptions. Not all exceptions are critical to the portal server. Some of them are due to the nature of multithreads of the application server, and can be ignored. As long as the key services of WebSphere Application Server and WebSphere Portal are started, the system should normally be fine. To find the set of the WebSphere Application Server and WebSphere Portal key services, refer to the Information Centers of these two products. The security configuration would be loaded early as shown in the log, and the following two lines show that it is successfully loaded: [8/2/07 11:52:24:734 EDT] 0000000a distSecurityC I started successfully [8/2/07 11:52:24:750 EDT] 0000000a distSecurityC I true SECJ0243I: Security service SECJ0210I: Security enabled WMM startup wmmApp is the WMM Enterprise Java Been (EJB) installed on the Application Server. Its successful startup is the first step for Portal security to function. If it fails to start, Portal security will not work. The typical sequence of the startup in SystemOut.log should look like the following: [4/30/07 16:15:54:429 PDT] 0000000a ApplicationMg A application: wmmApp [4/30/07 16:15:55:728 PDT] 0000000a EJBContainerI I start EJB jar: wmm.ejb.jar [4/30/07 16:15:55:763 PDT] 0000000a EJBContainerI I wmm.ejb.jar [4/30/07 16:15:55:931 PDT] 0000000a EJBContainerI I start EJB jar: wmm.internal.ejb.jar [4/30/07 16:15:55:953 PDT] 0000000a EJBContainerI I wmm.internal.ejb.jar [4/30/07 16:15:55:995 PDT] 0000000a ApplicationMg A started: wmmApp WSVR0200I: Starting WSVR0207I: Preparing to WSVR0037I: Starting EJB jar: WSVR0207I: Preparing to WSVR0037I: Starting EJB jar: WSVR0221I: Application Sometimes even though wmmApp is shown as started, WMM could still fail as follows: [8/14/07 15:11:29:188 EDT] 0000000a WSMM Message E com.ibm.ws.wmm.MemberRepositoryManager init Initialization failed due to invalid property "supportedMemberTypes". [8/14/07 15:11:29:203 EDT] 0000000a WSMM Message E com.ibm.ws.wmm.objectimpl.MemberServiceBeanBase ejbCreate() com.ibm.websphere.wmm.exception.InitializationException: Initialization failed due to invalid property "supportedMemberTypes". [8/14/07 15:11:29:234 EDT] 0000000a ExceptionUtil E CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "getConfigurationData". In this case, a typo in wmm.xml was the cause of the error. The failure of wmmApp would definitely cause PumaService in WebSphere Portal to fail, resulting in the failure of the portal server itself. 120 IBM WebSphere Portal V6 Self Help Guide