2009/6/10 Gintare Ragaisiene :
> Hello everyone,
>
> I've installed cocoon 2.2 webapp on Tomcat 6. For this I deployed .war file
> in Tomact's webapps directory.
> After a day I looked at the logs and found this exception:
>
> Jun 9, 2009 8:31:51 PM org.apache.cat
Hello everyone,
I've installed cocoon 2.2 webapp on Tomcat 6. For this I deployed .war file
in Tomact's webapps directory.
After a day I looked at the logs and found this exception:
Jun 9, 2009 8:31:51 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() f
Martyn Wilson pisze:
I have a cocoon application, which errors out with a default 500 page.
Thereis not reference to this in the cocoon.log.
Is there a configuration I am missing to log errors?
Please advise?
Have you tried to check container logs/console (of Tomcat/Jetty/whatever
I have a cocoon application, which errors out with a default 500 page. Thereis
not reference to this in the cocoon.log.
Is there a configuration I am missing to log errors?
Please advise?
Martyn Wilson
Jason Johnston wrote:
Since you're using Tomcat you can configure it to create an access log;
see http://tomcat.apache.org/tomcat-5.0-doc/config/valve.html for
details. I imagine the reason it is not configured to create one out of
the box is that usually Tomcat is behind an Apache reverse pro
addresses anywhere in the Cocoon or Tomcat
logs. Unless this is a configuration issue which I have missed, there
seems to be a major deficiency in the logging.
Since you're using Tomcat you can configure it to create an access log;
see http://tomcat.apache.org/tomcat-5.0-doc/config/valve.htm
Cocoon or Tomcat
logs. Unless this is a configuration issue which I have missed, there
seems to be a major deficiency in the logging.
Nevertheless, you
should always use httpd configured as proxy for this purpose.
As I explained in the original post, I will be doing this on the
production
Peter Flynn pisze:
But none of those files have any information about where the request has
come from (eg IP address), which makes them virtually useless.
AFAIR, they should contain information you need. Nevertheless, you should
always use httpd configured as proxy for this purpose.
--
Grze
Sebastian Wenzky wrote:
Peter Flynn wrote:
In my webapps/ROOT there's a logs directory, but none of the logs
contain any information about who has visited the site.
How do I turn on access logging? Or is it already on but hidden
somewhere I don't know about? This is an experimenta
Peter Flynn wrote:
In my webapps/ROOT there's a logs directory, but none of the logs
contain any information about who has visited the site.
How do I turn on access logging? Or is it already on but hidden
somewhere I don't know about? This is an experimental site, so it's
In my webapps/ROOT there's a logs directory, but none of the logs
contain any information about who has visited the site.
How do I turn on access logging? Or is it already on but hidden
somewhere I don't know about? This is an experimental site, so it's
running as root.
W
Where I can find a patern reference to manage what I want in my log?
%23.23{time:-MM-dd' 'HH:mm:ss.SSS} %5.5{priority}
%40.40{category} (%{host}%{uri}) %{thread}/%{class:short}:
%{message}\n%{throwable}
Thank you very much
Omar
--
Thhks for your answer too,
but what I'd like to have is just a log about what I'm sending.
I would like to be able to log what the sendmail do.
Omar
On 7/26/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
On 7/26/06, Omar Adobati <[EMAIL PROTECTED]> wrote:
> ...But now, how I can log the m
On 7/26/06, Omar Adobati <[EMAIL PROTECTED]> wrote:
...But now, how I can log the mail I'm sending?...
It would probably be useful to spy the network traffic between your
application and your mail server, see
http://marc.theaimsgroup.com/?t=11428652402&r=1&w=2
-Bertrand
---
INFO level also gives you what you want
(better then DEBUG ofcourse)
But, I doubt wether the SendmailTransformer logs all these things you want to
see. Then, you could extend/replace the SendMailTransformer with your own, and
just log anything you want.
Regards Ard
>
>
> it works
Set the sendmail category logging to DEBUG, and see what gets logged.
If you get what you want, try if INFO level also gives you what you want
(better then DEBUG ofcourse)
But, I doubt wether the SendmailTransformer logs all these things you want to
see. Then, you could extend/replace the
g.Sendmail"/>
>
This logger says, it will first try to log to sitemap/action/sendmail, if this
is not available sitemap/action, and otherwise to sitemap. You can very easily
configure this in logkit.xconf:
add a target:
${context-root}/WEB-INF/logs/sendmail.log
y to log to sitemap/action/sendmail, if this
is not available sitemap/action, and otherwise to sitemap. You can very easily
configure this in logkit.xconf:
add a target:
${context-root}/WEB-INF/logs/sendmail.log
%23.23{time:-MM-dd' 'HH:mm:ss.SSS} %5.5{priority}
Good Morning,
I know it would be a silly question, but I'm still new here...
I have configured my sitmap for SendMail action adding
and I suppose that the logger attribute is about a logging function.
Am I wrong? If not, where I can find the log? And, If I'm wrong, how I
can set-up
Title: Recording different site logs to different files
Hello
I'm currently utilising Cocoon 2.1 with IIS 6 to serve multiple customer sites from the one cocoon project using the Host Selector method (see code snippet
Paul Kelly wrote:
Howdy, apologies if this is a faq but I couldn't find anything in the
archives.
I just upgraded to 2.1 (previously I ad 2.0 on Tomcat 4) and I can no
longer trace xsl errors as easily through the logs. Used to be I'd get
the line # of embedded, included stylesheet
s.
I just upgraded to 2.1 (previously I ad 2.0 on Tomcat 4) and I can no
longer trace xsl errors as easily through the logs. Used to be I'd get
the line # of embedded, included stylesheets and some useful verbiage.
No more. Can someone tell me what changed and if this can be fixed? I
use
Howdy, apologies if this is a faq but I couldn't find anything in the archives.
I just upgraded to 2.1 (previously I ad 2.0 on Tomcat 4) and I can no
longer trace xsl errors as easily through the logs. Used to be I'd
get the line # of embedded, included stylesheets and some useful
ve
I choose the second way and it works perfectly.
thanks a lot
Flavio
>-- Original Message --
>Reply-To: [EMAIL PROTECTED]
>Date: Tue, 30 Dec 2003 10:18:18 +0100
>From: Stephan Coboos <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: problem with logs
>
>
&
ontext-root}/WEB-INF/logs/myAction.log
%7.7{priority} %{time} [%{category}] (%{uri})
%{thread}/%{class:short}: %{message}\n%{throwable}
false
...
Note that you have to set the log level to DEBUG!
After restarting cocoon, you can find the logs for you action in
WEB-INF/lo
Hi all,
i wrote a little action in which i send messages using getLogger().debug(..)
or getLogger().error(..) or getLogger().warn(..) ; the question is where
can i find the messages sent ?
I need to switch some parameters to activate loggers ?
May i redirect messages to my own log file ?
many tha
Wise Team wrote:
Hi all,
I' have forgotten to say that I'm working with tomcat 4.1.24, JVM 1.4.2
and Cocoon 2.1.
In 2.0.4 version, errors were in log files (core.log, sitemap.log)
and on my computer screen.
But with cocoon 2.1, errors are only on my screen.
Someone knows reasons of this beh
Hi all,
I' have forgotten to say that I'm working with tomcat 4.1.24, JVM 1.4.2
and Cocoon 2.1.
In 2.0.4 version, errors were in log files (core.log, sitemap.log)
and on my computer screen.
But with cocoon 2.1, errors are only on my screen.
Someone knows reasons of this behavior and knows s
Dear All,
I upgraded to Cocoon 2.1 and now, I can't see the errors raised in my
jsp pages. In version 2.0.4, I used to see them in core.log or sitemap.log.
I've tried to change all log-level to DEBUG in cocoon.xconf and web.xml.
I can see more messages, but not those raised in jsp pages.
Please
If I have 2 application servers running on the same machine,
or 2 machines that share a harddrive.
is there a way to configure the loggers to log to different
files for each engine.
Thanks,
Artur...
-
To unsubscribe, e-mail:
30 matches
Mail list logo
