Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Max pool size must be positive! with openjdk 8u131 within docker container #10704

Closed
gionn opened this issue Jun 6, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@gionn
Copy link

commented Jun 6, 2017

Hi,

I am running a java app with hazelcast 3.8.2 within docker, and after switching from openjdk:8u121-jre-alpine to openjdk:8u131-jre-alpine, I've started to get the following stacktrace during cluster bootstrap:

Caused by: java.lang.IllegalArgumentException: Max pool size must be positive!
  at com.hazelcast.util.executor.CachedExecutorServiceDelegate.<init>(CachedExecutorServiceDelegate.java:65)
  at com.hazelcast.spi.impl.executionservice.impl.ExecutionServiceImpl.createExecutor(ExecutionServiceImpl.java:199)
  at com.hazelcast.spi.impl.executionservice.impl.ExecutionServiceImpl.register(ExecutionServiceImpl.java:186)
  at com.hazelcast.spi.impl.executionservice.impl.ExecutionServiceImpl.<init>(ExecutionServiceImpl.java:148)
  at com.hazelcast.spi.impl.NodeEngineImpl.<init>(NodeEngineImpl.java:134)
  at com.hazelcast.instance.Node.<init>(Node.java:204)
  at com.hazelcast.instance.HazelcastInstanceImpl.createNode(HazelcastInstanceImpl.java:159)
  at com.hazelcast.instance.HazelcastInstanceImpl.<init>(HazelcastInstanceImpl.java:127)
  at com.hazelcast.instance.HazelcastInstanceFactory.constructHazelcastInstance(HazelcastInstanceFactory.java:218)
  at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(HazelcastInstanceFactory.java:176)
  at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(HazelcastInstanceFactory.java:126)

After googling a bit, it looks like that some jvm behaviour is changed in u131 when the app is run inside a container.

ref:
https://bugs.openjdk.java.net/browse/JDK-8140793
https://blogs.oracle.com/developers/official-docker-image-for-oracle-java-and-the-openjdk-roadmap-for-containers

@lazerion

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2017

@gionn Hi,
I will look into it, however it would be great if you could share Dockerfile with us?

@gionn

This comment has been minimized.

Copy link
Author

commented Jun 7, 2017

It's a spring boot application, so Dockerfile is really simple:

FROM openjdk:8u131-jre-alpine
ADD target/app.jar /usr/local/java/app.jar
CMD exec java -jar /usr/local/java/app.jar

Thanks!

@lazerion

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2017

Hi @gionn
I have changed our OSS docker image to openjdk:8u131-jre-alpine and shebang.
Instance is up, could you please check java -version on failing container.

docker exec <container-id> java -version
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (IcedTea 3.4.0) (Alpine 8.131.11-r1)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
@gionn

This comment has been minimized.

Copy link
Author

commented Jun 7, 2017

You are right, it looks like that I trigger the bug only when running integration tests in CircleCI 1.0, probably this is glitch in their Docker environment with updated jvm and not an hazelcast fault.

Thanks for your support @lazerion!

@lazerion

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2017

@gionn You're welcome.

@lazerion lazerion closed this Jun 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.