Disconnected published application still running app

[Luvsql]

We have constant issues where are users are disconnected from Citrix. When I go into the CMC, it shows as disconnected, but I cannot shadow it or connect to it to close the application properly. When a user is showing as disconnected, the appliction's exe is still running on that server. When these sessions are logged off, the application is forced to terminate and since the user could have been in the middle of a transaction, we are experiencing data corruption issues all the time in our sql database. Is there anything we can do to allow a disconnected session to be shadowed so that someone can ensure that transactions/data is properly saved before the app is reset?

We are using Metaframe xp 1.2 with FR2. We have 6 servers in one farm. Sometimes the user is reconnected, but most times it does not.

 

[Ogi]

Hi,

Recommendations are, move to FR3 as that reconnects a lot better than previous versions.

Also you'd be better off logging the user off rather than resetting the session.

Have you tried setting Shadowing that doesn't require the user to click yes, although this is a big security threat you could do this in the short term to see if the disconnected sessions are causing your issues!

Cheers,
Carl.

 

[Luvsql]

The problem is citrix is disconnecting the user, which closes the session, but not the application. If we attempt to shadow that session, the only options are log off or reset (either of which terminates the app instead of logging it off). We can shadow any user without their response needed.

If a user is in the middle of a transaction, citrix terminates the application and we lose data ie that transaction is sitting in limbo becuase the app is still running but the user or adminstrators cannot connect to it to fix it or log it off properly. Even if we logged it off, how can citrix save the transaction etc without the user being able to re-connect their session and enter that information?

 

[CitrixEngineer]

Do I understand that the basis of the issue is that the sessions are regularly disconnecting? What you are describing sounds like the way I would expect MetaFrame to work - except for the disconnections. If a user is disconnected, then I would think it desirable that the applications in the session were still running so the user can log back in and pick up from where they left off.

This sounds like poor network connections. Latency can be adjusted within the client - and at the server end; consult the Admin guides for more info.

As Ogi says, this feature has been greatly enhanced in FR3. If the session is terminated, then I would also expect the app to be terminated - and yes, any SQL Server connections will be lost and data will corrupt.

I hope I have understood the root cause of the issue correctly.