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)" <de...@db.apache.org> on 2005/12/10 03:02:10 UTC
[jira] Commented: (DERBY-614) Execution failed because of a Distributed Protocol Error
[ http://issues.apache.org/jira/browse/DERBY-614?page=comments#action_12360015 ]
Kathey Marsden commented on DERBY-614:
--------------------------------------
I committed this patch
Date: Fri Dec 9 17:51:26 2005
New Revision: 355689
URL: http://svn.apache.org/viewcvs?rev=355689&view=rev
Thanks so much for the wonderful fix and the great javadoc you added.
One thing I did notice that deserves followup and may be related to the intermittent hangs you have seen, is that there was a finalizeChain() call in the old file on line 6139 that seems to be missing from the new version, line 6278.
This might be the source of the hang you reported for one of the dss chaining bugs (I can't seem to find that mail now).
Can you take a look at that and also clean up the out of date patch attachments to 614.
> Execution failed because of a Distributed Protocol Error
> --------------------------------------------------------
>
> Key: DERBY-614
> URL: http://issues.apache.org/jira/browse/DERBY-614
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.1.1.0
> Environment: Linux 2.4, Sun JDK 1.4.2_07, full SYSINFO will be attached.
> Reporter: Bryan Pendleton
> Assignee: Bryan Pendleton
> Attachments: clientSideTrace.txt, clientStack.txt, derby-614-with-tests.diff, derby-614.stat, derby-614.zip, derbyTrace.txt, derbynetclientmats_report.txt, query.txt, serverSideTrace.txt, spec.html, svn-diff-2005-12-04.txt, svn-status-2005-12-04.txt, sysinfo.derby
>
> I am intermittently receiving Distributed Protocol Error exceptions in my client code. Simultaneously,
> my derby.log is recording Distributed Protocol Error exceptions on the server side.
> I cannot reliably reproduce this problem.
> However, the problem always occurs in the same section of my application, so I can at least
> describe that section of my application. (I'll do so in an attachment).
> Here is the error I receive on the server side. Sometimes, the CODPNT is 2116 and the
> Error Code Value is 1d, rather than 2114 and e.
> 2005-10-05 02:10:23.663 GMT Thread[DRDAConnThread_2,5,main] (DATABASE = BuildFar
> m), (DRDAID = GA0A0026.P7E6-4182154075488704215{136532}), Execution failed becau
> se of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 2114; Er
> ror Code Value = e
> Execution failed because of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM;
> CODPNT arg = 2114; Error Code Value = e
> 2005-10-05 02:10:23.663 GMT Thread[DRDAConnThread_2,5,main] (DATABASE = BuildFar
> m), (DRDAID = GA0A0026.P7E6-4182154075488704215{136532}), null
> null
> org.apache.derby.impl.drda.DRDAProtocolException
> at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(Unknown Sourc
> e)
> at org.apache.derby.impl.drda.DRDAConnThread.missingCodePoint(Unknown So
> urce)
> at org.apache.derby.impl.drda.DRDAConnThread.parseCNTQRY(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.splitQRYDTA(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(Unknown Source)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Sou
> rce)
> at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-614) Execution failed because of a Distributed
Protocol Error
Posted by Bryan Pendleton <bp...@amberpoint.com>.
> One thing I did notice that deserves followup and may be related to the intermittent hangs you have seen, is that there was a finalizeChain() call in the old file on line 6139 that seems to be missing from the new version, line 6278.
> This might be the source of the hang you reported for one of the dss chaining bugs (I can't seem to find that mail now).
>
> Can you take a look at that and also clean up the out of date patch attachments to 614.
Yes, I will follow up on both these items.
Thank you very much for reviewing and committing the patch.
bryan