Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Please allow Java debugging as a permanent development tool again - or allow debugging only for http task
Background for our request: We develop XPages-based applications with a large Java framework with a larger development team. Up to Domino 10 we have used the Java Debugging on a regular basis many times a day, therefore on all of our development we had enabled the Java debugging using the following ini files:
>> JavaDebugOptions=transport=dt_socket,server=y,suspend=n,address=8000 (or other ports)
Current situation: Starting with Domino 11 beta versions the Domino server crashes after 2-3 minutes if this debug parameters are set in notes.ini. We have discussed this issue with the HCL support (case CS0104024) and were informed about the following knowledge base article: https://hclpnpsupport.hcltech.com/csm?id=kb_article&sysparm_article=KB0076859
Our problem: So with this solution we have to start the server without Java debugging enabled, then stop http task, enable debug, restart http again and disable debug parameters in good time before restarting the server to prevent the server crash after restart. This is extremely unsatisfactory for us, since we have to restart the server every now and then.
Our wish is to either have the behavior from Domino 9 / Domino 10 back, or to have HTTPJavaDebugOptions parameter only for http task as requested in https://domino-ideas.hcltechsw.com/ideas/DDXP-I-448