You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by bl...@vmunix.com on 2004/09/27 23:27:33 UTC
JK2 causes SEGV in httpd
I have recently configured Apache 2.0.51 with mod_jk2.so based on the information
from the book "Professional Apache Tomcat 5", and now all requests
to the web server cause a segmentation fault. :) Is there something in my
config that may be causing this? Thanks for any and all help. If it doesn't
look like there are any config errors, please let me know and I'll maybe try on a
different platform. Here are the details of my configuration:
------------------
Apache: 2.0.51 w/ mod_so enabled.
O/S: Suse Linux 9.0
Linux linux 2.4.21-99-default #2 Wed Jun 23 08:37:25 PDT 2004 i686 i686 i386 GNU/Linux
JK2: Suse-9.0-i386 (Binary) from the Jakarta web site.
Tomcat: 5.0.28 (binary from the jakarta web site.) (works fine)
-------------------
-------------------
strace error:
[pid 4816] read(8, "GET / HTTP/1.0\r\n", 8000) = 16
[pid 4816] gettimeofday({1115242251, 884552}, NULL) = 0
[pid 4816] poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 300000) = 1
[pid 4816] read(8, "\r\n", 8000) = 2
[pid 4816] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
-------------------
------------------
httpd startup info:
[Wed May 04 18:47:47 2005] [notice] config.update(): done logger.apache2
[Wed May 04 18:47:47 2005] [notice] config.update(): done config
[Wed May 04 18:47:47 2005] [notice] config.update(): done channel.socket:localhost:8009
[Wed May 04 18:47:47 2005] [notice] config.update(): done shm
[Wed May 04 18:47:47 2005] [notice] config.update(): done ajp13:localhost:8009
[Wed May 04 18:47:47 2005] [notice] config.update(): done uri:/jsp-examples/*
-----------------
-------------------
httpd configuration:
LoadModule jk2_module /usr/local/apache2/modules/mod_jk2.so
JkSet config.file /usr/local/apache2/conf/workers2.properties
-------------------
--------------------
workers2.properties
[logger.apache2]
file=/var/tmp/workers.log
level=INFO
debug=4
[config]
file=/usr/local/apache2/conf/workers2.properties
debug=0
[channel.socket:localhost:8009]
host=localhost
port=8009
tomcatId=myTomcat
[shm]
file=/var/tmp/jk2.shm
size=1000000
[ajp13:localhost:8009]
channel=channel.socket:myTomcat
[uri:/jsp-examples/*]
info=mapping the jsp-examples context of Tomcat
------------------------
jk2.properties
## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
## WHEN YOU EDIT THE FILE.
## COMMENTS WILL BE _LOST_
## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
channelSocket.address=localhost
channelSocket.port=8009
shm.file=/var/tmp/jk2.shm
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
# shm.file=${jkHome}/work/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
---------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: JK2 causes SEGV in httpd
Posted by QM <qm...@brandxdev.net>.
On Mon, Sep 27, 2004 at 05:27:33PM -0400, blaine@vmunix.com wrote:
: I have recently configured Apache 2.0.51 with mod_jk2.so based on the information
: from the book "Professional Apache Tomcat 5", and now all requests
: to the web server cause a segmentation fault. :) Is there something in my
: config that may be causing this?
A segmentation fault is caused by a dereference error in native code
(English: C/C++ accessing memory incorrectly, such as trying "*" or "->"
ops on a null pointer.)
That's a code bug. It may have been uncovered due to your
configuration, but certianly not caused by it.
Have you tried a later version of JK2? You could also try rebuilding
JK2 from source, so it builds against all of the latest APR headers and
such.
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org