On Fri, Dec 2, 2011 at 2:27 AM, geemang wrote:
> I did a little experiment by adding
>
> private void initializeUDPServerSocketCommunicationLayer() throws
> Exception {
> ...
>
> connectionlessServerBootstrap.setOption("receiveBufferSizePredictorFactory",
> new FixedReceiveBufferSizePredictorFac
Hi
Can you post details of the Camel route? Does processing the mail take
a long time, so when the DELETE flag is to be set, the mail session
could eventually have timed out, and closed ?
On Thu, Dec 1, 2011 at 11:07 PM, awillia wrote:
> I am using imap to read messages from a folder and am get
I did a little experiment by adding
private void initializeUDPServerSocketCommunicationLayer() throws
Exception {
...
connectionlessServerBootstrap.setOption("receiveBufferSizePredictorFactory",
new FixedReceiveBufferSizePredictorFactory(1024));
...
}
to the NettyConsumer.java class
Which doe
I'm having the same problem, trying to receive messages that are over 768 in
size.
I found an article:
http://massapi.com/class/org/jboss/netty/channel/socket/nio/NioDatagramChannelFactory.java.html
that shows the setting I believe we need.
Also I believe there is a ticket open for this:
https://
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
Hi, I'm using a detour so that if a message has a "suscription" flag it then
connects to a database and creates an entry (in addition to the normal
processing of the message).
from("quickfix:marketdata.cfg").
filter(header(QuickfixjEndpoint.MESSAGE_TYPE_KEY).isEqualTo(MsgType.MARKET_DATA_REQUEST))
Now I have this error :
[che.camel.example.etl.Customer] ultPollingConsumerPollStrategy WARN
Consumer
Consumer[jpa://org.apache.camel.example.etl.Customer?consumeDelete=false&consumeLockEntity=false&delay=3000]
could not poll endpoint:
Endpoint[jpa://org.apache.camel.example.etl.Customer?consume
On Dec 1, 2011, at 11:07 AM, Claus Ibsen wrote:
> Hi
>
> Seems a bit odd, as using a Processor gives you directly access to the
> Exchange, so if you add an header on the Exchange, then it ought to be
> there, when the JmsProducer is invoked.
>
> Could you check whether the exchange has also an O
Thanks Claus,
I'll take a look at your link and give it a go.
Cheers, Tom
On Thu, Dec 1, 2011 at 7:03 AM, Claus Ibsen wrote:
> On Thu, Dec 1, 2011 at 10:10 AM, Tom Howe wrote:
>> Hi Claus,
>> Thanks for your response - I've never done this before, would you be
>> able to point me to some exampl
It's me again...
I was wondering that if I have Route and I have defined onException-method
to catch all exceptions, like:
routeDef.onException(Exception.class).Process(...Jaadi jaadi processing); It
does not catch exceptions happening in the polling endpoint... Is that
because I am doing somet
Hi Arkadi
Nice to see you at the Java Riga Day.
Congrat on this release. Seems like yet another valuerable Camel component.
You may consider adding a SipeConfiguration class or just
setter/getters on a SipeComponent.
Then people can configure once common configuration, if that makes sense.
Then
Hi
Seems a bit odd, as using a Processor gives you directly access to the
Exchange, so if you add an header on the Exchange, then it ought to be
there, when the JmsProducer is invoked.
Could you check whether the exchange has also an OUT message in the processor?
But it should really not have tha
On Thu, Dec 1, 2011 at 10:10 AM, Tom Howe wrote:
> Hi Claus,
> Thanks for your response - I've never done this before, would you be
> able to point me to some example code?
>
Camel uses the Spring Transaction API. So I would suggest to take a
look at that. And how to programmatically being/commi
On Thu, Dec 1, 2011 at 10:08 AM, Jason Dillon wrote:
> This does not really help, as if you set the retry on startup and it exceeds
> an exception is thrown and the route does not get added.
>
> I need to route to be added regardless if it can actually make a connection
> at the time of adding o
The exception seems to indicate the class is not an JPA entity. Does
the class have the JPA @Entity annotation.
On Thu, Dec 1, 2011 at 10:45 AM, Idriss wrote:
> I get this error :
>
>
> [el (camel) thread #4 - Threads] Tracer INFO
> ID-user-PC-62687-1322732337713-0-7 >>>
Ok, i found a workaround but i don't know if the solution is clean.
public class MySecondRoute extends RouteBuilder {
@Override
public void configure() throws Exception {
XStream xstream = new XStream();
xstream.setClassLoader(getCl
Hi !
I migrate a little project from Spring to Aries but i have a problem with my
Camel route and XStream.
This route works with Spring :
public class MyFirstRoute extends SpringRouteBuilder {
@Override
public void configure() throws Exception {
from("vm:repo")
I just created a JIRA[1] for it, and will commit a quick fix for it.
[1]https://issues.apache.org/jira/browse/CAMEL-4729
On Thu Dec 1 01:16:49 2011, Claus Ibsen wrote:
On Wed, Nov 30, 2011 at 2:26 PM, Willem Jiang wrote:
No, camel-seda component doesn't support to set the default queue size
Gert Vanthienen wrote
>
> I just raised https://issues.apache.org/jira/browse/CAMEL-4147 to keep
> track of this request.
>
Even in a Spring application in ServiceMix (4.3), this error can also occur.
This seems to be a race condition, when camel-core is not yet fully started
and an application
I get this error :
[el (camel) thread #4 - Threads] Tracer INFO
ID-user-PC-62687-1322732337713-0-7 >>> (route1)
org.apache.camel.example.etl.CustomerTransformer@ea213 -->
jpa://org.apache.camel.example.etl.Customer2 <<< Pattern:InOnly,
Headers:{breadcrumbId=ID-user-PC-626
Hi
Yeah the wording could be improved. Any recommendation?
On Thu, Dec 1, 2011 at 12:28 AM, Jason Dillon wrote:
> Any reason why these are at INFO level in DefaultCamelContext?
>
>
> if (doNotStartRoutesOnFirstStart) {
> log.info("Cannot start routes as CamelContext has been configured with
Hi Claus,
Thanks for your response - I've never done this before, would you be
able to point me to some example code?
Thanks, Tom
On Wed, Nov 30, 2011 at 7:53 AM, Claus Ibsen wrote:
> On Wed, Nov 30, 2011 at 5:06 PM, Tom Howe wrote:
>> Hi,
>>
>> If I want to consumer from a queue using Polling
Yes, I know how to make it work... but I was confused why the configuration for
these parameters was not like all of the other parameters for the component.
... and really this response doesn't answer that. Why is this configuration
different than everything else?
--jason
On Nov 30, 2011, at
This does not really help, as if you set the retry on startup and it exceeds an
exception is thrown and the route does not get added.
I need to route to be added regardless if it can actually make a connection at
the time of adding or not. The connectivity to the jms endpoint may or may not
be
25 matches
Mail list logo
