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

Running Docker image fails #44

Open
manideep418 opened this issue Jan 22, 2020 · 3 comments
Open

Running Docker image fails #44

manideep418 opened this issue Jan 22, 2020 · 3 comments

Comments

@manideep418
Copy link

manideep418 commented Jan 22, 2020

Running the docker image using docker-compose file fails. docker run not reading the environment variables specified in the docker-compose file.
`version: "2"

services:
zeebe:
container_name: zeebe_worker_lock_order
image: camunda/zeebe-http-worker
environment:
- ZEEBE_CLIENT_WORKER_DEFAULTNAME='Lock Order'
- ZEEBE_CLIENT_WORKER_DEFAULTTYPE='LockOrder'
- ZEEBE_CLIENT_BROKER_CONTACTPOINT='127.0.0.1:26500'
Failing with below error
zeebe_worker_lock_order | 2020-01-23 15:17:24.031 WARN 1 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'zeebeClientLifecycle'; nested exception is java.lang.NullPointerException: target
zeebe_worker_lock_order | 2020-01-23 15:17:24.033 INFO 1 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Shutting down ExecutorService 'applicationTaskExecutor'
zeebe_worker_lock_order | 2020-01-23 15:17:24.049 WARN 1 --- [ main] o.s.b.f.support.DisposableBeanAdapter : Destroy method 'close' on bean with name 'zeebeClientLifecycle' threw an exception: java.lang.NullPointerException
zeebe_worker_lock_order | 2020-01-23 15:17:24.066 INFO 1 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
zeebe_worker_lock_order | 2020-01-23 15:17:24.138 INFO 1 --- [ main] ConditionEvaluationReportLoggingListener :
zeebe_worker_lock_order |
zeebe_worker_lock_order | Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
zeebe_worker_lock_order | 2020-01-23 15:17:24.153 ERROR 1 --- [ main] o.s.boot.SpringApplication : Application run failed
zeebe_worker_lock_order |
zeebe_worker_lock_order | org.springframework.context.ApplicationContextException: Failed to start bean 'zeebeClientLifecycle'; nested exception is java.lang.NullPointerException: target
zeebe_worker_lock_order | at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:185) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:162) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE] zeebe_worker_lock_order | at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
zeebe_worker_lock_order | at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
zeebe_worker_lock_order | at io.zeebe.http.ZeebeHttpWorkerApplication.main(ZeebeHttpWorkerApplication.java:39) ~[classes!/:0.21.0-alpha4]
zeebe_worker_lock_order | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
zeebe_worker_lock_order | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:na]
zeebe_worker_lock_order | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:na]
zeebe_worker_lock_order | at java.base/java.lang.reflect.Method.invoke(Unknown Source) ~[na:na]
zeebe_worker_lock_order | at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) ~[app.jar:0.21.0-alpha4]
zeebe_worker_lock_order | at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) ~[app.jar:0.21.0-alpha4]
zeebe_worker_lock_order | at org.springframework.boot.loader.Launcher.launch(Launcher.java:51) ~[app.jar:0.21.0-alpha4]
zeebe_worker_lock_order | at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52) ~[app.jar:0.21.0-alpha4]
zeebe_worker_lock_order | Caused by: java.lang.NullPointerException: target
zeebe_worker_lock_order | at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:787) ~[guava-20.0.jar!/:na]
zeebe_worker_lock_order | at io.grpc.internal.AbstractManagedChannelImplBuilder.(AbstractManagedChannelImplBuilder.java:180) ~[grpc-core-1.24.0.jar!/:1.24.0]
zeebe_worker_lock_order | at io.grpc.netty.NettyChannelBuilder.(NettyChannelBuilder.java:128) ~[grpc-netty-1.24.0.jar!/:1.24.0]
zeebe_worker_lock_order | at io.grpc.netty.NettyChannelBuilder.(NettyChannelBuilder.java:123) ~[grpc-netty-1.24.0.jar!/:1.24.0]
zeebe_worker_lock_order | at io.grpc.netty.NettyChannelBuilder.forAddress(NettyChannelBuilder.java:109) ~[grpc-netty-1.24.0.jar!/:1.24.0]
zeebe_worker_lock_order | at io.zeebe.client.impl.ZeebeClientImpl.buildChannel(ZeebeClientImpl.java:119) ~[zeebe-client-java-0.21.1.jar!/:0.21.1]
zeebe_worker_lock_order | at io.zeebe.client.impl.ZeebeClientImpl.(ZeebeClientImpl.java:76) ~[zeebe-client-java-0.21.1.jar!/:0.21.1]
zeebe_worker_lock_order | at io.zeebe.client.impl.ZeebeClientBuilderImpl.build(ZeebeClientBuilderImpl.java:221) ~[zeebe-client-java-0.21.1.jar!/:0.21.1]
zeebe_worker_lock_order | at io.zeebe.spring.client.config.ZeebeClientSpringConfiguration.lambda$zeebeClientObjectFactory$0(ZeebeClientSpringConfiguration.java:39) ~[spring-zeebe-0.7.1.jar!/:0.7.1]
zeebe_worker_lock_order | at io.zeebe.spring.util.ZeebeAutoStartUpLifecycle.start(ZeebeAutoStartUpLifecycle.java:52) ~[spring-zeebe-util-0.7.1.jar!/:0.7.1]
zeebe_worker_lock_order | at io.zeebe.spring.client.ZeebeClientLifecycle.start(ZeebeClientLifecycle.java:46) ~[spring-zeebe-0.7.1.jar!/:0.7.1]
zeebe_worker_lock_order | at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
zeebe_worker_lock_order | ... 22 common frames omitted
zeebe_worker_lock_order |
Gracefully stopping... (press Ctrl+C again to force)
Stopping zeebe_worker_lock_order ... done

`

