Hello everybody,
Since yesterday we’ve been encountering an issue on the Axes subsystem/PGM-AXES5250 job with the error message below.
Many users can’t connect to the Axes version of our TMS (transport management system)
It seems to be relating to the Virtual Terminal Management which seems to be limited to 1000 simultaneous sessions.
Has anyone any idea on how to fix that issue ?
Maximum number of active virtual terminal reached
Moderator: jeanmichel
Maximum number of active virtual terminal reached
- Attachments
-
- errormsg.png (277.45 KiB) Viewed 4984 times
-
- Posts: 37
- Joined: 26 Jul 2017, 13:20
Re: Maximum number of active virtual terminal reached
Hi FrancK
Had a different, but similar, problem with a bank provider in Indonesia. I think they were running out of memory in the server job.
Their solution was to create multiple instances of aXes. This would require you to run the server jobs under different ports. You would identify a group of customers to use the new port.
The setup is different for W3 & JSM versions.
The Indonesians created a copy of the TS folders for each of their 3 instances, but I think it would be possible to get it to run using a single set of source folders.
Tim
Had a different, but similar, problem with a bank provider in Indonesia. I think they were running out of memory in the server job.
Their solution was to create multiple instances of aXes. This would require you to run the server jobs under different ports. You would identify a group of customers to use the new port.
The setup is different for W3 & JSM versions.
The Indonesians created a copy of the TS folders for each of their 3 instances, but I think it would be possible to get it to run using a single set of source folders.
Tim
Re: Maximum number of active virtual terminal reached
Hello Tim,
Thank you for that answer.
While waiting for a response from Lansa support and/or IBM on the origin of the Open Virtual Terminal Path (QTVOPNVT) API error message, we are in the process of implementing this solution.
But for us it must remain a temporary solution because it requires double or even triple maintenance.
So if anyone has another idea he's welcome!
Here's the IBM API documentation : https://www.audentia-gestion.fr/IBM/PDF/vt.pdf
Thank you for that answer.
While waiting for a response from Lansa support and/or IBM on the origin of the Open Virtual Terminal Path (QTVOPNVT) API error message, we are in the process of implementing this solution.
But for us it must remain a temporary solution because it requires double or even triple maintenance.
So if anyone has another idea he's welcome!
Here's the IBM API documentation : https://www.audentia-gestion.fr/IBM/PDF/vt.pdf