<![CDATA[Request timed out]]>Hi,

Since upgrading to v1.2.11 I've been getting more "Request timed out" errors in the management console when doing various changes. (applying templates, creating a container, moving nodes, ...)

It doesn't always happen, andsometimes the operation goes through anyway, other times I have to do it again or it only succeeds partially (eg 3 out of 20 nodes are in the template, the others aren't)

Has something changed that could be causing resource locks or delays?

Thanks!

Kind regards,
bdefloo

]]>https://forum.netxms.org/topic/2905/request-timed-outRSS for NodeFri, 13 Nov 2026 07:25:02 GMTWed, 05 Feb 2014 10:50:14 GMT60<![CDATA[Reply to Request timed out on Fri, 21 Feb 2014 20:07:18 GMT]]>Yes, it is available (you can get current sources by cloning git repository http://git.netxms.org/public/netxms.git and switching to branch "develop"). But it is client side change, and building console may be non-trivial task (you will need Maven for building client library and Eclispe 3.7 with right set of plugins listed in src/java/eclipse_addons.txt for building console).

Best regards,
Victor

]]>https://forum.netxms.org/post/12932https://forum.netxms.org/post/12932Fri, 21 Feb 2014 20:07:18 GMT<![CDATA[Reply to Request timed out on Fri, 21 Feb 2014 19:25:30 GMT]]>Great thanks for the quick reply.

Is the fix available in the source snapshot by chance?

]]>https://forum.netxms.org/post/12930https://forum.netxms.org/post/12930Fri, 21 Feb 2014 19:25:30 GMT<![CDATA[Reply to Request timed out on Fri, 21 Feb 2014 19:15:27 GMT]]>Hi!

There is hard-coded read timeout on server side, which is used to detect dead sessions. Normally it should not happen, because client sends keep-alive messages once per minute. However, there is a bug in 1.2.12 which prevents client from sending these messages, and so inactive session terminated after 15 minutes. I already fix this bug, and after 1.2.13 release problem should be gone.

Best regards,
Victor

]]>https://forum.netxms.org/post/12929https://forum.netxms.org/post/12929Fri, 21 Feb 2014 19:15:27 GMT<![CDATA[Reply to Request timed out on Fri, 21 Feb 2014 16:53:45 GMT]]>To add we are seeing a similar issue.. we are running 1.2.12 compiled for Linux using ODBC. The database is MS SQL 2012. With the past three releases we did not experience the management console timing out, but did see intermittent issues with the alarm browser and syncing the alarms.

With the new release 1.2.12, we are seeing the client session establish and then 15 minutes later the session time out.

Here is what the log is showing....
[21-Feb-2014 09:20:47.600] [DEBUG] [CLSN-0] Server time zone: CST-06CDT
[21-Feb-2014 09:20:48.176] [DEBUG] [CLSN-0] User xxxxxxxxxx@xx.xx.xx.xx authenticated
[21-Feb-2014 09:20:51.350] [DEBUG] [CLSN-0] listLibraryImages: category=*ANY*
........
[21-Feb-2014 09:35:53.465] [DEBUG] [CLSN-0] RecvNXCPMessageEx: receive timeout
[21-Feb-2014 09:35:53.465] [DEBUG] *Locks* All locks for session 0 removed
[21-Feb-2014 09:35:53.465] [DEBUG] [CLSN-0] Session closed

Has a new feature been added to time out any client sessions after 15 minutes or based on a configuraiton that I need to review?

Appreciate the help

]]>https://forum.netxms.org/post/12928https://forum.netxms.org/post/12928Fri, 21 Feb 2014 16:53:45 GMT<![CDATA[Reply to Request timed out on Wed, 19 Feb 2014 20:42:23 GMT]]>After upgrading to 1.2.12 we've been experiencing the issue below in management console and web portal.

"Cannot synchronize alarm list: Broken pipe
Broken pipe"

It generates the event "SYS_THREAD_HANG", Thread "Syncer Thread" is not responding

Restarting the client or refreshing the web browser clears the issue temporarily.

