Hello Saurabh!

I cannot reproduce your issue. I created a simple Camel route which only
logs the body of the received DeliverSM message:

public class SmppUserIssueIntegrationTest extends CamelTestSupport {

    @Test
    public void sendDataSM() throws Exception {
        Thread.sleep(60000 * 60);
    }

    protected RouteBuilder createRouteBuilder() throws Exception {
        return new RouteBuilder() {
            public void configure() throws Exception {
                from("smpp://smppclient@localhost
:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer")
                    .log("processing exchange ${body}");
            }
        };
    }
}

>From my SMSC test client (using Selenium SMPPSim), I sent multiple
DeliverSM messages and all are received in the Camel route:

...
2013-06-16 17:24:40,209 [pool-1-thread-1] DEBUG
MessageReceiverListenerImpl    - Received a deliverSm PDUHeader(73,
00000005, 00000000, 69)
2013-06-16 17:24:40,209 [pool-1-thread-1] INFO
route1                         - processing exchange Hello from SMPPSim
2013-06-16 17:24:40,394 [pool-1-thread-2] DEBUG
MessageReceiverListenerImpl    - Received a deliverSm PDUHeader(73,
00000005, 00000000, 70)
2013-06-16 17:24:40,394 [pool-1-thread-2] INFO
route1                         - processing exchange Hello from SMPPSim
2013-06-16 17:24:40,623 [pool-1-thread-3] DEBUG
MessageReceiverListenerImpl    - Received a deliverSm PDUHeader(73,
00000005, 00000000, 71)
2013-06-16 17:24:40,624 [pool-1-thread-3] INFO
route1                         - processing exchange Hello from SMPPSim


You write "that Deliver_sm packet is not processed by the camel exchange".
Still not clear for me what do you mean exactly. Do you not see the log
output "Processing SMS exchange : ..." for this message?

Do you see any other log message? E.g. "Received a deliverSm ..."? This is
the log message Camel logs (on DEBUG) when it receives an message. If you
cannot see this log message for the missing messages, I'm afraid this is an
issue in the underlying JSMPP library we are using.

May be one of your multiple "if" statements are not correct?

Is your ChannelMessagesBean thread safe?

Best,

Christian Müller
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Sun, Jun 16, 2013 at 10:20 AM, saurabhmehan <[email protected]>wrote:

> Hi Christian,
>
> Please find the valid link as follows for code:
> http://camel.465427.n5.nabble.com/file/n5734036/SmsMessageProcessor.java
>
>
> "When I say the message is discarded", I figured out this case by analyzing
> tcpdump from both servers as follows:
> 1. Sent MO(Mobile Originated) SMS that is Deliver_sm packet from the
> simulator installed on one server.
> 2. To the receiver server where SMPP EndPoint is configured using camel.
> 3. The Deliver_sm request is received on the server where camel smpp
> endpoint is configured(confirmed from snoop taken on the receiver server
> where smpp endpoint is configured.)
> 4. But that Deliver_sm packet is not processed by the camel exchange.
>
> Please find the snoop as an attachment.
> Refer 477128 sequence number.(Type : *smpp.sequence_number == 477128* in
> the
> filter field of wireshark.)
>
> SmS_SO3_2.pcap
> <http://camel.465427.n5.nabble.com/file/n5734242/SmS_SO3_2.pcap>
>
>
> Thanks & Regards
> Saurabh Mehan
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-SMPP-component-question-tp5734019p5734242.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

Reply via email to