How to increase autolock timeout on azure service bus using camel
up vote
0
down vote
favorite
I am using azure service bus for my project. I was able to establish the connection through camel amqp following this link Accessing Azure Service Bus with Apache Camel?
Now I am able to read the messages through the service bus queue, but I am having issues in increasing the auto-timeout lock for the messages. I have the set the timeout lock to be 30 seconds in the service bus properties, but for certain messages who need more time I want the time to extend.
I looked for solution online, but couldn't find anything that resolved the issue. I was trying to use backoffmultiplier() available with camel but it failed too.
Below is my implementation of what I have tried so far.
The URI to connect to the queue where I have specified requestTimeout and requestTimeoutChecker
QUEUE_CONNECTION=amqp:queue:testqueue?requestTimeout=4000&requestTimeoutCheckerInterval=3000&acknowledgementModeName=CLIENT_ACKNOWLEDGE&concurrentConsumers=2
The exception handling where I have used backoffmultiplier
onException(Exception.class).
process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Exception.class);
logger.error("Exception in exchange : ",cause);
// we now have the caused exception
}
}).useExponentialBackOff().backOffMultiplier(2).maximumRedeliveries(3);
Am I missing anything here? TIA.
add a comment |
up vote
0
down vote
favorite
I am using azure service bus for my project. I was able to establish the connection through camel amqp following this link Accessing Azure Service Bus with Apache Camel?
Now I am able to read the messages through the service bus queue, but I am having issues in increasing the auto-timeout lock for the messages. I have the set the timeout lock to be 30 seconds in the service bus properties, but for certain messages who need more time I want the time to extend.
I looked for solution online, but couldn't find anything that resolved the issue. I was trying to use backoffmultiplier() available with camel but it failed too.
Below is my implementation of what I have tried so far.
The URI to connect to the queue where I have specified requestTimeout and requestTimeoutChecker
QUEUE_CONNECTION=amqp:queue:testqueue?requestTimeout=4000&requestTimeoutCheckerInterval=3000&acknowledgementModeName=CLIENT_ACKNOWLEDGE&concurrentConsumers=2
The exception handling where I have used backoffmultiplier
onException(Exception.class).
process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Exception.class);
logger.error("Exception in exchange : ",cause);
// we now have the caused exception
}
}).useExponentialBackOff().backOffMultiplier(2).maximumRedeliveries(3);
Am I missing anything here? TIA.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using azure service bus for my project. I was able to establish the connection through camel amqp following this link Accessing Azure Service Bus with Apache Camel?
Now I am able to read the messages through the service bus queue, but I am having issues in increasing the auto-timeout lock for the messages. I have the set the timeout lock to be 30 seconds in the service bus properties, but for certain messages who need more time I want the time to extend.
I looked for solution online, but couldn't find anything that resolved the issue. I was trying to use backoffmultiplier() available with camel but it failed too.
Below is my implementation of what I have tried so far.
The URI to connect to the queue where I have specified requestTimeout and requestTimeoutChecker
QUEUE_CONNECTION=amqp:queue:testqueue?requestTimeout=4000&requestTimeoutCheckerInterval=3000&acknowledgementModeName=CLIENT_ACKNOWLEDGE&concurrentConsumers=2
The exception handling where I have used backoffmultiplier
onException(Exception.class).
process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Exception.class);
logger.error("Exception in exchange : ",cause);
// we now have the caused exception
}
}).useExponentialBackOff().backOffMultiplier(2).maximumRedeliveries(3);
Am I missing anything here? TIA.
I am using azure service bus for my project. I was able to establish the connection through camel amqp following this link Accessing Azure Service Bus with Apache Camel?
Now I am able to read the messages through the service bus queue, but I am having issues in increasing the auto-timeout lock for the messages. I have the set the timeout lock to be 30 seconds in the service bus properties, but for certain messages who need more time I want the time to extend.
I looked for solution online, but couldn't find anything that resolved the issue. I was trying to use backoffmultiplier() available with camel but it failed too.
Below is my implementation of what I have tried so far.
The URI to connect to the queue where I have specified requestTimeout and requestTimeoutChecker
QUEUE_CONNECTION=amqp:queue:testqueue?requestTimeout=4000&requestTimeoutCheckerInterval=3000&acknowledgementModeName=CLIENT_ACKNOWLEDGE&concurrentConsumers=2
The exception handling where I have used backoffmultiplier
onException(Exception.class).
process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Exception.class);
logger.error("Exception in exchange : ",cause);
// we now have the caused exception
}
}).useExponentialBackOff().backOffMultiplier(2).maximumRedeliveries(3);
Am I missing anything here? TIA.
asked Nov 8 at 17:15
Nikhil Jain
319112
319112
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53212921%2fhow-to-increase-autolock-timeout-on-azure-service-bus-using-camel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown