Hi Nathan,
Nathan Anderson wrote:
Thanks for the reply. In trying some more I realized that with AppFuse 1.x we needed to
"prepare" Tomcat for deployment. Is there still a need for this step? If so
what changes need to be made to Tomcat?
I don't believe you need to do any preparation (apart from the DB of
course). I've not had to do that with TC 5.5 - deploying manually just
worked for me.
See below for answers to your questions...
----- "Rob Hills" <[EMAIL PROTECTED]> wrote:
Hi Nathan,
Nathan Anderson wrote:
So I finally have my AppFuse 2 (Struts 2 + Hibernate) webapp ready
to deploy to my production server. But I appear to be a bit stuck...
I'm sure there is some way to have maven 2 deploy for me, but I have
not figured out how yet. So I was just planning on going old school
and copy the .war file to my Tomcat 5.5 webapps directory. [I don't
think it is critical, but I installed Tomcat 5.5 using packages
available for Ubuntu 7.10].
The problem is it isn't starting up, and this is all that shows up
in the logs:
Nov 15, 2007 7:55:20 AM org.apache.catalina.core.StandardContext
start
SEVERE: Error listenerStart
Nov 15, 2007 7:55:20 AM org.apache.catalina.core.StandardContext
start
SEVERE: Context [/mywebapp] startup failed due to previous errors
So my question is two fold... 1) Any guess what could be causing my
app that was working to not work in this environment? and 2) is there
a better way to deploy my app?
Question 1 - could permissions be a problem? Maybe try deploying your
app using Tomcat's manager interface. That should get around any
filesystem permissions issues and working through that will help for
question 2.
My first attempt was to just throw the .war in the webapps folder, but I did deploy via the /manager app on my most recent attempt. The error message above is from the /manager deployed version.
I also suspected Java security could be a problem because it is enabled by
default for Tomcat on Ubuntu. But disabling Java security made no difference.
I don't believe Java security would be likely to cause this kind of
problem. Maybe if you were trying to read/write the filesystem outside
your context and from within your web app, that might cause problems,
but otherwise I'd be surprised.
Question 2 - I use the Tomcat Maven plugin reasonably successfully on
I may be rushing things, but it didn't work immediately for me... It appears
to me that the tomcat maven plugin is just using the /manager app, so until I
can do it manually I'm not likely to be able to use the plugin to automate
deployment. Aside from that I did make a profile and when I tried to run
tomcat:deploy I hit an OutOfMemoryError. :/
So I guess I need to solve one problem at a time. For now I'd be happy with just deploying the war manually.
I agree there - if you can't deploy it "manually" via the manager then
the maven plugin won't work.
I note Matt's comments about tomcat logs and I agree, if you can find
the full stack trace, that should help. A couple more thoughts on the
"bleeding obvious" things that I forget sometimes - you've got the DB up
and running and access to it all sorted out I presume? Also, does TC
have permissions to write its log files? In my fumblings with TC on
Linux in the past, I've found myself caught out because I tried to get
TC to write its logs to /var/log/tomcat and then forgot to give it write
permissions to the folder :-(
Good Luck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
