Zulu Community

Performance issue with WAS Liberty as dev server

Updated on January 16, 2018 in General Zulu Questions
7 on January 13, 2018

When evaluating JDK 8.0.152 for Windows in a local development environment using Eclipse and IBM WAS Liberty, I get painfully long start-up times. The start-up time is approximately 2-4 times longer compared to IBM:s Java, which is not desirable in a dev environment. The reasons that behind evaluating Zulu is that we wanted to standardise on one Java for all our app servers and that WAS Liberty is now supported by IBM on OpenJDK.

Are there anything I could tweak or check in order to speed things up?

  • Liked by
  • andrewoberstar
Reply
0 on January 15, 2018

I’ve seen the same kind of issue with Tomcat from Eclipse. Are you using Eclipse Oxygen? I noticed that my issue does not seem to be present in Eclipse Neon.

Here’s a bug I opened with Eclipse in hopes of getting a fix. https://bugs.eclipse.org/bugs/show_bug.cgi?id=529694

  • Liked by
Reply
Cancel
5 on January 15, 2018

Hello everyone. The problem you are facing is a point in time issue with the 8u152 October CPU build, at least as far as we know so far. One of our Zulu Enterprise subscribers asked Azul to digitally sign all the JARs in the JDK as part of their heightened security standards. We did that change on their behalf, and saw no real problems in our QA testing so we applied the technique across our whole build and QA pipeline such that all Zulu binaries were to have signed JARs. After the 8u152 release went out, however, we have since received reports of the same slow down behavior you are reporting, and across several flavors of application servers and not just Liberty. As such, we rolled back the change to cease signing all Zulu JARs and are preparing our Zulu 8u161 binaries for the January CPU without such JAR signing. The tweak you need will be 1.) to update to the newer Zulu once the January CPU ships, or 2.) if you need something today, drop back to an older Zulu release build. Hopefully this helps clarify. –Matt

on January 15, 2018

This is great news! I look forward to the January binaries.

on January 16, 2018

Thank you for this info! I will try out an older build right away.

on January 16, 2018

Hi Matt,

do you have any hypothesis on why this slow-down happens when signing the JARs? I am thinking it might be some sort of anti virus on Windows-machines because I can’t observe this problem on either Linux or MacOS (Zulu starts just as fast as adoptopenjdk.net and oracle’s JDK).

/D

on January 16, 2018

Just to add, my (perhaps naive) thought is that it’s only the startup speed that is affected by signing (when the rt.jar is checked)… but wouldn’t that happen on Linux or MacOS also?

on January 16, 2018

Hi danpfe, only Windows jars were signed in October release, so Linux and Mac dodged the bullet.

Show more replies
  • Liked by
Reply
Cancel