You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/09/29 14:48:35 UTC
DO NOT REPLY [Bug 23483] New: -
More than 42 channels causes JK2 to segfault
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