PRPC62SP2 installation has failed on Websphere
Hi Team,
We are trying to install PRPC62sp2 on Websphere 8.x and its throwing the below exception.
WAS Version : Proprietary information hidden
Cluster : Single Node
JVM Java Version : 1.6
[3/8/16 7:57:31:541 EST] 00000020 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [ges_pega_prsysmgmt] [/prsysmgmt] [/jmxclienterror.jsp]: Initialization successful.
[3/8/16 7:57:35:968 EST] 00000020 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [ges_pega_prweb] [/prweb] [WebStandard]: Initialization successful.
[3/8/16 7:57:36:329 EST] 00000020 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[WebStandard]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: PegaRULES server not available
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:643)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1189)
at com.pega.pegarules.web.impl.WebStandardImpl.sendOutput(WebStandardImpl.java:426)
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
Hi Team,
We are trying to install PRPC62sp2 on Websphere 8.x and its throwing the below exception.
WAS Version : Proprietary information hidden
Cluster : Single Node
JVM Java Version : 1.6
[3/8/16 7:57:31:541 EST] 00000020 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [ges_pega_prsysmgmt] [/prsysmgmt] [/jmxclienterror.jsp]: Initialization successful.
[3/8/16 7:57:35:968 EST] 00000020 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [ges_pega_prweb] [/prweb] [WebStandard]: Initialization successful.
[3/8/16 7:57:36:329 EST] 00000020 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[WebStandard]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: PegaRULES server not available
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:643)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1189)
at com.pega.pegarules.web.impl.WebStandardImpl.sendOutput(WebStandardImpl.java:426)
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1662)
[3/8/16 8:03:41:079 EST] 00000021 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[WebStandard]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: PegaRULES server not available
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:643)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1189)
at com.pega.pegarules.web.impl.WebStandardImpl.sendOutput(WebStandardImpl.java:426)
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
Attaching sysout as well.
Accepted Solution
Pegasystems Inc.
US
Taking a quick peek at the ERROR stack, looks like you haven't configured the PRPCWorkManager in WAS. Please refer to section "Configure WebSphere WorkManager" in the 6.2SP2 install guide. Link below -
https://docs-previous.pega.com/product-release-prpc-62-sp2-installation-guide-websphere-7-db2
Pegasystems Inc.
US
Looks like you were running WAS 7. Was it working at the time? Also you have some MDB of your own MRIAcknowledgment, can you make sure no messages on the queue before starting up the server? You may also want to try OOTB ear deployment first to eliminate your own customization. Once the OOTB works, you can then use your own ear (with your own MDB in prbeans.jar).
Accepted Solution
Pegasystems Inc.
US
Taking a quick peek at the ERROR stack, looks like you haven't configured the PRPCWorkManager in WAS. Please refer to section "Configure WebSphere WorkManager" in the 6.2SP2 install guide. Link below -
https://docs-previous.pega.com/product-release-prpc-62-sp2-installation-guide-websphere-7-db2
Virtusa IT Consulting
AE
Hi Abdul,
Agreeing to Ankur Das as it is evident from the sysout log file that I was unable to identify wm/PegaWorkManager.
[1/18/16 4:53:40:290 EST] 00000000 ResourceMgrIm I WSVR0049I: Binding DefaultWorkManager as wm/default
[1/18/16 4:53:40:297 EST] 00000000 ResourceMgrIm I WSVR0049I: Binding AsyncRequestDispatcherWorkManager as wm/ard
Thanks,
Habeeb Baig
JP Morgan
US
Tried reinstalling the application in WAS.
Compared data sources with old environment and changed few properties, JVM is up with below errors
[3/14/16 2:44:38:476 EDT] 00000009 priv E JNDI API lookup failed for factory: javax.naming.NameNotFoundException: Name comp/env/jms/tcf not found in context "java:".
javax.naming.NameNotFoundException: Name comp/env/jms/tcf not found in context "java:".
at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1837)
at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1166)
at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1095)@@z
Attaching the latest_sysout logs to above.
Pegasystems Inc.
IN
Hi Abdul,
How are you?
I see that this JVM is in hung state as suggested by this message:
[3/14/16 1:52:35:324 EDT] 00000012 ThreadMonitor W WSVR0605W: Thread "dlccasgespy01" (00000009) has been active for 714267 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
From older logs, I see that you have many custom JMS resources, therefore, I request you to configure all needed by customer ear to get this fixed.
Also, as suggested above, re-check configuration of PRPCWorkManager