[
https://issues.apache.org/jira/browse/DERBY-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-3251:
--------------------------------------
Urgency: Normal
Labels: derby_triage10_8 (was: )
> NetworkServerTestSetup.startSeparateProcess() can end up with the server
> stalled.
> ---------------------------------------------------------------------------------
>
> Key: DERBY-3251
> URL: https://issues.apache.org/jira/browse/DERBY-3251
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.1.4, 10.4.1.3
> Reporter: Daniel John Debrunner
> Priority: Minor
> Labels: derby_triage10_8
>
> NetworkServerTestSetup.startSeparateProcess() starts up the server but
> provides no threads to read the streams that the server will write to.
> I think this can end up with the server process blocking if the buffer
> underlying the streams fills up, ie. if the server writes too much output.
> The old test harness code contains BackgroundStreamDrainer class that could
> be used (or cleaned up and brought into o.a.derbytesting.junit) to fulfill
> the need.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
