No, that's not how time servers work. You set your computer up to
synchronize with a time server, and periodically a daemon contacts the
server to sync. Synchronizing once an hour should be sufficient in most
cases. You can't go to a central place to get a timestamp because you have
no idea how long the round trip is going to take, and as you point out that
would be pretty high overhead anyway.
----- Original Message -----
From: "Wei Jiang" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 25, 2001 5:30 PM
Subject: Re: [JBoss-user] async logging
> Yes, this is a viable solution, but with performance penality.
>
> When you in a clustering enviroment, you need to access a "center" to
> get a timestamp. This is an extra "remote call" for every logging method
> call.
>
> Have a look at SuperLogging from http://www.acelet.com. It solves all
> issues in a clustering environment.
>
> --- Guy Rouillier <[EMAIL PROTECTED]> wrote:
> > This issue can be addressed by timestamping your log messages on the way
out
> > rather than on the way in. That is, put the timestamp into the
JMSAppender.
> > Things of course get complicated in a multi-server environment where you
> > need coordinated time, but a time server can take care of that.
> >
> > ----- Original Message -----
> > From: "Wei Jiang" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, May 25, 2001 12:42 PM
> > Subject: Re: [JBoss-user] async logging
> >
> >
> > > Async does not guarantee the deliver time, so it is not chronological.
> > > Thank twice before using it.
> > >
> > > --- Scott M Stark <[EMAIL PROTECTED]> wrote:
> > > > The log4j api will be the logging api in JBoss 2.3+ and so this
simply
> > > > becomes
> > > > a log4j configuration issue.
> > > >
> > > > ----- Original Message -----
> > > > From: "Gabor Dolla" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Thursday, May 24, 2001 1:38 AM
> > > > Subject: [JBoss-user] async logging
> > > >
> > > >
> > > > > Hi
> > > > >
> > > > > Is there any plan to implement async logging ?
> > > > > I saw an implementation of it recently in a commercial product.
> > > > > I guess it could be implemented on top of log4j and JMS easily and
> > > > > this could be transparent to the users of log4j.
> > > > > When the user call log.info("Hello"); it'd generate a message
> > > > > and a separate mbean would process it asynchronously maybe in a
> > different
> > > > > VM on a different machine. Also this would allow central logging.
> > > > >
> > > > > Sorry if this has been discussed earlier.
> > > > >
> > > > > Gabor
> > > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > JBoss-user mailing list
> > > > [EMAIL PROTECTED]
> > > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Yahoo! Auctions - buy the things you want at great prices
> > > http://auctions.yahoo.com/
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
