Comments on: 2 Common Concurrency Pitfalls in AEM and How to Avoid Them
https://blogs.perficient.com/2017/12/05/2-common-concurrency-pitfalls-in-aem-and-how-to-avoid-them/
Expert Digital InsightsTue, 19 Nov 2019 18:21:53 +0000
hourly
1
By: Dan Klco
https://blogs.perficient.com/2017/12/05/2-common-concurrency-pitfalls-in-aem-and-how-to-avoid-them/#comment-18530
Tue, 19 Nov 2019 18:21:53 +0000https://blogs.perficient.com/adobe/?p=12455#comment-18530In reply to Zey.
@Zey,
Wouldn’t that be great if it were the case. Unfortunately, OSGi services are not thread-safe. You can use synchronization to make operations within a service thread safe, but not directly via OSGi.
]]>
By: Zey
https://blogs.perficient.com/2017/12/05/2-common-concurrency-pitfalls-in-aem-and-how-to-avoid-them/#comment-18529
Tue, 19 Nov 2019 11:29:18 +0000https://blogs.perficient.com/adobe/?p=12455#comment-18529The concurrency issues don’t exist if OSGi services/components are thread safe. I believe a OSGi service can be obtained by a thread/caller at a time.
]]>