UTFDataFormatException: malformed input UTF Format

Question

I am Trying to Send Some Info Before Sending File to My Socket Server Through UTF, When I Send only A File Name :

   File fil=new File(filepath);  
   dos.writeUTF (fil.getName());

it Works fine, But When i Add Some Custom String to It :

  dos.writeUTF((("@REQUEST@ROOM:"+roomName+"@FILENAME:"+fil.getName())));

i get This Error :

 UTFDataFormatException: malformed input UTF Format

Could You Help me Here Please ?

UTFDataFormatException: malformed input UTF Format this is the Log on The Server Dude — dasdas
– dasdas, Commented Jul 21, 2014 at 1:09
there is no Stack Trace on the Exception,Since i Dont Have the Source for jre-8 — dasdas
– dasdas, Commented Jul 21, 2014 at 1:14
That statement doesn't make sense. You don't need JRE source code to get a stack trace. — user207421
– user207421, Commented Jul 21, 2014 at 1:21

user207421 · Accepted Answer · 2014-07-21 01:21:26Z

1

You don't get that exception when writing. You get it when reading: typically when calling readUTF() when the next thing in the input isn't produced by writeUTF(). In other words, an application protocol error. In this case it isn't produced by what you've posted but by what you haven't posted.

I don't see why you don't write the extended piece of data in separate writes and read it in separate reads, rather than giving yourself the trouble of concatenating and then splitting it up again.

I also don't know what all the extra parentheses are supposed to be for. Don't write redundant syntax.

answered Jul 21, 2014 at 1:21

user207421

312k45 gold badges324 silver badges493 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

dasdas Over a year ago

i found the answer, thanks any way, but by the way, the Reason i have appended them togeather is lesser (even a bit) communication, so higher speed

user207421 Over a year ago

The speed difference won't be measurable but the extra complication and cost and risk of the way you've done it certainly is.

dasdas Over a year ago

what risk? you mean NPE Exception Posibility?

dasdas Over a year ago

if thats What You Meant , I have first Assured There is no Way In the Hell the Reuqest be Null :) either ill be Happy to know What You Mean

user207421 Over a year ago

I mean the risk of the encoding and the decoding not matching up so you have to debug them, which is far lower if you separate them.

Collectives™ on Stack Overflow

UTFDataFormatException: malformed input UTF Format

1 Answer 1

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related