I am using Sage Intergy which uses Progress database. I have contacted all those people that I know in N.Y. area and no one can help me. For some crazy reason, this software opens up a connection (per user) and never releases itself. having over 45 clients using Remote desktop, I sometimes see over 100 connections open and no one is on. I know this has nothing to do with the RDP but it seem that I am not the only person facing this issue. What I am trying to find out if these connections are for database or other internal APP. Has anyone faces such issue?
Connection problem with Sage Intergy
- Thread starter mig2000
- Start date
cj_brandt
Active Member
Intergy uses 2 connections for each user. 1 is a connection via a State Reset App Server and the other is a connection with the mpro client.
Intergy is used in several locations that use it with Citrix and I have not heard anyone complain about the issue you are having where users that log out are not disconnected from the database.
Have you contacted Sage for Technical Assistance ? They have a lot of experience helping customers with Citrix access issues.
Intergy is used in several locations that use it with Citrix and I have not heard anyone complain about the issue you are having where users that log out are not disconnected from the database.
Have you contacted Sage for Technical Assistance ? They have a lot of experience helping customers with Citrix access issues.
Here is the problem. Each Sage user opens up 2 connections. Thee are times that each users might login from multiple connection which kind of double the connection again. the biggest problem is when the users logoff, the connection does NOT get released. Sage is aware of it and have not done anything about it.
TomBascom
Curmudgeon
"logs off" <> "closes window" <> "turns off pc"
If they are really and truly logging off properly then I very strongly doubt that you have the problem that you describe.
So it is probably a case of mishandling the abnormal "log offs". Often this sort of thing can be addressed by adjusting the TCP Keepalive settings. The default is 2 hours -- which is far too long. Try 5 minutes. (Keepalive is not an idle session timer -- it is a broken connection detection mechanism.)
Oh, and remote desktop sessions by design do not terminate when the user closes their window or reboots their PC etc. Handling multiple open RDP sessions is yet another wrinkle.
If they are really and truly logging off properly then I very strongly doubt that you have the problem that you describe.
So it is probably a case of mishandling the abnormal "log offs". Often this sort of thing can be addressed by adjusting the TCP Keepalive settings. The default is 2 hours -- which is far too long. Try 5 minutes. (Keepalive is not an idle session timer -- it is a broken connection detection mechanism.)
Oh, and remote desktop sessions by design do not terminate when the user closes their window or reboots their PC etc. Handling multiple open RDP sessions is yet another wrinkle.
cj_brandt
Active Member
have you considered running a script that would log off idle sessions ?
You could use the VST's to determine if a user had no read activity in the db for the last XX minutes - if not then disconnect them. An easier approach would be disconnect sessions after the office closes - unless you use Intergy 24x7.
You could use the VST's to determine if a user had no read activity in the db for the last XX minutes - if not then disconnect them. An easier approach would be disconnect sessions after the office closes - unless you use Intergy 24x7.
Here is what the real issues are. Each user in Intergy opens 2 connections. Sage admits to that as well because that is how it is designed. All users use Citrix to access the system. If I have over 40 users to access the system, I sometime see over 90 connections as sometimes the same user logs in from another workstation. Most of the times (do not know the sequence) , these connections do not get released. All parameters are set for 5 min.
According to Sage, no monitoring or script can run on any servers because it can crash the database. I only have over 50 users and can not imagine what others do when running this system with larger users. I know most of Sage users are not more than 5 to 10 users.
Thanks
Tom
According to Sage, no monitoring or script can run on any servers because it can crash the database. I only have over 50 users and can not imagine what others do when running this system with larger users. I know most of Sage users are not more than 5 to 10 users.
Thanks
Tom
TomBascom
Curmudgeon
Actually, I don't see a description of an issue anywhere below.
Nobody disputes that.
I don't see it as a problem. As you say, that is how it is designed.
That seems quite typical as well.
In your original post you also mentioned Remote Desktop. How does that fit into this picture? Are they using Citrix to get to a RDP session?
This is the part that makes no sense.
What is it that you think users are doing that should result in something being "released"?
What do you look at that says to you that something wasn't released?
Why do you think that that is a problem? (As near as I can figure, you seem to think that that is a problem. Why? What harm is being done? What consequences are there from this lack of release?)
Presumably you are referring to the subset of "all" that makes up TCP keepalive? Or do you mean something else?
Somebody is badly misunderstanding or miscommunicating with somebody. That is simply untrue.
So far you haven't described an actual problem. You say that something (a connection of some sort) doesn't get released but don't say what that something is in any detail nor why it is a problem for it to not be released.
Yes, that is typical too. But it doesn't mean that larger systems do not exist or are not successful.