Discussion
While Deploying prpc_j2ee14 Application getting error in PEGA 7.1 .7 Version
Team,
Please help me to find the solution of the issue in PEGA 7.1.7.
My configuration :
installed Pega 7.1.7 in Linux with oracle 11.2.0.4 Version Database and also installed Weblogic 11g(10.3.6.0), while deploying prpc_j2ee14.ear file we are getting some error. Please find the error pasted below.
ERROR:
####<May 22, 2015 2:01:53 PM IST> <Emergency> <com.pega.pegarules.internal.bootstrap.PRBootstrap> <TACOEPEGADEV.gdnindia.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1432283513176> <BEA-000000> <prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings>
####<May 22, 2015 2:01:53 PM IST> <Error> <com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource> <TACOEPEGADEV.gdnindia.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1432283513177> <BEA-000000> <Unable to obtain DataSource for java:comp/env/jdbc/PegaRULES; javax.naming.NameNotFoundException: While trying to look up comp/env/jdbc/PegaRULES in /app/webapp/prweb/1433747971.; remaining name 'comp/env/jdbc/PegaRULES'>
####<May 22, 2015 2:01:53 PM IST> <Emergency> <com.pega.pegarules.internal.bootstrap.PRBootstrap> <TACOEPEGADEV.gdnindia.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1432283513178> <BEA-000000> <PRBootstrap.calculateEngineCodeVersionFromDB() - unable to calculate codeset version from database: null>
####<May 22, 2015 2:01:53 PM IST> <Emergency> <com.pega.pegarules.internal.bootstrap.PRMiniLoader> <TACOEPEGADEV.gdnindia.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1432283513178> <BEA-000000> <Will load phase 2 bootstrap from Pega-EngineCode:>
####<May 22, 2015 2:01:53 PM IST> <Emergency> <com.pega.pegarules.internal.bootstrap.PRBootstrap> <TACOEPEGADEV.gdnindia.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1432283513179> <BEA-000000> <
============ PegaRULES Bootstrap Configuration ============
Date: Fri May 22 14:01:53 IST 2015
Java Version: Oracle Corporation 1.7.0_79
Configuration: zip:/u01/app/Middleware/weblogic/user_projects/domains/pega_domain/servers/AdminServer/tmp/_WL_user/prpc_j2ee14/2zj6g8/APP-INF/lib/prresources.jar!/prbootstrap.properties
Pega-EngineCode:
(!) Unable to locate classes on filesystem
=============== End Bootstrap Configuration ===============
>
####<May 22, 2015 2:01:53 PM IST> <Error> <com.pega.pegarules.internal.bootstrap.PRBootstrap> <TACOEPEGADEV.gdnindia.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1432283513180> <BEA-000000> <Error initializing PRAppLoader
java.lang.ClassNotFoundException: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
at com.pega.pegarules.internal.bootstrap.PRMiniLoader.loadClass(PRMiniLoader.java:388)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.loadPhase2BootstrapClass(PRBootstrap.java:685)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:629)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:376)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextDestroyed(WebAppLifeCycleListenerBoot.java:67)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3225)
at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1545)
at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:509)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:677)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Thanks
Kannan
The error that is most glaring to me is (!) Unable to locate classes on filesystem.
Can you check that you have specified the classpath properly? Sometimes it's good to have a 2nd pair of eyes to help you go through your configuration settings again. Much easier to catch typos and mistakes.
Failing which, I suggest you contact Pega support for further assistance if necessary.