Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 40877]  New:  - JK1 and IIS6: Problem with
 multithreading / shared memory
Message-ID: <bug-40877-78@http.issues.apache.org/bugzilla/>
Date: Thu,  2 Nov 2006 09:01:42 -0800 (PST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40877>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40877

           Summary: JK1 and IIS6: Problem with multithreading / shared
                    memory
           Product: Tomcat 5
           Version: Unknown
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Native:JK
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: bjoern@syltonline.de


Hi Mladen,
We migrate from JK2 to JK1 in the moment. We encountered some problems on 
bigger Webfarms with the JK1 / IIS6 in full Application Isolation mode. The 
main blocker is, when a Application pool is run in multithreading 
configuration (App-Pool-> Properties->Performance-> Web-Garden-> Number of 
Worker Processes), the JK does not start right: (Loglevel Info)

[Thu Nov 02 16:35:53 2006] [5872:5924] [error] validate::jk_lb_worker.c 
(1104): allocating worker record from shared memory
[Thu Nov 02 16:35:53 2006] [5872:5924] [error] wc_create_worker::jk_worker.c 
(158): validate failed for P-NG-TC3Hx
[Thu Nov 02 16:35:53 2006] [5872:5924] [error] build_worker_map::jk_worker.c 
(256): failed to create worker P-NG-TC3Hx
[Thu Nov 02 16:35:54 2006] [4012:6612] [error] wc_create_worker::jk_worker.c 
(146): factory for lb failed for P-NG-TC3Hx
[Thu Nov 02 16:35:54 2006] [4012:6612] [error] build_worker_map::jk_worker.c 
(256): failed to create worker P-NG-TC3Hx
[Thu Nov 02 16:35:57 2006] [1672:6912] [error] wc_create_worker::jk_worker.c 
(146): factory for lb failed for P-NG-TC3Hx
[Thu Nov 02 16:35:57 2006] [1672:6912] [error] build_worker_map::jk_worker.c 
(256): failed to create worker P-NG-TC3Hx
[Thu Nov 02 16:36:27 2006] [6100:3092] [error] wc_create_worker::jk_worker.c 
(146): factory for lb failed for P-NG-TC3Hx
[Thu Nov 02 16:36:27 2006] [6100:3092] [error] build_worker_map::jk_worker.c 
(256): failed to create worker P-NG-TC3Hx

It runs fine with a singler worker process. I also tried to 
reduce "connection_pool_size" to 1 (from 64) because there are known probs 
with Apache prefork, but it didn't help. This is a real production blocker.

I also realized that in the jkstatus, the live-config and stati apply only to 
the application pool this web is in. If i reconfigure a jk in a web in a 
different pool, it is totally independent. As I understand it, all jk-
instances on one server should share this information through a shared memory 
area. This doesn't seem to work either.With that bug, one can't use the nice 
feature to reconfigure the jk online on IIS6 with multiple application pools.

If you need config files or debug logs, please ask. These are from production 
environment, so I'd prefere to send them personally.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org