You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cayenne.apache.org by Tarik <ch...@gmail.com> on 2008/01/06 23:41:51 UTC
Can't see server errors when running ROP
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.
Here is the client exception. Server shows nothing.
>> [v.3.0M1 Jul 17 2007 05:51:33] Remote error. URL -
http://localhost:8080/cayenne-service; CAUSE - Server returned HTTP response
code: 500 for URL: http://localhost:8080/cayenne-service [
org.apache.cayenne.CayenneRuntimeException]
>> org.apache.cayenne.remote.hessian.HessianConnection.doSendMessage(
HessianConnection.java:145)
>> org.apache.cayenne.remote.BaseConnection.sendMessage(BaseConnection.java
:73)
>> org.apache.cayenne.remote.ClientChannel.send(ClientChannel.java:276)
>> org.apache.cayenne.remote.ClientChannel.onQuery(ClientChannel.java:110)
>> org.apache.cayenne.util.ObjectContextQueryAction.runQuery(
ObjectContextQueryAction.java:282)
>> org.apache.cayenne.CayenneContextQueryAction.execute(
CayenneContextQueryAction.java:51)
Re: Can't see server errors when running ROP
Posted by Tarik <ch...@gmail.com>.
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...@ish.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
>
>
>
Re: Can't see server errors when running ROP
Posted by Aristedes Maniatis <ar...@ish.com.au>.
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