https://issues.apache.org/bugzilla/show_bug.cgi?id=46352
--- Comment #9 from Patrick Middleton <[EMAIL PROTECTED]> 2008-12-09 09:33:20 PST --- What I found was that in jk_translate, in the 'good' configuration, e (or, *ext ... the rule_extension_t) remained null after the first call to ap_set_module_config(). There is a second call to ap_set_module_config(). My logging shows that the rule_extension_t has been set before this, and also before the call to map_uri_to_worker_ext() a few lines earlier. In the 'bad' configuration, a crash was occurring before getting as far as three logging calls I added around map_uri_to_worker_ext() and ap_set_module_config(). I noticed that in the 'bad' configuration, there were no JkMount directives at all, so I added some. This did not prevent crashing. Later, the 'good' configuration was crashing too. Right now neither are crashing. Intermittent problems of /services/ , /services/index.jsp and /services.html producing server 404 pages or Tomcat resource-unavailable pages continues. Using <Location> to add a 'SetHandler jakarta-servlet' directive continues to move in and out of the configuration. I am guessing wildly here, but from the symptoms it looks to me like some memory is being allocated for a control structure like a rule_extension_t, and then not initialised by code because it appears to have been initialised already. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
