[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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.3.3.1, 10.4.2.0, 10.5.1.1
• Component/s: Network Server
• Issue & fix info: Release Note Needed
• Bug behavior facts: Regression
• Assignee: Katherine Marsden
• Reporter: Katherine Marsden
• Created: 02/Jun/08 14:36
• Updated: 30/Jun/09 16:12
• Resolved: 11/Jun/08 15:44

Description

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.

Issue Links

• is related to: DERBY-3110 server hangs after trace on command fails
• relates to: DERBY-4128 Failure in ServerPropertiesTest due to java.security.AccessControlException on the server side, in 10.4 to 10.5.1. soft upgrade mode
• relates to: DERBY-4153 Document that starting with 10.5 network server will attempt to create the trace directory if it does not exist