Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega 7.1.7 server crash in multi-node environment during startup

SA-8939

Summary



You have a Pega 7.1.7 instance running on WebSphere either as a single node or in a cluster. The server fails to come up and crashes during startup.

Error Messages



Java core in Unix environment:

1TISIGINFO Dump Event "gpf" (00002000) received
1TIDATETIME Date: 2015/04/02 at 16:22:09
1TIFILENAME Javacore filename: /apps/server/core/profile/javacore.20150402.162153.13304006.0004.txt
1TIREQFLAGS Request Flags: 0x81 (exclusive+preempt)
1TIPREPSTATE Prep State: 0x0
1TIPREPINFO Exclusive VM access not taken: data may not be consistent across javacore sections


Java core in Windows environment:


Unhandled exception
Type=Segmentation error vmState=0x00000000
Windows_ExceptionCode=c0000005 J9Generic_Signal=00000004 ExceptionAddress=000007FFFF301E21 ContextFlags=0010005f


Steps to Reproduce



Bring up Pega 7.1.7 on a WebSphere platform.

Root Cause



The root cause of this problem is a bug in the Java SDK distributed with WebSphere prior to Fix pack 25.

Resolution



Java SDK SR11 of Fix Pack 25 or later for WebSphere Application Server 7.0 solves the issue.
 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us