-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Meridian-2019.1.0, 25.1.0
-
Fix Version/s: Meridian-2019.1.2, 25.1.2
-
Component/s: Polling / Monitors / Outages
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Sprint:Horizon 2019 - November 27th
We add JCIFS Monitoring at 21 Nov 3:45pm and do a OpenNMS restart.
We see a continously increase of java threads since this restart.
At Nov 23 1:16pm OpenNMS crashed with "java.lang.OutOfMemoryError" and we get a heap dump.
Only two servers become the CIFS pollers with different services:
<service name="CIFS-Customer-Software" interval="30000" user-defined="true" status="off">
<parameter key="retry" value="1" />
<parameter key="timeout" value="3000" />
<parameter key="domain" value="DOMAIN" />
<parameter key="username" value="opennms-user" />
<parameter key="password" value="password" />
<parameter key="path" value="/customer-software/" />
<parameter key="mode" value="path_exist" />
</service>
<service name="CIFS-Xchange" interval="30000" user-defined="true" status="off">
<parameter key="retry" value="1" />
<parameter key="timeout" value="3000" />
<parameter key="domain" value="DOMAIN" />
<parameter key="username" value="opennms-user" />
<parameter key="password" value="password" />
<parameter key="path" value="/xchange/" />
<parameter key="mode" value="path_exist" />
</service>
<monitor service="CIFS-Customer-Software" class-name="org.opennms.netmgt.poller.monitors.JCifsMonitor" />
<monitor service="CIFS-Xchange" class-name="org.opennms.netmgt.poller.monitors.JCifsMonitor" />
