2007/3/30, Mladen Turk <[EMAIL PROTECTED]>:
Henri Gomez wrote:
>
> I allready told you that you didn't have to delay the release for i5
> problems and you could go on with it.
>
Sounds fair.
If you came up with the patches, we can bump a next release
that'll fix them. However, since we got that far I wonder why
the logging is faulty. Can it be because of fputs instead fwrite,
and EBCDIC? If you can, try replacing fputs with fwrite and see
if it works.
Well I'm working on locating the problems :
Two problems for now :
- The l->log() problem
- Something related to HTTP 500 error and the following part of code
in mod_jk.c :
if (!r->sent_bodyct && r->status >= HTTP_BAD_REQUEST) {
jk_log(xconf->log, JK_LOG_INFO, "No body with status=%d"
" for worker=%s",
r->status, worker_name);
JK_TRACE_EXIT(xconf->log);
return r->status;
On i5 the r->sent_bodyct is allways set to 0.
As such when we get an HTTP 500 error (ie a SOAP Fault), jk think
there is no body to send back to client (which is not true) and let
Apache handle the 500 error instead of relaying the XML fault content
sent by Tomcat
If I discard the r->sent_bodyct check, I get the correct SOAP replies
in my client.
if (0 && r->status >= HTTP_BAD_REQUEST) {
jk_log(xconf->log, JK_LOG_INFO, "No body with status=%d"
" for worker=%s",
r->status, worker_name);
JK_TRACE_EXIT(xconf->log);
return r->status;
There is something weird in mod_jk on i5, and I'm looking for all the
various #ifdef AS400 to check what's is going on.
I didn't understand why the sent_bodyct is not set since I see the
content in jk log ;(
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
