tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Przemys³aw Korona <przemyslaw.kor...@ckzeto.com.pl>
Subject mod jk2 problem, segmetation fault
Date Tue, 01 Jul 2003 15:52:18 GMT
Hi there,
I have a problem with integrating tomcat and apache using jk2.

System configuration: suse 8.1
			apache 1.3.26
			  tomcat 4.1.24

Correct me if I am wrong, but to establish link bw. apache and tomcat I 
need to:
- add a connector in server.xml
     <Connector acceptCount="10" bufferSize="2048" 
className="org.apache.ajp.tomcat4.Ajp13Connector" 
port="8009"      minProcessors="5" maxProcessors="75" debug="0" 
enableLookups="true">
         <Factory 
className="org.apache.catalina.net.DefaultServerSocketFactory"/>
     </Connector>

- load jk2 module in httpd.conf

- configure workers2.properties
[shm]
file=/srv/www/logs/jk2.shm

[channel.socket:192.168.230.14:8009]
info=Ajp13 forwarding over socket
tomcatId=192.168.230.14:8009

[uri:/examples/*]
info=Map the whole webapp

- configure jk2.properties
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config  is working
  shm.file=/srv/www/logs/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


It seems that in tomcat everything is fine (catalina.out after starting 
tomcat ends with:
2003-07-01 17:24:33 HttpConnector[8443] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][0] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][1] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][2] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][3] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][4] Starting background thread
2003-07-01 17:24:34 Ajp13Connector[8009] Opening server socket on all host 
IP addresses
2003-07-01 17:24:34 Ajp13Connector[8009] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][0] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][1] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][2] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][3] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][4] Starting background thread


However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003]  ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:08 2003]  ( info) [mod_jk2.c (292)]: mod_jk.post_config() 
init worker env
[Tue Jul 01 14:47:08 2003]  (error) [jk_logger_file.c (171)]: Can't open 
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003]  ( info) [jk_config_file.c (320)]: cfg.update() 
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003]  ( info) [jk_config_file.c (331)]: 
config.setConfig():  Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003]  (error) [jk_logger_file.c (171)]: Can't open 
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003]  (debug) [jk_uriMap.c (315)]: uriMap.init() 
Fixing Host *
[Tue Jul 01 14:47:08 2003]  ( info) [jk_workerEnv.c (403)]: 
workerEnv.init() ok /srv/www//conf/workers2.properties
Create config for main host
[Tue Jul 01 14:47:09 2003]  ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:09 2003]  ( info) [mod_jk2.c (292)]: mod_jk.post_config() 
init worker env
[Tue Jul 01 14:47:09 2003]  (error) [jk_logger_file.c (171)]: Can't open 
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003]  ( info) [jk_config_file.c (320)]: cfg.update() 
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:09 2003]  ( info) [jk_config_file.c (331)]: 
config.setConfig():  Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:09 2003]  (error) [jk_logger_file.c (171)]: Can't open 
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003]  (debug) [jk_uriMap.c (315)]: uriMap.init() 
Fixing Host *
[Tue Jul 01 14:47:09 2003]  ( info) [jk_workerEnv.c (403)]: 
workerEnv.init() ok /srv/www//conf/workers2.properties
[Tue Jul  1 16:47:10 2003] [notice] Apache/1.3.26 (Linux/SuSE) 
mod_jk2/2.0.0 configured -- resuming normal operations
[Tue Jul  1 16:47:10 2003] [notice] suEXEC mechanism enabled (wrapper: 
/usr/sbin/suexec)
[Tue Jul  1 16:47:10 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)

Finally when I try to open a page from tomcat without specifying port 8080 
in apache a following error is added:
[Tue Jul  1 16:47:49 2003] [notice] child pid 16282 exit signal 
Segmentation fault (11)

While in tomcat there is no information, that some page was requested.
Does anyone have any idea what is causing this Segmentation fault?

Regards,
Przemek


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


Mime
View raw message