[
https://issues.apache.org/jira/browse/DERBY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramin Moazeni updated DERBY-1272:
---------------------------------
Attachment: DERBY-1272v5.diff
Attaching a new patch built on top of the latest trunk.
Please note that I added the ${derby.tools.src.dir} to the
java/engine/org/apache/derby/iapi/build.xml to get the src to compile instead of
java/engine/org/apache/derby/impl/services/build.xml and
java/engine/org/apache/derby/iapi/types/build.xml since I was still
getting the following errors:
[javac] Found 2 semantic errors compiling
"/home/ramin/opensource/derby/trunk/java/engine/org/apache/derby/impl/services/monitor/BaseMonitor.java":
[javac] 1945.
org.apache.derby.tools.sysinfo.getInfo(systemStreams.stream().getPrintWriter());
[javac] ^--------------------^
[javac] *** Semantic Error: "tools" is either a misplaced package name or a
non-existent entity. An expression name is expected in this context.
[javac] 1947.
org.apache.derby.tools.sysinfo.getInfo(getTempWriter());
[javac] ^--------------------^
[javac] *** Semantic Error: "tools" is either a misplaced package name or a
non-existent entity. An expression name is expected in this context.
With the v5 patch, I am not able to reproduce this issue on Linux and WinXP. I
ran the test using
classes and jars, sane and insane and they all completed successfully without
any errors.
I appreciate your feedback.
Thanks
Ramin
> Change sysinfo to print to error log (derby.log) on boot of derby if
> derby.stream.error.logSeverityLevel=0
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1272
> URL: https://issues.apache.org/jira/browse/DERBY-1272
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.1.2.1, 10.1.3.1, 10.2.1.6
> Reporter: Kathey Marsden
> Assignee: Ramin Moazeni
> Priority: Minor
> Attachments: derby-1272-pre.diff, derby-1272-pre2.diff,
> derby-1272-pre3.diff, derby-1272-v4.diff, DERBY-1272v5.diff
>
>
> It is often very difficult to collect correct sysinfo output from user
> environments because sysinfo run from the commandline does not have the same
> classpath as the jvm that started Derby or Derby was loaded with a custom
> classloader.
> It would be very helpful in assisting users in diagnosing their issues if
> sysinfo dumped to the error log if derby.stream.error.logSeverityLevel=0 or
> even by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
