[
https://issues.apache.org/jira/browse/CAMEL-16611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
G Kal updated CAMEL-16611:
--------------------------
Description:
These two parameters configure the internal task executor, that handles PDUs.
Since the core and max threads of this thread pool is set to the same number
(org.jsmpp.session.SMPPSession.{color:#000000}BoundSessionStateListener){color}
more threads than needed are created !
The default value of pduProcessorDegree = 3, which means that each SMPP session
would spawn 3 threads. For a big number of sessions (SMPP Producer/Consumer)
with a really small window, this is really unnecessary (1 thread with a fair
sized queue could handle low traffic scenarios when the processing time of the
route is fast!)
Could these two JSMPP parameters be exported and configurable as an advanced
configuration?
was:
The default value of pduProcessorDegree = 3, which means that each SMPP session
would spawn 3 threads. For a big number of sessions (SMPP Producer/Consumer)
with a really small window, this is really unnecessary.
Could this Jsmpp parameter be exported and configurable as an advanced
configuration?
> camel-smpp: Export JSMPP's pduProcessorDegree and queueCapacity to
> SmppConfiguration
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-16611
> URL: https://issues.apache.org/jira/browse/CAMEL-16611
> Project: Camel
> Issue Type: New Feature
> Components: camel-smpp
> Affects Versions: 3.7.3
> Reporter: G Kal
> Priority: Minor
> Fix For: 3.11.0
>
>
> These two parameters configure the internal task executor, that handles PDUs.
> Since the core and max threads of this thread pool is set to the same number
> (org.jsmpp.session.SMPPSession.{color:#000000}BoundSessionStateListener){color}
> more threads than needed are created !
> The default value of pduProcessorDegree = 3, which means that each SMPP
> session would spawn 3 threads. For a big number of sessions (SMPP
> Producer/Consumer) with a really small window, this is really unnecessary (1
> thread with a fair sized queue could handle low traffic scenarios when the
> processing time of the route is fast!)
> Could these two JSMPP parameters be exported and configurable as an advanced
> configuration?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
