|
From: Rick S. <rs...@as...> - 2004-06-22 12:34:56
|
Leif, Some of our messages are pretty large(ie Base64 encoding of images, don't ask... :-[ ). I think it is quite reasonable for there to be a fixed limit. I would propose 2048 or 4096 characters even. I would hazard to guess that performance would not degrade too badly given a larger fixed buffer. What do you think? Rick Leif Mortenson wrote: > Rick, > Currently for performance reasons, a fixed buffer is used when > reading the JVM > output. The way it is implemented, this causes a linefeed each 1024 > characters > for very long lines. There is not a way to change this behavior in > the current release. > I will look into getting that cleaned up. It has been a minor > annoyance in a couple > of my applications as well. > At some point, I want to make the buffer dynamically scale. But I > am trying to > get a release out. If it is within reason, I can quickly up the size > a bit. How long are > the lines you are trying to log? > > Glad to hear we are helping with mental health in our own little > way. :-) > > Cheers, > Leif > > Rick Szeto wrote: > >> Hi all, >> I am experiencing long logs entries to the console logfile being >> truncated. Is there a configuration parameter I missing that will fix >> this? Or is this a know problem? >> >> Any help would be greatly appricated. >> >> BTW, the wrapper is the only thing that is keeping me sane in our >> production environment. >> Thanks. >> >> Rick Szeto > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital > self defense, top technical experts, no vendor pitches, unmatched > networking opportunities. Visit www.blackhat.com > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > . > |