...
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Property | Type | Description |
|---|
| beanstalk.jobId | long | Job ID | | beanstalk.tube | string | the name of the tube that contains this job | | beanstalk.state | string | “ready” or “delayed” or “reserved” or “buried” (must be “reserved”) | | beanstalk.priority | long | the priority value set | | beanstalk.age | int | the time in seconds since the put command that created this job | | beanstalk.time-left | int | the number of seconds left until the server puts this job into the ready queue | | beanstalk.timeouts | int | the number of times this job has timed out during a reservation | | beanstalk.releases | int | the number of times a client has released this job from a reservation | | beanstalk.buries | int | the number of times this job has been buried | | beanstalk.kicks | int | the number of times this job has been kicked |
|
Examples
This Camel component lets you both request the jobs for processing and supply them to Beanstalkd daemon. Our simple demo routes may look like
| Code Block |
|---|
from("beanstalk:testTube").
log("Processing job #${property.beanstalk.jobId} with body ${in.body}").
process(new Processor() {
@Override
public void process(Exchange exchange) {
// try to make integer value out of body
exchange.getIn().setBody( Integer.valueOf(exchange.getIn().getBody(classOf[String])) );
}
}).
log("Parsed job #${property.beanstalk.jobId} to body ${in.body}"); |
| Code Block |
|---|
from("timer:dig?period=30seconds").
setBody(constant(10)).log("Kick ${in.body} buried/delayed tasks").
to("beanstalk:testTube?command=kick"); |
In the first route we are listening for new jobs in tube “testTube”. When they are arriving, we are trying to parse integer value from the message body. If done successful, we log it and this successful exchange completion makes Camel component to delete this job from Beanstalk automatically. Contrary, when we cannot parse the job data, the exchange failed and the Camel component buries it by default, so that it can be processed later or probably we are going to inspect failed jobs manually.
So the second route periodically requests Beanstalk to kick 10 jobs out of buried and/or delayed state to the normal queue.
| Include Page |
|---|
| Endpoint See Also |
|---|
| Endpoint See Also |
|---|
|
