Re: ProtocolDecoderException on android

2010-11-15 Thread Jason Weinstein
I don't know if this will be helpful, but i quickly deconstructed the AbstractIoBuffer code into a simple main method (from first google result i found, note not even 2.0.1) I am a little curious as to why the special serialization code is needed. For example: if (desc.forCl

Re: ProtocolDecoderException on android

2010-11-15 Thread Mark Proctor
amField.resolve(ObjectStreamField.java:351) >> 11-05 10:06:25.879: INFO/System.out(1801): at >> java.io.ObjectInputStream.readNewClassDesc(ObjectInputStream.java:1863) >> 11-05 10:06:25.879: INFO/System.out(1801): at >> java.io.ObjectInputStream.readClassDesc(Ob

Re: ProtocolDecoderException on android

2010-11-05 Thread Jason Weinstein
This is not much to work with, but i'd imagine that you didn't get the full object back on the client. Perhaps the server closed the connection before completing the write. Did you flush after write? Or perhaps you closed the client side prior to a full receive? You may want to try a simple

ProtocolDecoderException on android

2010-11-05 Thread matus
Hi, I am creating a simple Android app for reading user tasks from server using Apache Mina. When tested with Java Swing client everything works fine.On Android however, a run into ia problem. The client connects ok, but after I get A protocolDecoderException when receiveing message from server. I