{code}
..
[1/30/09 12:50:00:831 EST] 00000026 WebGroup A SRVE0169I: Loading Web Module: WebSphere Portal Server.
[1/30/09 12:50:02:693 EST] 00000026 WebApp A SRVE0180I: [wps#wps.war] [/wps] [Servlet.LOG]: ServiceManager: Loading from file:/opt/IBM/WebSphere/wp_profile/PortalServer/config/config/services.properties
[1/30/09 12:50:02:743 EST] 00000026 LogManagerDef I com.ibm.wps.logging.LogManagerDefaultImpl init
--------------------------------------------------------------------------------
IBM WebSphere Portal 6.1
Licensed Materials - Property of IBM
5724-E76, 5655-R17, and 5655-M44
(C) Copyright IBM Corp. 2001, 2007 - All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
--------------------------------------------------------------------------------
Build Level:
wp610_493_01 (2008-06-18 17:24)
--------------------------------------------------------------------------------
[1/30/09 12:50:02:755 EST] 00000026 Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
java.lang.NoClassDefFoundError: com.ibm.wps.services.ServiceHelper
at com.ibm.wps.services.ServiceManager.loadServiceProperties(ServiceManager.java:805)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:380)
at com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:285)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:179)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:114)
at com.ibm.wps.engine.Servlet.init(Servlet.java:239)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:192)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1221)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:152)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:831)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:486)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:323)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:290)
at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:92)
at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1303)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2122)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
[1/30/09 12:50:02:775 EST] 00000026 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/IBM/WebSphere/wp_profile/logs/ffdc/WebSphere_Portal_00000026_09.01.30_12.50.02_0.txt
[1/30/09 12:50:03:013 EST] 00000026 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/IBM/WebSphere/wp_profile/logs/ffdc/WebSphere_Portal_00000026_09.01.30_12.50.02_0.txt
[1/30/09 12:50:03:017 EST] 00000026 ServletWrappe E Deregister the mbean because of uncaught init() exception thrown by servlet portal: javax.servlet.UnavailableException: Initialization of one or more services failed.
at com.ibm.wps.engine.Servlet.init(Servlet.java:251)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:192)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1221)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:152)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:831)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:486)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:323)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:290)
at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:92)
at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1303)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2122)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
Caused by: java.lang.NoClassDefFoundError: com.ibm.wps.services.ServiceHelper
at com.ibm.wps.services.ServiceManager.loadServiceProperties(ServiceManager.java:805)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:380)
at com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:285)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:179)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:114)
at com.ibm.wps.engine.Servlet.init(Servlet.java:239)
... 23 more
,
..
{code}
And it goes on with more things failing (which I assume is because of the initial failure).
Does anybody have any clue about what is going on?
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
Yes, the PortalServer/shared/app/ext/wp.base.ext.jar file exists, and is readable (I can uncompress it with it giving any errors). I also tried making the file world readable and restarted the WebSphere_Portal server, but it made no difference.
I haven't changed anything to do with these folders either (especially since the last successful restart of the portal WebSphere_Portal server).
Make a copy of Server.xml and had reset the property
name="ws.ext.dirs"
value="${WPS_HOME}/shared/ext${WPS_PATH_SEPARATOR}${WPS_HOME}/shared/ext
I'm not sure if this was totally correct, but when I tried starting up the server again, it seems to have come up without any errors.
A big thanks for your help.
Property from working server...
Property from broken server...
Note the property ID is the same and that the description is the same. This leads me to believe that the ws.ext.dirs property was overwritten when I enabled the Warning level on the runtime messages. Looks to me like a bug! Comments from IBM???
Thanks.
-FF
The postings on this site are my own and do not necessarily represent the positions, strategies or opinions of IBM.
I got into similar situation after enabling the tracing from WAS console. now I don't have any 'ext' folder under PortalServer\shared\app, is there a way to restore the server?
Thanks,
leiz
Attempting to reproduce this in-house at the moment. If you can elaborate on the exact steps you took to make this happen, would greatly appreciate it. Thanks.
-Travis
While I would agree with Fang that this is most likely a WAS defect, it should also be addressed by Portal development as well since I imagine altering this setting has no consequences for WAS servers (server1, dmgr, etc).
~HT
-Travis