Jpeg image loaded with Loader- loadBytes() does not display when app is deployed on remote server

Question

I am loading a JPEG  image from the server, using the Loader->loadBytes() and that works when the app is deployed under my local Tomcat server.  When I deploy it on other servers the image is not displayed,  instead of the image I see II*
On the server side I have java, Spring, BlazeDs and I use RemoteObject on the client.
The code that loads the image looks like below:
private function imageLoadResultHandler(event:ResultEvent):void {
    var result:ArrayCollection = event.result as ArrayCollection
    var bytes : ByteArray = result.getItemAt(0) as ByteArray;
    _loader = new Loader();
    _loader.contentLoaderInfo.addEventListener(Event.COMPLETE, loaderCompleteHandler);
    _loader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, loaderFaultHandler);
    _loader.loadBytes(bytes);
private function loaderCompleteHandler(event:Event):void {
    var loaderInfo:LoaderInfo = event.currentTarget as LoaderInfo;
    var img:Image = new Image();
    img.source = loaderInfo.content;
    myPanel.addChild(img);
<mx:RemoteObject id="ro" destination="imageLoadService">
     <mx:method name="loadImage" result="imageLoadResultHandler(event)" fault="faultHandler(event)" />
</mx:RemoteObject>
Any help with this problem is much appreciated.
Thank you,
Lumi Velicanu

Answer 1

Hi Dmitri,
Thank you for the prompt reply, your question about the jpeg content was a helpful pointer.
I solved the problem, it had nothing to do with flex, it was all on the java side. The image was obtained from converting a TIFF to a JPEG, the conversion was failing and the flex loader was receiveing a tiff and it did not know how to display it.
The java problem was kind of interesting, I'll post it here as an FYI in case anybody cares :
On my server the first writer returned by ImageIO was an instance of JPEGImageWriter and on the other servers was CLibJPEGImageWriter. And it happens that  only JPEGImageWrite can write the type of TIFF that we are having.
The fix was to iterate through all the writers and pick the instace of JPEGImageWrite, instead of the first one found.
Lumi