Right... it's the same on trunk. I'll look at it later today hopefully. Thanks for tracking this down, Alan!
-- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com > -----Original Message----- > From: Zhemzhitsky Sergey [mailto:[email protected]] > Sent: Wednesday, June 27, 2012 2:21 AM > To: 'Alan Conway'; [email protected] > Subject: RE: Milliseconds in log messages > > Hi Alan, > > Currently I'm using qpid c++ client 0.14 and outputHiresNow displays > unformatted time. > > Best Regards, > Sergey > > -----Original Message----- > From: Alan Conway [mailto:[email protected]] > Sent: Tuesday, June 26, 2012 6:53 PM > To: [email protected] > Cc: Zhemzhitsky Sergey > Subject: Re: Milliseconds in log messages > > On 06/22/2012 07:02 AM, Zhemzhitsky Sergey wrote: > > Hello Steve, > > > > Here is the issue https://issues.apache.org/jira/browse/QPID-4084. It also > contains a recommendation hot it possibly can be fixed. > > > > Best Regards, > > Sergey > > > > -----Original Message----- > > From: Steve Huston [mailto:[email protected]] > > Sent: Thursday, June 21, 2012 9:39 PM > > To: [email protected] > > Subject: RE: Milliseconds in log messages > > > > Hi Sergey, > > > >> Currently qpid supports two ways of timestamp logging: ordinary and > >> with high resolution timer (--log-hires-timestamp). > >> > >> Here is the log output with ordinary formatted timestamps: > > 2012-06- > >> 21 19:51:50 debug XXX > >> Here is the log output with hires timestamps: > >> 1340294674.411677244s debug XXX > > > > Right. > > > >> The problem is that quite often it's necessary to have formatted > > timestamps > >> with milliseconds in log files. > > > > This has been the case for a while on the posix broker - > > 2012-06-26 10:50:21.800176860 [Broker] critical Unexpected error: Can't bind > to port 0.0.0.0:5672: Address already in use > (../../qpid/cpp/src/qpid/sys/posix/Socket.cpp:206) > > I didn't implement it on windows, as I'm not very knowledgeable there. It > shouldn't be difficult though. > > > _______________________________________________________ > > The information contained in this message may be privileged and conf > idential and protected from disclosure. If you are not the original intended > recipient, you are hereby notified that any review, retransmission, > dissemination, or other use of, or taking of any action in reliance upon, this > information is prohibited. If you have received this communication in error, > please notify the sender immediately by replying to this message and delete > it from your computer. Thank you for your cooperation. Troika Dialog, Russia. > If you need assistance please contact our Contact Center (+7495) 258 0500 or > go to www.troika.ru/eng/Contacts/system.wbp > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
