Question

3
Replies
403
Views
SRINIVAS BONTHU Member since 2012 11 posts
Unitedhealth Group
Posted: 3 years ago
Last activity: 3 years 8 months ago
Closed

PRPC Server is taking longer time to start after upgrading from 6.2 SP2 to 7.1.9

Hi All,

I have few environments which are running on JBOSS 6.x which were recently upgraded from 6.2 SP2 to 7.1.9 are taking a lot of time to startup (More than 1 and 1/2 hr). This issue is only happening on PRPC apps running on JBOSS. I didn't observed similar behavior with PRPC apps running on Websphere. After below nothing is being written in logs,

2017-02-07 16:16:22,217 INFO [stdout] (Dispatcher-Thread-99) 2017-02-07 16:16:22,214 [ apsrp8578.uhc.com] [ STANDARD] [ ] [ ] (ternal.async.PassivationDaemon) INFO - PegaRULES PassivationDaemon initialized in e-tier.
2017-02-07 16:17:22,223 ERROR [stderr] (Thread-107) Feb 07, 2017 4:17:22 PM com.pega.pegarules.ra.priv.PRResourceNode$AsyncTask run
2017-02-07 16:17:22,223 ERROR [stderr] (Thread-107) INFO: Attempting to connect to JMS queue for asynchronous task execution
2017-02-07 16:17:22,218 INFO [com.pega.pegarules.ra.priv] (Thread-107) Attempting to connect to JMS queue for asynchronous task execution
2017-02-07 16:17:22,283 ERROR [stderr] (Thread-107) Feb 07, 2017 4:17:22 PM com.pega.pegarules.ra.priv.PRResourceNode$AsyncTask run
2017-02-07 16:17:22,283 ERROR [stderr] (Thread-107) INFO: Publishing acknowledgement request message: {NodeID=21b3373fba3317196537a7dec0d2f789, ClientID=21b3373fba3317196537a7dec0d2f789, ResourceType=ACK_REQUIRED}
2017-02-07 16:17:22,283 INFO [com.pega.pegarules.ra.priv] (Thread-107) Publishing acknowledgement request message: {NodeID=21b3373fba3317196537a7dec0d2f789, ClientID=21b3373fba3317196537a7dec0d2f789, ResourceType=ACK_REQUIRED}
2017-02-07 16:17:27,285 INFO [stdout] (Thread-107) Resource Adapter successfully connected to JMS resource and published task message.

Below is the summary of the environment,

AppServer - JBOSS 6.4, 6.2 versions

DB - ORACLE 12c

Host OS - Linux

Heap Size - 4GB, 8GB(we have JVM's which are also taking longer time even have 8 GB memory)

Could anyone please help me in troubleshooting this issue? I really appreciate your help.

***Moderator Edit: Vidyaranjan | Updated Categories***

Low-Code App Development System Administration Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn