[mod_cluster-issues] [JBoss JIRA] Resolved: (MODCLUSTER-199) Segmentation fault in Apache worker when using different balancernames and Aliases.

Segmentation fault in Apache worker when using different balancernames and Aliases. ----------------------------------------------------------------------------------- Key: MODCLUSTER-199 URL: https://issues.jboss.org/browse/MODCLUSTER-199 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: RedHat EL 5.5 x86_64, Apache 2.2.3, mod_cluster-1.1.0.Final-linux2-x64 Reporter: Geert Pante Assignee: Jean-Frederic Clere Attachments: core.zip Hi all, We did a test setup with 2 apache servers and 2 backend JBoss servers. One JBoss Server has 2 applications deployed on one alias, and the other one has one application deployed as ROOT application context. In the jbossweb server.xml we set Aliases, and this worked most of the time, with applications http://alias1/app1, http://alias1/app2 and http://alias2/ all proxied nicely through both apache servers. The names alias1 and alias2 were mapped to a virtual IP that could be switched dynamically between the apache servers. However, we did have some problems that after a restart of one of the apache server, it would get 'All workers are in error state' for one of the applications, and it would no longer send ajp ping requests. The JBoss server continues to send STATUS messages happily. In mod_cluster-manager all seems well, too. Initially we used a default ManagerBalancerName in the Apache config, so both were using the same balancer. As a test we tried to remove the ManagerBalancerName in the apache config, and set a balancername in the mod_cluster-beans.xml. In mod_cluster-manager we saw the different balancers now, but again, on one of the apache servers, the proxying does not work, this time with a segmentation fault. See attached coredump =============================================== Core was generated by `/usr/sbin/httpd'. Program terminated with signal 11, Segmentation fault. (gdb) thread apply all bt full Thread 2 (Thread 31682): #0 0x00002b81583146f7 in kill () from /lib64/libc.so.6 No symbol table info available. #1 <signal handler called> No symbol table info available. #2 0x00002b815835d7c0 in strlen () from /lib64/libc.so.6 No symbol table info available. #3 0x00002b8157ca840e in ?? () from /usr/lib64/libapr-1.so.0 No symbol table info available. #4 0x7069626d00000000 in ?? () No symbol table info available. #5 0x00002b815f9755c8 in ?? () No symbol table info available. #6 0x00002b815669e230 in ?? () No symbol table info available. #7 0x00002b81566a1e08 in ?? () No symbol table info available. #8 0x00002b815f973f90 in ?? () No symbol table info available. #9 0x00002b815f32365f in cluster_get_sessionid (r=0x2b815f973f18, stickyval=0x1 <Address 0x1 out of bounds>, uri=0x2b815f9755c8 "/", sticky_used=0x7) at mod_proxy_cluster.c:1032 sticky = <value optimized out> sticky_path = <value optimized out> route = <value optimized out> #10 0x00002b815f324e92 in get_route_balancer (r=0x2b815f973f90, conf=0x2b815669d1a8) at mod_proxy_cluster.c:1788 balancer = 0x2b81566a1e08 route = <value optimized out> sessionid = <value optimized out> sticky_used = <value optimized out> i = 1 #11 0x00002b815f3251d5 in proxy_cluster_trans (r=0x1) at mod_proxy_cluster.c:1938 balancer = 0x2b815f973f90 "\030?\227_\201+" sconf = 0x2b815f9755c8 conf = 0x1 #12 0x00002b81563e4ba2 in ap_run_translate_name () No symbol table info available. #13 0x00002b81563e5e62 in ap_process_request_internal () No symbol table info available. #14 0x00002b81563f7968 in ap_should_client_block () No symbol table info available. #15 0x00002b815f963870 in ?? () No symbol table info available. #16 0x00002b815f973f90 in ?? () No symbol table info available. #17 0x00002b815f963870 in ?? () No symbol table info available. #18 0x0000000000000000 in ?? () No symbol table info available. Thread 1 (Thread 31683): #0 0x00002b81583b0fc2 in select () from /lib64/libc.so.6 No symbol table info available.