Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
10.6.1.0
-
None
-
Newcomer, Patch Available
-
Seen in production
Description
The bug is part of DERBY-1272. In production environment, derby.jar can be located different than the derbyclient.jar It can be easier if we have jvm version information and path of derby.jar are in the derby.log
Attachments
Attachments
Issue Links
- is part of
-
DERBY-1272 Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0
- Closed
- relates to
-
DERBY-4944 Embedded Derby does not start when derby.jar is dynamically uploaded / added to the classpath
- Closed