Changes for page Debugging
Last modified by Simon Urli on 2023/10/10 11:46
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. ThomasMortagne1 +xwiki:XWiki.VincentMassol - Content
-
... ... @@ -323,7 +323,7 @@ 323 323 324 324 If you get the following exception, it can mean that you're on Mac and that your ##tools.jar## is not added to the classpath. Apparently ##bminstall.sh## thinks that if you're on Mac then you don't need ##tools.jar## which is apparently wrong nowadays. 325 325 326 -{{code language= "none"}}326 +{{code language='none'}} 327 327 Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/tools/attach/AttachNotSupportedException 328 328 at java.lang.Class.getDeclaredMethods0(Native Method) 329 329 at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) ... ... @@ -342,7 +342,7 @@ 342 342 343 343 In this case, edit ##bminstall.sh## and add the following line below the ##OS=`uname`## line in order to override it: 344 344 345 -{{code language= "none"}}345 +{{code language='none'}} 346 346 OS=whatever 347 347 {{/code}} 348 348 ... ... @@ -393,6 +393,6 @@ 393 393 394 394 = Analyze Out Of Memory issues = 395 395 396 -You can enable automatic memory dump when using ##-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/where/to/save/the/memory/dumps## which will generate a memory dump as soon as Java detect an Out Of memory error.See https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/clopts001.html#CHDFDIJI for more details.396 +You can enable automatic memory dump when using ##-XX:+HeapDumpOnOutOfMemoryError## which will generate a memory dump as soon as Java detect an Out Of memory error. 397 397 398 398 Since 7.2RC1 the option is enabled by default in Jetty based distributions and the memory dump will ends up in ##data/## folder.