Not much to go on here, can you post relevant sections of your log
file after you make a request? If you've not already, put log-level to
debug.
--tim
On Tue, Dec 21, 2010 at 7:51 AM, Szabo, Patrick (LNG-VIE)
patrick.sz...@lexisnexis.at wrote:
Hi,
It seems to have something todo with the
I started forrest with forrest run -l log.txt and i do get the txt-file but if
i browse to a page nothing is written into the file.
Still there is an error in the log file:
14:08:10.857 EVENT Checking Resource aliases
14:08:10.982 EVENT Starting Jetty/4.2.19
14:08:11.045 EVENT Started
I was thinking the actual log file itself, not stdout.
--tim
On Tue, Dec 21, 2010 at 8:14 AM, Szabo, Patrick (LNG-VIE)
patrick.sz...@lexisnexis.at wrote:
I started forrest with forrest run -l log.txt and i do get the txt-file but
if i browse to a page nothing is written into the file.
Still
Can you tell me where that file is located ?!
. . . . . . . . . . . . . . . . . . . . . . . . . .
Patrick Szabo
XSLT-Entwickler
LexisNexis
Marxergasse 25, 1030 Wien
mailto:patrick.sz...@lexisnexis.at
Tel.: +43 (1) 534 52 - 1573
Fax: +43 (1) 534 52 - 146
-Ursprüngliche Nachricht-
On Tue, Dec 21, 2010 at 8:26 AM, Szabo, Patrick (LNG-VIE)
patrick.sz...@lexisnexis.at wrote:
Can you tell me where that file is located ?!
http://forrest.apache.org/howto-dev.html#debug-logfiles
http://forrest.apache.org/docs_0_90/faq.html#logs
. . . . . . . . . . . . . . . . . . . . . . .
I guess this is what's going wrong:
ERROR (2010-12-21) 14:32.34:132 [access] (/cpf/news/vpi.html)
PoolThread-7/CocoonServlet: Internal Cocoon Problem
org.apache.cocoon.ProcessingException: Error executing pipeline.:
org.apache.cocoon.ProcessingException: Error executing pipeline.:
I'll try and install ngrep.sf.net.
There is an outgoing connection available.
Also i don't think that would be a possible explanation because the files that
do work also contain dtd-declarations (of another dtd though).
Thx
. . . . . . . . . . . . . . . . . . . . . . . . . .
Patrick Szabo
Okay, there are so many outgoing connections that it is impossbile for me to
distinguish which one of them is caused by forrest.
I used wireshark becuase it supports filters and has a gui but even with that i
couldn't find anything.
Any suggestions what excatly i should be looking for ?!
.
