UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.

The events in the event browser show huge difference between the time created and time received and

The events in the event browser show huge difference between the time created and time received and

The customer notices that the events in the event browser are showing difference of the time created and the time first received of minutes. When the do a continues ping against the reverse proxy URL of OBM they see that from time to time it does not respond showing a timeout error. Also, the opr-gateway logs show connection disconnected errors on the GWs. In 300 times connecting to OBM it failed 8 times. The same fails happen against both GWs URLs directly. When running opcagt on OBM GWs, sometimes it is replying with buffering issue for the RP URL.

Solution

On each GWS do the below:

ovc -kill

del %ovdatadir%\tmp\bbc\*

del %ovdatadir%\datafiles\bbc\*

set

[bbc.http]

SSL_HANDSHAKE_TIMEOUT=300000 to 600000

ovc -start


This was to help the ovbbccb from reporting as unavailable. It was found one agent had a 1GB msg data queue file and was hammering the server. Basically, opcmsga adds the events into the msgagtdf file before forwarding to the message receiver in the WDE. Usually the size of msgagtdf file increases when the agents goes into buffering state or when the processing of the events by opcmsga is slower. The modification that we did in the customer environment was to increase the value of HOSTNAME_CACHE_TIMEOUT to 86400 (24hrs) from the default value of (30mins). This increase in the timeout would help opcmsga to cache the resolved hostnames for longer duration and eventually helping to resolve them quickly rather than to query DNS server every 30min that could take time and lead to slower processing and contributing to delay in sending the events. This change would have helped opcmsga to process the events faster thereby regulating the size of queue files.

Micro Focus Software Support
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of Micro Focus.
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

 

Labels (1)

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2021-03-22 09:54
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.