At 21:12 19.04.2002, Sören Stuckenbrock wrote: >Hi there, > >mod_perl-newbie needs help! >I have a nasty problem using Perl Modules under mod_perl. >I've developed a CGI-Application, that retrieves its configuration values >from a module that gets included (with "use") in every Script of the >application. >So far no problem. > >But when I try to set up more than one instance of the application on the >same (virtual) server under different paths, with different configuration >values in the config-module (which I must do) mod_perl mixes up the >different configuration-modules. Every httpd-child only loads the >configuraion module of the applications instance that it first served a >request for. >If the same process serves a request for a different instance later, it >always uses the config-module of the instance it first served a request for, >because it thinks it already has loaded the right module.
This is because once you use a module (say My::Config), it won't be reloaded as that package name has already been loaded. If your configuration files are different, and in different locations, you should be giving them different names: say My::App1::Config, My::App2::Config, etc. THen you won't have that problem. See http://perl.apache.org/preview/modperl-docs/dst_html/docs/1.0/guide/porting.html#Writing_Configuration_Files for more information. -- Per Einar Ellefsen [EMAIL PROTECTED]
