You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Pascal Schumacher (Jira)" <ji...@apache.org> on 2022/01/11 14:43:00 UTC

[jira] [Created] (CAMEL-17472) camel-smpp: Consumer reconnect no longer works after updating to 3.14.0

Pascal Schumacher created CAMEL-17472:
-----------------------------------------

             Summary: camel-smpp: Consumer reconnect no longer works after updating to 3.14.0
                 Key: CAMEL-17472
                 URL: https://issues.apache.org/jira/browse/CAMEL-17472
             Project: Camel
          Issue Type: Bug
          Components: camel-smpp
    Affects Versions: 3.14.0
            Reporter: Pascal Schumacher


We using camel-smpp with Spring Boot.

After updating the from version 3.13.0 to 3.14.0 reconnecting (at least for the consumer, do not know if the producer is also affected) does not seem to work.

We use the default values for maxReconnect and initialReconnectDelay. We set reconnectDelay to 60000.

With version 3.13.0 and before camel tried to reconnect for a long time. With camel 3.14.0 there does not seem to be any reconnect attempts:

{code}
Jan 11, 2022 @ 04:20:11.499 - SmppConsumer - Lost connection to: smpp://72279@193.254.168.1:9446 - trying to reconnect...
Jan 11, 2022 @ 04:20:16.516 - BackgroundTask - The task smpp-reconnect does not have more budget to continue running
Jan 11, 2022 @ 04:20:17.516 - BackgroundTask - The task smpp-reconnect does not have more budget to continue running
Jan 11, 2022 @ 04:20:18.516 - BackgroundTask - The task smpp-reconnect does not have more budget to continue running
Jan 11, 2022 @ 04:20:19.516 - BackgroundTask - The task smpp-reconnect does not have more budget to continue running
Jan 11, 2022 @ 04:20:20.516 - BackgroundTask - The task smpp-reconnect does not have more budget to continue running
Jan 11, 2022 @ 04:20:21.516 - BackgroundTask - The task smpp-reconnect does not have more budget to continue running
... (endless repeat of the last log message)
{code}

I guess this was caused by https://issues.apache.org/jira/browse/CAMEL-17121

 

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)