The previous "Request timed out" issue from 1.2.11 seems to be resolved.

]]>https://forum.netxms.org/post/12880https://forum.netxms.org/post/12880Wed, 19 Feb 2014 20:42:23 GMT<![CDATA[Reply to Request timed out on Wed, 19 Feb 2014 08:55:29 GMT]]>had this problem with 1.2.11 x64 2k8 srv and pgsql.
upgraded just now to 1.2.12, will check...

]]>https://forum.netxms.org/post/12853https://forum.netxms.org/post/12853Wed, 19 Feb 2014 08:55:29 GMT<![CDATA[Reply to Request timed out on Tue, 18 Feb 2014 11:12:52 GMT]]>hmm.. looks like it's solved  😄
At least for me it is.
So far no more requests timed out anymore.

]]>https://forum.netxms.org/post/12832https://forum.netxms.org/post/12832Tue, 18 Feb 2014 11:12:52 GMT<![CDATA[Reply to Request timed out on Mon, 17 Feb 2014 13:13:30 GMT]]>Please try version 1.2.12. We have fixed lot of bugs here, hopefully timeout problem will be gone.

Best regards,
Victor

]]>https://forum.netxms.org/post/12806https://forum.netxms.org/post/12806Mon, 17 Feb 2014 13:13:30 GMT<![CDATA[Reply to Request timed out on Wed, 12 Feb 2014 14:07:08 GMT]]>connection with the client gets completely messed up here.. I have to kill my client and reconnect a freshly started one to continue working.
Happens a lot when changing settings in Business Services as well.

]]>https://forum.netxms.org/post/12772https://forum.netxms.org/post/12772Wed, 12 Feb 2014 14:07:08 GMT<![CDATA[Reply to Request timed out on Wed, 12 Feb 2014 12:18:25 GMT]]>Same issues as everything is describing. Whenever we try to delete more than a handful of alarms we get the error message popup but after a refresh the alarms go away. Very annoying but still functional.

Client Version: 1.2.11
Microsoft SQL Database

]]>https://forum.netxms.org/post/12769https://forum.netxms.org/post/12769Wed, 12 Feb 2014 12:18:25 GMT<![CDATA[Reply to Request timed out on Thu, 06 Feb 2014 07:05:24 GMT]]>Same here. "Cannot terminate alarm: Request timed out", lots.

CentOS, mysql, NetXMS 2.11.

Regards,
  Peter.

]]>https://forum.netxms.org/post/12706https://forum.netxms.org/post/12706Thu, 06 Feb 2014 07:05:24 GMT<![CDATA[Reply to Request timed out on Thu, 06 Feb 2014 21:55:37 GMT]]>I noticed same problem on Win XP and SQLite database.
Usually on dashboard's charts.
Status line shows small progress bar and message 'Get DCI value for history graph' if I remember correctly.

Regards, Grzegorz.

EDIT: Forgot to mention, NetXMS ver. 1.2.11 and corrected message text.

]]>https://forum.netxms.org/post/12703https://forum.netxms.org/post/12703Thu, 06 Feb 2014 21:55:37 GMT<![CDATA[Reply to Request timed out on Wed, 05 Feb 2014 16:31:30 GMT]]>Same here on Windows 2003 R2 x64 with MSSQL 2008 R2

Best regards,
Marco

]]>https://forum.netxms.org/post/12700https://forum.netxms.org/post/12700Wed, 05 Feb 2014 16:31:30 GMT<![CDATA[Reply to Request timed out on Wed, 05 Feb 2014 16:08:31 GMT]]>Hi,

I have NetXMS x64 and MS SQL 2012 Express x64 on a Windows 2008 R2 server.

]]>https://forum.netxms.org/post/12699https://forum.netxms.org/post/12699Wed, 05 Feb 2014 16:08:31 GMT<![CDATA[Reply to Request timed out on Wed, 05 Feb 2014 15:53:22 GMT]]>What database you are using?

Best regards,
Victor

]]>https://forum.netxms.org/post/12698https://forum.netxms.org/post/12698Wed, 05 Feb 2014 15:53:22 GMT<![CDATA[Reply to Request timed out on Wed, 05 Feb 2014 15:32:26 GMT]]>same here.. it queues the request and finally it times out..

]]>https://forum.netxms.org/post/12696https://forum.netxms.org/post/12696Wed, 05 Feb 2014 15:32:26 GMT