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] Commented: (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 Wed, 04 Jun 2008 22:43:45 GMT

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

Myrna van Lunteren commented on DERBY-3701:
-------------------------------------------

I keep going back and forth on your question. I think - as Dag said on the list - if the permissions
are in place we should create the dirs.
But should this be backported? Or should we just give an error message in those earlier versions?
Either way will change the behavior, and might be an unwelcome surprise to people who have
set this in their application.
But of course not having a connection is worse, that does need to get fixed.
I think maybe a compromise would be to have the stack print to derby.log in older versions.
It would still mean more disk space used but not as much as if the full tracing would get
created.


> 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
>         Attachments: derby-3701_diff.txt, derby-3701_try1_diff.txt, DerbyIssue.java
>
>
> 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