You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Daniel Pocock (JIRA)" <ji...@apache.org> on 2015/02/15 17:22:12 UTC
[jira] [Commented] (CAMEL-8207) camel-smpp - trying to create
multiple receiver binds
[ https://issues.apache.org/jira/browse/CAMEL-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322046#comment-14322046 ]
Daniel Pocock commented on CAMEL-8207:
--------------------------------------
Of all the outstanding camel-smpp issues, this is probably one of the more serious ones that needs to be addressed
> 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 comments about threading issues in jSMPP:
> https://issues.jboss.org/browse/MR-838
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)