Re: [Wrapper-user] Can't get JVM output logged correclty (flush doesn't seems to work)

[Luc B. <lu...@fa...>]

Hi Leif,

Thanks for the quick answer. I'm using XP SP2 and the wrapper version =
3.2.3.
In fact I think that I maybe know the reason of the strange behavior but =
I'm
not really sure.. the fact is that those messages that are delayed are =
maybe
not sysout but stuff coming from a native library (I don't have source =
code
access so I'm not really sure..)

Cheers,
Luc

> -----Message d'origine-----
> De=A0: wra...@li... =
[mailto:wrapper-user-
> bo...@li...] De la part de Leif Mortenson
> Envoy=E9=A0: jeudi 10 janvier 2008 15:55
> =C0=A0: wra...@li...
> Objet=A0: Re: [Wrapper-user] Can't get JVM output logged correclty =
(flush
> doesn't seems to work)
>=20
> Luc,
> What platform and version are you using? Are you seeing anything
> at all in the log or is only output from the JVM that is being =
delayed?
> I am not aware of any problems like this in the past.
>=20
> Cheers,
> Leif
>=20
>=20
> Luc Boutier wrote:
> >
> > Hi,
> >
> > I have set the wrapper to log JVM input into a file and
> > wrapper.console.flush=3Dtrue to have =93sysout=94 lines written
> > synchronously in the log but the JVM output only appears after
> > stopping the service.
> >
> > The stuff that are logged using logging are correctly written in
> > =91real-time=92.
> >
> > See my configuration:
> >
> > =
#********************************************************************
> >
> > # Wrapper Logging Properties
> >
> > =
#********************************************************************
> >
> > # Format of output for the console. (See docs for formats)
> >
> > wrapper.console.format=3DPM
> >
> > wrapper.console.flush=3Dtrue
> >
> > # Log Level for console output. (See docs for log levels)
> >
> > wrapper.console.loglevel=3DINFO
> >
> > # Log file to use for wrapper output logging.
> >
> > wrapper.logfile=3D../logs/wrapper.log
> >
> > # Format of output for the log file. (See docs for formats)
> >
> > wrapper.logfile.format=3DLPTM
> >
> > # Log Level for log file output. (See docs for log levels)
> >
> > wrapper.logfile.loglevel=3DINFO
> >
> > # Maximum size that the log file will be allowed to grow to before
> >
> > # the log is rolled. Size is specified in bytes. The default value
> >
> > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or
> >
> > # 'm' (mb) suffix. For example: 10m =3D 10 megabytes.
> >
> > wrapper.logfile.maxsize=3D0
> >
> > # Maximum number of rolled log files which will be allowed before =
old
> >
> > # files are deleted. The default value of 0 implies no limit.
> >
> > wrapper.logfile.maxfiles=3D0
> >
> > # Log Level for sys/event log output. (See docs for log levels)
> >
> > wrapper.syslog.loglevel=3DNONE
> >
> > Any Idea ?
> >
> > Thanks,
> >
> > Luc
> >
> >
>=20
> =
-----------------------------------------------------------------------
> --
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> =
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/market
> place
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user