Looking at the code, all the exceptions - including in doPost() - do
logging . Enable logging and you should see errors.
In the following log4j.properties - providing you have a log4j.jar
under WEB-INF/lib, you've enabled log4j by editing
commons-logging.properties, and you've replaced the log4j properties
with this one - two files are put in tomcat/logs , one for
org.apache classes and another for com.myapp. Also, you'll see the
messages in catalina.out :
log4j.appender.console1=org.apache.log4j.ConsoleAppender
log4j.appender.console1.layout=org.apache.log4j.PatternLayout
log4j.appender.console1.layout.ConversionPattern=%m
log4j.appender.console2=org.apache.log4j.ConsoleAppender
log4j.appender.console2.layout=org.apache.log4j.PatternLayout
log4j.appender.console2.layout.ConversionPattern=%d [%c] - %m%n
log4j.appender.apacheOrg=org.apache.log4j.RollingFileAppender
log4j.appender.apacheOrg.layout=org.apache.log4j.PatternLayout
log4j.appender.apacheOrg.layout.ConversionPattern=%d [%c] - %m%n
log4j.appender.apacheOrg.File=${catalina.home}/logs/apache_logs.log
log4j.appender.apacheOrg.MaxFileSize=40000KB
log4j.appender.apacheOrg.MaxBackupIndex=1
log4j.appender.appErros=org.apache.log4j.RollingFileAppender
log4j.appender.appErros.layout=org.apache.log4j.PatternLayout
log4j.appender.appErros.layout.ConversionPattern=%m
log4j.appender.appErros.File=app_erros.log
log4j.appender.appErros.MaxFileSize=400KB
log4j.appender.appErros.MaxBackupIndex=1
log4j.appender.appDebug=org.apache.log4j.RollingFileAppender
log4j.appender.appDebug.layout=org.apache.log4j.PatternLayout
#log4j.appender.appDebug.layout.ConversionPattern=%-4r %-5p %c %x - %m%n
log4j.appender.appDebug.layout.ConversionPattern=%d [%c] - %m%n
log4j.appender.appDebug.File=${catalina.home}/logs/app_debug.log
log4j.appender.appDebug.MaxFileSize=40000KB
log4j.appender.appDebug.MaxBackupIndex=1
log4j.rootLogger=DEBUG, console2
log4j.category.com.myapp=DEBUG, console2, appDebug
log4j.category.org.apache=DEBUG, console2, apacheOrg
HTH,
Robert
On 9/8/06, Doolittle, Todd <[EMAIL PROTECTED]> wrote:
I noticed this also. When the Axis code service code throws an
exception, no stack trace is logged. I found a bug in the Axis servlet
that caused it to throw a null pointer exception. There was nothing in
the Tomcat logs. The only indication was that the Tomcat console
showed...
Sep 8, 2006 1:50:34 PM org.apache.axis2.transport.http.AxisServlet
doPost SEVERE: java.lang.NullPointerException
Is there some way to get Axis to dump a stack trace to the Tomcat logs
when it throws an exception?
-----Original Message-----
From: zolv [mailto:[EMAIL PROTECTED]
Sent: Friday, September 08, 2006 1:47 PM
To: [email protected]
Subject: Re: [axis2] Problems with response
> My guess is that you have a stacktrace on the server side that will
> point to the problem. If its still not clear what the cause is, post
> your code and the stacktrace and maybe we can help.
I understand, but this is the only output what I get (on server (in
fact: service) side). Code that makes an output is in try/catch and
there is no exception thrown. My code doesn't throws any exceptions. My
service method finished normally, and this is what I get in Tomcat's
(5.5.17) console AFTER my "return response; // OMElement response;"
There is one thing in addition. When I cut down the output, so the
output SOAP message is smaller (no changes in service code!), then
everything works fine. So It's something like, that I'm trying send too
big SOAP messages. Is some restrictions in SOAP standards/Axis2 engine
about SOAP message max size?
I think sourcecode isn't needed. Imagine sth like this (hand coding
now):
OMElement response = factory.createElement( ... );
for( int i = 0 ; i < 1000 ; i++ ) {
response.addChild( factory.createElement( ... ) );
}
return response;
(I will try to do it tomorrow in work, but I'm sure that It will
generate the same error.)
Thanx for answer.
Radek Adamiak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
