This is a good way.  Unfortunately, I believe resin-admin uses  
Quercus.  I have disabled Quercus because I have php apps running  
that are not running properly under it.  When I enable php  
processing, Resin takes control over ALL files with the php  
extension, which shouldn't be the case (btw, I do run an Apache  

mod_caucho is taking over all control of all files with the php  
extension.  I guess I should consider this a bug since mod_caucho  
should only pass php processing to Resin only for the specific web- 
app paths and not all PHP files.  This way, I can have Resin Quercus  
coexisting peacefully with PHP itself.


On Oct 6, 2007, at 12:35 PM, Scott Ferguson wrote:

> On Oct 6, 2007, at 12:03 PM, Chris Chen wrote:
>> Rather than doing all the profiling like you (which I would have
>> liked to but i was too lazy), I just did a thread dump.
> By the way, the Resin admin now has a quick-and-dirty profiler (and
> thread dumper and heap dumper) which is really handy when you're too
> lazy to configure a full profiler, or on a live system when you want
> some data immediately.
> -- Scott
> _______________________________________________
> resin-interest mailing list

resin-interest mailing list

Reply via email to