Package: tomcat5
Version: 5.0.30-12
Severity: minor
*** Please type your report below this line ***
The file RUNNING.txt claims tomcat is running on port 8080
while it is actually running on port 8180 as said in the README
-- System Information:
Debian Release: 4.0
APT prefers testing
APT
Ah, so the situation is the result of your local configuration which
disables rotatelogs?
No, it's in 5.5.20-4 in the archive.
This might lower the importance of the bug (it's currently considered
release critical).
I think we should release 5.5.20-2 which is in testing. It has no RC
On Tue, Dec 12, 2006, Marcus Better wrote:
It's usually to diagnose startup problems.
I propose that we add a debug mode, disabled by default, in which we send
stdout and stderr to a regular file, or even the named pipe, and tell the
user to read it manually.
In normal operation we
Hello Marcus,
I'm using the package with a lot of data sources and it works fine.
Maybe the problem is in the way you define and link the datasource.
I use this in my virtual host:
Context docBase=/home/app path=/app
ResourceLink type=javax.sql.DataSource
name=jdbc/mydb global=jdbc/mydb
/
But you need to bootstrap it somehow, and during the bootstrap, there's
usually a simple logger which logs to stdout.
I retract my previous proposal, and propose instead to send the initial
messages to the syslog. That would be logical for a daemon.
I found this blog post
on the
Is it Debian specific to depend on jsvc to start tomcat?
It's actually the method recommended by upstream:
http://tomcat.apache.org/tomcat-5.5-doc/setup.html
It's true that it requires a native app (not a library), but it seems to be an
improvement over the previous method. For instance we
On Tue, Dec 12, 2006, Marcus Better wrote:
It's actually the method recommended by upstream
Oh, perfect then.
It's true that it requires a native app (not a library), but it seems to be
an
improvement over the previous method. For instance we get a clean shutdown
procedure, which
(I don't recall running into that, nor that two JVMs thing,
This was mostly an issue on an overloaded system, I think. Not sure what was
going on, but the init script would never succeed in stopping Tomcat until
the timeout elapsed.
The second JVM invocation is the java call in catalina.sh
I straced the process and it happily stats the specified workers file,
but doesn't attempt to open it, which would explain why it complains if
you give it a non-existant file.
--
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua stulta superstitione.
Hi, I modified the scripts in java-package to it provide the support to
the Java 6 (released today). Also I created both directories sun-j2re1.6
and sun-j2sdk1.6 and i made some modifications in install file and
remove file that i copied from the sun-j2re1.5 and sun-j2sdk1.5,
respectively. The
10 matches
Mail list logo
