search

orkes-io / orkes-conductor-community

Orkes Conductor is a microservices orchestration engine.
Other
110 stars 27 forks source link

redis:Could not get a resource from the pool,Pool not open #8

Open lianjunwei opened 1 year ago

lianjunwei commented 1 year ago

I encountered an error. During the startup process, Redis shut down abnormally, causing the service to fail to start. First of all, I'm sure that Redis itself is OK. image

v1r3n commented 1 year ago

Hi @lianjunwei are you using the standalone container the one described here? https://github.com/orkes-io/orkes-conductor-community#simple-self-contained-script-to-launch-the-docker-image

lianjunwei commented 1 year ago

Hi @lianjunwei are you using the standalone container the one described here? https://github.com/orkes-io/orkes-conductor-community#simple-self-contained-script-to-launch-the-docker-image

@v1r3n the standalone container is OK. I run the compiled source code.

Taqi-Techverx commented 1 year ago

image facing same issue

rajindersaini commented 1 year ago

Facing the same issue while running from the code, can someone look into this please.

411 [http-nio-8080-exec-1] INFO org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/] [] - Initializing Spring DispatcherServlet 'dispatcherServlet' 2411 [http-nio-8080-exec-1] INFO org.springframework.web.servlet.DispatcherServlet [] - Initializing Servlet 'dispatcherServlet' 2412 [http-nio-8080-exec-1] INFO org.springframework.web.servlet.DispatcherServlet [] - Completed initialization in 1 ms 2642 [http-nio-8080-exec-4] ERROR com.netflix.conductor.core.operation.StartWorkflowOperation [] - Unable to start workflow: kitchensink java.lang.RuntimeException: redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool at io.orkes.conductor.mq.redis.single.RedisQueueMonitor.loadScript(RedisQueueMonitor.java:81) ~[orkes-redis-queues-1.0.3.jar:?]

gsvieira1 commented 5 months ago

facing same issue. Is there anybody could help me to solve this problem? I don't know is this issue has been updated or fixed before.