You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mayank S (Jira)" <ji...@apache.org> on 2024/11/01 06:02:00 UTC
[jira] [Commented] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
[ https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894774#comment-17894774 ]
Mayank S commented on OFBIZ-13153:
----------------------------------
Hi, its the festive season in India and I am on vacation. Will revert as soon as I am back to work and able to check this configuration.
> "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)