Post that log if the issue is still present. at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1662), ***Updated by Moderator: Vidyaranjan. Pegasystems is the leader in cloud software for customer engagement and operational excellence. Robotic Process Automation Design Patterns, https://collaborate.pega.com/question/pega-821-oraclejdbcoracleconnection-not-part-build-path, https://community.pega.com/knowledgebase/documents/pega-platform-81-installation-guide-jboss-redhat-eap-and-oracle, HTTP Status 503 - PegaRULES server not available, Error 503: PegaRULES server not available, PegaRULES server not available after install. This is a feature of IIS, at Application Pool level, called Rapid-Fail Protection. For the past 30 years, our technology CRM, digital process automation, robotics, AI, and more has empowered the worlds leading companies to achieve breakthrough results. Are you using your own prlogging.xml? at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1320) at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272) at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.updateDefinition(BasicApplicationContext.java:491) 2016-02-16 16:04:16,944 [LOAD_PEGACONCLUSIONS] [ STANDARD] [ ] [ ] (dictionary.ConclusionCacheImpl) INFO - Starting conclusion pre-load at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) We tried to recycle our JVMs and when we tried to check if the servers are up and running, we saw this error mentioned: "Error 503: PegaRULES server not available". at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.allocateSessionAuthorization(PRRequestorImpl.java:2009) However after that when we restarted the JVMs, this issue started appearing. at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:388) Have you seen the following already:https://collaborate.pega.com/question/503-error. at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.createRequestorImpl(NodeRequestorMgt.java:1479) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592) If you have a similar request, please write a new post. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223) 2. HTTP Status 503 - PegaRULES server not available | Support Center. Mule support case mentioned that this is caused by the gateway. at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5486) The implication is that this is a temporary condition which will be alleviated after some delay. 'Service Unavailable' problem with the following tricks. at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701) the Web site is simply unavailable. YES. at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doGet(WebStandardBoot.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 4. at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:945) Talk to sales Call +1 (888) 610-2915 and find the hosting plan that's right for you. Removed user added Ask the Expert tag. at java.lang.reflect.Method.invoke(Method.java:611) Kindly keep backup of all these outside of Websphere directory. at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:508) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4812) Experience the benefits of Support Center when you log in. at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(GlobalContextCache.java:582) If the house is heavy and the land underneath marshy, your home will collapse like a deck of cards. In this case, it may be enough to just refresh the page to resolve the HTTP 503 error. If you have a similar request, please write a new post. When RPC . at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Thank You Everyone So Much For Watch My Video On " How To Fix Roblox 503 Service Unavailable || Roblox 503 Service Unavailable No server is available ". If known, the length of the delay MAY be indicated in a Retry-After header. at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) Message PegaRULES server not available. or The given user Identity of Application Pool may be invalid due to expired password or locked. This content is closed to future replies and is no longer being maintained or updated. This content is closed to future replies and is no longer being maintained or updated. - Already tried to reinstall Pega. at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:611) Please contact your PegaRULES system administrator. Server: INBOMVD818402 2020-02-04 22:56:59,835 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed Pega Knowledge 7.31 Low-Code App Development Financial Services Senior System Architect Pega Academy ; Request a live demo Get a personalized demo of our powerful dashboard and hosting features. at com.pega.pegarules.session.internal.mgmt.base.ThreadPassivation.configureThreadImpl(ThreadPassivation.java:322) Read the new Privacy . at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138) Thank you for your response.this solved my issue after defining jdbc as global module. at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:299) at com.pega.pegarules.session.internal.PRSessionProviderImpl.borrowRequestor(PRSessionProviderImpl.java:655) Discover program benefits and enablement resources, Manage your organization's relationship with Pega, Drive success with centralized content and resources, Complete missions, earn badges, and stay current, Browse library of UI/UX templates, patterns, and components. @Noel. Discover program benefits and enablement resources, Manage your organization's relationship with Pega, Drive success with centralized content and resources, Complete missions, earn badges, and stay current, Browse library of UI/UX templates, patterns, and components. Log in or sign up to set up personalized notifications. You have access to the response in the exception's Response property (in case there's a 503 response, the exception that's raised is a WebException, which has a Response property). at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.(PRThreadImpl.java:134) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2087) - Test connection is successful on PegRULES datasource. Solution 4: Contacting the website's administrator or support. almost every morning when logging into plesk panel i get the error message "error 503, service not available". There can be an incorrect parameter in the Java side, which is not letting you connect to the Java stack. Solution 2: Restarting your computer, router, etc., or changing your DNS server. at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1998) User other browsers to see if there is any difference. The 503 response from the IIS machine, Service Unavailable, is the result of repeated application crashes. 2. 2020-02-04 22:56:37,753 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) java.lang.ClassNotFoundException: oracle.jdbc.OracleConnection, internal.mgmt.PREnvironment) ERROR - com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception 44 more at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1270) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2016-02-16 16:04:18,192 [l LOAD_ASSEMBLYCACHE] [ STANDARD] [ ] [ ] (pcentric.RACacheAppCentricImpl) INFO - End of reload processing, loaded 0 rows, elapsed time is 109 milliseconds. at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100) Discover program benefits and enablement resources, Manage your organization's relationship with Pega, Drive success with centralized content and resources, Complete missions, earn badges, and stay current, Browse library of UI/UX templates, patterns, and components. Please contact your system administrator.. at java.lang.reflect.Method.invoke(Method.java:497) HTTP 503 troubleshooting: options from server operators. at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:664) Robotic Process Automation Design Patterns, https://docs-previous.pega.com/pega-72-platform-installation-guide-tomcat-and-oracle, HTTP Status 503 - PegaRULES server not available, Error 503: PegaRULES server not available, Error 503: PegaRULES server not available while accessing PEGA Application. Log in or sign up to set up personalized notifications. at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:380) Thanks for your reply. I have Power BI Report Server (May 2019) installed on SQL Server 2016 Enterprise working perfectly. Maximum age in hours for Usage data is 96. This content is closed to future replies and is no longer being maintained or updated. Please check if all the admin accounts in your organization have the same issue. i also did the owa/ecp VD reset from another server (aka server 1) that is working fine (because i cant open ecp from the one that is failing, aka server 2), i selected the server 2, and did the VD resets. at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:311) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1272) 2016-02-16 16:04:29,830 [ FRCVASR1892] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Contact a Moderator. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at com.pega.pegarules.generation.internal.PRGenProviderImpl.finishInit(PRGenProviderImpl.java:658) 503 Service unavailable. Log in or sign up to set up personalized notifications. Type Status Report. at java.util.HashMap.put(HashMap.java:611) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at com.pega.pegarules.generation.internal.vtable.dao.VirtualTableDataAccessObject.loadTable(VirtualTableDataAccessObject.java:74) Caused by: at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1270) at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:218) 31 more Log in or sign up to set up personalized notifications. Please double check on that. at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.(BasicApplicationContext.java:159) i cand find anything useful in the event viewer, i just see this inside the system32/logfiles/HTTPERR now i see some changes inside that log. Moving forward, there are 2 suggestions that we think makes sense: 1. at javax.servlet.http.HttpServlet.service(HttpServlet.java:718) 2016-02-16 16:04:16,289 [ALDECLARATIVECLASSES] [ STANDARD] [ ] [ ] (bi.DeclarativeCacheManagerImpl) INFO - Starting global declarative cache pre-load at java.util.concurrent.FutureTask.run(FutureTask.java:266) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:874) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:945) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:970) at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) Hi @ivan.cherkasov our dev team have investigated this issue using the versions you gave and have the following advice:. 1. at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1998) If you are running server on VM, Please have a look at below thread to see if it helps at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5398) at com.pega.pegarules.generation.internal.vtable.dao.AbstractVirtualTableCacheQuery$ResultSetReader.next(AbstractVirtualTableCacheQuery.java:350) Apologies for confusion, shouldn't have been an end-user option***. Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request " The application code, below is trying to mark the items as "Read" but fails. at com.pega.pegarules.data.internal.access.ResultSetIteratorImpl.next(ResultSetIteratorImpl.java:252) The origin returned a 503 error without a response header, so Fastly used the default response. at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166) 2016-02-16 16:04:18,083 [l LOAD_ASSEMBLYCACHE] [ STANDARD] [ ] [ ] ( external.async.IStartupTask) INFO - load reloadCache ..starting But today I was upgrading to the September 2019 version, the installation completed normally, but when I opened the reports the following message was displayed in the browser: at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408) 73 more. From the HAproxy docs: It can happen from many reasons: The status code is always 3-digit. 41 more at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370) LOGs are attached along with. Accordingly, lighttpd shows some errors: at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138) Log in or sign up to set up user profile. at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) you need to catch this exception and handle it properly We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. To improve your experience, please update your browser. Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:841) Learn more. Experience the benefits of Support Center when you log in. at com.pega.pegarules.generation.internal.vtable.dao.AbstractVirtualTableQueryProcessor.process(AbstractVirtualTableQueryProcessor.java:66) Solution 1: Refreshing the page. Check the log file to see why Pega7 failed to properly initialize. Robotic Process Automation Design Patterns, Error 503: PegaRULES server not available while accessing PEGA Application, HTTP Status 503 - PegaRULES server not available, PegaRULES server not available after install. Your issue is likely due to the fact that you need to define jdbc driver as a global module:https://community.pega.com/knowledgebase/documents/pega-platform-81-installation-guide-jboss-redhat-eap-and-oracle. at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1146) WP core does not disable it by default or arbitrarily. If youve driven a car, used a credit card, called a company for service, opened an account, flown on a plane, submitted a claim, or performed countless other everyday tasks, chances are youve interacted with Pega. at java.lang.Thread.run(Thread.java:745) E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[WebStandard]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: PegaRULES server not available at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1091) Experience the benefits of Support Center when you log in. (Path - Windows run command > inetMgr > Application Pools > AOSService) at com.pega.pegarules.session.internal.authorization.context.AuthorizationContextManagerImpl.getContext(AuthorizationContextManagerImpl.java:132) About Pegasystems. Discover program benefits and enablement resources, Manage your organization's relationship with Pega, Drive success with centralized content and resources, Complete missions, earn badges, and stay current, Browse library of UI/UX templates, patterns, and components. There can be few probable reasons for this:- 1. The most common reasons this generic text appears include: The origin server generated a 503 error and Fastly passed it through as is. com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure Exception: The remote server returned an error: (503) Server Unavailable. 2016-02-16 16:05:15,323 [ALDECLARATIVECLASSES] [ STANDARD] [ ] [ ] ( external.async.IStartupTask) INFO - load global declarative classes ..done, Follow the steps in the following guidehttps://docs-previous.pega.com/pega-72-platform-installation-guide-tomcat-and-oracle. at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1721) at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:218) StackTrace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.IdentityServer.Management.Proxy.Providers.ProxyTrustProvider.EstablishTrustWithSts(ICredentials credentials, String thumbprint) AD FS server: AD FS Tracing/Debug Source: AD FS Tracing Event ID: 107 Yes i did it but not solve the issue. Log in or sign up to set up user profile. at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:311) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:527) anyone else who is getting this error? - PRPC ear is shown as running in Application server. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 2016-02-16 16:04:18,036 [ FRCVASR1892] [ STANDARD] [ ] [ ] (ternal.vtable.VirtualTableImpl) INFO - Virtual Table Preload Starting at com.pega.pegarules.web.impl.WebStandardImpl.sendOutput(WebStandardImpl.java:643) Pegasystems is the leader in cloud software for customer engagement and operational excellence. If you have a similar request, please write a new post. at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83) 2016-02-16 16:04:18,192 [l LOAD_ASSEMBLYCACHE] [ STANDARD] [ ] [ ] (pcentric.RACacheAppCentricImpl) INFO - reload added 0 assembledClasses 0 shortcuts. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of the Web server machine. [ You don't have to lose your sleep over server errors. 3. - pgAdmin has the Satistics of "select pzlastmodified, pzbinarycontent from rulesschema.pr_engineclasses.", - tomcat/app manager says "OK - Started application at context path /prweb". at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.createRequestor(PRNodeImpl.java:273) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) Problem during method invocation (contextInitialized) java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.web.servlet.WebAppLifeCycleListener at com.pega.pegarules.session.internal.authorization.context.RuleApplicationFlattener$DbAppReader.toClipboardPage(RuleApplicationFlattener.java:278) at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:527) It didn't help. To improve your experience, please update your browser. at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:617) Caused by: com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.createAppStackForAccessGroup(BasicApplicationContext.java:660) Log in or sign up to set up user profile. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) Links may no longer function. The request failed. at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:461) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) Check Resource Usage. I would suggest start up the engine with OOTB deployment (prlogging.xml would be inside prresources.jar) and go from there. at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:664) java.lang.reflect.InvocationTargetException at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1998) The first digit indicates a general status : - 1xx = informational message to be skipped (eg: 100, 101) - 2xx = OK, content is following (eg: 200, 206) - 3xx = OK, no content . wdisp/system, icm/HTTP/mod, SRCSRV, SRCVHOST, SRCURL, 503 Service not available, Not Reachable, KBA , icmenosystemfound , BC-CST-WDP , Web Dispatcher , Problem About this page This is a preview of a SAP Knowledge Base Article. Pegasystems is the leader in cloud software for customer engagement and operational excellence. 2. com.pega.pegarules.pub.context.InvalidConfigurationException: No such Rule-Application instance: RUSA:03.05.01 I'd recommend checking the security permissions of the folder used as the site's root. The resources that a server uses are RAM, CPU, I/O, entry processes, and website inodes. 3. at com.pega.pegarules.session.internal.authorization.Authorization.onBeforeThreadUse(Authorization.java:1629) Problem still exists. at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:759) We'll get back to you in one business day. To improve your experience, please update your browser. This content is closed to future replies and is no longer being maintained or updated. select distinct pysystemname from pr_data_admin where pxobjclass like 'Data-Admin-Requestor'; and using one of the names from the result set the following in your prconfig.xml for example . We have seen different articles regarding this issue, we tried all the solution but nothing been helpful. It's not clear where the problem is. This specific error is appearing in the systemout.log file that I want to highlight (New systemout.log file generated is attached along with): [8/5/15 16:29:44:538 EDT] 0000005f SystemOut O 2015-08-05 16:29:44,538 [ server.startup : 0] [ ] [ ] [ ] ( context.web.WebEnvironment) INFO - Web tier using local JNDI context, factory = com.ibm.websphere.naming.WsnInitialContextFactory, url = corbaloc:rir:/NameServiceServerRoot, [8/5/15 16:29:44:539 EDT] 0000005f PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Problem during method invocation (contextInitialized), java.lang.StringIndexOutOfBoundsException, at java.lang.String.(String.java:183), at com.pega.pegarules.priv.util.LogDeleteUtil.readFromFile(LogDeleteUtil.java:296), at com.pega.pegarules.priv.util.DailySizeRollingFileAppenderPega.handleFirstLogEvent(DailySizeRollingFileAppenderPega.java:167), at com.pega.pegarules.priv.util.DailySizeRollingFileAppenderPega.subAppend(DailySizeRollingFileAppenderPega.java:148), at com.pega.apache.log4j.WriterAppender.append(WriterAppender.java:159), at com.pega.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230), at com.pega.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66), at com.pega.apache.log4j.AsyncAppender.append(AsyncAppender.java:146), at com.pega.apache.log4j.Category.callAppenders(Category.java:206), at com.pega.pegarules.priv.LogHelper.infoForced(LogHelper.java:1198), at com.pega.pegarules.priv.context.web.WebEnvironment.getJNDIContexts(WebEnvironment.java:324), at com.pega.pegarules.priv.context.web.WebEnvironment._runDiscovery_privact(WebEnvironment.java:260), at com.pega.pegarules.priv.context.web.WebEnvironment.runDiscovery(WebEnvironment.java:166), at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:269), at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:218), at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83), at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1704), at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:411), at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88), at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169), at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749), at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634), at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:426), at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:718), at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1177), at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1370), at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639), at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968), at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:776), at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2195), at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5477), at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5603), at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255), at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2200), at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:435), at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123), at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:378), at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:126), at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:984), at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:502). We have requested that Google expedite a re-index, which may take several days.