![Surprise, surprice][1] Oracle has fixed this issue with update **[Java 1.8 8 update 144][3]** ([release notes][4]). Btw. we will/have fixed the issue too with 5.1.13, 6.0.9 and 6.7, by applying a workaround. However, we recommend to update to java 1.5 8 update 144. [1]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [2]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [3]: http://www.oracle.com/technetwork/java/javase/downloads/index.html [4]: http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html

![Surprise, surprice][1] Oracle has fixed this issue with update **[Java 1.8 update 144][3]** ([release notes][4]). Btw. we have will/have fixed the issue too with 5.1.13, 6.0.9 and 6.7, by applying a workaround. However, we recommend to update to java 1.5 update 144. [1]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [2]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [3]: http://www.oracle.com/technetwork/java/javase/downloads/index.html [4]: http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html

[Surprise, surprise][1]: ![Surprise, surprice][1] Oracle has fixed this issue with update **[Java 1.8 update 144][2]** 144][3]** ([release notes][3]).notes][4]). Btw. we have fixed the issue too with 5.1.13, 6.0.9 and 6.7, by applying a workaround. However, we recommend to update to java 1.5 update 144. [1]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [2]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [3]: http://www.oracle.com/technetwork/java/javase/downloads/index.html [3]: [4]: http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html

[Surprise, surprise][1]: Oracle has fixed this issue with update **[Java 1.8 update 144][2]**.144][2]** ([release notes][3]). Btw. we have fixed the issue too with 5.1.13, 6.0.9 and 6.7, by applying a workaround. However, we recommend to update to java 1.5 update 144. [1]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [2]: http://www.oracle.com/technetwork/java/javase/downloads/index.htmlhttp://www.oracle.com/technetwork/java/javase/downloads/index.html [3]: http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html

We [Surprise, surprise][1]: Oracle has fixed this issue with update **[Java 1.8 update 144][2]**. Btw. we have found fixed the issue too with 5.1.13, 6.0.9 and 6.7, by applying a workaround. However, we will release new hotfix versions for all supported Axon.ivy versions (5.1.x, 6.0.x, 6.7) soon. More information will follow. recommend to update to java 1.5 update 144. For now: **Don't upgrade clients to Java 1.8 update 141** [1]: https://img.buzzfeed.com/buzzfeed-static/static/enhanced/web05/2012/4/17/12/anigif_enhanced-buzz-18321-1334679990-18.gif [2]: http://www.oracle.com/technetwork/java/javase/downloads/index.html

We have found the issue and we will release soon new hotfix versions for all supported Axon.ivy versions (5.1.x, 6.0.x, 6.7). 6.7) soon. More information will follow. For now: **Don't upgrade clients to Java 1.8 update 141**

Currently We have found the issue and we are at the analysis of the problem and searching a convenient solution. will release soon new hotfix versions for all supported Axon.ivy versions (5.1.x, 6.0.x, 6.7). More information will follow. For now: **Don't upgrade clients to Java 1.8 update 141**

Currently we are at the analysis of the problem and searching a convenient solution. More information will follow. For now: **Don't upgrade the clients to Java 1.8 update 141**

Currently we are at the analysis of the problem and searching a convenient solution. More information will follow. For now: **Don't upgrade the clients to Java 1.8 update 141**