How can I active the geoserver log? I have seen that there is an entry in the web interface to activate it, but even if I turn it on, nothing seems to be written in /webapps/geoserver/logs/geoserver.log
I would like to have all of console messages written into a file.
<br>-- <br> Aitor Calero García<br> [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br> [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br> Atos Research & Innovation<br> Atos Origin Spain<br> C/ Albarracín, 25 - 28037 Madrid (Spain) <br> Tel. (+34) 91 214 8805 <br> Fax. (+34) 91 754 3252<br> [http://www.atosresearch.eu](http://www.atosresearch.eu)<br> Before printing this e-mail, think if it is really necessary<br><br>
|
Aitor Calero García ha scritto:
How can I active the geoserver log? I have seen that there is an entry in the web interface to activate it, but even if I turn it on, nothing seems to be written in /webapps/geoserver/logs/geoserver.log
I would like to have all of console messages written into a file.
Strange. I have a bit of questions you may answer to help me tracking
down this.
After changing the setting you did submit/apply/save right?
Looking at the console, one of the first messages should be the
GEOSERVER_DATA_DIR location, do you see it and does it correspond
with what you expect?
Which version of GeoServer are you using? If it's a nightly, is it
from trunk or 1.5.x?
Cheers
Andrea
El vie, 17-08-2007 a las 11:10 +0200, Andrea Aime escribió:
After changing the setting you did submit/apply/save right?
Of course, 
Looking at the console, one of the first messages should be the
GEOSERVER_DATA_DIR location, do you see it and does it correspond
with what you expect?
Yes I can see it and it is where it should be.
Which version of GeoServer are you using? If it's a nightly, is it
from trunk or 1.5.x?
I am using 1.5.3.
Cheers
Andrea
<br>-- <br> Aitor Calero García<br> [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br> [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br> Atos Research & Innovation<br> Atos Origin Spain<br> C/ Albarracín, 25 - 28037 Madrid (Spain) <br> Tel. (+34) 91 214 8805 <br> Fax. (+34) 91 754 3252<br> [http://www.atosresearch.eu](http://www.atosresearch.eu)<br> Before printing this e-mail, think if it is really necessary<br><br>
|
Aitor Calero García ha scritto:
El vie, 17-08-2007 a las 11:10 +0200, Andrea Aime escribió:
After changing the setting you did submit/apply/save right?
Of course,
Looking at the console, one of the first messages should be the
GEOSERVER_DATA_DIR location, do you see it and does it correspond
with what you expect?
Yes I can see it and it is where it should be.
Which version of GeoServer are you using? If it's a nightly, is it
from trunk or 1.5.x?
I am using 1.5.3.
Ok, looked into this, and mostly reproduced... the log file is
being created, but apparently nothing gets in it... well, this is
happening because the log to file is being aggressively buffered
so you have to accumulate a few kilobytes of logs before they do
appear on the file...
Now, it's definitely possible to remove the buffering, but
that would mean that every logs statement will hit the disk,
slowing down GeoServer quite a bit...
Cheers
Andrea
Andrea Aime ha scritto:
Aitor Calero García ha scritto:
El vie, 17-08-2007 a las 11:10 +0200, Andrea Aime escribió:
After changing the setting you did submit/apply/save right?
Of course,
Looking at the console, one of the first messages should be the
GEOSERVER_DATA_DIR location, do you see it and does it correspond
with what you expect?
Yes I can see it and it is where it should be.
Which version of GeoServer are you using? If it's a nightly, is it
from trunk or 1.5.x?
I am using 1.5.3.
Ok, looked into this, and mostly reproduced... the log file is
being created, but apparently nothing gets in it... well, this is
happening because the log to file is being aggressively buffered
so you have to accumulate a few kilobytes of logs before they do
appear on the file...
Hum, so, I've looked a bit more and it seems there is a double
buffering involved here.
We do use a BufferedOutputStream for the output, whose size
was 512 bytes in jdk 1.4.2, but crept up to 8192 in JDK 1.5
onwards. At the same time, the jdk logging library is doing
its own buffering of the messages to be written on the log,
using another apparently unmodifiable 8kb buffer.
As a result, thing are really written out only when they
sum up to 16kb... sigh...
Cheers
Andrea
Thank you, Andrea, for your kindly support, but It does not seem very clear to me, would it be possible to activate log file or not?
If I understood well, log files are written if (correct me if I am wrong) every single log line is 16 kb long, isn’t it?
Aitor Calero García ha scritto:
Thank you, Andrea, for your kindly support, but It does not seem very clear to me, would it be possible to activate log file or not?
Yes it is. It works on my computer.
If I understood well, log files are written if (correct me if I am wrong) every single log line is 16 kb long, isn't it?
No, a little different. Log lines are accumulated into a memory buffer,
and they end up being written on the disk only when the buffer reaches
16kb of size, so you may have to accumulate various log lines to see
anything appear on the disk.
Cheers
Andrea