# (SocketTimeoutException:Read Timed out ) after 7.3.1 upgrade **URL:** \ **Category:** Ignition\ **Created:** [November 17, 2011, 5:50pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618 "2011-11-17T17:50:04Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![ecujak](https://avatars.discourse-cdn.com/v4/letter/e/839c29/32.png) [@ecujak](https://forum.inductiveautomation.com/u/ecujak)\ **Post date:** [December 7, 2011, 6:32pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/21 "2011-12-07T18:32:51Z")
I manually copied the file above that was downloaded using my browser to the following folder: C:\Documents and Settings\user.ignition\cache\gwMyServer\_8088\_8043\_main\C0 I then executed the designer jlnp file and I am now able to open the designer. There has to be a better way. What happens when we have large projects? Will we need to download jars manually on all clients? ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [December 7, 2011, 7:40pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/22 "2011-12-07T19:40:07Z")
It’s not the size of the project in this case, it’s this one particular module that gets loaded in the Designer that is large (~20mb). Also, I still think that it’s something particular to your setup, since nobody else is having this problem. I’ve built a special version of the bootstrap launcher (that’s what does the downloading) to give us a bit more information about the download. 1. Shut down your Gateway. 2. Backup the files under [tt]%IGNITION\_INSTALL\_DIR%/lib/core/launch[/tt] 3. I’ve attached a zip file. Unpack it’s contents into that directory. 4. Start the Gateway back up. 5. Clear the Java cache on the client machine that exhibits the issue. [tt]Control Panel \> Java \> “Settings…” \> “Delete Files…”[/tt] 6. Clear the Ignition client cache on the same machine. It’s stored under [tt]%USER\_DIR%/.ignition)[/tt] Try again and post the client launch logs. [dist.zip](https://us1.discourse-cdn.com/inductiveautomation/original/1X/8c658942341954c54c343e197d8cbed9c0021edc.zip) (321 KB) ---
**Author:** ![ecujak](https://avatars.discourse-cdn.com/v4/letter/e/839c29/32.png) [@ecujak](https://forum.inductiveautomation.com/u/ecujak)\ **Post date:** [December 8, 2011, 4:58pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/23 "2011-12-08T16:58:08Z")
It looks like the download is just timing out. I don’t know why it will finish using a browser and not through your process. Can we extend the timeout period? [JavaConsoleLog.20111208.txt](https://us1.discourse-cdn.com/inductiveautomation/original/1X/1b84ca28304abb2160de75c617bacd65b925f083.txt) (20.8 KB) ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [December 8, 2011, 5:50pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/24 "2011-12-08T17:50:05Z")
Yes, I understand that it’s timing out. And we could increase the timeout. What I’m confused about is why your download speed between this client and the gateway is so slow. You’re averaging 11.5 kb/sec transfer. That’s really slow. That’s like dial-up modem slow. (marginally faster, but same order of magnitude). At that speed, it would take you about 20 minutes to download that jar file that you’re getting stuck on. Whats the network situation like between this client and the gateway? Something is very wrong. How long did it take to download that jar in the browser? ---
**Author:** ![ecujak](https://avatars.discourse-cdn.com/v4/letter/e/839c29/32.png) [@ecujak](https://forum.inductiveautomation.com/u/ecujak)\ **Post date:** [December 8, 2011, 6:25pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/25 "2011-12-08T18:25:51Z")
it takes less than a minute to download using the browser. ---
**Author:** ![ecujak](https://avatars.discourse-cdn.com/v4/letter/e/839c29/32.png) [@ecujak](https://forum.inductiveautomation.com/u/ecujak)\ **Post date:** [December 8, 2011, 6:46pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/26 "2011-12-08T18:46:29Z")
This was a configuration issue on the Server. Someone had set the NIC at 100/Half duplex… I am sorry to take your time. Thank you for your help. It now takes 15 seconds to download everything, with cache cleared. ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [December 8, 2011, 6:53pm UTC](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618/27 "2011-12-08T18:53:38Z")
[quote=“ecujak”]This was a configuration issue on the Server. Someone had set the NIC at 100/Half duplex… I am sorry to take your time. Thank you for your help.[/quote]Huh, that’s a new one. Glad you got it figured out. [quote=“ecujak”]It now takes 15 seconds to download everything, with cache cleared.[/quote]That’s more like it! [Previous page](https://forum.inductiveautomation.com/t/sockettimeoutexception-read-timed-out-after-7-3-1-upgrade/3618.md?page=1)