Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

You can append query options to the URI in the following format: ?option=value&option=value&…

Options

...

Name

Since

Default

Description

size

 

 

The maximum capacity of the SEDA queue (i.e.,

...

the

...

number

...

of

...

messages

...

it

...

can

...

hold).

...

The

...

default

...

value

...

in

...

Camel

...

2.2

...

or

...

older

...

is

...

1000

...

.

...

From

...

Camel

...

2.3

...

onwards,

...

the

...

size

...

is

...

unbounded

...

by

...

default.

...

Notice:

...

Mind

...

if

...

you

...

use

...

this

...

option,

...

then

...

its

...

the

...

first

...

endpoint

...

being

...

created

...

with

...

the

...

queue

...

name,

...

that

...

determines

...

the

...

size.

...

To

...

make

...

sure

...

all

...

endpoints

...

use

...

same

...

size,

...

then

...

configure

...

the

...

size

...

option

...

on

...

all

...

of

...

them,

...

or

...

the

...

first

...

endpoint

...

being

...

created.

...

From

...

Camel

...

2.11

...

onwards,

...

a

...

validation

...

is

...

taken

...

place

...

to

...

ensure

...

if

...

using

...

mixed

...

queue

...

sizes

...

for

...

the

...

same

...

queue

...

name,

...

Camel

...

would

...

detect

...

this

...

and

...

fail

...

creating

...

the

...

endpoint.

...

concurrentConsumers

 

1

Number of concurrent threads processing exchanges.

waitForTaskToComplete

 

IfReplyExpected

Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: Always, Never or IfReplyExpected. The first two values are self-explanatory. The last value, IfReplyExpected, will only wait if the message is Request Reply based. The default option is IfReplyExpected. See more information about Async messaging.

timeout

 

30000

Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See waitForTaskToComplete and Async for more details. In Camel 2.2 you can now disable timeout by using 0 or a negative value.

multipleConsumers

2.2

false

Specifies whether multiple consumers are allowed. If enabled, you can use SEDA for Publish-Subscribe messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint.

limitConcurrentConsumers

2.3

true

Whether to limit the number of concurrentConsumers to the maximum of 500. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off.

blockWhenFull

2.9

false

Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted. By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted.

queueSize

2.9

 

Component only: The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if size is not in use.

pollTimeout

2.9.3

1000

Consumer only – The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown.

purgeWhenStopping

2.11.1

false

Whether to purge the task queue when stopping the consumer/route. This allows to stop faster, as any pending messages on the queue is discarded.

queue

2.12.0

null

Define the queue instance which will be used by seda endpoint

queueFactory

2.12.0

null

Define the QueueFactory which could create the queue for the seda endpoint

failIfNoConsumers

2.12.0

false

Whether the producer should fail by throwing an exception, when sending to a SEDA queue with no active consumers.

Choosing BlockingQueue implementation

...