Re: Can't see server errors when running ROP

From: Tarik (cherta..mail.com)
Date: Tue Jan 08 2008 - 21:36:50 EST

Next message: Álvaro Martínez: "Re: Selective commit"

Previous message: marco turchi: "Commit Exception Error"
In reply to: Aristedes Maniatis: "Re: Can't see server errors when running ROP"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Great. That did it. I set my log4j.config to the following and it worked.
Thanks Ari.

log4j.debug=true
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.rootLogger=DEBUG, stdout

On Jan 6, 2008 8:04 PM, Aristedes Maniatis <ar..sh.com.au> wrote:

>
> On 07/01/2008, at 9:41 AM, Tarik wrote:
>
> > I can't see the server stacktrace when there is an exception caused
> > by a ROP
> > client. Say if I for example screw up a query parameter. I figure
> > it's
> > probably a log4j property but I can't figure it out despite numerous
> > attempts. I am running Cayenne3 server on JettyLauncher directly from
> > Eclipse.
>
>
>
> I'm guessing that you might not have the log4j properties file in the
> right place. Make sure it is being picked up properly by adding:
>
> log4j.debug=true
>
> to the file. Or else,
>
> log4j.rootLogger=DEBUG, stdout
>
> should give you lots of output to sift through and make sure you are
> on the right track.
>
>
> Ari
>
>
> -------------------------->
> ish
> http://www.ish.com.au
> Level 1, 30 Wilson Street Newtown 2042 Australia
> phone +61 2 9550 5001 fax +61 2 9550 4001
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
>
>

Next message: Álvaro Martínez: "Re: Selective commit"
Previous message: marco turchi: "Commit Exception Error"
In reply to: Aristedes Maniatis: "Re: Can't see server errors when running ROP"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Tue Jan 08 2008 - 21:37:31 EST