# Issues with slow launching of Clients

**URL:** <https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697>\
**Category:** General Discussion\
**Created:** [July 6, 2017, 12:57am UTC](https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697 "2017-07-06T00:57:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [July 6, 2017, 12:57am UTC](https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697/1 "2017-07-06T00:57:19Z")

</div>

Lately I am seeing issues with the time a client is launched and the time the actual project opens up. This occurs in version 7.7 , 7,8 applications. This occurs over multiple installs, so it is not an OS or PC resource issue. Sometimes by the time the desktop shortcut is doubled clicked and the application actually gives some sort of indication of launching, 20 -30 seconds may have elapsed. So , what ends up happening , the customer will double click the launch shortcut again and again, and what usually ends up happening in Client limited applications, the # of clients open exceeds the license count, and a Logon Screen prompting username / password is usually the the last window to open.

is this something I am the only one experiencing ?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 6, 2017, 3:26am UTC](https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697/2 "2017-07-06T03:26:39Z")

</div>

I saw such behavior a few years ago, but thought it was a linux thing. Haven’t seen it since I switched to always using the native client launchers.

---

<div class="post-metadata">

**Author:** ![pdibenedetto](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pdibenedetto/32/6364_2.png) [@pdibenedetto](https://forum.inductiveautomation.com/u/pdibenedetto)\
**Post date:** [July 7, 2017, 2:31am UTC](https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697/3 "2017-07-07T02:31:26Z")

</div>

I agree with Phil. Are you using java web start shortcuts or native client launcher shortcuts?

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [July 8, 2017, 7:27pm UTC](https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697/4 "2017-07-08T19:27:41Z")

</div>

thanks,  
i will try the Native Launcher again

---

<div class="post-metadata">

**Author:** ![AlThePal](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/althepal/32/3603_2.png) [@AlThePal](https://forum.inductiveautomation.com/u/AlThePal)\
**Post date:** [July 11, 2017, 4:00pm UTC](https://forum.inductiveautomation.com/t/issues-with-slow-launching-of-clients/14697/5 "2017-07-11T16:00:23Z")

</div>

We did see an issue with one customer with a multi-homed (multiple network card) server when using Java web start. The client would try to communicate to the first IP address (which it couldn’t access) and had to timeout before it tried the second IP address (which succeeded).