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 such animal; perhaps you mean getRealPath()?
Yes, I
From: Aaron Axelsen [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
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 trying to accomplish
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-appname
which doesn't exist.
Works
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
Axelsen [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
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-rack-0.9.1.jar since those are the ones that were
- Original Message -
From: Aaron Axelsen [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
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 recap on what
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-portable
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 the
- Original Message -
From: Aaron Axelsen [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
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-rack-0.9.1.jar
Johnny Kewl wrote:
- Original Message - From: Aaron Axelsen [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
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
-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:
Host name=nix-tester.mcs.uww.edu appBase=D:/path/to/webroots/docs
~unpackWARs=true autoDeploy=true
~Context path=
Aaron Axelsen wrote:
Is there a trick to get antiJarLocking and antiResourceLocking to work
with tomcat 6? I have the following in the config:
Host name=nix-tester.mcs.uww.edu appBase=D:/path/to/webroots/docs
~unpackWARs=true autoDeploy=true
~Context path= docBase=. debug=5
-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
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
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:
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 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:
17 matches
Mail list logo
