A few points:
1. Java 1.4 is YEARS obsolete. It should not be used in production anymore
unless there is some reason why upgrading is impossible. And if there is such
a reason, time to fix it and upgrade.
2. All modern Java versions, including 1.4 I believe, use native system
operating syste
"You might want to install the same version of Tomcat standalone, and
create a comparable virtual host configuration just to see how logging
works normally. Then transfer that test case to your JBoss environment
and see what happens."
And it turns out that one of the webapps was stomping on global
"When will you get the idea to take this to a JBoss list??? Logging in
Tomcat works absolutely fine with virtual hosts in standalone mode,
right out of the box."
I also asked on a JBoss forum and they thought it's Tomcat. Right now I'm
going through the JBoss deployer code, and will set up test
Does anyone have any ideas on this? This whole thing is basically not usable
for real work if exceptions are silently dropped, which is what is happening.
Surely someone has implemented some kind of log system that works in Tomcat?
Or at least there's a way to dump exceptions to System.out or
Oh my. Ok, you need to get some basic familiarity with Tomcat before you leap
into that.
First, your applet.class file should not be in WEB-INF.
Second, don't do this as a servlet. Make a simple static HTML page work, with
the applet, first. Disregard WEB-INF entirely. Getting an applet to
"But unless you've changed your environment, you're not using the logging
facilities of Tomcat - you're using those of JBoss. We always get the
full stack traces under either. Are you sure you haven't disabled
logging in whichever you're actually using?"
I'm sure what's happening is there is a c
More progress: it looks like System.out and System.err are being captured by
classes in org.apache.tomcat.util.log. I could probably recompile those
classes to NOT do anything. Alternatively, if I could find out where in Tomcat
those are being instantiated, that might be under configurable con
I found a partial solution (requires Java 6):
I wrote my own class:
class MyLogger {
public static void log(String message) {
if(System.console() != null) System.console().printf("consoleLogger:
%s\n", message);
}
}
This has the unique advantage of working, unlike System.out.
It
"I would like to run Tomcat 5.5.x on JDK6. Is this supported?
If not, are there obvious red flags with this combination?"
I've been using it with JDK6 for a while now and it is fine. I don't think I
had to change anything at all. Java 6 is a good improvement, too.
__
"What a curious thing to say. I'm running JULI in standalone Tomcat
5.5.20 with multiple hosts with all expected log files created and log
entries made."
It's what I'm observing and it's totally reproducible. For all my apps that are
not on virtual hosts, logging works fine. For apps that are o
I'm tracking down part of the problem. I think this relates to JULI, a
terrible mistake that happened around Tomcat 5.5.9. It is fragile junk which
results in no log entries whenever virtual hosting is used. I can't figure out
how to get it to do anything more sophisticated than "silently dro
Here's a very strange problem:
I'm running Tomcat, embedded within JBoss. This is the latest version (5.5.20
I believe) of TC.
When I run this application on my office computer here, which has no virt.
hosts, console log messages show up as expected.
When I then move it over to my production
I ended up going with Jetty. It was not too difficult to write my own handlers
for content within Jetty. It didn't have any built-in handlers where I could
give it a URL as a base, but I was able to write a primitive static content
handler and a very primitive Servlet handler which are enough
"what/which tasks do you want this embedded tomcat to accomplish?"
Very simple tasks! I have a few Servlets and a few simple JSPs and a little
bit of static content (html files and images) that I need it to run. No other
external things, like no DB or anything else. No need for any other fanc
"There's a bit of real documentation here:
http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/cat
alina/startup/Embedded.html
Unfortunately, the promising "See also:" link doesn't lead to much, but
looking at the source code for org/apache/catalina/startup/Catalina.java
should be
Hello Tomcat users,
Here's what I'm trying to do:
I have a simple web application. I need to ship it as a JAR file that runs
anywhere, without needing to be unpacked or installed. I need it so that you
run this JAR file, and it pops up a Swing dialog that asks which port to bind
to, and then
16 matches
Mail list logo
