avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Hammerbacher (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-287) Make RPC interop tests work with new Python implementation
Date Tue, 09 Feb 2010 07:35:27 GMT

     [ https://issues.apache.org/jira/browse/AVRO-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jeff Hammerbacher updated AVRO-287:

    Attachment: javaserverpyclient

So I now have the Java client talking happily to the Python server after much debugging (and
flushing of stdout and subclassing of HTTPServer). I have the RPC interop bash script running
for every combination of Java and Python except the Python client talking to the Java server.
This bug is a fun one, as have been the previous two.

When the Java server is run as a foreground or background process in a separate terminal from
the Python client, everything is fine. However, when the Java server is run as a background
process in the same terminal as the Python client, the first handshake happens fine, but the
server sends the client a block with a correct block length (as if sending the correct response)
but empty block content (mysteriously). I've used Wireshark to capture the exchange between
the Java server and the Python client and attached it to this issue.

Any guidance on how to debug the Java server to figure out how the content of the second message
is not hitting the wire would be much appreciated.

> Make RPC interop tests work with new Python implementation
> ----------------------------------------------------------
>                 Key: AVRO-287
>                 URL: https://issues.apache.org/jira/browse/AVRO-287
>             Project: Avro
>          Issue Type: Test
>          Components: python
>            Reporter: Jeff Hammerbacher
>            Assignee: Jeff Hammerbacher
>             Fix For: 1.3.0
>         Attachments: AVRO-287.patch, echo.avpr, HelloClient.java, HelloServer.java, hw.py,

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message