Error 503: Failed to startload target servlet Servlet - Websphere

This is a discussion on Error 503: Failed to startload target servlet Servlet - Websphere ; [1/11/07 15:06:38:603 CST] 76c353ea WebGroup E SRVE0020E: [Servlet Error]-[portal]: Failed to load servlet: javax.servlet.UnavailableException: Initialization of one or more services failed. at com.ibm.wps.engine.Servlet.init(Servlet.java:211) at com.ibm.ws.webcontainer.servlet.StrictServletInsta nce.doInit(StrictServletInstance.java:82) at com.ibm.ws.webcontainer.servlet.StrictLifecycleSer vlet._init(StrictLifecycleServlet.java:147) at com.ibm.ws.webcontainer.servlet.PreInitializedServ letState.init(StrictLifecycleServlet.java:270) at com.ibm.ws.webcontainer.servlet.StrictLifecycleSer vlet.init(StrictLifecycleServlet.java:113) at com.ibm.ws.webcontainer.servlet.ServletInstance.in it(ServletInstance.java:189) at javax.servlet.GenericServlet.init(GenericServlet.j ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Error 503: Failed to startload target servlet Servlet

  1. Error 503: Failed to startload target servlet Servlet

    [1/11/07 15:06:38:603 CST] 76c353ea WebGroup E SRVE0020E: [Servlet Error]-[portal]: Failed to load servlet: javax.servlet.UnavailableException: Initialization of one or more services failed.
    at com.ibm.wps.engine.Servlet.init(Servlet.java:211)
    at com.ibm.ws.webcontainer.servlet.StrictServletInsta nce.doInit(StrictServletInstance.java:82)
    at com.ibm.ws.webcontainer.servlet.StrictLifecycleSer vlet._init(StrictLifecycleServlet.java:147)
    at com.ibm.ws.webcontainer.servlet.PreInitializedServ letState.init(StrictLifecycleServlet.java:270)
    at com.ibm.ws.webcontainer.servlet.StrictLifecycleSer vlet.init(StrictLifecycleServlet.java:113)
    at com.ibm.ws.webcontainer.servlet.ServletInstance.in it(ServletInstance.java:189)
    at javax.servlet.GenericServlet.init(GenericServlet.j ava(Compiled Code))
    at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.addServlet(WebAppServletManager.java(Compiled Code))
    at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.loadServlet(WebAppServletManager.java:224)
    at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.getServletReference(WebAppServletManager.java:45 5)
    at com.ibm.ws.webcontainer.webapp.WebApp.getServletRe ference(WebApp.java:726)
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cherInfo.calculateInfo(WebAppRequestDispatcherInfo .java:207)
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cherInfo.(WebAppRequestDispatcherInfo.java:78)
    at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDi spatcher(WebApp.java:1564)
    at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDi spatcher(WebApp.java:1523)
    at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleIn vocationHook(WebAppInvoker.java:290)
    at com.ibm.ws.webcontainer.cache.invocation.CachedInv ocation.handleInvocation(CachedInvocation.java:71)
    at com.ibm.ws.webcontainer.srp.ServletRequestProcesso r.dispatchByURI(ServletRequestProcessor.java:246)
    at com.ibm.ws.webcontainer.oselistener.OSEListenerDis patcher.service(OSEListener.java:334)
    at com.ibm.ws.webcontainer.http.HttpConnection.handle Request(HttpConnection.java:56)
    at com.ibm.ws.http.HttpConnection.readAndHandleReques t(HttpConnection.java:652)
    at com.ibm.ws.http.HttpConnection.run(HttpConnection. java:448)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:936)
    Caused by: java.lang.Exception: ServiceManager: Previous initialization was not successful.
    at com.ibm.wps.services.ServiceManager.initInternal(S erviceManager.java:231)
    at com.ibm.wps.services.ServiceManager.init(ServiceMa nager.java:191)
    at com.ibm.wps.services.ServiceManager.init(ServiceMa nager.java:128)
    at com.ibm.wps.engine.Servlet.init(Servlet.java:205)
    ... 22 more



  2. Re: Error 503: Failed to startload target servlet Servlet

    If you are connected to a remote DB with the Portal, do ensure the database connectivity is proper and check the database you are connecting is started or not. Normally this error comes when the Portal server is not able to contact the database manager to fetch important data.


+ Reply to Thread