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 2008/04/03 21:57:32 UTC
[jira] Commented: (DERBY-3110) server hangs after trace on command
fails
[ https://issues.apache.org/jira/browse/DERBY-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585265#action_12585265 ]
Kathey Marsden commented on DERBY-3110:
---------------------------------------
I am thinking this may be a problem with synchronization with Derby rather than a problem with the JVM. The thread dump shows a ping thread waiting for response from the server and ClientThread waiting to accept connections. If I try to ping the server once the hang occurs my client hangs, as though, the ClientThread is accepting connections, but not designating a thread to pick them up.
> server hangs after trace on command fails
> -----------------------------------------
>
> Key: DERBY-3110
> URL: https://issues.apache.org/jira/browse/DERBY-3110
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.3.1.4
> Reporter: Sebb
> Assignee: Kathey Marsden
> Fix For: 10.3.2.1, 10.4.0.0
>
> Attachments: derby-3110_diff.txt, derby-3110_diff2.txt, derby-3110_stat.txt, derby-3110_stat2.txt, derby-3110_test_diff.txt
>
>
> Tried turning on trace:
> >networkservercontrol trace on
> Invalid reply from network server: Insufficient data.
> The server process shows the following stack trace:
> access denied (java.io.FilePermission Server58.trace write)
> java.security.AccessControlException: access denied (java.io.FilePermission Server58.trace write)
> at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
> at java.security.AccessController.checkPermission(AccessController.java:401)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:169)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
> at java.io.FileWriter.<init>(FileWriter.java:46)
> at org.apache.derby.impl.drda.DssTrace.startComBufferTrace(Unknown Source)
> at org.apache.derby.impl.drda.Session.initTrace(Unknown Source)
> at org.apache.derby.impl.drda.Session.setTraceOn(Unknown Source)
> at org.apache.derby.impl.drda.NetworkServerControlImpl.setTrace(Unknown Source)
> at org.apache.derby.impl.drda.NetworkServerControlImpl.processCommands(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.sessionInitialState(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> The server now does not respond to ping or shutdown, and has to be killed.
> See also DERBY-3103
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.