Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 5 Jan 2015 14:59:34 +0000 (UTC)
From: "Daniel Pocock (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12764918.1420469935000.10465.1420469974391@Atlassian.JIRA>
In-Reply-To: <JIRA.12764918.1420469935000@Atlassian.JIRA>
References: <JIRA.12764918.1420469935000@Atlassian.JIRA>
 <JIRA.12764918.1420469935713@arcas>
Subject: [jira] [Created] (CAMEL-8207) camel-smpp - trying to create
 multiple receiver binds
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Daniel Pocock created CAMEL-8207:
------------------------------------

             Summary: camel-smpp - trying to create multiple receiver binds
                 Key: CAMEL-8207
                 URL: https://issues.apache.org/jira/browse/CAMEL-8207
             Project: Camel
          Issue Type: Bug
          Components: camel-smpp
    Affects Versions: 2.14.1
         Environment: n/a
            Reporter: Daniel Pocock


I've noticed that the producer is just creating one transmitter bind but the consumer appears to try and create multiple receiver binds.

I tried putting threads(1, 1) into the consumer route but it still appears to try and create multiple receiver binds.

There are many scenarios where somebody would only want to use a single receiver bind

Many providers limit the number of binds and the component creates a lot of noise in the log file when it can't create additional binds because the SMSC rejects the additional connections with negative response code 5.

I went looking for information about this and found the following related components about threading issues in jSMPP:

https://issues.jboss.org/browse/MR-838


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)