-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corrupted domain.xml after configuration changes PAYARA-3880 #3992
Comments
Internal bug ID PAYARA-3880 |
#4002 will address creation of This could mean that there is a less visible issue when |
Domain,xml gets corrupted not just when editing a existing parameter, the problem occurs even when adding new parameter. I tried to add a new jvm option via admin gui in payara 5.192 and the server failed to restart. Just to verify, i tried adding the same jvm option from command line (asadmin) in a clean new instance of 5.192 and it worked great. |
@pkumar72 Your observation fits the exceptions. The issue is located in the processing applied when changing JVM options though the GUI. Since any change will process all options the problem also occurs for exiting options matching the requirements to trigger the issue. |
Another note: while my comment #3992 (comment) should still be valid I did have problems reproducing the EOL issue after #4002 was merged. |
Glad this is getting fixed... in my particular case, it was jvm option -XX:NewRatio=2. After saving changes (using the admin GUI), this option was getting changed to [9|]--add-exports:-XX:NewRatio=2. After changing it back, the EOL error went away. |
This was fixed on 5.193 any further issues raise a new issue. |
After changing -Xmx512m to -Xmx1024m, for example, the admin console saves to configuration entries: -Xmx512m & -Xmx1024m=. If I try to remove one of the entries the following exception is thrown
Environment
The text was updated successfully, but these errors were encountered: