db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-3701) java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept connections and client hang if tracing is turned on but traceDirectory does not exist
Date Mon, 25 Aug 2008 15:21:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625396#action_12625396
] 

myrna edited comment on DERBY-3701 at 8/25/08 8:20 AM:
--------------------------------------------------------------------

If I understand correctly, the backport to older branches still represents a change from earlier
behavior of older releases off those branches in that now a warning/error message will come
to derby.log (although the dirs still do not get created).

The one reason why I think we might want to have a release note mentioning that is that derby.log
can get really big that way.

      was (Author: myrna):
    If I understand correctly, the backport to older branches still represents a change from
earlier behavior of older releases off those branches in that now messages will come to derby.log
(although the dirs still do not get created).

The one reason why I think we might want to have a release note mentioning that is that derby.log
can get really big that way.
  
> java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept connections and client hang
if tracing is turned on but traceDirectory does not exist
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3701
>                 URL: https://issues.apache.org/jira/browse/DERBY-3701
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>             Fix For: 10.4.2.0, 10.5.0.0
>
>         Attachments: derby-3701_diff.txt, derby-3701_try1_diff.txt, DerbyIssue.java,
releaseNote.html, releaseNote.html, releaseNote.html
>
>
> Attempting to connect to network server if  derby.drda.traceAll is set to true and  derby.drda.traceDirectory
is set to a non-existent directory causes the following exception on the console when the
client attempts to connect and causes the client to hang.
> java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept connections.
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java:
> 3172)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java:1829
> )
>         at org.apache.derby.impl.drda.ClientThread.run(ClientThread.java:116)
> See attached program DerbyIssue.java for reproducible test case.
> This is a regression. It did not occur with 10.3.1.4.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message