Android console version is broken or didn't recompile properly or whatever reason it is.
Filename suggests it's 2.2.1. But after launch program says 2.1.2 and didn't connect to the server due to incompatible version of exchange protocol.
Thanks for your work. You do a great job. It makes our lives much easier 
P.S. Oh, and Android AppManager says it's 2.1.0
@victor said in XMPP delays.:
Still seems that problem is with XMPP library. XMPP sender action waits on mutex to acquire XMPP handle. On what operating system your server is running? If it is Linux, can you attach gdb to server process after
Quite unlikely. I did a quick review of the code. Mutex (which actually is a critical section) object is never passed to the XMPP library.
Remove the MutexLock/MutexUnlock in SendXMPPMessage since it looks single-threaded anyway and we'll see if it helps. Not very many of us, XMPP users 
I have the same problem.
Server 2008 R2.
Event queue is frozen for almost 10 minutes.
XMPP user subscribed and server answers to console command instantly even during "freeze".
Log fragments:
[27-Jan-2015 11:46:04.231] [DEBUG] Event 402 match EPP rule 15
[27-Jan-2015 11:46:04.231] [DEBUG] AlarmManager: adding new active alarm, current alarm count 14
[27-Jan-2015 11:46:04.231] [DEBUG] *actions* Executing action 2 (Send XMPP message to ***) of type XMPP MESSAGE
[27-Jan-2015 11:46:04.231] [DEBUG] *actions* Sending XMPP message to v***: "Test: Threshold reached for data collection item "Toner left" (Parameter: Dummy; Threshold value: 10; Actual value: 7.000000)"
...
[27-Jan-2015 11:47:21.856] [DEBUG] XMPP: RECV: <message id="***" to="e***" type="chat" from="v***"><body>Show wat</body><thread>**</thread><request xmlns="urn:xmpp:receipts"/></message>
[27-Jan-2015 11:47:21.856] [DEBUG] XMPP: Incoming message from v***: Show wat
[27-Jan-2015 11:47:21.856] [DEBUG] User admin authenticated for XMPP commands
[27-Jan-2015 11:47:21.856] [DEBUG] XMPP: SENT: <message to="v***" type="chat"><body>Thread Interval Status
----------------------------------------------------------------------------
Item Poller 20 Running
Syncer Thread 130 Running
Poll Manager 60 Running
</body></message>
...
[27-Jan-2015 11:54:28.869] [DEBUG] XMPP: RECV: <message id="***" to="e***" type="chat" from="v***"><body>Show que</body><thread>***</thread><request xmlns="urn:xmpp:receipts"/></message>
[27-Jan-2015 11:54:28.869] [DEBUG] XMPP: Incoming message from v***: Show que
[27-Jan-2015 11:54:28.869] [DEBUG] User admin authenticated for XMPP commands
[27-Jan-2015 11:54:28.869] [DEBUG] XMPP: SENT: <message to="v***" type="chat"><body>Condition poller : 0
Configuration poller : 0
Topology poller : 0
Data collector : 0
DCI cache loader : 0
Database writer : 1
Database writer (IData) : 0
Database writer (raw DCI values) : 0
Event processor : 5
Network discovery poller : 0
Node poller : 0
Routing table poller : 0
Status poller : 0
Syslog processing : 0
Syslog writer : 0
</body></message>
...
[27-Jan-2015 11:54:33.783] [DEBUG] XMPP: SENT: <message to="v***" type="chat"><body>Test: Threshold reached for data collection item "Toner left" (Parameter: Dummy; Threshold value: 10; Actual value: 7.000000)</body></message>
[27-Jan-2015 11:54:33.783] [DEBUG] Event 402 with code 17 passed event processing policy
[27-Jan-2015 11:54:33.783] [DEBUG] CorrelateEvent: event SYS_NODE_WARNING id 403 source Kyocera TA 181 [146]
[27-Jan-2015 11:54:33.783] [DEBUG] Database Connection Pool: handle 0000000000FBA400 acquired (call from .\evproc.cpp:103)
[27-Jan-2015 11:54:33.783] [DEBUG] CorrelateEvent: finished, rootId=0
@alk said in NetXMS 2.0-M1 released:
- stop server
- copy existing netxmsd.conf into netxmsd.conf.old
- create user and database in new DBMS
- edit netxmsd.conf β change DBDriver and all other DB* parameters
- run "nxdbmgr migrate /etc/netxmsd.conf.old"
Well I used another step "3.5 - Initialize database", because migrate didn't work on empty database (said something about not detecting something (the same as check command on empty database), but anyway it didn't work out, since migration command breaks on syncronization of the first table "config" or something like that with error of SQL statement preparation.
So since it was clean installation and I didn't set up much DCIs so I just used new initialized MySQL database without migration.
If you need/want this SQLite database for some additional testing I can send it to you.
@alk said in NetXMS 2.0-M1 released:
SQLite never was intended for use in production environment, and we will probably remove support in future altogether.
Well, that's the answer Ok, I'll use other DBMS.
@tomaskir said in NetXMS 2.0-M1 released:
DCI tables do not work with SQLite.
This is a known issue.
As a workaround for now, you can use a different DB.
How terrible I didn't know about that.
But as a guy who do some programming, I'm aware of the fact, that if there is some issue that prevents using of the product you should provide some bugfix rather than "it's a known issue" even for free and open source product
And since I have this particular bug isolated I can provide some (or even all in my case) data to fix it.
This one is much more serious:
I can't create or deleteΒ DCI.
History:
I tried to play with SNMP's table DCI, but wasn't successful. Later we'll get back to that
But I created one for the node (printer). And since that I can't create or delete DCI. Looks like after "sync" period something breaks, sync thread stops answering to watchdog and I can't connect with console.
So, my opinion - something is wrong in sync thread.
Error is 100% reproducible, so I can supply you with any kind of data.
DB is SQLite, Windows server 2008 R2, but since data is accumulated correctly I do believe something is wrong in sync thread (or with SQLite).
Funny bug:
configuration parameter in nxagent ListenAddress actually read backwards.
So instead of 192.168.1.2 you should write 2.1.168.192