Hi all
Today I updated the tomcat6-maven-plugin version in my project from
2.0-beta-1 to 2.0.
Since then I got this exceptions when I'm starting the embedded tomcat
instance:
Sep 17, 2012 2:17:15 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Sep 17, 2012
Hi,
yup there is an issue here:
http://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunWarMojo.java
only for tomcat6 mojo.
can you load a jira entry for that ?
Thanks,
--
Olivier
2012/9/17 Florian Maertl
Jira is raised:
https://issues.apache.org/jira/browse/MTOMCAT-175
Thanks
Florian
-Original Message-
From: Olivier Lamy [mailto:ol...@apache.org]
Sent: Montag, 17. September 2012 15:19
To: Tomcat Users List
Subject: Re: warDirectory property wrong evaluated in release version
2.0 ?
Hi,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ragini,
On 9/17/12 8:55 AM, Ragini wrote:
In the output, I have noticed that the main class which is
responsible to execute jsp page is Lorg/apache/jsp.
Your JSP files are translated into Java source files that use
org.apache.jsp as a prefix. So,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benson,
On 9/14/12 12:12 PM, Benson Margulies wrote:
Apologies for the accidental use of HTML.
The problem below is triggered by the facts that:
a) spring-web contains a ServletContainerInitializer b) even with
metadata-complete, tomcat does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Izolda,
On 9/16/12 6:19 AM, Kiss Izolda wrote:
I have configured Tomcat to use log4j according to
http://tomcat.apache.org/tomcat-7.0-doc/logging.html I have used
the same log4j.properties. My web application is using log4j as
well. There is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kiran,
On 9/13/12 8:24 PM, Kiran Badi wrote:
On 9/13/2012 8:13 AM, Christopher Schultz wrote:
Large sites will use a single URL that ends up resolving the
images from some kind of data source. That data source might be a
disk (e.g. you could
On 9/17/2012 9:31 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Izolda,
On 9/16/12 6:19 AM, Kiss Izolda wrote:
I have configured Tomcat to use log4j according to
http://tomcat.apache.org/tomcat-7.0-doc/logging.html I have used
the same log4j.properties. My web
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 9/17/12 1:36 PM, Mark Eggers wrote:
So really, for me, it boils down to this.
1. Place log4j.xml in WEB-INF/classes 2. Write a servlet context
listener a. contextInitialized - just write something to the log b.
contextDestroyed - shut
Hi,
In Summary, I was hoping somebody could look over my configuration and give
me some guidance. I have configured what I think I need to and I have no
evidence to suggest anything is working and I don't know how to verify the
pieces of the puzzle. Any help on troubleshooting would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John,
On 9/17/12 3:50 PM, John Rellis wrote:
Location /jk-status # Inside Location we can omit the URL in
JkMount JkMount jk-status Order deny,allow Deny from all Allow from
all /Location Location /jk-manager # Inside Location we can
omit the URL
Thanks Chris.
My replies will be a little sporadic as I am cooking a 10 pm dinner :)
From what I was reading I thought I could hit some sort of manager there
but it was never able to, when I hit
http://balancer/jkmanager
I get nothing just a 404.
This is in my apache2.conf: (i removed them
12 matches
Mail list logo
