cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] Commented: (CXF-2002) Server async jms transport needs dynamic mechanism to throttle message consumption
Date Sat, 24 Jan 2009 12:49:59 GMT


Christian Schneider commented on CXF-2002:

We are currently using the Spring DefaultMessageListenerContainer.
It supports setting the maxConcurrentConsumers to limit the number of listener threads.

It start a task for each message with the SimpleAsyncTaskExecutor.
This will by default start an unlimited number of threads. But you can set a limit by using
the concurrencyLimit property. Currently this can only be set by using the new config style
JmsConfigurationFeature and injecting a SimpleAsyncTaskExecutor.

When using the old config style setting the concurrencyLimit is not possible. I will add a
JmsConfiguration property for this that can be also be set by using the sessionPool highWaterMark
in the old config style.

Do you think this will solve the problem?

> Server async jms transport needs dynamic mechanism to throttle message consumption
> ----------------------------------------------------------------------------------
>                 Key: CXF-2002
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.0.10
>            Reporter: Ron Gavlin
> Currently, the server-side async jms transport has no mechanism to throttle consumption
of incoming messages. This becomes problematic in scenarios where a large backlog of messages
exists on the input queue. In this case, it is likely that the cxf server will overload its
internal work item queues resulting in problems. A dynamic throttling mechanism on the async
jms server is required to avoid this problem.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message