Re: war files not deploying on redhat
Hi,
I don't know if it was just a typo in your post, but AutoDeploy
should be |autoDeploy.
-- Edgar Alves
|
Paul Warner wrote:
Hello,
I have read the documentation and searched the archives, and whatever I have
found, I have tried, but still my .war files will not unpack and auto deploy.
I
have been running a tomcat server for several months in which the .war files
unpacked and auto-deployed perfectly. But with this new installation, the
Redhat way, with files all over the place, I have not been able to make it
work.
I am using Tomcat 5.0.28 via an rpm on Redhat EL 3. I am accessing the tomcat
server via apache and the jk2 connector. I have the server.xml file configured
with:
Host name=localhost debug=0 appBase=webApps
unpackWARs=true AutoDeploy=true
xmlValidation=false xmlNamespaceAware=false
My application has its context.xml file in the META-INF directory correctly
pointing to the appname, /copse. I have an xml file in
/etc/tomcat5/Catalina/localhost/copse.xml which has in it:
Context docBase=${catalina.home}/build/copse.war
privileged=true antiResourceLocking=false
antiJARLocking=false/Context
The /webapps directory and its contents are owned by tomcat, the tomcat process
owner. root has CATALINA_HOME in its environment, set to /usr/share/tomcat5.
I have a link in /usr/share/tomcat5 to /var/lib/tomcat5/build, which contains
the copse.war file. tomcat has read and write privs for this build/ directory
and all its files.
The differences between my working installation and the 'broken' one seem to
be:
1. root owned the instance of tomcat in the working version, tomcat owns the
instance of tomcat in the broken one
2. file permissions were not all tomcat rw in the broken one, but this I have
fixed now - as far as I know all relevant files are owned by tomcat
3. CATALINA_HOME wasn't set properly for root at first in the 'broken' install
-
but this also has been fixed (I believe). It points to the directory that
holds
all the softlinks to the other directories, such as conf, webapps, build, and
so
on.
I have resorted to unpacking the war file myself, and the application works.
But unpacking by hand is cumbersome and time-consuming. Does anyone have the
(I
presume simple) key to unlock this problem?
Thanks,
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: war files not deploying on redhat
Hi,
I don't know if it was just a typo in your post, but AutoDeploy
should be |autoDeploy.
-- Edgar Alves
Thanks for the quick answer and sharp eye - but it WAS a typo, sorry! In the
server.xml file, it is listed as autoDeploy=true. It is the basic server.xml
file, not really altered by me, and almost exactly matches the server.xml file
on the other machine, the one that works.
Thanks,
Paul
|
Paul Warner wrote:
Hello,
I have read the documentation and searched the archives, and
whatever I have
found, I have tried, but still my .war files will not unpack
and auto deploy. I
have been running a tomcat server for several months in
which the .war files
unpacked and auto-deployed perfectly. But with this new
installation, the
Redhat way, with files all over the place, I have not been
able to make it
work.
I am using Tomcat 5.0.28 via an rpm on Redhat EL 3. I am
accessing the tomcat
server via apache and the jk2 connector. I have the
server.xml file configured
with:
Host name=localhost debug=0 appBase=webApps
unpackWARs=true AutoDeploy=true
xmlValidation=false xmlNamespaceAware=false
My application has its context.xml file in the META-INF
directory correctly
pointing to the appname, /copse. I have an xml file in
/etc/tomcat5/Catalina/localhost/copse.xml which has in it:
Context docBase=${catalina.home}/build/copse.war
privileged=true antiResourceLocking=false
antiJARLocking=false/Context
The /webapps directory and its contents are owned by tomcat,
the tomcat process
owner. root has CATALINA_HOME in its environment, set to
/usr/share/tomcat5.
I have a link in /usr/share/tomcat5 to
/var/lib/tomcat5/build, which contains
the copse.war file. tomcat has read and write privs for
this build/ directory
and all its files.
The differences between my working installation and the
'broken' one seem to be:
1. root owned the instance of tomcat in the working version,
tomcat owns the
instance of tomcat in the broken one
2. file permissions were not all tomcat rw in the broken
one, but this I have
fixed now - as far as I know all relevant files are owned by tomcat
3. CATALINA_HOME wasn't set properly for root at first in
the 'broken' install -
but this also has been fixed (I believe). It points to the
directory that holds
all the softlinks to the other directories, such as conf,
webapps, build, and so
on.
I have resorted to unpacking the war file myself, and the
application works.
But unpacking by hand is cumbersome and time-consuming.
Does anyone have the (I
presume simple) key to unlock this problem?
Thanks,
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: war files not deploying on redhat
A typo in a post about a typo... :) s/|autodeploy/autoDeploy/ Edgar Alves wrote: Hi, I don't know if it was just a typo in your post, but AutoDeploy should be |autoDeploy. -- Edgar Alves | Paul Warner wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
