SpectroSERVER VNM.OUT file increased to 20 MB

book

Article ID: 222500

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

We see that our Primary SS has increased in size to 20 megs.

 

We are seeing a lot of messages like this in the VNM.OUT file.

 


May 06 16:09:06 ERROR TRACE at CsWatchNotificationQueue.cc(271): A(n) association notification has exceeded the maximum internal queue size: The client [email protected]<OC Server name> may be unresponsive. Dumping pending queue:
CsOrbRelWatcher (MH: 0x13030075, relation: 0x1003a)
CsOrbRelWatcher (MH: 0x13030075, relation: 0x1003a)
CsOrbRelWatcher (MH: 0x13030075, relation: 0x1003a)
CsOrbRelWatcher (MH: 0x13030075, relation: 0x1003a)
CsOrbRelWatcher (MH: 0x13030075, relation: 0x1003a)
CsOrbRelWatcher (MH: 0x13030075, relation: 0x1003a)
...

Cause

The dump is a CORBA debug that may be useful in some troubleshooting situations

Environment

Release : 10.4.x, 21.x

Component :SPCCSS

Resolution

This was fixed out of the box in Spectrum 10.4.3 with an option to add a .vnmrc option to disable unwanted debugging output to the VNM.OUT file.

If the CORBA debug data is not wanted and you are on Spectrum 10.4.3 or higher you can add this line to the $SPECROOT/SS/.vnmrc file

dump_pending_corba_client_notifications=FALSE

Additional Information

Symptom: Huge notification queue data dumped into VNM.out
Resolution: Making pending queue dumping configurable through the .vnrmc option. (DE485366, 10.4.3)