<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Over 32.000 connections from NetXMS server to DB in CLOSE_WAIT status]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">NetXMS was not monitored on development system for several days. During that time oracle DB password has expired:<br />
[04-Dec-2014 09:31:17.278] [ERROR] Unable to establish connection with database (ORA-28002: the password will expire within 5 days)<br />
This issue was not noticed, but it was not the problem itself.</p>
<p dir="auto">We had a problem with backups of development system as Networker client was failing.<br />
After analysis I found over 32.000 connections from netxmsd towards DB in CLOSE_WAIT status:</p>
<p dir="auto">153.98.100.55.36421  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.35894  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.33549  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.65128  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.60114  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.53602  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.57421  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT<br />
153.98.100.55.33275  153.98.100.57.1525   49152      0 49152      0 CLOSE_WAIT</p>
<p dir="auto">NetXMS was opening new connection until Solaris 10 reached the limit of open connections.<br />
As a consequence this caused issues with other applications.</p>
<p dir="auto">I think that some internal limits of connections within NetXMS should be defined to avoid serious problems when DB is not available or not accessible for some time.</p>
<p dir="auto">Best regards,<br />
Marcin</p>
]]></description><link>https://forum.netxms.org/topic/3498/over-32.000-connections-from-netxms-server-to-db-in-close_wait-status</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 22:33:33 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/3498.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Dec 2014 09:02:53 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Over 32.000 connections from NetXMS server to DB in CLOSE_WAIT status on Thu, 04 Dec 2014 13:09:07 GMT]]></title><description><![CDATA[<p dir="auto">On NetXMS server side.<br />
Stopping NetXMS server service took around 15 minutes.<br />
During that time amount of connections in CLOSE_WAIT state was slowly decreasing.</p>
]]></description><link>https://forum.netxms.org/post/15464</link><guid isPermaLink="true">https://forum.netxms.org/post/15464</guid><dc:creator><![CDATA[Marcin]]></dc:creator><pubDate>Thu, 04 Dec 2014 13:09:07 GMT</pubDate></item><item><title><![CDATA[Reply to Over 32.000 connections from NetXMS server to DB in CLOSE_WAIT status on Thu, 04 Dec 2014 11:29:03 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">it's quite strange because NetXMS server closes Oracle session if it cannot login and opens new one. Theoretically closing session in Oracle client should close underlying socket as well. Were those connections on DB server side or on NetXMS server side? I'll also check if we close Oracle session correctly.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/15462</link><guid isPermaLink="true">https://forum.netxms.org/post/15462</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 04 Dec 2014 11:29:03 GMT</pubDate></item></channel></rss>