Unable to create a "heap.bin" memory dump file for GroupWise 18 Webaccess troubleshooting on the Windows 2012 Server platform.

  • 7022636
  • 02-Feb-2018
  • 02-Feb-2018

Environment

GroupWise 2014 R2
GroupWise 18

Situation

Unable to create a "heap.bin" memory dump file for GroupWise 14.2.2 or GroupWise 18 Webaccess troubleshooting on the Windows 2012 Server platform.

Resolution

This has been fixed.

Note:  You must also have the update files also to have the fix :

  - GroupWise 14.2.2 build 129662 or higher
 
  - GroupWise 18 build 129661 or higher


This issue was caused by a change in Java 8 Update 141, as listed here:

http://www.oracle.com/technetwork/java/javase/8u141-relnotes-3720385.html

You can search in this url for the Changes section :

Changes

core-svc/java.lang.management
JMX Diagnostic improvements
com.sun.management.HotSpotDiagnostic::dumpHeap API is modified to throw IllegalArgumentException if the supplied file name does not end with “.hprof” suffix. Existing applications which do not provide a file name
ending with the “.hprof” extension will fail with IllegalArgumentException. In that case, applications can either choose to handle the exception or restore old behavior by setting system property
'jdk.management.heapdump.allowAnyFileSuffix' to true.

So the only thing different you have to do is to create the GroupWise 18 Webaccess memory dump file with a different file name extenstion other than .bin :

** NOTE:  This same information about the need to use a file extension other than .bin, applies also to a linux version of Oracle Java 8 build 141 or higher **
** The log file path for Webaccess for the linux platform would be /var/opt/novell/groupwise/webaccess/logs **

1.  You do not have to stop or restart the "grpwise-tomcat8" windows service

2.  In the C:\Novell\GroupWise\Webaccess\logs\ directory, create an empty file called : "heap.hprof" 
(no quotes, just use this name, but the important part is it MUST have the file extenstion of .hprof)

3.  Ideally start the creation and population of data into this file just before the problem begins and during the problem.

4.  You must have GW18 build 129661 or higher


Or as an alternative you can try : Windows :

1.  Having Oracle Java 8 JDK installed on the Windows server and issue this command :

2.  cd to the Java JDK bin directory and issue the command below :

3.  jmap -dump:format=b,file=C:\heap.hprof <pid-Of-grpwise-tomcat8>

  // You must have read write permissions to the C:\ drive to create the file at C:\
  // To find out the pid of the grpwise-tomcat8 process under windows, go to the
  // Windows Task Manager, click on the Services tab, scroll down to "Tomcat8" and the number to the right is the PID number.
 
 
Or as an alternative you can try : Linux :
 
  1.  Having Oracle Java 8 JDK installed on the Windows server and issue this command :
 
  2.  cd to the Java JDK bin directory and issue the command below :
 
  3.  jmap -dump:format=b,file=/tmp/heap.hprof <pid-Of-grpwise-tomcat8>
 
    // You must have read write permissions to the /tmp directory to create the file
    // To find out the pid of the grpwise-tomcat8 process under linux :
       - Issue the command as "root" "ps -eaf | grep grpwise-tomcat8"

Cause

Change in Oracle Java JDK 8 version.

Additional Information

Note:  This problem could also occur on the SLES11 or SLES12 Linux platform.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.