We may need to rely on the ORB experts for more suggestions.
One question: Can you tell whether the client-side code is stalled,
waiting? Or it is looping and using up CPU?
If you could capture a thread dump that could be helpful. I realize you
have already tracked the stall to the is_a method but if there is a deadlock
the thread dump should help reveal it.
Also, if you have the time and energy, you could try this:
1. On your server, run the package-appclient command. It creates a zip file
which you can copy to the remote system and then expand there. It will
contain all the files necessary to launch any client using the appclient
command.
2. Next, get the bits for your client to the remote system so you can run it
manually there. On your server system, run
asadmin get-client-stubs -appname name-of-your-app localdir
This will create a subdirectory structure at localdir. Zip this directory
and all its children, copy it to the remote system, and unzip it into any
directory there. Then you can launch this client using
appclient -jar localDirOnRemoteSystem/appNameClient.jar
where, of course, the directory name and the name of the client JAR will
depend on your environment.
If the same behavior happens when you launch the client this way, then
debugging using the appclient launch will be easier than doing so with the
Java Web Start launch.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/882266