Requirements: Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.,
,
Memory issues detection approach
Throttled mode of service load is most convenient way to identify memory leaks or another memory utilization issues. The utility https://github.com/khandramai/gatling-folio-performance for emulation of load regime was implemented based on load and performance testing framework Gatling.
In scope of this investigation cyclic CRUD operations in 25 threads during 4 hours was used as base load. Monitoring of service operating was carried out with using the VisualVM profiler.
Deep analysis of the memory utilization was performed with using Eclipse Memory Analyzer on the basis of memory dumps prepared in advance during the operation of the service (after 1 hour of service operating).
Founded issues
JMX reporting based on Dropwizard metrics
Description
TBD
Detailed investigation
Emulation of the load on local equipment showed the following results.
CPU/Heap utilization:
Heap dumps: mod-invoices.hprof, mod-invoices-storage.hprof.
Heap dumps analysis showed that problem relates to drop wizard metrics collecting. After manual disabling of metrics collecting load test passes successfully with the following CPU/Heap utilization during 4 hours:
mod-invoice
mod-invoice-storage
Heap dumps analysis showed that issue was fixed.
Summary
Disable Dropwizard metrics on production environment.