@@ -96,17 +96,16 @@ This is meant to protect the target resource from being accessed from too many t
9696the same time, similar to the effect of a pool size limit for a thread pool or a
9797connection pool that blocks access if its limit is reached.
9898
99- You may optionally set the limit to 1 , effectively locking access to the target bean
99+ You may optionally set the limit to `1` , effectively locking access to the target bean
100100instance:
101101
102102[source,java,indent=0,subs="verbatim,quotes"]
103103----
104- @ConcurrencyLimit(1) // <1>
104+ @ConcurrencyLimit(1)
105105public void sendNotification() {
106106 this.jmsClient.destination("notifications").send(...);
107107}
108108----
109- <1> 1 is the default, but specifying it makes the intent clearer.
110109
111110Such limiting is particularly useful with Virtual Threads where there is generally no
112111thread pool limit in place. For asynchronous tasks, this can be constrained on
@@ -116,6 +115,9 @@ For synchronous invocations, this annotation provides equivalent behavior throug
116115which has been available since Spring Framework 1.0 for programmatic use with the AOP
117116framework.
118117
118+ TIP: `@ConcurrencyLimit` also has a `limitString` attribute that provides property
119+ placeholder and SpEL support, as an alternative to the `int` based examples above.
120+ 119121
120122[[resilience-annotations-configuration]]
121123== Enabling Resilient Methods
0 commit comments