You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2012/09/24 22:14:08 UTC
[jira] [Updated] (DERBY-5848) Starting and stopping server leaves
ASCII NULL garbage in derby.log
[ https://issues.apache.org/jira/browse/DERBY-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5848:
----------------------------------
Issue & fix info: Newcomer,Repro attached (was: Repro attached)
Urgency: Normal
Labels: derby_triage10_10 (was: )
> Starting and stopping server leaves ASCII NULL garbage in derby.log
> -------------------------------------------------------------------
>
> Key: DERBY-5848
> URL: https://issues.apache.org/jira/browse/DERBY-5848
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.9.1.0
> Environment: Solaris 11 x64, Java 1.7.0_05
> Reporter: Dag H. Wanvik
> Priority: Minor
> Labels: derby_triage10_10
> Attachments: repro.sh
>
>
> I see two instances (one qua derby.log, one qua console?) of
> ----------------------------------------------------------------
> Thu Jul 05 13:35:46 CEST 2012: Shutting down Derby engine
> ----------------------------------------------------------------
> in derby.log, but between them I see 4148 ASCII null characters.
> Enclosing repro script. Notice that the failed connect attempt between the server start and shutdown is required to see this effect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira