Steps to reproduce:
- Run 4 or more concurrent Zabbix clients (same user id/ password) from different forked processes
- When one of them finishes before the other, session is invalidated on server side and causes an exception on the other clients
To get a new session:
To close the session:
Each session should stay alive regardless if other sessions are active. To be clear, this is not a multi threaded application but 4 or more different scripts running different get_history methods.