In the SMPP specification, the error code '0x000000FF' (which is 255) is documented as "Unknow error". It doesn't look wrong to me. If you want to return another error code, simply catch the exception in your route and rethrow an org.jsmpp.extra.ProcessRequestException (with the error code you want) which is returned to the SMSC.
Sounds right? In general Camel will first stop the consumer on a route (from smpp://...) so that you will not receive further requests. By default, Camel will shut down gracefully [1]. Do you need more than 5 minutes to shut down? In this case (you should really think about your architecture), it could be happen that you do not ack the message because Camel forced the shut down. But in this case I would expect the SMSC should resend the message. [1] http://camel.apache.org/graceful-shutdown.html Best, Christian On Tue, Mar 26, 2013 at 2:11 PM, fclose <f...@closebase.com> wrote: > I'll looked in the code and the only place I found that an error code could > be generated is in > > org.apache.camel.component.smpp.MessageReceiverListenerImpl line 105 > > this seems to send back to the smsc an error 255, which is unkown to the > smsc. > > > I'll try to confirm that the error is really happening in > MessageReceiverListenerImpl.onAcceptDataSm() > If this is the case, does it mean, that there's a problem when we still > receive messages and the route is in the process of stopping itself ? > > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/SMPP-stop-route-problem-tp5729769p5729848.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
