> What version of Tomcat are you running? If (as is likely currently)
> it is one that bundles Commons Pool 1.3, there is something funny
> going on because the line number where wait on borrowObject is
> occurring in the thread dumps would indicate that
>
> a) the pool is exhausted and
> b) the m
On Jan 27, 2008 4:32 PM, Clay Collier <[EMAIL PROTECTED]> wrote:
> Hi all-
>
> I'm running into a recurring problem with an application that uses
> DBCP pooling to access a database. The application initially seems to
> run fine; in the test environment, it has no problem dealing with a
> large vo
Hi ALL,
I am using
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20060511
(SR2))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
j9vmwi3223-2006050
4 (JIT enabled)
J9VM - 20060501_06428_lHdSMR
JIT - 20060428_1800_r8
GC - 20060501_AA)
JCL
Ok, so I redownloaded both Tomcat 5 and Tomcat 6. Tomcat 5 was working
before, even though I had installed it from the service installer (and
never using it as a service). After reinstalling it from the zip, it is
still working just fine. When I tried to run "tomcat6.exe" from the
Tomcat6 zip fi
> From: Karr, David [mailto:[EMAIL PROTECTED]
> Subject: Problems installing Tomcat 6 along existing Tomcat
> 5, and JAVA_HOME points to 1.4.2
>
> This is ironic, as I have no intention of using the
> Windows service, I just used the installed
> because it's more convenient than the zip file.
Due to constraints on my current work, my JAVA_HOME points to a JDK
1.4.2 distro. When I installed Tomcat 5.5.25, I pointed it to a Java 5
JDK that I have installed. It appears to be working relatively well.
I wanted to try installing Tomcat 6, to take a look at JSF 1.2. When I
installed it, I
Nevermind. The issue had nothing to do with apache, tomcat, or mod_proxy_ajp
- but instead with how I started tomcat. Resolved now. Thank you.
-M
Michael L wrote:
>
> I am using Apache 2.2 with mod_proxy_ajp and tomcat 5.5.25. Using straight
> ProxyPass connection (no load balancing). It seem
for an implementation of Bayeux (soon to be proposed to tomcat-dev) that
works with CometProcessor
http://svn.hanik.com/viewvc/tomcat-bayeux/
User: tomcat
Password: tomcat
just deploy the war file generated from the ant build script
Filip
Martin Gainty wrote:
I downloaded the CometProcessor
I'd set keepAliveTime to 10 as well,
Filip
Raúl García wrote:
Hi Again, once again thanks for your time, but we still have problems,
We applied the "keepAliveCount=0" param. and last Wednesday 23 Jan we
restart both nodes.
Around 11 hour after the startup, node 1 reports a new error, but both
On Jan 27, 2008 3:42 PM, Delian Krustev <[EMAIL PROTECTED]> wrote:
> It is Tomcat 6.0.14 started with its security manager enabled.
>
> The host configuration is as follows:
>
> appBase="/home/USER/web-root"
Aside from the fact that putting Context elements in server.xml is
strongly disc
Hi,
This seems to happen when there is a broken WAR inside a vhost.
Other vhosts work fine at the same time.
2008-01-27 23:21:07.556049500 INFO: HTMLManager: list: Listing contexts for
virtual host 'DOMAIN'
2008-01-27 23:21:07.556050500 Jan 27, 2008 11:21:07 PM
org.apache.catalina.core
Hi all-
I'm running into a recurring problem with an application that uses
DBCP pooling to access a database. The application initially seems to
run fine; in the test environment, it has no problem dealing with a
large volume of connections and responds to everything the way that
you would expect
I am using Apache 2.2 with mod_proxy_ajp and tomcat 5.5.25. Using straight
ProxyPass connection (no load balancing). It seems that whenever Apache is
restarted - tomcat instances die. Any way to avoid that?
Thanks.
--
View this message in context:
http://www.nabble.com/Tomcat-dies-when-apache
My first thought when dealing with linux is to verify the file
permissions and/or ownership are set so at minimum the user tomcat is
running as has at least read permissions on all the files in your
webapp. Otherwise your logs should hold more information regarding
what's happening.
--David
> From: Konstantin Kolinko [mailto:[EMAIL PROTECTED]
> Subject: Re: broken webapp after upgrading Tomcat
>
> 1) Please check how WEB-INF, classes, mvcs directories and web.xml
> file names are spelled on the Linux machine.
>
> 2) You may configure AccessLogValve in your META-INF/context.xml to
>
It is strange. Looks like it should be working.
1) Please check how WEB-INF, classes, mvcs directories and web.xml
file names are spelled on the Linux machine.
2) You may configure AccessLogValve in your META-INF/context.xml to
log all requests that are coming to your application. See
http://tomc
Hi there,
Hope someone can help. I was running Tomcat 5.5 and running a webapp just
fine on it on a Linux server. I just upgraded to Tomcat 6.0 and copied my
webapp files over to it. Theoretically it should run without a hitch but
Murphy's Law is coming into play. To run a check, I also insta
Since you need to do a clean/rebuild, which is an operation that occurs
on the webapp building side, i'll tend to say it's not related to tomcat
but more on the way your build process workd, it may be that it fails to
see the servlet need a recompilation on the developer's IDE. Compiling
servle
Mark Lange wrote:
>
> Frequently i get an invalid verb error when i request an tomcat served
> page.
>
I solved my problem.
I removed the ISAPI-Filter from the website node and added it to the top
level node "websites",
now the invalid verb error is gone.
Bye Mark
--
View this message in cont
19 matches
Mail list logo