Application Launcher does not display apps
Sun ONE UDS 5.0.3 Application Launcher fails to load itself on users' PCs, with the list of applications available to our model node.
This problem will arise apparently spontaneously and simultaneously on all PCs (~50 at a time) of that model node, after a period of proper functioning.
It will clear up just as mysteriously on all nodes at once after a period of the applications' unavailability.
The problem has only showed up in the past 3 weeks or so and has been increasing in frequency and duration.
In an attempt to force a PC to download new applications, the following workarounds have been attempted:
1. Delete the node's configuration repository ($FORTE_ROOT\sysdata\envrepos\nodename.bt?).
2. Delete an application from the node (e.g., $FORTE_ROOT\userapp\logonwin\cl0\logonw0.bt?)
3. Uninstall an application, reload its distribution, and reinstall it.
None of the above efforts resulted in anything being downloaded, and the Application Launcher window remained empty. After a few more attempts to bring it up, it suddenly recovered on everyone's PCs.
This is happening in our 24/7 production environment, and it's a serious problem; people can not do their work.
There are no error messages; UDS does not complain; it acts as if it's doing what is expected; the applications are not downloaded, and nobody can start them.
Just as I was typing this, it started working again. I suggested that the users log in and not log out, as it will likely stop working shortly.
Can anyone explain this, or at least tell me how to make it work consistently?
KenG.
[1730 byte] By [
keng_mmhm] at [2007-11-25 22:31:27]
# 2
Thanks for your response, Anton.
A redesign at this point is not really a viable option.
Deleting the client's config repos gets the node a new config repos, and the Launch Server output indicates that it's going to go get apps, but those messages just fly by; nothing actually gets downloaded.
A Sun rep thinks this this error is relevant:
--
SYSTEM ERROR: System Error: Too many open
files, opening
'/usr/forteprod/install/scripts/pubaplts.inf' with mode 'r'
Class: qqos_FileResourceException
Error #: [101, 184]
Detected at: qqos_File::Open at 4
Error Time: Thu Apr 6 10:32:34
Distributed method called: qqsm_EnvAgentProxy.ExecuteCommand!53 (object
name site/systemmonitor/environmentmgr) from partition
"LauncherGUI_cl0_Client", (partitionId =
09F11630-8FFA-11D9-9E41-5F5B761FAA77:0x1426b:0x2, taskId =
[09F11630-8FFA-11D9-9E41-5F5B761FAA77:0x1426b.5]) in application
"FTLaunch_cl0", pid 2432 on node CON35692 in environment ProdEnv
Exception occurred (remotely) on partition "Node Manager", (partitionId =
09F11630-8FFA-11D9-9E41-5F5B761FAA77:0x14089, taskId =
[09F11630-8FFA-11D9-9E41-5F5B761FAA77:0x1426b:0x2.17]) in application
"System Manager", pid 1553 on node sunProdCent in environment ProdEnv.
--
# 4
> If you get that error when the app download is
> supposed to happen then I would agree. It looks like
> an o/s issue. What o/s are you using for your
> clients? And where are you getting this error? If its
> on the server, there may be a limit there (Unix have
> user settable limits on the number of files open),
> because in order to download the app the Env Mgr must
> open the file on the server. Also check your memory
> on the server (Env/Node mgr) and check the log files
> for out of memory errors - how big is the client part?
Clients are XP + a few Win2Ks.
No "out of memory" errors in the logs.
The "Too many open files" errors are raised on the central server node (Solaris). Max files is set to 1024, but pfiles indicates that the number of open files hasn't gotten above 258 today. The number varies, but hovers within a very few over 256.
Is there a Forte environment variable for this sort of thing?
