# Trouble starting client (JxBrowser OS error)

**URL:** <https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186>\
**Category:** Ignition\
**Created:** [August 29, 2017, 3:55am UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186 "2017-08-29T03:55:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jenko](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@Jenko](https://forum.inductiveautomation.com/u/Jenko)\
**Post date:** [August 29, 2017, 3:55am UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186/1 "2017-08-29T03:55:51Z")

</div>

Hi, I’m hoping someone can point me at a solution to my problem. When I try to start a native Linux client on my Ubuntu MATE install, I get the following error just before the client opens:  
“java.lang.ExceptionInInitializerError” but no further info.

Does anyone know what this means and where should I look to diagnose the problem?

Thanks for your help.

Dan

---

<div class="post-metadata">

**Author:** ![Jenko](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@Jenko](https://forum.inductiveautomation.com/u/Jenko)\
**Post date:** [August 29, 2017, 6:08am UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186/2 "2017-08-29T06:08:02Z")

</div>

I think i’ve found the culprit - JxBrowser is not compatible with ARM architecture and its throwing this error on client startup.

It never used to do this - I could previously load clients that weren’t supported by JxBrowser and I assume the error was thrown when i tried to view those pages.

Does anyone know how to start a client that ignores the WebBrowser module?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 29, 2017, 1:32pm UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186/3 "2017-08-29T13:32:21Z")

</div>

We’ve got an open ticket for this already.

I think something changed in a newer version of JXBrowser. I don’t know if there’s a workaround right now.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 29, 2017, 3:51pm UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186/4 "2017-08-29T15:51:25Z")

</div>

You can try the 7.9.1 version of the Web Browser module - it’s a much older version of the JxBrowser module that doesn’t seem to throw the ExceptionInitializerError

---

<div class="post-metadata">

**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\
**Post date:** [August 29, 2017, 6:31pm UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186/5 "2017-08-29T18:31:07Z")

</div>

Yes, I went through this with support a few weeks ago. We downgraded to the 7.9.1 version. Anything newer also throws an exception and will not load on Windows XP… Inductive said they are going to catch the exception in a newer version so unsupported clients just won’t be able to use the component, but can still launch.

---

<div class="post-metadata">

**Author:** ![Jenko](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@Jenko](https://forum.inductiveautomation.com/u/Jenko)\
**Post date:** [August 29, 2017, 11:43pm UTC](https://forum.inductiveautomation.com/t/trouble-starting-client-jxbrowser-os-error/15186/6 "2017-08-29T23:43:54Z")

</div>

Thanks for your help everyone, I downgraded the Web Browser Module to 7.9.1 version and both my XP clients and my ARM based clients worked.

I appreciate your help.
