BTW, there is still the log problem in V5R4 which make requests core :

000002EE:940456 Stack:  mpmt_pthread.c : request thread exception
000002EE:940504 Stack:  Library    / Program     Module      Stmt
Procedure
000002EE:940520 Stack:  QSYS       / QLESPI      QLECRTTH    17    :
LE_Create_Thread2__FP12crtth_parm_t
000002EE:940528 Stack:  QSYS       / QP0WPINT    QP0WSPTHR   19    :
pthread_create_part2
                                           TRCTCPAPP Output
000002EE:940544 Stack:  QHTTPSVR   / QZSRAPR     THREAD      2     :
dummy_worker
000002EE:940552 Stack:  QHTTPSVR   / QZSRCORE    MPMT_PTHRE  21    :
request_thread
000002EE:940560 Stack:  QHTTPSVR   / QZSRCORE    HTTP_ASYNC  6     :
ap_process_IOCP
000002EE:940568 Stack:  QHTTPSVR   / QZSRCORE    HTTP_ASYNC  47    :
asyncIO_wait
000002EE:940576 Stack:  QHTTPSVR   / QZSRCORE    CONNECTION  5     :
ap_run_process_connection
000002EE:940592 Stack:  QHTTPSVR   / QZSRCORE    HTTP_CORE   12    :
ap_process_http_connection
000002EE:940600 Stack:  QHTTPSVR   / QZSRCORE    HTTP_REQUE  19    :
ap_process_request
000002EE:940608 Stack:  QHTTPSVR   / QZSRCORE    HTTP_CONFI  27    :
ap_invoke_handler
000002EE:940616 Stack:  QHTTPSVR   / QZSRCORE    HTTP_CONFI  5     :
ap_run_handler
000002EE:940624 Stack:  QHTTPSVR   / MOD_JK1222  MOD_JK      83    :
jk_handler
000002EE:940640 Stack:  QHTTPSVR   / MOD_JK1222  JK_AJP_COM  51    :
ajp_service
000002EE:940648 Stack:  QHTTPSVR   / MOD_JK1222  JK_AJP_COM  39    :
ajp_get_reply
000002EE:944592 Stack:  QHTTPSVR   / MOD_JK1222  JK_AJP_COM  30    :
ajp_process_callback
000002EE:944608 Stack:  QHTTPSVR   / MOD_JK1222  MOD_JK      17    :
ws_write
000002EE:944616 Stack:  QHTTPSVR   / MOD_JK1222  JK_UTIL     36    :
jk_log
000002EE:944624 Stack:  QHTTPSVR   / QZSRCORE    MPMT_PTHRE  11    :
Request_Thread_Excp_Handler
000002EE:944640 Stack:  QHTTPSVR   / QZSRCORE    MPMT_PTHRE  26    :
Common_Thread_Excp_Handler_Code
000002EE:944648 Stack:  QHTTPSVR   / QZSRAPR     OS400TRACE  7     :
apr_dstack_CCSID
000002EE:944656 Stack:  QSYS       / QP0ZCPA     QP0ZUDBG    3     :
Qp0zDumpStack
000002EE:944672 Stack:  QSYS       / QP0ZSCPA    QP0ZSDBG    2     :
Qp0zSUDumpStack
000002EE:944680 Stack:  QSYS       / QP0ZSCPA    QP0ZSDBG    12    :
Qp0zSUDumpTargetStack
000002EE:944680 Stack:  Completed

Still the jk_log problem ;(


2007/4/20, Mladen Turk <[EMAIL PROTECTED]>:
Henri Gomez wrote:
> 2007/4/20, Mladen Turk <[EMAIL PROTECTED]>:
>> [EMAIL PROTECTED] wrote:
>> > Author: hgomez
>> >
>> > -#ifdef AS400
>> > +#if defined(AS400) && !defined(AS400_UTF8)
>>
>> So, seems that UTF8 is now default for AS400
>
> On i5/OS V5R4 (not on previous release)
>

But they are supposed to work, right?

>
> - If we couldn't get support for i5/OS (AS400) from IBM labs, should
> we stop support i5/OS in JK ?

Probably. We have the same situation with iPlanet
(SunOne, or what ever they are calling that nowadays)

 From all your comments it is obvious that the IBM Httpd
server is a product that has very little in common with
standard httpd distributions from ASF. Although they might
name their product (apache httpd based), it is obviously
not an ASF compatible product.
So, dropping a support is the only thing we can do.
If someone is willing to support it, then it should be
listed as a separate 'web container', but not as a Apache
Httpd. Trying to insert #ifdef for every change there is
would lead to nowhere.

Think we had the same thing with Domino, that was
IBM version of IIS server, and guess how it ended?

Regards,
Mladen.

---------------------------------------------------------------------
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]

Reply via email to