[ http://issues.apache.org/jira/browse/DERBY-982?page=all ]
Andrew McIntyre updated DERBY-982:
----------------------------------
Attachment: derby-982-v4.diff
Helps to read the javadoc. From the doc for PipedReader: "Attempting to use
both objects from a single thread is not recommended, as it may deadlock the
thread."
And that's what was happening on my machine. So, attaching updated patch which
spawns a new thread to read the information from sysinfo.getInfo(), and reads
and verifies the first line. Not a great test, but better than nothing.
If there is no negative feedback, I plan to commit this patch 7/18 or 7/19.
> sysinfo api does not provide genus name for client
> --------------------------------------------------
>
> Key: DERBY-982
> URL: http://issues.apache.org/jira/browse/DERBY-982
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.1.2.1
> Reporter: Kathey Marsden
> Assigned To: Andrew McIntyre
> Fix For: 10.2.0.0
>
> Attachments: derby-982-v4.diff, derby-982.diff, derby-982_v2.diff,
> derby-982_v3.diff
>
>
> The sysinfo api does not provide access to the genus name for client to allow
> applications to retrieve information from sysinfo about the client
> information.
> http://db.apache.org/derby/javadoc/publishedapi/org/apache/derby/tools/sysinfo.html
> Note: Currently ProductGenusNames has a genus name for network server but
> network server is closely tied to the engine so should always have the same
> version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
