Camel
  1. Camel
  2. CAMEL-3853

SMPP connector lazySessionCreation

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.6.0
    • Fix Version/s: Future
    • Component/s: camel-smpp
    • Labels:
      None

      Description

      Currently I am facing issue, when connecting to SMSC using smpp conector. If SMSC is down, and smpp connection cannot be created, then camel context will shut down, and also all other context, so camel cannot start up.
      Camel context with smpp was set to autostart=false, but smpp still tries to create connection and fails.

      It would be nice to have option for lazySessionCreation like in mina. The best will be feature when smpp could start in reconnecting state (tring to connect in defined interval) in case SMSC is down.

        Activity

        Show
        Claus Ibsen added a comment - See nabble http://camel.465427.n5.nabble.com/Camel-context-shutdown-after-route-with-smpp-initialization-failure-tp4291032p4291032.html
        Hide
        Claus Ibsen added a comment -

        You are of course welcome to work on a patch to add this new feature.

        Show
        Claus Ibsen added a comment - You are of course welcome to work on a patch to add this new feature.
        Hide
        Claus Ibsen added a comment -

        For example check the camel-mina source code to be inspired how that lazy session option works.

        Show
        Claus Ibsen added a comment - For example check the camel-mina source code to be inspired how that lazy session option works.
        Hide
        Peter Argalas added a comment -

        I have just applied Mina's lazySessionCreation concept to SMPPProducer. It was easy and is working.

        Question is how to deal with SMPPConsumer, that will receive delivery notifications or any other communication from SMSC?

        Any advise here? Automatic reconnect after exception in doStart method should be triggered and exception should not be propagated to routeBuilder. What do you think?

        Show
        Peter Argalas added a comment - I have just applied Mina's lazySessionCreation concept to SMPPProducer. It was easy and is working. Question is how to deal with SMPPConsumer, that will receive delivery notifications or any other communication from SMSC? Any advise here? Automatic reconnect after exception in doStart method should be triggered and exception should not be propagated to routeBuilder. What do you think?
        Hide
        Christian Müller added a comment -

        Peter, I do not have a better idea than your proposal. This behavior should be configurable and the default configuration should throw the exception, if we cannot connect to the SMSC.
        Do you work on this patch?

        Show
        Christian Müller added a comment - Peter, I do not have a better idea than your proposal. This behavior should be configurable and the default configuration should throw the exception, if we cannot connect to the SMSC. Do you work on this patch?
        Hide
        Peter Argalas added a comment -

        Sorry no, we have found out that we need to communicate with SMSC via EMI/UCP. So I have stopped SMPP activities.

        Show
        Peter Argalas added a comment - Sorry no, we have found out that we need to communicate with SMSC via EMI/UCP. So I have stopped SMPP activities.
        Hide
        Christian Müller added a comment -

        Committed r1095826
        Added the lazySessionCreation option.

        Show
        Christian Müller added a comment - Committed r1095826 Added the lazySessionCreation option.
        Hide
        Christian Müller added a comment -

        Updated the wiki page as well.

        Show
        Christian Müller added a comment - Updated the wiki page as well.

          People

          • Assignee:
            Christian Müller
            Reporter:
            Peter Argalas
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development