tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 23483] New: - More than 42 channels causes JK2 to segfault
Date Mon, 29 Sep 2003 12:48:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23483>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23483

More than 42 channels causes JK2 to segfault

           Summary: More than 42 channels causes JK2 to segfault
           Product: Tomcat 4
           Version: 4.1.27
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: keith@kgbinternet.com


workers2.properties setting up connections to Apache2 works great for 
up to 42 constructs like:

[channel.un:somename]
info=AF_UNIX socket connecting to  "host"
file=/home/somename/jakarta-tomcat/work/jk2.socket
debug=0

but as soon as I add the 43rd, Apache segfaults on the restart.  Is there 
some hard coded array or something somewhere?  I'm using the Jk2 that came 
with Tomcat 4.1.27

Mime
View raw message