J visual vm is complaining of deadlock since upgrading to the 2.4.4_16 from _06 and using setting
-Dobjectdb.temp.no-resize-clear=true
The only other change is that we no longer create recovery or replay files as we were not using these.
i have attached our full server strack trace.
if you could advise that would be great.
Dan
Thank you for this report. Build 2.4.4_17 should fix this deadlock.
could we have some more details as to what has changed and what caused the deadlock? we would like to use this in production but i think at this time we need to understand a little better if it safe to do so or not.
A synchronized that was added in build 2.4.4_10 to fix another problem caused the deadlock.
All builds pass the same tests before release, but that deadlock was not detected.
Before using any build in production it is highly recommended to test it with you application extensively.