Hi, the route is like the following. In answer to your question, no we
quickly put it on a queue and then return. For now we have changed it to use
pop3 for now which resolved this problem, but still appears to repeat some
messages sometimes.
from("imap://user@ipaddress") // from IMAP
.pro
I am using imap to read messages from a folder and am getting the following
two exceptions for some messages.
I saw another thread that referred to this and suggested that use the
disconnect option that was put into 2.8.3. I have moved to this version but
it doesn't fix the problem.
does anybody
Thanks, I am not able to move t0 2.9 just yet because going into production
soon.
I have basically ended up setting the basic auth headers myself and then
they get passwed through with request. Is easier for now, I will look at new
options once move to 2.9.
Thanks for you help.
--
View this mess
Thank you for the reply. I am using the camel cxf end point, so this:
import org.apache.camel.component.cxf.CxfEndpoint;
I have seen some configuration setting for a conduit, but I am trying to do
this programatically (the routes are dynamically created based on database
configuration). So I have
I would like to use HTTP basic authentication when making a web service call
using CXF.
This is basically my code.
CxfEndpoint cxfEndpoint = new CxfEndpoint(app.getMessageServiceUrl(),
camelContext);
cxfEndpoint.setServiceClass(PartnerSMSService.class.getCanonicalName());
RouteDefinition def = fr
Thanks Claus, 2.9 is not officially released yet is it?
Sorry have another question. If I was to use this to schedule messages would
I be able to hold many messages, (eg. 1000), or does it hold onto a thread
and so would cause me performance problems?
Would it be better to use something like qua
I am using camel 2.8 and can't seem to get asynchronous delaying of messages
working.
This is my sample code. The checkDelay method delays the first message for
10 seconds and does not delay the following messages.
from("activemq:sandbox:sendqueue").routeId("Test Route")
.process(setInternalM
Thanks for the reply. I have spent more time on this and think it is to do
with the PDUReaderworker in SMPPSession. When a session is created it
constructs a thread pool on readers.
In some cases these threads are not being destroyed when the session is
closed after each attempt to reconnect. I su
I have been looking into this further. Below is the log while it is trying to
connect to the SMS-C.
I actually think it might be constantly reconnecting, even though it may not
need to. So it may actually be the SMPPProducer.
It attempts twice each time. The first one receives a negative bind res
2.8
--
View this message in context:
http://camel.465427.n5.nabble.com/Unreleased-thread-possible-in-SMPP-component-tp4922901p4928632.html
Sent from the Camel - Users mailing list archive at Nabble.com.
We are using the SMPP component to integrate our messaging platform with
SMS-Cs. I have found that we occasionally get a massive rise in number of
threads in the system.
It would go from around 300 threads used with a steady rise up to over 5,000
threads.
Looking at when this occurs I think it is
Have found that this may have been caused by having optimizeAcknowledge set
to true. Now that is false I am pretty sure that all get cleared.
--
View this message in context:
http://camel.465427.n5.nabble.com/Messages-remaining-inflight-after-processing-tp4878148p4878345.html
Sent from the Camel
I have several situations where I have a route that is processing messages
off a queue, but after processing the message remains in flight, such that
if the application is restarted that message gets processed again. Is there
any way of of forcing an acknowledgement back to the queue to make sure t
I have moved up to the version 2.8 of the SMPP component but it causes a null
pointer whenever I send a message.
I have tracked it down to SmppProducer calling session.submitShortMessage
passing in submitSm.getOptionalParametes().
In SmppBinding these optional parameters are set if the message is
Thank you for your responses. I have ended up implementing my own that throws
an exception and then retries until the quota is changed at which point the
messages are released.
--
View this message in context:
http://camel.465427.n5.nabble.com/Unable-to-change-throttle-with-inflight-messages-tp47
I would like to be able to change the throttle value dynamically based on a
some setting.
I have created a bean that returns this value, so it basically looks like
this.
def.throttle(bean("applicationService",
"getApplicationChannelQuota")).timePeriodMillis(DAY_IN_MILLI_SECONDS)
We are essential
16 matches
Mail list logo