DO NOT REPLY [Bug 9439] New: - mod_jk on solaris not working with apache 2.0.35

[bu...@apache.org]

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=9439>.
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=9439

mod_jk on solaris not working with apache 2.0.35

           Summary: mod_jk on solaris not working with apache 2.0.35
           Product: Tomcat 4
           Version: 4.0.3 Final
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Connector:Other
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: drosenstark@alchemedia.com


In trying to get mod_jk to work on Solaris 8 for apache 2.0.35, i found a 
problem in the startup, which is that the function init_jk was getting called 
multiple times when it should not have been. This led to the number of workers 
being doubled and then it was not working.

The fix is simple: add the same check that appears in the function 
jk_post_config to the child_init function, so that the code reads as follows:
if(!conf->was_initialized) {
     conf->was_initialized = JK_TRUE;        
     init_jk( pconf, conf, s );
}

instead of just calling the init_jk without that check.

I also found that apxs was not working as expected, perhaps due to the fact 
that it was missing -G in the gcc command, but I am not sure

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>