[
https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890340#comment-17890340
]
Jacques Le Roux commented on OFBIZ-13153:
-----------------------------------------
Hi Mayank ,
As synchronizng a whole method can have side effects, I'd suggest to start a
thread in [dev ML|https://ofbiz.apache.org/mailing-lists.html] before blindly
applying this change to OOTB code, TIA
> "null DispatchContext" issue under high load and concurrency
> ------------------------------------------------------------
>
> Key: OFBIZ-13153
> URL: https://issues.apache.org/jira/browse/OFBIZ-13153
> Project: OFBiz
> Issue Type: Bug
> Components: framework/service
> Affects Versions: 18.12.16
> Environment: Virtual Machine:
> OS: RHEL 8.9
> VCPU: 16
> Total RAM: 64 GB
> Heap allocation (Xmx): 8 GB
> Reporter: Mayank S
> Priority: Major
> Labels: performance
> Fix For: 18.12.17
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> While performance-testing Ofbiz 18 under high load (200 concurrent users), we
> have observed an intermittent error, stating "null DispatchContext".
> While doing more analysis, we realized it is a thread-safety issue, and it
> was fixed by adding the 'synchronized' keyword to the following method
> signatures in ServiceDispatcher.java:
> public static synchronized getInstance (Delegator delegator)
> public static synchronized void register (DispatchContext context)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
