On 04/05/2010 05:12, Dave Filchak wrote:
Thanks for this. I did use the address attribute for port 80. No check
that. I think what I did was pit address=XXX.XXX.XXX.XXX but did not
specify the port ... just the address as it also listens on ports up in
the 8000 range I believe. How do I stop
On 04/05/2010 06:22, Paul Chany wrote:
Warren Pace warren.p...@gmail.com writes:
If you installed your Tomcat using the Debian package manager, take a
look at the tomcat startup script. While it's been a number of years
since I used Debian, I seem to remember this from back in the day -
Christopher Schultz wrote:
Mario,
On 5/3/2010 8:18 AM, Mario Splivalo wrote:
André Warnier wrote:
Mario Splivalo wrote:
One just have to love Tomcat documentation :)
Specially considering the price you pay for it.
Oh, that is so professional. So, it's cheap therefore it can be
A bit more searching on the apache bugzilla led me to this:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43866
This enhancement request describes (probably a bit clearer) the gap in
functionality going from 5.0 to 5.5/6.0 - namely there's no
useDirtyFlag, so no way to tell the (more
On 04/05/2010 07:51, Mario Splivalo wrote:
Christopher Schultz wrote:
Mario,
...
Yes, it actually makes sense now, to use executors for desired behavior.
It's just that I somehow missed the introduction of the executors.
I still don't understand the actual benefit of using executors - is
Petr Hracek wrote:
If I understand right then sun.net.www.protocol.http.HttpURLConnection is
not part of any class, right / is obsolete?
Or is there any other class?
Sorry for that stupid question but I do not understand. Code has been really
adopted.
Petr,
I think what they are telling you
On 04/05/2010 10:32, André Warnier wrote:
Petr Hracek wrote:
If I understand right then sun.net.www.protocol.http.HttpURLConnection is
not part of any class, right / is obsolete?
Or is there any other class?
Sorry for that stupid question but I do not understand. Code has been
really
Hello again,
Today I was able to get an application deployed with auto-deploy, by
simply copying the directory into webapps.
I still can't deploy an application at another disk location using the
GUI or the URL call, same error:
FAIL - Failed to deploy application at context path /JSPTut2
On 05/03/2010 02:53 PM, Pid wrote:
On 03/05/2010 18:30, Mark Shifman wrote:
On 05/03/2010 12:48 PM, Pid wrote:
On 03/05/2010 17:15, Mark Shifman wrote:
I have a web app running under tomcat-6.0.26 with
JreMemoryLeakPreventionListener, java jdk1.6.0_18.
Using jmap -histo pid, I can watch
I'm trying to enable TLS (or SSL) in a Tomcat 5.5.29 server, on a
Windows XP machine.
Whatever I do, I always end up with a server that just delivers plain
HTML on port 443, and it doesn't even try to use TLS. That is, I can
connect to http://localhost:443/ and get the same as http://localhost/
On 4 May 2010 14:22, Looijmans, Mike mike.looijm...@oce.com wrote:
I'm trying to enable TLS (or SSL) in a Tomcat 5.5.29 server, on a
Windows XP machine.
Whatever I do, I always end up with a server that just delivers plain
HTML on port 443, and it doesn't even try to use TLS.
[...]
!--
2010/5/4 Looijmans, Mike mike.looijm...@oce.com:
May 4, 2010 3:13:52 PM org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-443
The Apr in the above message means that you are using APR version
of the connector.
!-- Define a SSL HTTP/1.1 Connector on
From: Looijmans, Mike [mailto:mike.looijm...@oce.com]
Subject: Tomcat 5.5 won't do TLS
Connector port=443 maxHttpHeaderSize=8192
maxThreads=150 minSpareThreads=2 maxSpareThreads=75
enableLookups=false disableUploadTimeout=true
acceptCount=10 scheme=https secure=true
Hi,
I have a problem with configuring mod_proxy_ajp to access Tomcat5 through
Apache2. My setup:
CentOS release 5.4 (Final)
httpd-2.2.3-31.el5.centos.4
tomcat5-5.5.23-0jpp.7.el5_3.2
I have in /etc/httpd/conf.d/proxy_ajp.conf:
Location /tomcat/
ProxyPass ajp://localhost:8009/
Hi List,
Since a few weeks now, I started to notice in the catalina.out log file
messages regarding the cluster's operatability.
It reports that a member or members in my cluster have disappeared, and
appeared (member still alive) again. That's reasonable...the strange thing
is that they occur at
On 04/05/2010 14:10, Mark Shifman wrote:
On 05/03/2010 02:53 PM, Pid wrote:
On 03/05/2010 18:30, Mark Shifman wrote:
On 05/03/2010 12:48 PM, Pid wrote:
On 03/05/2010 17:15, Mark Shifman wrote:
I have a web app running under tomcat-6.0.26 with
JreMemoryLeakPreventionListener, java
Hey all,
We are using Tomcat 6 on a Windows XP box. We have a web application
named abc. It was initially in the c:\Tomcat\webapps directory. I then
moved the c:\Tomcat\webapps\abc directory to c:\Tomcat\abc. I then
changed the Tomcat/conf/server.xml file to reflect this change...
Host
On 04/05/2010 17:32, Joe Hansen wrote:
Hey all,
We are using Tomcat 6 on a Windows XP box. We have a web application
named abc. It was initially in the c:\Tomcat\webapps directory. I then
moved the c:\Tomcat\webapps\abc directory to c:\Tomcat\abc. I then
changed the Tomcat/conf/server.xml
Thanks.
I'll try Jconsole.
mas
On 05/04/2010 12:28 PM, Pid wrote:
On 04/05/2010 14:10, Mark Shifman wrote:
On 05/03/2010 02:53 PM, Pid wrote:
On 03/05/2010 18:30, Mark Shifman wrote:
On 05/03/2010 12:48 PM, Pid wrote:
On 03/05/2010 17:15, Mark Shifman wrote:
I have a web app running under
Thank you for the super quick reply Mark! We are using Java Spring.
The reason for moving the web application out of the webapps directory
was that the Spring Context Loader was loading twice. First because
its in the webapps directory. Secondly, because it is being referred
to by the Host entry
On 04/05/2010 17:43, Joe Hansen wrote:
Thank you for the super quick reply Mark! We are using Java Spring.
The reason for moving the web application out of the webapps directory
was that the Spring Context Loader was loading twice. First because
its in the webapps directory. Secondly, because
Mark, Here's the server.xml before moving abc out of the webapps directory:
?xml version='1.0' encoding='utf-8'?
Server port=8005 shutdown=SHUTDOWN
Listener className=org.apache.catalina.core.AprLifecycleListener
SSLEngine=on /
Listener className=org.apache.catalina.core.JasperListener /
On 04/05/2010 17:59, Joe Hansen wrote:
Mark, Here's the server.xml before moving abc out of the webapps directory:
Host name=abc.local appBase=webapps/abc
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false
From: Joe Hansen [mailto:joe.hansen...@gmail.com]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
Host name=localhost appBase=webapps
/Host
Host name=abc.local appBase=webapps/abc
First problem: overlapping
Thanks for the reply, Mark. You made me understand the mess I have created.
I have written two web applications abc and xyz. I have mapped
abc.local and xyz.local to my machine's IP Address in my Windows HOST
file. So when I visit http://abc.local, I would want the abc web
application to be
From: Joe Hansen [mailto:joe.hansen...@gmail.com]
Subject: RE: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
Looks like I have some reading to do! Will post back after
I read some Tomcat documentation.
Start here:
Dear users,
I am trying to setup tomcat clustering/session replication between two
tomcats of version 6.0.18. The following is the cluster snippet inserted
into server.xml of both servers:
Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster
channelSendOptions=8
Many Thanks for the link Chuck! Here's what I did.
1. Created a directory named c:\Tomcat\abc\ROOT.
2. Moved the previous contents of c:\Tomcat\webapps\abc to
c:\Tomcat\abc\ROOT directory.
3. Created c:\Tomcat\abc\ROOT\META-INF\context.xml. Here's that file.
?xml version=1.0 encoding=UTF-8?
Joe Hansen wrote:
Many Thanks for the link Chuck! Here's what I did.
1. Created a directory named c:\Tomcat\abc\ROOT.
2. Moved the previous contents of c:\Tomcat\webapps\abc to
c:\Tomcat\abc\ROOT directory.
...
Let me throw in my grain of salt.
I like things organised in a logical way, with a
On Tue, 2010-05-04 at 16:53 +1000, Kevin Jansz wrote:
PS thanks for the responses. Martin, the session manager project
sounds awesome but the use of memcached (c-based native code server if
I read correctly) would make it a non-starter for us. The future use
of ehcache sounds promising, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 5/4/2010 1:26 PM, Joe Hansen wrote:
I have written two web applications abc and xyz. I have mapped
abc.local and xyz.local to my machine's IP Address in my Windows HOST
file. So when I visit http://abc.local, I would want the abc web
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
You want this:
webapps/abc
webapps/abc/ROOT -- this is your abc webapp
webapps/abc/ROOT/META-INF
Anyone can explain if I can use hibernate validator in tomcat 6 webapp? Current
use case tests are not failing using validator annotations but is it because it
will only work in EE container?
Thanks Andre and Chuck.
Andre, I renamed Tomcat/abc/ to Tomcat/webapps-abc/ to keep the naming
consistent. The directory structure that you've advocated is exactly
the same as the one Chuck told me. And I have implemented that.
However, logging is still an issue. One webapp's log4j seems to
post one code sample with one validation
also post version number of annotated jars and hibernate you are using and
where you put them
contents of hibernate.cfg.xml
which container are you using..ARE you SURE you are using Tomcat..if so which
version of Tomcat?
Martin Gainty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 5/4/2010 4:08 PM, Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
You want this:
On 04/05/2010 18:59, Joe Hansen wrote:
Many Thanks for the link Chuck! Here's what I did.
1. Created a directory named c:\Tomcat\abc\ROOT.
2. Moved the previous contents of c:\Tomcat\webapps\abc to
c:\Tomcat\abc\ROOT directory.
3. Created c:\Tomcat\abc\ROOT\META-INF\context.xml. Here's that
On 04/05/2010 21:27, Yucca Nel wrote:
Anyone can explain if I can use hibernate validator in tomcat 6 webapp?
Current use case tests are not failing using validator annotations but is it
because it will only work in EE container?
Erm, yes?
Without more information I can't advise, someone
From: Joe Hansen [mailto:joe.hansen...@gmail.com]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
However, logging is still an issue. One webapp's log4j seems to stomp
over other webapp's log files. What could I be doing wrong?
Where
Chuck,
Initially I placed log4j-1.2.15.jar in the c:\Tomcat\lib directory
only. This resulted in abc webapp logging in the
c:\Tomcat\logs\xyz.log file.
When I copied the log4j-1.2.15.jar to
c:\Tomcat\webapps-abc\ROOT\WEB-INF\lib and
c:\Tomcat\webapps-xyz\ROOT\WEB-INF\lib directories, it created
From: Joe Hansen [mailto:joe.hansen...@gmail.com]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
Initially I placed log4j-1.2.15.jar in the c:\Tomcat\lib
directory only. This resulted in abc webapp logging in the
Chuck,
There are common classes in Tomcat/lib/ but they don't attempt to do
any logging. However, the abc Spring Web application does initialize a
Quartz object which runs once every hour and does some logging. I
don't know if that has any implications.
Thanks,
Joe
Here's the stack trace from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 5/4/2010 1:59 PM, Joe Hansen wrote:
2. But the web application logging is working wierdly.The log entries
are written to c:\Tomcat\logs\xyz.log (i.e. the xyz web application's
log) instead of writing to c:\Tomcat\logs\abc.log. .
Here's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 5/4/2010 6:15 PM, Joe Hansen wrote:
There are common classes in Tomcat/lib/ but they don't attempt to do
any logging.
Are you sure?
However, the abc Spring Web application does initialize a
Quartz object which runs once every hour and
Thanks for the reply, Charles!
When commons-logging.jar is present in Tomcat/lib and WEB-INF/lib
directories, I get the following error :
Invalid class loader hierarchy. You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed.
Here's the complete stack
X-zuka-RWMailScanner-ID: AEE69538190.ABB3E
X-zuka-rw-MailScanner-Information: Please contact the ISP for more information
Received: from Magnolia.local (unknown [70.48.209.168])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
X-zuka-RWMailScanner-ID: AEE69538190.ABB3E
X-zuka-rw-MailScanner-Information: Please contact the ISP for more information
Received: from Magnolia.local (unknown [70.48.209.168])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
Oh, I forgot to mention in my other message: you should put log4j.log
into your webapp's WEB-INF/lib directory
Dave Filchak wrote:
...
this :
httpd: Syntax error on line 439 of /usr/local/apache2/conf/httpd.conf:
API module structure `jk_module' in file
/usr/local/apache2/modules/mod_jk-1.2.28-httpd-2.0.X.so is garbled -
perhaps this is not an Apache module DSO?
...
and this :
LoadModule
From: Joe Hansen [mailto:joe.hansen...@gmail.com]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
When commons-logging.jar is present in Tomcat/lib and WEB-INF/lib
directories, I get the following error :
As you should. As Chris
Chuck, please note that when commons-logging.jar is present only in
the WEB-INF/lib directory,
I get the following error:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
So, either I get
a) Invalid class loader hierarchy. You have more than one version of
Joe Hansen wrote:
Chuck, please note that when commons-logging.jar is present only in
the WEB-INF/lib directory,
I get the following error:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
So, either I get
a) Invalid class loader hierarchy. You have more than one version
This thread has grown too long. For anyone following this thread,
here's the summary:
Two web applications, each with a Virtual Host entry in server.xml file.
Tomcat/webapps-abc
Tomcat/webapps-xyz
These two web applications have different log4j.properties files.
These log4j property files log to
Hello Tom,
I am facing a similar issue. Could you please send that piece of code that
was causing you this
error, just that snippet should be good.
Thanks
Tom Price-3 wrote:
Hi all,
No more help required - I traced back all the references to the Request
objects and it did turn out to
From: Joe Hansen [mailto:joe.hansen...@gmail.com]
Subject: Re: Log4j logging doesn't work when a web application is moved
outside Tomcat/webapps directory
Scenario 1:
log4j.jar is in Tomcat/lib directory
log4j.jar is NOT in WEB-INF/lib directories
Have you added *anything* else to
55 matches
Mail list logo
