Hello @Bouare F.
First of all look for the PurePath Hotspots and the main contributors to the transaction. 120 seconds or 2 minutes means something is configured for the timeout purpose.
Secondly, there is a huge inter-tier time between two Java apps/tiers, therefore, we will have to understand this time further during the analysis.
In general this looks like waiting for SOAP response. Until transaction went back, thread is on waiting state. If SOAP was responded fast, check how much time was taken between starting execution on your application side and reaching soap service. It may be issue with application. I suggest as well CPU sampling during loadtest.