[ 
https://issues.apache.org/jira/browse/CAMEL-15307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-15307:
-----------------------------------

    Assignee: Claus Ibsen

> camel-spring - Graceful shutdown is not working anymore 
> --------------------------------------------------------
>
>                 Key: CAMEL-15307
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15307
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 3.3.0, 3.4.0, 3.4.1
>         Environment: Windows 10
> openJDK 1.8, Oracle JDK 1.8
>            Reporter: Oliver Holzmann
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 3.5.0
>
>         Attachments: camel-context.xml
>
>
> We are using {{org.apache.camel.spring.Main}} to run our Camel applications 
> within a spring context. After updating from Camel 2.24.3 to 3.4.1 the 
> gracefull shutdown is not working anymore.
> When calling {{Strg+C}} in a windows shell (or stopping a service wrapper) 
> the camel context is not stopped/closed and the jvm simply stops after 
> logging this:
> {code:java}
> 2020-07-17 08:49:17,559 [ad #7 - CamelHangupInterceptor] INFO  
> DefaultMainShutdownStrategy    - Received hang up - stopping the main 
> instance.
> 2020-07-17 08:49:17,559 [pache.camel.spring.Main.main()] DEBUG MainSupport    
>                 - Stopping Spring ApplicationContext: 
> org.springframework.context.support.ClassPathXmlApplicationContext@15512f1a
> {code}
> In Camel 2.25.1 gracefull shutdown also works fine.
> Also using Camel version 3.4.0 or 3.3.0 didn't solve the issue.
> I debugged the behaviour and found that, when keeping the 
> {{CamelHangupInterceptor}} thread from 
> {{org.apache.camel.main.DefaultMainShutdownStrategy}} running after the 
> {{shutdown}} call, the Camel context is stopped correctly. But when the 
> {{CamelHangupInterceptor}} thread ends also the JVM is stopping.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to