CA Service Management

Hi Team,

For CA SDM 14.1.03, daily at 8 am in the morning, following files get generated in the bin folder:

hs_err_pid86880.log

hs_err_pid76016.log

hs_err_pid76016.mdmp

Size of these files is more than 8 GB.

Why such files are getting generated?

Kindly provide your valuable suggestions.

Thanks & Regards,

Balram

Hi Balram,

By any chance do you have CA Siteminder integrated with SDM?

Thanks

Junaid

Hi Junaid,

Thanks for your response.

It is not integrated with Siteminder. It is integrated with CA Spectrum only.

Regards,

Balram

One thing I can suggest is to navigate to the following: File Explorer > right-click Computer > Properties > Advanced System Settings > Startup and Recovery Settings and change the Write debugging information to 'small memory dump', or change the location to a device where the memory dumps won't cause an out-of-space error.

Also can you let me know what is the current Java version in your environment?

The current setting that you suggested in set to 'None'. Should I change it to 'small memory dump'? Java version is 1.7.0_10. OS is Windows server 2012 R2.

Let the setting be unchanged.

How about trying to upgrade the java version from 1.7 to 1.8 ,you can refer the below link for JRE upgradation.

Step 3- Install Other Components - CA Service Management - 14.1 - CA Technologies Documentation 

Currently, it is not possible to upgrade java. Can we go for changing the setting to 'small memory dump' or it wont make much difference?

Any idea which process is generating these pid files in the bin folder? And what is the error stating about? 

Hi Balaram,

In one of the case we have figured out that those errors are generated by the OneClicknotification related. 

hs_err_pid<xxxx>.log files shows some information as below.

I have reviewed couple of more hs_err_pid<xxxx>.log files and java dump files.

VM Arguments:

jvm_args: -DFILE_NAME=\sfeg.

java_command: OCNotify.jar

java_class_path (initial): OCNotify.jar

Launcher Type: SUN_STANDARD

Call stack of this thread is:

j  sun.net.www.protocol.http.Handler.openConnection(Ljava/net/URL;)Ljava/net/URLConnection;+6

j  java.net.URL.openConnection()Ljava/net/URLConnection;+5

j  OneClickNotification.sendRequest(Ljava/lang/String;)V+262

j  OneClickNotification.main([Ljava/lang/String;)V+152

v  ~StubRoutines::call_stub

It seems while making some http connection, it is throwing these errors.

Check the content of hs_err_pid<***>.log file for some information like above. So that we can figure out which process is causing these errors.

Hope this helps.

Thanks & Regards,

Hema.

Hi Hema,

We are also facing similar kind of issue. Please find the logs as below

Windows Application Log :-

Faulting application name: java.exe, version: 8.0.1120.15, time stamp: 0x57e4b249
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000002
Faulting process id: 0xb154
Faulting application start time: 0x01d2e0caf46dce4c
Faulting application path: C:\Program Files\Java\jre1.8.0_112\bin\java.exe
Faulting module path: unknown
Report Id: 3e57a85e-4cbe-11e7-80f2-00155d026f28
Faulting package full name:
Faulting package-relative application ID:

hs_err_pid<xxxx>.log 

VM Arguments:
jvm_args: -DFILE_NAME=\s4pfk.
java_command: OCNotify.jar
java_class_path (initial): OCNotify.jar
Launcher Type: SUN_STANDARD

Request you to look into and suggest.

Regards,

Piyush Mer

Hey Piyush,

Normally SDM uses 32bit JRE,  the above path seems to indicate that somehow 64bit JRE is coming into picture. 

The OneClick integration program is crashing for some reason, and that's what is generating these dump files.  Maybe re-running the one click configuration program on the SDM server helps resolve this?  Try to run the program with SDM JRE  set in your PATH  and not  the 64bit Java 8 it seems to get launched under right now?

_R