Hello Tolga!
Already done and will be part of Camel 2.8 (see the issue).
Thanks for reporting this issue.
Best,
Christian
On Thu, Jul 7, 2011 at 3:10 AM, Tolga Tarhan wrote:
> Christian,
>
> Sorry for the long delay in responding. I agree that changing the logic
> only
> in the case of this SM
Christian,
Sorry for the long delay in responding. I agree that changing the logic only
in the case of this SMPP-specific exception, ProcessRequestException, is a
relatively straight-forward way to go. I've got the camel-smpp code checked
out, if you'd like me to take the first stab at a patch.
T
Tracked with https://issues.apache.org/jira/browse/CAMEL-4136
Tolga,
today I had the time to look into it.
At present the SmppConsumer catches any Exception in the
onAcceptDeliverSm(DeliverSm) and let the exception handler handle it. This
is the way Camel handle the exceptions.
In a real production system, I would not expect that you will let the
logging err
Hello Tolga!
I will have a look in it.
If you can share your route with us, it would be very helpful. And we love
contributions (which also include unit tests)... :-)
Best,
Christian
On Wed, May 25, 2011 at 3:09 AM, Tolga Tarhan wrote:
> All,
>
> The SMPP protocol allows a ESME to reject a mes
All,
The SMPP protocol allows a ESME to reject a message temporarily if
it's having trouble processing it (by responding with ESME_RX_T_APPN -
ESME Receiver temporary error). This seems to be the most logical
thing to do when an exception occurs during
onAcceptDeliverSm(DeliverSm) so that the SMSC
