One of our users is having a problem connecing to our project.
He is getting the following error:
“Error Launching Application: SocketTimeoutException: connect timed out”
I don’t think this is a firewall issue, as he can bring up the web page on port 8088.
Any ideas what could be wrong here?
Its hard to say. If you can, go to the Java icon in your Windows Control Panel. (I’m assuming its Windows until told otherwise).
Go to the Advanced tab, and under “Java Console” select “Show Console”
Then launch again and report back with the contents of what appears in the console.
Thanks. It is Windows. We will try this out tomorrow and post the results.
Also, what version are you running?
Finally managed to get the results.
This is our version information:
Ignition Platform 7.1.6 (b5739)
SQL Bridge Module 5.1.6 (b5739) Activated
Vision Module 4.1.6 (b5739) Activated
Reporting Module 1.2.6 (b5739) Activated
This is the Java information
Java Web Start 1.6.0_23
Using JRE version 1.6.0_23-b05 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\gerryf
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
0-5: set trace level to <n>
----------------------------------------------------
Starting Bootstrap Loader v2.0
Connect Step [attempt 1] connecting to: http://scadaserver01:8088/main...
Connect attempt 0 for address http://scadaserver01:8088/main failed.
java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.downloadManifest(ConnectStep.java:99)
at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.downloadManifest(ConnectStep.java:72)
at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.run(ConnectStep.java:46)
at com.inductiveautomation.ignition.client.launch.AbstractStepRunner.run(AbstractStepRunner.java:31)
at java.lang.Thread.run(Unknown Source)
java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.downloadManifest(ConnectStep.java:99)
at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.downloadManifest(ConnectStep.java:72)
at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.run(ConnectStep.java:46)
at com.inductiveautomation.ignition.client.launch.AbstractStepRunner.run(AbstractStepRunner.java:31)
at java.lang.Thread.run(Unknown Source)Sounds like either a networking issue or a Java networking issue.
From that machine, can you ping scadaserver01?
Go into the Java Control Panel and click on the “Network Settings…” button.
What is it set to? If you’re able to ping from the machine, try setting it to Direct Connection.
I have had that trouble on mine also.
I deleted “%USER_DIR%/.ignition” directory and then ran and all worked. I will repost if it returns.
This is for anyone else that may be having this issue also.
That did not fix it for me permanent. It will work for a bit then do it again when you click on the link placed on desktop. Delete directory and all will be good again for a bit. I called and talked with Bobby in Tech-Support and he seen the issue. He was going to try and reproduce it there. He may respond here if he has anymore info.
I had to fix a couple boxes today myself. Still looking for a fix here.
I am still seeing this problem intermittently on client machines. There doesn’t seem to be a pattern - sometimes I can connect 6 times in a row, and then it stops working. Other times, it just won’t connect at all.
One point of information is the following - the server is accessible both on the customer’s internal network and externally via the internet.
When I access it using the external IP, I never have this problem.
The customer’s users are the ones seeing this problem when they access the server using the server name (“SCADAServer01”) on the internal network. They can’t use the external IP address due to the way the network is configured.
Don’t know if this is relevant but it might add something to the investigation.
Over the weekend I updated our Ignition to 7.2.3. I have not had a call with this problem yet this week. I see there is also a Java Ver 24 out now also. Just an FYI
There is certainly something going on here with the client cache mixing up the address of the Gateway, but I haven’t narrowed it down. Can you guys all go check whether or not “Autodetect HTTP” is checked or not under redundancy settings please?
For my own future reference, I think this post is also related.
Carl,
Yes auto detect HTTP is checked.
I was in the Denver training reason for the late delay.
I did find something interesting on the boxes that were doing this. If they error and won’t load if I go into the java control panel and under debugging turn on both Trace and logging it will fire the next time you click on it… This is weird
I think it is some sort of race condition going on and turning the logging on lets the right one win.
I will keep you posted as I find more.
Hi
I recently did the upgrade from 7.1.8 to 7.2.4 and this is what happened to some of the clients
Error when trying to use existing desktop shortcut to launch application “unable to launch application” I think was the error. Similar to when the server is not running. I tried clearing the java cache and fresh install but the shortcuts would not be removed. Re launch project and it would open but on next launch the gateway could not be found error 503 I think. The only way I could get it to work was to do a Java update on these clients and then the new shortcuts would work. It was only happening on a few clients that would have similar OS and java updates as other clients.
On a separate point about 7.2.4 some labels that would have had the cursor set to hand have returned to the default arrow cursor after upgrade
Thanks
Aidan
Hi
This is a follow on from my previous post. Today I had more issues with clients not been able to open shortcut on desktop. This had been working yesterday. The upgrade was done at weekend. The only way I could solve the problem was to upgrade the java version to 6.24 from 6.19. I took a screen shot of error and also copied the java console information. I will update if I see more issues.
Regards
Aidan
Console Launch Error.txt (1.99 KB)
I started having this issue also after upgrading from 7.1 to 7.2.4. I can launch from the gateway homepage with no issues, but if I try from the desktop links it throws up this error.
it also does it when I try and launch from inside of the designer, full screen.
It sounds like the desktop link must have the wrong address cached. Try clearing the Java cache (Control Panel>Java>General>Temporary Internet Files- Settings>Delete), which should remove the shortcut, and then launch from the gateway to re-create it. Then see if you still have a problem.
Regards,
I have been error free for 3 days now. Here is what I did, in case it may help.
In the Redundancy I unselected the “Autodetect HTTP Address” and added the server and port info into the “HTTP Addreses” space right below. Then cleared the Java all out on the clients and it has worked. I sure hope I did not just Jinx myself…
