Next release candidate
Just looking for quick input. Most of the patches floating out there should now be committed. We need to address the double-loading of aspnetmount's. And load any .NET version by explicit name (e.g. even the 2.0 beta versions, whichever, by their version and signature.) Other than coming up with those two patches, can anyone point at some patch I've missed before I throw together the next candidate? Bill
RE: httpmodule bug
At 02:14 AM 11/24/2004, Yussef Alkhamrichi wrote: But we have to decide what to do here. Either 1) the hosts aren't being torn down (and we need to), or 2) we need to avoid 'test creating' the hosts at initial startup. The gs (global server_rec) pointer is volatile upon subsequent config phases. I've had a good look at the code and tested some minor changes. But I've a question: In the method 'asp_net_pre_config' we are making sure that global conf is persistent. If the global conf is persistent consequently all hosts in conf-hosts should be created (and thus have ASP.NET configured) exactly once. I ask this because you mentioned the test creating by the way Apache functions, I don't see in which phase the testcreating takes place. If you look here, in function main() for calls to ap_read_config http://svn.apache.org/viewcvs.cgi/httpd/httpd/trunk/server/main.c?rev=106103view=markup you will see that we read the config, run the pre, open_logs and post config phases once before the for () loop, and each time the server gracefully restarts within that loop. But you will notice the process-pool is created only once, up front, and persists for the lifetime of this process. A related question is wether or not the data set by apr_pool_userdata_setn holds during the two passes of configurating Apache as was mentioned before ? Not against the configuration pool. But the process pool lives much longer. This is why we root out the conf-pool's parent, our process pool. Bill
Re: httpmodule bug
By the way using old RC1 MSI Will look at HttpApplication state settings between turkey cooking and eating - seems something touchs them? (?) Go relax Bill Jeff - Original Message - Sent: Wednesday, November 24, 2004 5:05 PM Subject: Re: httpmodule bug From: Yussef Alkhamrichi Hope someone out there puts together a custom HttpModule and tries this out, I will continue to search if I can find this bug (sadly there isn't a way to hack into the config file loading of .NET). I tried a simple Hello HttpModule and on first try: Server Error in '/TestHttpModules' Application. The module 'HelloWorldModule' is already in the application and cannot be added again Tried remove in web.config Line 2: system.web Line 3: httpModules Line 4:remove name=HelloWorldModule / Line 5: add name=HelloWorldModule Line 6:type=HelloWorldModule, HelloWorldModule / Parser Error Message: There is no 'HelloWorldModule' module in the application to remove. Tried blocking out the whole name this time... httpModules !-- remove name=HelloWorldModule / add name=HelloWorldModule type=HelloWorldModule, HelloWorldModule / -- /httpModules System.Threading.ThreadAbortException: Thread was being aborted. Adding a clear works configuration system.web httpModules !-- remove name=HelloWorldModule / -- clear / add name=HelloWorldModule type=HelloWorldModule, HelloWorldModule / /httpModules /system.web /configuration Moving clear to bottom httpModules !-- remove name=HelloWorldModule / clear / -- add name=HelloWorldModule type=HelloWorldModule, HelloWorldModule / clear / /httpModules runs with no error but not httpmodules output either! Seems mod_aspdotnet needs a clear first as you said! Jeff
