Beta 7.2: Error Launching application

After successful Windowed Pubslihed launched the first time: close and subsequence launch thru windowed staging or published, got error: launching application: SocketTimeoutException: connect timeout
Launch Full Screen, or Applet is OK.

Java Web Start 1.6.0_21
Using JRE version 1.6.0_21-b07 Java HotSpot™ Client VM
User home directory = C:\Documents and Settings\TacHuynh

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

Starting Bootstrap Loader v2.0
Connect Step [attempt 1] connecting to: 192.168.3.165:8088/main….
Connect attempt 0 for address 192.168.3.165: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.(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:32)
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.(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:32)
at java.lang.Thread.run(Unknown Source)

Hmm. Basic question, but is “http://192.168.3.165:8088” the correct address for your server?

yes, that is the correct ip for the server

The title said Beta 7.2.

Is this consistent across multiple client machines? Can they all launch a single time and then not launch due to connect timeouts?

What happens if you delete your [tt]%USER_DIR%/.ignition[/tt] folder and try launching again?

I’m having the same problem…Deleted the .ignition folder and it starts working again. It fails to connect the very next launch after folder deletion. It is occurring on multiple client machines.

If you can reproduce this reliably it would be helpful if you could call in and have us take a look at your system over GoToMeeting.