I think that you have many processes because each tomcat thread is
mapped on a system process.
I think this depends on the java vm/kernel, but I don't know the details.
But it shouldn't be a problem, as long as I know.
Also on my debian system, with kernel 2.4, I have the same behaviuor.
Hope th
Hi Rainer
a very big thanks for your help, and also for your work in the
connector project.
My work and passion depends on your work: I will never thank enough
you and the many people working on opensource projects like tomcat.
I will test the new version as soon as it's released.
Best regards
E
I don't know if this helps, but I had a similar problems once, and it
was caused by a filter which was reading a parameter from the request.
This first access set the encoding to 8859-1, overriding all my
following settings.
I would start from this ... hope this helps.
Good luck!
Enrico
On 18/1
]> wrote:
Adding to my own comments: I think I found a problem. So one more question:
Do you also observe a real problem, or only the info log messages. Do
the requests actually fail?
Regards,
Rainer
Enrico Donelli schrieb:
> Thanks Rainer for your reply!
>
> Here's my mo
Does the directory /etc/apache2/logs
exist and again, does the apache user have write permissions there?
Does the log message already show, when you are starting? If yes, could
you reproduce with JkLogLevel trace and provide the resulting file?
Regards,
Rainer
Enrico Donelli schrieb:
> Hi a
Hi all,
I'm having some problems with the mod_jk connector.
In mod_jk logs file I have a lot of lines like
[Fri Nov 17 23:07:18 2006] [12236:7072] [error]
jk_child_init::mod_jk.c (2406): Attachning
shm:/etc/apache2/logs/jk-runtime-status errno=2
and from time to time the connector completely loc
