Can you try to produce a stripped-down example (e.g. a proto file and a *short* stripped-down .java file) that exhibits the problem? The byte pattern in your email does look valid to me, so there's more likely some issue where that isn't really what the protocol buffer code is seeing for some reason.
On Thu, Jan 14, 2010 at 4:51 PM, mancha <madhavan...@gmail.com> wrote: > Hi, > When dequeing the message using a Java client, the get the > following error. I am sending the data from a c++ server. > com.google.protobuf.InvalidProtocolBufferException: Protocol > message contained an invalid tag (zero) > > I verified that the byte pattern on enqueuing from the c++ client > is the same as the byte pattern I am sending to > SComm.PositionUpdate.parseFrom(one_buf); in Java. > The byte pattern in one_buf is 10 3 86 79 68 > > and the class is ofcourse PositionUpdate with an outer class name > SComm. > > How do I debug this further? > > Any help is appreciated. > > Thanks, > Madhav. > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to proto...@googlegroups.com. > To unsubscribe from this group, send email to > protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
