[DERBY-4715] Write jvm information and path of derby.jar to derby.log - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: 10.6.1.0
Fix Version/s: 10.5.3.1, 10.6.2.1, 10.7.1.1
Component/s: Miscellaneous
Labels:
None

Issue & fix info:

Newcomer, Patch Available
Bug behavior facts:

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

- Sort By Name
- Sort By Date
- Ascending
- Descending

derby.log
02/Jul/10 04:47
1 kB
Lily Wei
DERBY-4715-1.diff
02/Jul/10 04:47
6 kB
Lily Wei
DERBY-4715-10.5_967304.diff
03/Aug/10 15:20
20 kB
Lily Wei
DERBY-4715-10.6_967304.diff
03/Aug/10 15:20
21 kB
Lily Wei
DERBY-4715-2.diff
07/Jul/10 06:23
19 kB
Lily Wei
DERBY-4715-3.diff
10/Jul/10 04:52
19 kB
Lily Wei
DERBY-4715-4.diff
12/Jul/10 21:11
19 kB
Lily Wei
DERBY-4715-5.diff
13/Jul/10 16:16
19 kB
Lily Wei
DERBY-4715-6.diff
20/Jul/10 16:15
3 kB
Lily Wei
DERBY-4715-7.diff
21/Jul/10 15:48
3 kB
Lily Wei
DERBY-4715-8.diff
21/Jul/10 19:27
3 kB
Lily Wei

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

Activity

People

Assignee:: Lily Wei

Reporter:: Lily Wei

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Dates

Created:: 25/Jun/10 15:47

Updated:: 15/Dec/10 13:44

Resolved:: 24/Jul/10 00:19