If a servlet registered on the internal server attempts to 
set the response encoding to UTF-8, then the server prints 
a message to stdout ("Unsuported encoding: UTF-8"). The 
message is harmless. 




This happens every time a user requests a replay through 
the HTTP Monitor. The servlet which serves up the data of 
the old request to the server side component needs to set 
the encoding to UTF-8 in case the original request contains 
Japanese characters for example. setEncoding is used to set 
the HTTP Header (without which the receiving URLConnection 
will not parse the stream correctly), but the Tomcat server 
also tries to open the writer with the encoding (which is 
unnecessary anyway, all you need is a 16bit writer). 




I don't expect that it is worth fixing this bug since the 
server will presumably be upgraded soon anyway.