On Thu, Oct 30, 2008 at 10:52 PM, Caldarale, Charles R
<[EMAIL PROTECTED]> wrote:
>> From: James Ravn [mailto:[EMAIL PROTECTED]
>> Subject: Re: antioJarLocking not working
>>
>> jruby-rack makes a call to the ServletContext's getRootPath() method
>
> No
> From: James Ravn [mailto:[EMAIL PROTECTED]
> Subject: Re: antioJarLocking not working
>
> jruby-rack makes a call to the ServletContext's getRootPath() method
No such animal; perhaps you mean getRealPath()?
> It looks like this is returning the erroneous "/temp-appna
> From: Aaron Axelsen <[EMAIL PROTECTED]>
> To: Tomcat Users List
> Date: Sun, 31 Aug 2008 14:39:46 -0500
> Subject: Re: antioJarLocking not working
> I tried sticking the jars there - but it did not seem to make any
> difference.
>
> Let me recap on what we are
using tomcat 6.018.
Vikas
--
View this message in context:
http://www.nabble.com/antioJarLocking-not-working-tp19187318p19565053.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail
- Original Message -
From: "Aaron Axelsen" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, August 31, 2008 9:39 PM
Subject: Re: antioJarLocking not working
I tried sticking the jars there - but it did not seem to make any
difference.
Let me reca
From: "Aaron Axelsen" <[EMAIL PROTECTED]>
>> To: "Tomcat Users List"
>> Sent: Thursday, August 28, 2008 10:19 PM
>> Subject: Re: antioJarLocking not working
>>
>>
>>
>>> The jar's its probably having issues with
Johnny Kewl wrote:
>
> - Original Message - From: "Aaron Axelsen" <[EMAIL PROTECTED]>
> To: "Tomcat Users List"
> Sent: Thursday, August 28, 2008 10:19 PM
> Subject: Re: antioJarLocking not working
>
>
>> The jar's its proba
- Original Message -
From: "Aaron Axelsen" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Thursday, August 28, 2008 10:19 PM
Subject: Re: antioJarLocking not working
The jar's its probably having issues with are jruby-complete-1.1.3.jar
and jruby
The jar's its probably having issues with are jruby-complete-1.1.3.jar
and jruby-rack-0.9.1.jar since those are the ones that were getting
locked. Any suggestions on anything else I can try to attempt to
resolve it?
-- Aaron
Mark Thomas wrote:
> Aaron Axelsen wrote:
>
>> I set the workdir on
Aaron Axelsen wrote:
> I set the workdir on the global context - I can see that files are being
> created there, however that same error still exists. For some reason it
> insists on looking in Tomcat 6\temp-Foo5
>
> Any suggestions?
It looks like a bug in the jar. It might be using a non-portab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I set the workdir on the global context - I can see that files are being
created there, however that same error still exists. For some reason it
insists on looking in Tomcat 6\temp-Foo5
Any suggestions?
Mark Thomas wrote:
| Aaron Axelsen wrote:
Aaron Axelsen wrote:
> I understand how it works - the problem is that the folder is not
> actually getting created. I double checked permissions - and the apache
> user does have full permissions to that tomcat 6 folder. Any thoughts?
>
> The name of the war is temp Foo5.war. I can see folders
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I understand how it works - the problem is that the folder is not
actually getting created. I double checked permissions - and the apache
user does have full permissions to that tomcat 6 folder. Any thoughts?
The name of the war is temp Foo5.war.
Aaron Axelsen wrote:
> Is there any reason its going to look in temp-Foo5?
That is how the antiresource locking works. It copies the entire war to a
temp location with a unique name and runs it from there. If you reload it
would probably use temp-Foo6 etc.
Mark
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The reason we have docbase == appbase is because students will upload
war files to the doc base for deployment within a given subdomain.
However, that said, there is no reason why we need to set the context
path at all, since the war files all dep
Aaron Axelsen wrote:
> Is there a trick to get antiJarLocking and antiResourceLocking to work
> with tomcat 6? I have the following in the config:
>
> ~unpackWARs="true" autoDeploy="true">
> ~ antiResourceLocking="true" />
Setting docBase==appBase is going to get you a world of pain.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a trick to get antiJarLocking and antiResourceLocking to work
with tomcat 6? I have the following in the config:
~antiResourceLocking="true" />
~
~
There do not appear to be any error logs on anything, but the jar's
17 matches
Mail list logo
