yes, Igor. I wanted to display 404 error page when go to localhost:8080.
By the way, i cant locate any folder except myapps folder under /ROOT
directory.
--
View this message in context:
http://tomcat.10.n6.nabble.com/Remove-apache-tomcat-default-home-page-tp4991774p4991782.html
Sent from
On 4 Jan 2013, at 04:39, ana kando anaka...@yahoo.com wrote:
Hi all,
I just installed a software that bundled with apache tomcat. I successfully
installed the software and can run the software at
http://localhost:8080/myapps/
However, when i remove /myapps from browser, it will go
On 3 Jan 2013, at 23:04, Martin Gainty mgai...@hotmail.com wrote:
Martin
__ If computers were self-aware
they would'nt need human beingsAuthor Unknown
Indeed.
-
To
From: anakando [mailto:anaka...@yahoo.com]
Subject: Re: Remove apache tomcat default home page
i cant locate any folder except myapps folder under /ROOT directory.
So besides having a horribly out of date version of Tomcat, the configuration
is also illegal. The webapp should not be under
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 1/3/13 10:54 AM, John Rellis wrote:
I am using apache 2.2.3 and mod_jk as a load balancer for two
tomcat 7 instances over AJP 1.3.
Which exact version of mod_jk are you using? I'm guessing you are
stuck on httpd 2.2.3 because of your
On 04/01/2013 20:08, Christopher Schultz wrote:
On 1/3/13 10:54 AM, John Rellis wrote:
I am using apache 2.2.3 and mod_jk as a load balancer for two
tomcat 7 instances over AJP 1.3.
Which exact version of mod_jk are you using? I'm guessing you are
stuck on httpd 2.2.3 because of your
On 03/01/2013 21:52, Igor Cicimov wrote:
On 04/01/2013 2:25 AM, Arunkumar Janarthanan arunkumar.webad...@gmail.com
wrote:
Thanks Mark, I am working on parallely setting up another environment with
Tomcat 6.x, however to clear an urgent audit I need to show the Apache
connector uses secure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pascal,
On 1/3/13 12:49 PM, Davoust, Pascal wrote:
I'm using the tomcat jdbc connection pool (7.0.34) to connect
against a PostgreSQL database (version 8.4 - jdbc driver 9.0.801)
and I'm having a potentially dodgy situation with the validation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pid,
On 1/4/13 3:22 PM, Pid wrote:
On 04/01/2013 20:08, Christopher Schultz wrote:
On 1/3/13 10:54 AM, John Rellis wrote:
I am using apache 2.2.3 and mod_jk as a load balancer for
two tomcat 7 instances over AJP 1.3.
Which exact version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pid,
On 1/4/13 3:22 PM, Pid wrote:
On 04/01/2013 20:08, Christopher Schultz wrote:
On 1/3/13 10:54 AM, John Rellis wrote:
I am using apache 2.2.3 and mod_jk as a load balancer for
two tomcat 7 instances over AJP 1.3.
Which exact version of
On 04/01/2013 20:34, Christopher Schultz wrote:
Pascal,
On 1/3/13 12:49 PM, Davoust, Pascal wrote:
I'm using the tomcat jdbc connection pool (7.0.34) to connect
against a PostgreSQL database (version 8.4 - jdbc driver 9.0.801)
and I'm having a potentially dodgy situation with the validation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arun,
On 1/3/13 10:24 AM, Arunkumar Janarthanan wrote:
*Apache conf:*
ProxyPassMatch ^/(.*\.jsp|.*\.do)(;jsessionid=.*)?$
balancer://lb1/$1
Why are you intentionally removing the jsessionid from being forwarded
to the worker? I think you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pid,
On 1/4/13 4:26 PM, Pid wrote:
On 04/01/2013 20:34, Christopher Schultz wrote:
On 1/3/13 12:49 PM, Davoust, Pascal wrote:
I then had a look at the corresponding code into the tomcat
jdbc pool (source 7.0.34), and more specifically in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 1/3/13 6:03 PM, Martin Gainty wrote:
Does anyone know how to hint a Hibernate predicate with something
like select /*+ index(emp_alias ix_emp) */ ... from scott.emp
emp_alias
Short answer: you can't.
Long answer: Google for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tim,
On 1/3/13 10:09 AM, Tim Watts wrote:
I just re-read your original email and I may have missed something.
Are you saying that you get an IOException when you call
request.getInputStream() during a 500 response? If so can you
please post
Indeed I was referring to the tomcat jdbc-pool code, not mine :-).
Now, I would suggest to consider that this problem is more common than you
could imagine at first sight. First because this is randomly occuring, but
frequently enough so that it shows up in quite a few areas.
A few examples where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Felix,
On 1/3/13 3:49 PM, Felix Schumacher wrote:
Am 03.01.2013 15:31, schrieb kharp...@oreillyauto.com:
Hello All,
Yesterday we had a Tomcat6 server reach maxThreads and stay that
way until we restarted it. After researching a thread dump
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pascal,
On 1/4/13 5:56 PM, Davoust, Pascal wrote:
Indeed I was referring to the tomcat jdbc-pool code, not mine :-).
Now, I would suggest to consider that this problem is more common
than you could imagine at first sight. First because this is
Sorry, I probably did not make myself clear.
I certainly do not suggest to issue the rollback on each connection
checkout, but only as part of the validation process - because this is
where the problem lies and only there - which I would imagine is triggered
only occasionally (when connection is
19 matches
Mail list logo
