What happens if you run
mvn -Dcargo.wait=true
(See http://appfuse.org/display/APF/Maven+2)
This instructs Maven to build your project and deploy it in a freshly
downloaded container, which happens to be Tomcat 5.5 by default. If that
works, it ought to work in your other Tomcats I guess.
You should be able to see your app at
http://localhost:8081/yourapp-version
In case of a vanilla Appfuse project called yourapp:
http://localhost:8081/yourapp-1.0-SNAPSHOT
You could also tell Maven to deploy it in Jboss (4.0.5) instead of Tomcat.
mvn -Dcargo.wait=true -Pjboss
Jboss 4.0.5 uses Tomcat 5.5 internally, but I think it has a slightly
different infrastructure for logging; for instance a server-wide
log4j.xml config file is used instead of the app-specific log4j.xml that
usually sits in your WEB-INF/classes folder. Your stack traces seem to
suggest some permission problem related to the logging subsystem.
Perhaps trying Jboss will shed some light on the problem?
Ger-Jan
Waldo Rochow wrote:
Nathan, Ger-Jan and Matt,
Thank you all for your advice to date. However I'm still not having any
luck.
When I write a security policy for appfuse, the errors go away, but the
problem persists.
I have tried completely removing all references to tomcat from the
system and reinstalling it, in case it was a conflict between 5.5 and 6.
I have also noticed that when I don't have my policy in the system, the
tomcat6 manager shows my application, but won't start it. When I have
the policy in place, the application doesn't even show up in the manager.
What bothers me the most, is that it works in jetty, and jetty seems to
use an internal version of tomcat. The next thing that bothers me is
that I have over ten years experience writing web apps in Java, and I
have never had to futz around with policy files, so I'm a little
apprehensive to start doing that now.
It's a real shame, because I like the development approach that appfuse
offers, but I'm at a loss for using it in a production environment.
If you have any other ideas, I would love to hear them.
Regards,
Waldo
On Wed, Feb 11, 2009 at 3:18 PM, Ger-Jan te Dorsthorst <ger...@dds.nl
<mailto:ger...@dds.nl>> wrote:
Nathan Anderson wrote:
As I recall, you really only have 2 choices: disable the Java
security, or build a java security policy for your app. I have
never done the work of building a security policy, but my
understanding is that you basically need to run the app, see
what fails and add a policy to fix that problem and repeat.
Chances are if you fixed this problem with Commons Logging, it
will fail on something else further down the startup chain.
http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.html
may be helpful as well; see the last section: Troubleshooting.
Are you sure you would run in to this issue at all when deploying in
your ISP's Tomcat? Could it be just an overly restrictive policy in
your own Tomcat instance?
Look at your stack traces: two different proximate causes, same
ultimate cause in both cases: some log factory property cannot be
read, presumably because some java.util.PropertyPermission in the
policy is set too strict.
1. Top of strack trace:
On Wed, Feb 11, 2009 at 9:26 AM, Waldo Rochow <appf...@capra.net
<mailto:appf...@capra.net> <mailto:appf...@capra.net
<mailto:appf...@capra.net>>> wrote:
11-Feb-2009 11:18:25 AM
org.apache.catalina.core.StandardContext
listenerStart
SEVERE: Error configuring application listener of class
org.springframework.web.context.request.RequestContextListener
java.lang.ExceptionInInitializerError
at
org.springframework.web.context.request.RequestContextListener.<init>(RequestContextListener.java:55)
but the ultimate cause is further down:
Caused by: java.security.AccessControlException: access denied
(java.util.PropertyPermission
org.apache.commons.logging.LogFactory.HashtableImpl read)
2. Top of other stack trace, showing an apparently different error:
>> >> Feb 9, 2009 8:46:59 AM
org.apache.catalina.core.StandardContext
>> >> listenerStart
>> >> SEVERE: Error configuring application listener
of class
>> >> com.opensymphony.clickstream.ClickstreamListener
>> >> java.lang.ExceptionInInitializerError
>> >> at
>> >>
>> >>
com.opensymphony.clickstream.ClickstreamListener.<clinit>(ClickstreamListener.java:24)
however, as before the ultimate cause is:
>> >> Caused by: java.security.AccessControlException:
access denied
>> >> (java.util.PropertyPermission
>> >>
org.apache.commons.logging.LogFactory.HashtableImpl read)
Hope this helps,
Ger-Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
<mailto:users-unsubscr...@appfuse.dev.java.net>
For additional commands, e-mail: users-h...@appfuse.dev.java.net
<mailto:users-h...@appfuse.dev.java.net>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
