Check the proxy settings on the slow machine. That user might not have correct proxy settings, and a lot of extra network traffic/timeouts could be occurring?
Check the proxy settings on the slow machine. That user might not have correct proxy settings, and a lot of extra network traffic/timeouts could be occurring? We've had that issue with webstart before, downloading a jar from a local server was round tripping through the proxy to the other coast and back.
If you use something like Notepad to view the contents of the . Jnlp file, you'll see all the information it uses to run. Look for main-class (on the application-desc node).
This is the java class containing the main method. For more information you should refer to java.sun.com/javase/technologies/desktop... for the specification of jnlp. From here you could create a batch file with a proper classpath for running the application.
But, you are breaking away any of the advantages of using the jnlp method. So you'll need to keep that in mind. There is also a section 'resources' in the jnlp file which will show you jar files it requires and other webstart jnlp's.
You should be doing some checks outside of the actual application though. If these are similar machines, then it's very likely something is different. Defrag needed?
Network? Maybe the java-vm itself is taking too long to load.
Check the network settings of the user. It is my experience that minute long delays often is caused by DNS misconfiguration, bad routing tables (DNS must time out when no positive response is received), or simply an incorrect lmhosts file.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.