CamelSmppError=034,CamelSmppStatus=UNDELIV

2016-10-01 Thread raju jwala
Hi Team, I am facing issue in my application. My Application is using SMPP protocal and SMSC as gateway. I am getting CamelSmppError=034,CamelSmppStatus=UNDELIV on logs. The message is not delivered properly. Please tell me in which situation this errors will come and how to resolve this issue

Re: CamelSmppError=034,CamelSmppStatus=UNDELIV

2016-10-01 Thread raju jwala
Moreover, I am not getting help from any one. You are the only hope for me. Thanks On Sun, Oct 2, 2016 at 9:53 AM, raju jwala wrote: > Hi Team, > > I am facing issue in my application. > > My Application is using SMPP protocal and SMSC as gateway. > > I am getting CamelSmppError=034,CamelSmppSt

Re: New Apache Camel Logo

2016-10-01 Thread Wojciech Indyk
+1 :) -- Kind regards/ Pozdrawiam, Wojciech Indyk 2016-09-29 17:05 GMT+02:00 Luca Burgazzoli : > +1 > > --- > Luca Burgazzoli > > > On Thu, Sep 29, 2016 at 4:50 PM, Andrea Cosentino > wrote: > > Absolutely +1. > > > > We need a new logo! > > -- > > Andrea Cosentino > >

Re: Getting ready for Apache Camel 2.18 Release

2016-10-01 Thread Gregor Zurowski
Thanks for testing the build. I will start cutting the release candidate tomorrow. Thanks, Gregor On Sat, Oct 1, 2016 at 6:04 PM, Claus Ibsen wrote: > The job completed and there was 2 flaky tests about camel-quartz > (deprecated) which can happen from time to time. > > We are looking good for

Re: Getting ready for Apache Camel 2.18 Release

2016-10-01 Thread Claus Ibsen
The job completed and there was 2 flaky tests about camel-quartz (deprecated) which can happen from time to time. We are looking good for cutting the RC. On Sat, Oct 1, 2016 at 1:32 PM, Claus Ibsen wrote: > Hi > > The previous CI job was aborted after 5h30m because it was configured > to timeou

Re: Getting ready for Apache Camel 2.18 Release

2016-10-01 Thread Claus Ibsen
Hi The previous CI job was aborted after 5h30m because it was configured to timeout after that duration, but it was still going, it was running the itests at the time. So I have bumped up the timeout value and kicked off a new one https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.full

Camel.trunk.notest - Build # 2892 - Still Failing

2016-10-01 Thread Apache Jenkins Server
The Apache Jenkins build system has built Camel.trunk.notest (build #2892) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/2892/ to view the results.