API Provider integration restarts for no reason
See original GitHub issueThis is a…
[ ] Feature request
[x] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Documentation issue or request
Description
After deploying a simple API Provider integration (just the todo api with a single implemented flow), it gets restarted every couple of minutes. The provided API itself works fine, except during the restart, when it’s completely unavailable.
This is the log when the integration restarts:
2019-07-02 09:51:33.948 INFO 1 --- [ Thread-7] ationConfigEmbeddedWebApplicationContext : Closing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@2890c451: startup date [Tue Jul 02 09:49:08 UTC 2019]; root of context hierarchy
2019-07-02 09:51:33.951 INFO 1 --- [ Thread-7] o.s.c.support.DefaultLifecycleProcessor : Stopping beans in phase 2147483647
2019-07-02 09:51:33.952 INFO 1 --- [ Thread-7] o.a.camel.spring.SpringCamelContext : Apache Camel 2.21.0.fuse-740028 (CamelContext: todo-empty) is shutting down
2019-07-02 09:51:33.952 INFO 1 --- [ Thread-7] o.a.camel.impl.DefaultShutdownStrategy : Starting to graceful shutdown 11 routes (timeout 300 seconds)
2019-07-02 09:51:33.966 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: i-Lim33GffTi8X3S51NMNz shutdown complete, was consuming from: direct://2a2f0185-3980-4167-af96-55cb4af5196e
2019-07-02 09:51:33.969 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: i-Lim33GefTi8X3S51NMKz shutdown complete, was consuming from: direct://d44d3329-31ed-482e-95cd-2415ac248ced
2019-07-02 09:51:33.969 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: i-Lim33GefTi8X3S51NMHz shutdown complete, was consuming from: direct://9bf8441f-0d65-4646-a418-71c0dda1c7f3
2019-07-02 09:51:33.969 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: i-Lim33GefTi8X3S51NMEz shutdown complete, was consuming from: direct://e6f15c45-b648-441e-b0a8-450d5155820b
2019-07-02 09:51:33.970 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: i-Lim33GdfTi8X3S51NMBz shutdown complete, was consuming from: direct://5513c8d7-58ae-4b68-9455-0481d9475c17
2019-07-02 09:51:33.973 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: 2a2f0185-3980-4167-af96-55cb4af5196e shutdown complete, was consuming from: servlet:/api/%7Bid%7D?headerFilterStrategy=syndesisHeaderStrategy&httpMethodRestrict=DELETE
2019-07-02 09:51:33.973 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: d44d3329-31ed-482e-95cd-2415ac248ced shutdown complete, was consuming from: servlet:/api/%7Bid%7D?headerFilterStrategy=syndesisHeaderStrategy&httpMethodRestrict=PUT
2019-07-02 09:51:33.973 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: 9bf8441f-0d65-4646-a418-71c0dda1c7f3 shutdown complete, was consuming from: servlet:/api/%7Bid%7D?headerFilterStrategy=syndesisHeaderStrategy&httpMethodRestrict=GET
2019-07-02 09:51:33.973 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: e6f15c45-b648-441e-b0a8-450d5155820b shutdown complete, was consuming from: servlet:/api?headerFilterStrategy=syndesisHeaderStrategy&httpMethodRestrict=POST
2019-07-02 09:51:33.976 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: 5513c8d7-58ae-4b68-9455-0481d9475c17 shutdown complete, was consuming from: servlet:/api?headerFilterStrategy=syndesisHeaderStrategy&httpMethodRestrict=GET
2019-07-02 09:51:33.976 INFO 1 --- [ - ShutdownTask] o.a.camel.impl.DefaultShutdownStrategy : Route: route1 shutdown complete, was consuming from: servlet:/openapi.json?headerFilterStrategy=syndesisHeaderStrategy&httpMethodRestrict=GET
2019-07-02 09:51:33.977 INFO 1 --- [ Thread-7] o.a.camel.impl.DefaultShutdownStrategy : Graceful shutdown of 11 routes completed in 0 seconds
2019-07-02 09:51:34.003 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: direct-4-0
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: direct-3-0
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: direct-2-0
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: direct-1-0
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping component: sql-sql-0-1
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: sql-0-1
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: bean-3-1
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: direct-0-0
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: bean-4-1
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: bean-1-1
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: bean-2-1
2019-07-02 09:51:34.004 DEBUG 1 --- [ Thread-7] i.s.i.c.proxy.ComponentProxyComponent : Stopping connector: bean-0-3
2019-07-02 09:51:34.021 INFO 1 --- [ Thread-7] o.a.camel.spring.SpringCamelContext : Apache Camel 2.21.0.fuse-740028 (CamelContext: todo-empty) uptime 2 minutes
2019-07-02 09:51:34.021 INFO 1 --- [ Thread-7] o.a.camel.spring.SpringCamelContext : Apache Camel 2.21.0.fuse-740028 (CamelContext: todo-empty) is shutdown in 0.069 seconds
2019-07-02 09:51:34.021 INFO 1 --- [ Thread-7] o.s.c.support.DefaultLifecycleProcessor : Stopping beans in phase 0
2019-07-02 09:51:34.026 INFO 1 --- [ Thread-7] o.s.j.e.a.AnnotationMBeanExporter : Unregistering JMX-exposed beans on shutdown
2019-07-02 09:51:34.033 INFO 1 --- [ Thread-7] o.a.c.c.s.CamelHttpTransportServlet : Destroyed CamelHttpTransportServlet[CamelServlet]
Issue Analytics
- State:
- Created 4 years ago
- Comments:27 (22 by maintainers)
Top Results From Across the Web
How to "restart integration" due to instance migration?
Can anyone explain how to "restart an integration"? Our org was part of an instance migration and one of our APIs is not...
Read more >Fix the Most Common API Gateway Request Errors - Dashbird
Retries can help, especially when integrated services are currently restarting. Handling API Gateway 503 Error: Service Unavailable. If you see ...
Read more >Troubleshooting integrated authoring in App Connect ... - IBM
Verify that your API Connect instance is still available and running. If the instance is no longer running, restart it and then restart...
Read more >Chapter 6. Creating an integration that is triggered by a REST ...
An API provider integration allows REST API clients to invoke commands that trigger execution of the integration. When Fuse Online publishes an API...
Read more >Cannot start messaging broker in integration server, [Pending ...
Go to run>services.msc>restart the webMethods broker once and also please give correct broker connection settings in Integration server ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@asmigala good point!
turns out we have an option #4 (from @lburgazzoli) that uses a different Spring Boot management port in application.properties
management.port=8081
let’s see if this worksWhat happens when the OpenAPI specifies an operation at the
/health
path?