jk2.shm is created in the Apache2\logs directory which has permissions set
to: Everyone - Full Control.
Any other ideas?
-Original Message-
From: Mark Pelillo [mailto:[EMAIL PROTECTED]]
Sent: July 01, 2002 5:32 PM
To: Tomcat Users List
Subject: Re: Apache 2.0.39 modjk2
check
-Original Message-
From: Short, Dave [mailto:[EMAIL PROTECTED]]
Sent: 2. srpanj 2002 17:00
To: 'Tomcat Users List'
Subject: RE: Apache 2.0.39 modjk2
jk2.shm is created in the Apache2\logs directory which has
permissions set
to: Everyone - Full Control.
Any other ideas
So, these are debugging messages that can safely be ignored?
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]]
Sent: July 02, 2002 8:54 AM
To: 'Tomcat Users List'
Subject: RE: Apache 2.0.39 modjk2
-Original Message-
From: Short, Dave [mailto:[EMAIL PROTECTED
-Original Message-
From: Short, Dave [mailto:[EMAIL PROTECTED]]
Sent: 2. srpanj 2002 18:15
To: 'Tomcat Users List'
Subject: RE: Apache 2.0.39 modjk2
So, these are debugging messages that can safely be ignored?
Yes, as all warnigs can, until something hit you in the head
Thanks!
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]]
Sent: July 02, 2002 9:36 AM
To: 'Tomcat Users List'
Subject: RE: Apache 2.0.39 modjk2
-Original Message-
From: Short, Dave [mailto:[EMAIL PROTECTED]]
Sent: 2. srpanj 2002 18:15
To: 'Tomcat Users
Does anyone know why Apache 2.0.39 is reporting the [warn] messages in the
error.log file?
[Mon Jul 01 13:16:42 2002] [notice] Parent: Created child process 1752
[Mon Jul 01 13:16:42 2002] [notice] Child 1752: Child process is running
[Mon Jul 01 13:16:43 2002] [warn] workerEnv.init() ok
check the permissions of the directory where jk2.shm file is going.
Make sure the account which is running tomcat has permission to write
into the directory.
On Mon, 2002-07-01 at 15:25, Short, Dave wrote:
Does anyone know why Apache 2.0.39 is reporting the [warn] messages in the
error.log