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 2006/04/13 15:23:02 UTC

[jira] Resolved: (DERBY-614) Execution failed because of a Distributed Protocol Error

     [ http://issues.apache.org/jira/browse/DERBY-614?page=all ]
     
Kathey Marsden resolved DERBY-614:
----------------------------------

    Fix Version: 10.1.3.0
                 10.1.2.4
     Resolution: Fixed
      Assign To: Bryan Pendleton  (was: Kathey Marsden)

Checked this change into 10.1 branch:

Date: Thu Apr 13 06:14:26 2006
New Revision: 393798

URL: http://svn.apache.org/viewcvs?rev=393798&view=rev


Thanks again to Bryan for this great fix.  It will make an important addition to 10.1.3 and surely save lots of folks, including me,  countless hours of trying to track this down and get it resolved.

Kathey


> 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
>      Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.4
>  Attachments: clientSideTrace.txt, clientStack.txt, d614_a.diff, d614_a_with_close_stmts.diff, derby-614.zip, derby614_10_1.diff, 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] Resolved: (DERBY-614) Execution failed because of a Distributed Protocol Error

Posted by Bryan Pendleton <bp...@amberpoint.com>.
> Kathey Marsden resolved DERBY-614:
> ----------------------------------
> 
> Checked this change into 10.1 branch:

Thank you very much, Kathey! We have been running with a patched
version of Derby in our production environment for months; it will
be nice to be able to replace that with a more standard distribution.

bryan