[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12367681 ]
Bryan Pendleton commented on DERBY-515:
---
Committed derby-515-patch2-v1.diff to the trunk as revision 380722.
http://svn.apache.org/viewcvs?rev=380722view=rev
This was my
Network Server should log server start and shutdown time to derby.log
-
Key: DERBY-515
URL: http://issues.apache.org/jira/browse/DERBY-515
I am intending to (re)review and commit derby-515-patch2-v1.diff in
On 2/23/06, Bryan Pendleton [EMAIL PROTECTED] wrote:
Network Server should log server start and shutdown time to derby.log
-
Key: DERBY-515
URL: http://issues.apache.org/jira/browse/DERBY-515
I am
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12367233 ]
Deepa Remesh commented on DERBY-515:
Suresh pointed out to me that this change caused the following failure in
derbynetclientmats with 10.1 client and 10.2 server:
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366971 ]
Bryan Pendleton commented on DERBY-515:
---
I checked derby-515-patch2-v1.diff.
I thought it was a little odd that the diff contains changes to the two master
files which
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366972 ]
Kathey Marsden commented on DERBY-515:
--
Bryan, would you be willing to commit this when you get the needed accounts and
karma?
Network Server should log server start
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366973 ]
Bryan Pendleton commented on DERBY-515:
---
Yes, that sounds like a fine idea. Once I am fully set up, I will review and
commit this change.
Network Server should log
Deepa Remesh wrote:
On 2/16/06, Kathey Marsden (JIRA) derby-dev@db.apache.org wrote:
I committed this patch.
I think it would be good to add a comment to the code regarding why we use
CheapDateFormatter and GMT.
On your questions
1. I found that the test derbynet/NSinSameJVM.java has two
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366714 ]
Kathey Marsden commented on DERBY-515:
--
I committed this patch.
I think it would be good to add a comment to the code regarding why we use
CheapDateFormatter and GMT.
On
On 2/16/06, Kathey Marsden (JIRA) derby-dev@db.apache.org wrote:
I committed this patch.
I think it would be good to add a comment to the code regarding why we use
CheapDateFormatter and GMT.
On your questions
1. I found that the test derbynet/NSinSameJVM.java has two masters - one for
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366554 ]
Deepa Remesh commented on DERBY-515:
Thanks Bryan for looking at the patch.
I chose GMT to keep it consistent with what is used for Derby boot message. The
network server
I chose GMT to keep it consistent with what is used for Derby boot message.
Sounds good.
About using xxFILTERED-VERSION-NUMBERxx, I did'nt see other tests
doing it. I saw the current pattern in tests is to add master files with
version number to release/build.xml file. I would like
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12362113 ]
Kathey Marsden commented on DERBY-515:
--
A few thoughts looking at this patch. I am interested in input from others.
1) I think maybe we should print the time on the
I believe that the current log file format has been written to
be easy to parse - but not as easy as looking for a single
delimiter. Remember that the log file can contain arbitrary
text - so not sure if a single delimiter will work. The worst
case is log statement text which will print out
I worked on some Output LOG Mgr years ago - it had support for various
types of formatted-parameterizable log messages as well as being able
to redirect certain mesage types (i.e. INFO, SEVERE, FATAL, DEBUG,
TRACE, etc) to additional types of storage (FS, Table, etc) - One
feature users like
Derby still has an error log reading VTI: ErrorLogReader. It shows how a
reasonable engineer, in a pre-xml world, would approach the problem of
parsing a log file and presenting it in tabular form.
I retract my hasty suggestion that it would be easy to convert Derby
logs to a more structured
[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12319327 ]
Øystein Grøvlen commented on DERBY-515:
---
This would be even more helpful if the derby.log file was not overwritten on
the next startup. (Probably a separate issue).
Øystein Grøvlen (JIRA) wrote:
[
This would be even more helpful if the derby.log file was not overwritten on
the next startup. (Probably a separate issue).
The derby.infolog.append property is helpful in this regard.
http://db.apache.org/derby/docs/10.1/tuning/rtunproper13217.html
KM == Kathey Marsden [EMAIL PROTECTED] writes:
KM Ãystein Grøvlen (JIRA) wrote:
[
This would be even more helpful if the derby.log file was not
overwritten on the next startup. (Probably a separate issue).
KM The derby.infolog.append property is helpful
Øystein Grøvlen wrote:
KM == Kathey Marsden [EMAIL PROTECTED] writes:
KM Øystein Grøvlen (JIRA) wrote:
[
This would be even more helpful if the derby.log file was not overwritten on the next startup. (Probably a separate issue).
KM The
Well, the most common solution is log rotation. On restart, you rename
the old log to derby.log.1 and then derby.log.2 and so on. After n
log files, you start over again at derby.log.1.
This is also useful for long-running systems so you don't run out of
disk space because of your error
At the risk of overloading this topic: While we're talking about
improvements to our error logging, I'd like to see us emit more
structured logs. This is one of the things that xml is actually good
for. It would be pretty easy to turn our log records into xml entries.
This would make it easy
Please, God, no :). Machines like reading XML but people (at least
certain people) find it a bit horrific.
What I have seen done in the past is using a simple delimiter format, e.g.
|Fri Aug 19 14:06:31 PST
2005|org.apache.derby.engine.impl.jdbc.EmbedConnection|Thread
275|Invalid user,
I agree with going the delimited format route. Having the database
write out XML would probably impact preformance quite a bit. I also
wonder what would happen if the database were to die (power failure or
the like) and the XML file ended up invalid due to it missing those
crucial few closing
Actually, when derby.language.logStatementText=true is set, messages
that are currently printed to derby.log uses a : delimiter format.
e.g.
. Begin compiling prepared statement : SELECT * from tbl1 : end
compiling prepared statement
etc...
For really huge derby.log traces, I
XML is kind of dreary. I like your suggested format, David. It's easier
to read and easy enough to transform into xml for tools which groove on
that.
Cheers,
-Rick
David Van Couvering wrote:
Please, God, no :). Machines like reading XML but people (at least
certain people) find it a bit
, 2005 3:05 PM
Subject: Re: regarding derby.log being overwritten on startup. [was Re:
[jira] Commented: (DERBY-515) Network Server should log server start and
shutdown time to derby.log]
I agree with going the delimited format route. Having the database
write out XML would probably impact
27 matches
Mail list logo
