-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
If standalone/data/kernel/process-uuid (for standalone mode) exists but is empty, startup fails with:
java.util.NoSuchElementException: No value present at java.util.Optional.get(Optional.java:135) at org.jboss.as.controller.operations.common.ProcessEnvironment.obtainPr ocessUUID(ProcessEnvironment.java:188) at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:632)
If it exists but does not contain a valid UUID startup fails with the only slightly better:
java.lang.IllegalArgumentException: Invalid UUID string: at java.util.UUID.fromString(UUID.java:194) at org.jboss.as.controller.operations.common.ProcessEnvironment.obtainProcessUUID(ProcessEnvironment.java:188) at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:632)
These failure conditions should be handled more gracefully, ideally by ignoring the bad data and proceeding the same as if the file did not exist, but at the minimum with a more useful error message telling the user specifically what is wrong (that the problem is a corrupted standalone/data/kernel/process-uuid file).
- clones
-
JBEAP-24716 [GSS](7.4.z) WFCORE-6290 - Failure to handle errors loading process-uuid file
- Closed
- is depended on by
-
JBEAP-24716 [GSS](7.4.z) WFCORE-6290 - Failure to handle errors loading process-uuid file
- Closed