Awesome! Thank you very much!!!
On Fri, Feb 13, 2009 at 3:15 PM, Daniel Kulp wrote:
>
> This is a problem of how you are using the CachedOutputStream in the
> client.
> If you wireshark the actual stream, you'll see that the entire message is
> properly sent back to the client.
>
> Once it cross
This is a problem of how you are using the CachedOutputStream in the client.
If you wireshark the actual stream, you'll see that the entire message is
properly sent back to the client.
Once it crosses 64K, the CachedOutputStream starts using a temp file to store
content. However, when you
Oh, sorry, didn't know the the log was talking about truncating the log.
Well, I have a test case that reproduces the problem. It is a simple server
that only has on method that returns a list of WSImage. Each WSImage has
some info of the image, and an byte array that represents the bytes of the
im
It should be unlimitted already.What you are seeing is the Logging
interceptor truncating what it logs to the logger to avoid the logger sucking
everything into memory and taking down the server with OOM type issues. That
shouldn't be affecting what gets sent back to the client.
Can you
I have a service that returns a list of images. It seems to work, but when
the images are too big or there are several images I don't get all images,
just some of them.
>From the server side I get this messages
Outbound Message
---
Encoding: UTF-8
Headers: {}
Messages: Outb