@saig0
Copy link
Contributor

saig0 commented Sep 2, 2020

A new HTTP worker image is published on https://hub.docker.com/r/camunda/zeebe-http-worker.

Please verify if it is working now :)

@younes-io
Copy link

I can't run the latest Docker image of this repo :

2020-12-04 21:24:02.234  INFO 1 --- [           main] i.zeebe.http.ZeebeHttpWorkerApplication  : Starting ZeebeHttpWorkerApplication on d8e95588bc2b with PID 1 (/app/classes started by root in /)
2020-12-04 21:24:02.242 DEBUG 1 --- [           main] i.zeebe.http.ZeebeHttpWorkerApplication  : Running with Spring Boot v2.3.2.RELEASE, Spring v5.2.8.RELEASE
2020-12-04 21:24:02.243  INFO 1 --- [           main] i.zeebe.http.ZeebeHttpWorkerApplication  : No active profile set, falling back to default profiles: default
2020-12-04 21:24:04.347  INFO 1 --- [           main] i.z.s.c.c.p.ZeebeWorkerPostProcessor     : zeebeWorker: ClassInfo(bean=io.zeebe.http.ZeebeHttpWorkerApplication$$EnhancerBySpringCGLIB$$1a673fa1@55fee662, beanName=zeebeHttpWorkerApplication)
2020-12-04 21:24:05.053  INFO 1 --- [           main] i.z.s.c.c.p.ZeebeWorkerPostProcessor     : register job worker: ZeebeWorkerValue(type=http, name=http-worker, timeout=-1, maxJobsActive=-1, beanInfo=MethodInfo(classInfo=ClassInfo(bean=io.zeebe.http.ZeebeHttpWorkerApplication$$EnhancerBySpringCGLIB$$1a673fa1@55fee662, beanName=zeebeHttpWorkerApplication), method=public void io.zeebe.http.ZeebeHttpWorkerApplication.handleFooJob(io.zeebe.client.api.worker.JobClient,io.zeebe.client.api.response.ActivatedJob) throws java.io.IOException,java.lang.InterruptedException,java.util.concurrent.ExecutionException,java.util.concurrent.TimeoutException))
2020-12-04 21:24:05.122  INFO 1 --- [           main] i.zeebe.http.ZeebeHttpWorkerApplication  : Started ZeebeHttpWorkerApplication in 3.546 seconds (JVM running for 4.035)
2020-12-04 21:24:05.292  WARN 1 --- [ault-executor-1] io.zeebe.client.job.poller               : Failed to activated jobs for worker http-worker and job type http

io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
	at io.grpc.Status.asRuntimeException(Status.java:533) ~[grpc-api-1.30.2.jar:1.30.2]
	at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:460) ~[grpc-stub-1.30.2.jar:1.30.2]
	at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:426) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.ClientCallImpl.access$500(ClientCallImpl.java:66) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:689) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$900(ClientCallImpl.java:577) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:751) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:740) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[grpc-core-1.30.2.jar:1.30.2]
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) ~[grpc-core-1.30.2.jar:1.30.2]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:26500
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:na]
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:779) ~[na:na]
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330) ~[netty-transport-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334) ~[netty-transport-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702) ~[netty-transport-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) ~[netty-transport-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) ~[netty-transport-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) ~[netty-transport-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) ~[netty-common-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.50.Final.jar:4.1.50.Final]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.50.Final.jar:4.1.50.Final]
	at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]

@saig0
Copy link
Contributor

saig0 commented Dec 18, 2020

@YounesTea, the worker tries to connect to a Zeebe broker that runs on 127.0.0.1:26500. Please check if this is the correct address of your Zeebe broker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants