You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Adam Lukaszewski (Jira)" <ji...@apache.org> on 2023/05/19 09:12:00 UTC
[jira] [Updated] (CAMEL-19373) [spring-rabbitmq] Component does not Respect replyTimeout for InOut Exchanges
[ https://issues.apache.org/jira/browse/CAMEL-19373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lukaszewski updated CAMEL-19373:
-------------------------------------
Description:
Hi folks,
I think I found a bug in the spring-rabbitmq component. It seems that the *replyTimeout* settings (neither path nor spring properties) will be accepted by the component. I have create a [sample project|https://github.com/adamlukaszewski/spring-camel-rabbit-reply-timeout] for you to show the issue. The route is very simple:
{code}
public void configure() throws Exception {
from("timer:hello?repeatCount=1")
.transform(simple("Random number ${random(0,100)}"))
.log(LoggingLevel.ERROR,
">>>>>>> Timeout of replay should happen after 10 secs (application.properties) or 15 secs as " +
"here configured")
.to(ExchangePattern.InOut, "spring-rabbitmq:foo?routingKey=mykey&replyTimeout=15000");
}
{code}
I expect that the listener will throw a "Reply timed out" AmqpReplyTimeoutException after 15 seconds (or 10 seconds as defined in the [application.properties|http://application.properties/]). What is happening:
!image.png!
You see that after 30 secs the exception occurred. It seems that we are hitting here the default configurations of Spring AMQ instead the setup configurations.
!imageaa.png!
was:
Hi folks,
I think I found a bug in the spring-rabbitmq component. It seems that the *replyTimeout* settings (neither path nor spring properties) will be accepted by the component. I have create a [sample project|https://github.com/adamlukaszewski/spring-camel-rabbit-reply-timeout] for you to show the issue. The route is very simple:
{code}
public void configure() throws Exception {
from("timer:hello?repeatCount=1")
.transform(simple("Random number ${random(0,100)}"))
.log(LoggingLevel.ERROR,
">>>>>>> Timeout of replay should happen after 10 secs (application.properties) or 15 secs as " +
"here configured")
.to(ExchangePattern.InOut, "spring-rabbitmq:foo?routingKey=mykey&replyTimeout=15000");
}
{code}
I expect that the listener will throw a "Reply timed out" AmqpReplyTimeoutException after 15 seconds (or 10 seconds as defined in the [application.properties|http://application.properties/]). What is happening:
!image.png|thumbnail!
You see that after 30 secs the exception occurred. It seems that we are hitting here the default configurations of Spring AMQ instead the setup configurations.
!imageaa.png|thumbnail!
> [spring-rabbitmq] Component does not Respect replyTimeout for InOut Exchanges
> -----------------------------------------------------------------------------
>
> Key: CAMEL-19373
> URL: https://issues.apache.org/jira/browse/CAMEL-19373
> Project: Camel
> Issue Type: Bug
> Affects Versions: 3.20.4
> Reporter: Adam Lukaszewski
> Priority: Major
> Attachments: image.png, imageaa.png
>
>
> Hi folks,
> I think I found a bug in the spring-rabbitmq component. It seems that the *replyTimeout* settings (neither path nor spring properties) will be accepted by the component. I have create a [sample project|https://github.com/adamlukaszewski/spring-camel-rabbit-reply-timeout] for you to show the issue. The route is very simple:
> {code}
> public void configure() throws Exception {
> from("timer:hello?repeatCount=1")
> .transform(simple("Random number ${random(0,100)}"))
> .log(LoggingLevel.ERROR,
> ">>>>>>> Timeout of replay should happen after 10 secs (application.properties) or 15 secs as " +
> "here configured")
> .to(ExchangePattern.InOut, "spring-rabbitmq:foo?routingKey=mykey&replyTimeout=15000");
> }
> {code}
> I expect that the listener will throw a "Reply timed out" AmqpReplyTimeoutException after 15 seconds (or 10 seconds as defined in the [application.properties|http://application.properties/]). What is happening:
> !image.png!
> You see that after 30 secs the exception occurred. It seems that we are hitting here the default configurations of Spring AMQ instead the setup configurations.
> !imageaa.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)