Question
WebSphere v8.5.5 JVM is repeatedly Restarting itself after upgrade to WAS fixpack 8.5.5.14 and SDK 8.0.5.17
We have 2 PRPC apps, v721 ,v731 both same issue on same server using WebSphere fixpack Proprietary information hidden and SDK Proprietary information hidden. the JVMs repeatedly Restarting itself .
Other PRPC apps on the same server have no issues.
Switch back to Java-7 and issue stops. Debug logs are not providing a hint.
Data src is good, INFO - PegaRULES engine successfully started.
Has anyone run into this condition before ? thanks.
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
CareFirst BlueCross BlueShield
US
Appreciate the Info ! Yes the “Web Tier initialization was complete.” And server- ‘open for e-business’.
Thereafter we had this one error Prior to the Shutdown> ERROR Exception in SOAPAppenderPega.sendEvent() related to RULE-OBJ-ACTIVITY PEGAAESREMOTE-
We determined that the issue was related to its environment/JVM not global.
No port conflicts were found within the logs. However, Ports were reassigned and All is operational now.
The RC is unknown, sketchy at best. Thanks for the feedback.
Pegasystems Inc.
GB
My Pega 7.3.1 runs on the below WAS and IBM JVM and I don;t experience any issue:
WebSphere Platform Proprietary information hidden [ND Proprietary information hidden cf131801.05] [IBMJAVA71 Proprietary information hidden cf131751.02] [IBMJAVA8 Proprietary information hidden cf131751.02] running with process name wchans3w7Node28Cell\wchans3w7Node28\PEGA731_WAS85_SPLITSCHEMA_SERVER and process id 17220
Host Operating System is Windows 7, version 6.1
Java version = 1.8.0_151, Java Runtime Version = Proprietary information hidden - pwa6480sr5fp6-20171124_02(SR5 FP6), Java Compiler = j9jit29, Java VM name = IBM J9 VM
was.install.root = C:\Program Files (x86)\IBM\Websphere85\AppServer
user.install.root = C:\Program Files (x86)\IBM\Websphere85\AppServer\profiles\PEGA731_WAS85_SPLIT
Java Home = C:\Program Files (x86)\IBM\Websphere85\AppServer\java_1.8_64\jre
Any errors in WAS log file?
Regards
Simon
Does the server restart directly after startup or is this a random shutdown and restart after running for some time.
Does it reach "Web Tier initialization is complete"?
Is there any Shutdown initiated entry, perhaps after cluster joining attempt failed for hazelcast.
There are reasons an instance will shutdown ... but I can't think of any that would cause it to restart itself. However, if you have a batch process that restarts a downed node, that would explain that piece.