Created attachment 524023 [details] CPU usage all threads I realized that message delivery and consumption takes inappropriate time while EAP server's HW and MRG server's HW show only low utilization (EAP ~10% CPU usage, MRG ~5% CPU usage and ~22% IO wait). I run a test (for steps to run the test see bug no. 739898) with jProfiler installed and realized that ThreadPoolExecutor and its workers are blocked or waiting almost all the time. My suspicion is that there is a synchronization lock between individual threads preventing them to process messages in parallel. Attached is jProfiler's snapshot and screenshots from it. Unfortunatelly, given my schedule on the project, I'm not able to go any further in the analysis unless I have extra time.
Created attachment 524024 [details] CPU usage waiting threads
Created attachment 524025 [details] CPU usage blocked threads
Created attachment 524026 [details] Threads activity
Created attachment 524027 [details] Thread locks
Created attachment 524028 [details] jProfiler 6.2.2 snapshot
This would be a JMS client issue as the JCA adapter does not control or influence in anyway the behavior of IoReceiver and it's associated classes. Further, we do not pool JMS sessions on inbound delivery so a synchronization issue would not be in the adapter itself. As a result, I am changing the component of this bug to quid-java. I am also changing the target milestone as this is going to require more analysis and work that the 2.0.4 time frame allows at this point.
Latest performance results are here - https://docspace.corp.redhat.com/docs/DOC-88691 Now I work on freash jProfiler report. PM should decide whether these numbers are sufficient, however, it they do not comply with our PRD.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.