Re^6: Problems with multiple inheritance

We're on 5.8.6, and multiple inheritance is generally working for us. This is the first time this has been an issue, but the Apache::Reload issue makes sense. We have actually been running into more and more problems with using Apache::Reload as our code base has gotten more and more complicated. Even simple inheritance breaks it sometimes. This might just be the straw that breaks the camel's back that forces us to figure out a way to actually get the servers restarted.

BTW, we're running Solaris (9, soon 10) and it's my understanding that graceful restarts of apache are buggy, although I haven't checked to see if that's been fixed, otherwise we'd be using that.

If anyone has any recommendations on how to deal with restarting Apache servers in a clustered environment (I know this is getting off topic now) please let me know.

Comment on Re^6: Problems with multiple inheritance

Replies are listed 'Best First'.
Re^7: Problems with multiple inheritance by perrin (Chancellor) on Feb 23, 2007 at 20:39 UTC
You shouldn't use graceful restarts with mod_perl. You should shut it down and start it up. Having a cluster makes this easier, since it means you can take half the machines out of the load balancer, restart apache on them, put them back in the load balancer, and then do the same on the other half. Obviously this doesn't work when you have database schema changes too, but neither does your current system with Apache::Reload.	[reply]
Re^8: Problems with multiple inheritance by rhesa (Vicar) on Feb 24, 2007 at 01:35 UTC
You shouldn't use graceful restarts with mod_perl. Is this still true for Apache 2.x? I'm using 2.2 in production (with mod_perl 2.0.2), and always use graceful. I haven't ever seen an issue with it.	[reply]
Re^9: Problems with multiple inheritance by perrin (Chancellor) on Feb 26, 2007 at 17:07 UTC
Good point. I belive this is no longer an issue with mod_perl 2 because of the way interpreters are shut down. I haven't tried it though.	[reply]