Brian Madden Logo
Your independent source for application and desktop virtualization.
Marketplace

advertisement

Java Application hanging on MS Terminal Server, in the Terminal Services forum on BrianMadden.com

rated by 0 users
Not Answered This post has 0 verified answers | 0 Replies | 1 Follower

Not Ranked
Points 5
SJK posted on 11-19-2008 4:35 PM

We have a Java based app (Infor XA release 7.7, formerly known as MAPICS) that is running on JRE 1.4.2 (yeah I know, its unsupported now, this isn't optional.)

When running it on any XP, 2000 or 2003 server, it runs fine.

When running the app on any 2000, 2003, 2008 std or ent 32 bit or 64 bit (yes I tried them all) where Terminal Services is enabled, the javaw.exe application hangs when it hits the following limits

  • Working Memory set 312,000K (give or take 10,000 K)
  • VM Size 308,352K
  • Handles 1,186
  • Threads 33
  • User Objects 23
  • GDI Objects 40

That handles, threads, user and GDI objects remain constant while using the app.  Only the memory and VM Size grow.  When the memory exceeds 310,00K the application hangs and no longer responds to user interaction.  Again, on a non TS box, this issue does not arise.  But it happens on every version of Microsoft Terminal Server I can get my hands on, up to and including Server 2008 Enterprise, 64 bit.  Which makes some sense as it is a 32 bit app running in the 32 bit space.

If I open a second instance of the app within the same sign-in session it runs fine until it hits the same limits.  Its only the app that hangs, the user session is fine, all other sessions on the server run without issue.

I've tried the solutions in http://support.microsoft.com/kb/840342 Applications may not run correctly in a Terminal Services environment to no avail.  But that article doesn't seem to apply as the limits discussed are not the limits I am running into.

I've also played with the size of the interactive and non-interactive desktop heaps is determined by the registry setting under \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems.

Within the 'Windows' string value, there is a 'SharedSection' parameter that by default should read:

SharedSection=1024,3076,512

The 3076 interactive desktop heap size is the only number that seems to correlate with the issue I am having.  But on Server 2008 the values are 1024,20480,768 and I still have the same issue.

So what the heck is happening here?  Anyone know?  What is it about Terminal Server that is limiting this application that doesn't exist on every other non-TS enabled Windows platform?

 

 

All Replies

Page 1 of 1 (1 items) | RSS
Copyright © 1997-2008 The Brian Madden Company, LLC | Disclosures | Privacy | Terms of Use | Contact Info