Discussion
Pegasystems Inc.
US
Last activity: 21 Apr 2020 0:51 EDT
Critical HFIX-60101 (Pega Platform 7.4)
Pega has identified the HFIX-60101 as critical for ensuring a productive and secure development experience on our Pega Platform 7.4 release. If you are developing applications on this release version, we strongly encourage you to verify the this hot fix is installed in your environments and, if not, that you submit a hot fix request in My Support Portal to receive the necessary download files for installation.
Description
After a split brain recovery, remote operations could not be performed on the node that rejoined the cluster.
Pegasystems Inc.
US
Hi @EngincanY!
The description for HFIX-48716 is Thread Hangs after Hazelcast Lock Attempt
Hope that helps!
Marissa | Senior Moderator | Pega Collaboration Center
Pegasystems Inc.
IN
Hi,
HIFX-48716 is provided to fix an issue where Process Commander Requestors significantly slow/become unusable after repeated calls to Hazelcast. The following thread dump is repeatedly thrown after this issue begins to occur:
"https-openssl-nio-443-exec-9" Id=208 in WAITING BlockedCount : 0, BlockedTime : -1, WaitedCount : 63, WaitedTime : -1 at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(Unknown Source) at com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:153) at com.hazelcast.spi.impl.AbstractInvocationFuture.join(AbstractInvocationFuture.java:136) at com.hazelcast.concurrent.lock.LockProxySupport.lock(LockProxySupport.java:84) at com.hazelcast.concurrent.lock.LockProxySupport.lock(LockProxySupport.java:76) at com.hazelcast.map.impl.proxy.MapProxyImpl.lock(MapProxyImpl.java:262) at com.pega.pegarules.cluster.internal.PRHazelcastDistributedMapImpl.lock(PRHazelcastDistributedMapImpl.java:385) at com.pega.pegarules.data.internal.lock.LockUtils.waitTillLockIsAvailableOnPrSysLocksTableInDistributedMap(LockUtils.java:105)
Warm Regards,
Venkat