Tomcat 3.3 w/ mod_jk? Segmentation fault?
Topic: Tomcat
Dale Dunavan, Jan 11, 2002 [replies:6]
Running Tomcat 3.3 with mod_jk;
All seems fine via port 8080.
When I try to execute with Apache, I see the worker allocate, etc. but the segmentation fault occurs. Not much debugging to go on.
.
Anybody have any ideas, I've run out.
Thank you..
psantt@interaccess.com
Is this item
helpful? yes no
Previous votes Yes: 0 No: 0
|
|
 |
Re: Tomcat 3.3 w/ mod_jk? Segmentation fault?
Topic: Tomcat
Alessandro A. Garbagnati PREMIUM, Jan 12, 2002 [replies:5]
Dale,
The fact that Tomcat works fine on his port (as a standalone web-server + servlet-container), makes me think that the problem is on the mod_jk module or in Apache (but I doubt it).
Maybe you could get the source code of mod_jk and recompile it and see if the problem happens again.
Is this item
helpful? yes no
Previous votes Yes: 0 No: 0
|
|
|
|
|
Re[2]: Tomcat 3.3 w/ mod_jk? Segmentation fault?
Topic: Tomcat
Dale Dunavan, Jan 12, 2002 [replies:4]
Hey Alessandro (and all),
Additional info: apache 1.3.19 / Tomcat 3.3. / mod_jk usage / IBM 1.3.0 JVM;
I've tried a mix of tomcat4/3, ibm/sun 1.3.x jdk, mod_jk/mod_webapp... All seem to be giving the same issue...
Thanks for the contribution; I've gotten that far, and here's the debugging info I get from full debug on the mod_jk module (when just trying to get to the /examples/ stuff from the Tomcat build; the same debug info hits when I try a full path to a jsp inside the examples. the segmentation fault occurs inside mod_jk, but it seems to be getting quite far into it if it's a pure mod_jk problem(?)
[Sat Jan 12 14:19:24 2002] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker
[Sat Jan 12 14:19:24 2002] [jk_uri_worker_map.c (368)]: Attempting to map URI '/examples/'
[Sat Jan 12 14:19:24 2002] [jk_uri_worker_map.c (391)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 -> /examples/
[Sat Jan 12 14:19:24 2002] [jk_worker.c (123)]: Into wc_get_worker_for_name ajp13
[Sat Jan 12 14:19:24 2002] [jk_worker.c (127)]: wc_get_worker_for_name, done found a worker
from apache log...
[Sat Jan 12 14:19:24 2002] [notice] child pid 3634 exit signal Segmentation fault (11)
[Sat Jan 12 14:19:24 2002] [notice] child pid 3632 exit signal Segmentation fault (11)
Is this item
helpful? yes no
Previous votes Yes: 0 No: 0
|
|
|
|
|
|
|
Re[4]: Tomcat 3.3 w/ mod_jk? Segmentation fault?
Topic: Tomcat
Dale Dunavan, Jan 24, 2002 [replies:1]
Hey Will:
I finally figured this out a few days ago, and forgot to post the fix; for the more pure Unix inclined people, the fix is probably easy. The issue indeed lies with the way mod_jk.so works with different builds of Apache. You're pretty much stuck in rebulding the mod_jk.so module from the apxs that hopefully was included with your Apache build; (apxs is one big perl script...)
I'm not exactly comfortable with the c compiler options in Unix, so here it goes: Not the easiest, but it finally worked....
perl /directory to apache bin/apxs -o mod_jk.so -I/usr/local/jdk1.3.1/include/linux -I../jk -I/usr/local/jdk1.3.1/include -c *.c
I had several problems getting the source in the right directories; so I essentially moved all *.c and *.h files from the jk source into the directory I ran the apxs command from (or could have added the include directories in the command line, but was just too lazy...)
Also, I had to change a couple of lines in the apxs source code in order to get it to work. (Let me know if you have any issues with the apxs command giving you an error or two; if so I'll try to figure out what changes I made in the apxs script; Please let me know the error messages if you have a problem)
I know this isn't the greatest explanation, I took a lot of advice from http://jakarta.apache.org/tomcat/tomcat-3.2-doc/mod_jk-howto.html#s64
(assuming you're running with Linux; if not, look just above for explanations with other Unix flavors)
Is this item
helpful? yes no
Previous votes Yes: 0 No: 0
|
|
|
|
|
|
|
|
Re[5]: Tomcat 3.3 w/ mod_jk? Segmentation fault?
Topic: Tomcat
Will Glass-Husain, Jan 24, 2002
Thanks!
I figured that out as well, and was quite proud of my brainstorm-- no other solutions were posted on the net. Then I saw your response :-)
The issue is an incompatibility with the libc in the released mod_jk.so. Recompiling mod_jk.so worked fine for me as well.
For the record, here's the original problem description of the JDK from Sun
http://java.sun.com/j2se/1.3/relnotes.html
For the solution, I also found the mod_jk how-to very helpful.
WILL
Is this item
helpful? yes no
Previous votes Yes: 0 No: 0
|
|
|
|
|
|
|
