Running production site under Jetty

[Colin Paul Adams <co...@colina.demon.co.uk>]

I've had a mysterious problem running Cocoon using jetty - every so
often I get a Cocoon Resource Not found message, and jetty has to be
restarted.

Today I spent some time probing into the problem. It appears that
jetty unpacks the cocoon.war file into a directory under /tmp, and a
program called tmpwatch on my linux system is deleting this entire
directory after 10 days, as it reckons it's not being used.

What's the recommended way around this?
-- 
Colin Paul Adams
Preston Lancashire

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Running production site under Jetty

[Upayavira <uv...@upaya.co.uk>]

Colin Paul Adams wrote:

>I've had a mysterious problem running Cocoon using jetty - every so
>often I get a Cocoon Resource Not found message, and jetty has to be
>restarted.
>
>Today I spent some time probing into the problem. It appears that
>jetty unpacks the cocoon.war file into a directory under /tmp, and a
>program called tmpwatch on my linux system is deleting this entire
>directory after 10 days, as it reckons it's not being used.
>  
>
Er, not deploying as a war? Personally I've never seen the benefit really.

You can always unpack an archive yourself, and configure jetty to mount 
a webapp with:

    <Call name="addWebApplication">
        <Arg>/</Arg>
        <Arg>d:/documents/cocoon/mysite/cocoon-2.1/build/webapp/</Arg>
        <Set name="virtualHosts">
            <Array type="java.lang.String">
                <Item>mysite.com</Item>
                <Item>www.mysite.com</Item>
            </Array>
        </Set>
    </Call>

Does that make sense?

Regards, Upayavira



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org