from your original post:
Failed to install Tomcat5 service. Check your settings and
permissions.
suggests to me that you are not logged in as Administrator?
that's probably why the install fails. the DIR of your \bin directory looks
like installation failed halfway through.
as Yoav says,
I may be way off the mark here, but could this by any chance be related to
the JNI classloading issue raised by Benson last week could it? You'll find
more details if you search the archive, but the basic jist of that was:
1. if you try to load the same JNI class using two different classloaders
yes I experienced this exact problem in 5.0.27, and simply upgrading to
5.0.28 fixed it.
-Original Message-
From: Peter Rossbach [mailto:[EMAIL PROTECTED]
Sent: Monday 01 November 2004 07:50
To: Tomcat Users List
Subject: Re: context.xml deployed as folder in Tomcat 5
It is
do you have a context.xml in the war file or the webapps folder? See
comments re context xml files in 4th para in page below - the para beginning
In addition to nesting Context elements inside a Host element
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
the address already in use error indicates that the port is already in use
by another service (probably IIS from what you've said). you can't have two
services on the same port. stop IIS and check that IIS does not still have
hold of port 8080. use netstat -a at the dos prompt to check.
I believe that if your servlet is /mywebapp/myServlet and your user accesses
/mywebapp/myServlet/iwant/this/file, the iwant/this/file part is available
as the request parameter getPathInfo() and you can do what you like with
that - access a database, access any filesystem to which you have access,
I had always thought all sessions were lost when the server restarts. In
fact I just tried it and confirmed that (5.0.28). Are we maybe talking
about 2 different things?
I have nonstandard config (a very sparse server.xml, no explicit Manager
configured in server/web/context xml), and I do not
Following Yoav's earlier comments I've implemented a basic class
SessionLogger that implements HttpSessionListener,
HttpSessionActivationListener, HttpSessionAttributeListener,
ServletContextListener. It just writes amessages to stdout using
System.out.println() to log when each event fires,
This was answered on this list last week. So it's in the archive:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
pache.org
From memory I think you get rid of the ROOT webapp and set the context path
of mywebapp to / ?
-Original Message-
From: Jojo Paderes [mailto:[EMAIL
-Original Message-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: Friday 05 November 2004 07:01
To: Tomcat Users List
Subject: session-timeout means tomcat restart
Hi, I'm experiencing 2 interesting problems that may be related to my
session timeout.
1. It seems that
from your original post:
org.apache.jasper.JasperException: Unable to compile
class for JSP
root cause
Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
in other words, TC is unable to compile your JSP page class
Eric - you are correct, you do not need both resource-ref and Resource
(although I've found that having both does not cause a problem).
Back to your problem.
The error message indicates that TC cannot find the Resource.
I'm not sure if you are trying to use DBCP or not (in other words, does
tomcat5 and stop it with net stop tomcat5.
On Thu, 2004-11-04 at 20:15, Steve Kirk wrote:
Following Yoav's earlier comments I've implemented a basic class
SessionLogger that implements HttpSessionListener,
HttpSessionActivationListener, HttpSessionAttributeListener,
ServletContextListener
Ah yes I agree, but that's not quite what I was saying. Eric, sorry if that
was misleading.
Eric has a resource-ref already. I meant that if you have resource-ref
you do not need Resource as well in TC, because this is what the TC docs
say, and the Resource tag is a TC invention rather than
Remy, the server config reference at
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html
says, Each such Context MUST have a unique context path, which is defined
by the path attribute which implies that we must include the path attribute
in a Context, wherever it is configured.
-Original Message-
From: Raasi Potluri [mailto:[EMAIL PROTECTED]
which Tomcat version is the best and reliable version
for me to learn and best practive Servlets and Jsp. I
have tried to use Tomcat 5.0 and it has crashed. It
was working fine before. and now none of my servlets
Eric said:
Also, I noticed in many solutions the suggestion was made to edit the
myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
However, there is no myapp.xml in that directory on my server. Just 2
.xml's related to other applications and a manager.xml which I'm not
sure
That file is only updated in certain circumstances. check that your
circumstances fit those. here's a good place to start:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/host.html#Automatic%2
0Application%20Deployment
I adopted the habit of restarting with a script, which deletes the
to the
work directory?
How are you stopping Tomcat?
On Thu, 2004-11-04 at 20:15, Steve Kirk wrote:
Following Yoav's earlier comments I've implemented a basic class
SessionLogger that implements HttpSessionListener,
HttpSessionActivationListener, HttpSessionAttributeListener
-
From: Ben Souther [mailto:[EMAIL PROTECTED]
Sent: Friday 05 November 2004 15:08
To: Tomcat Users List
Subject: RE: sessionS info persistence when restart Tomcat
On Fri, 2004-11-05 at 09:06, Steve Kirk wrote:
SessionDestroyed shouldn't be called when tomcat shuts down.
good point
Remy mentioned earlier today on another thread that the path is ignored in a
context.xml file because it is redundant, but I _think_ he was talking about
5.5 rather than 5.0. I have deleted the post now but I think he said that
the docBase is probably also ignored. search the archive to check me
, Steve Kirk wrote:
Thanks Ben, have looked at your war, and my test code
covers the same as
yours plus some of the other Listener events. The
sessionCreated and
sessionDestroyed events work fine on my code (5.0.28). The
problem is that
the other events I mentioned are not called - e.g
-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: Saturday 06 November 2004 00:51
To: Steve Kirk
Cc: Tomcat Users List
Subject: Re: session-timeout means tomcat restart
Well, this is amazingly frustrating. My TC 5.0.28 running on Linux
FC2 is completely crashing about every half hr when I
OK no-one's answered so here's an idea. Not sure if this is right but maybe
if I get it wrong someone will correct me ;)
I think it's that, despite appearances, you are in fact running a
precompiled servlet class, which is installed by default, rather than a JSP
page via
My favourite answer to any query about a server being painfully slow: does
the slowdown coincide with a slowdown or outage of your DNS service? This
can have suprisingly big impact if TC is doing reverse lookups of the IP of
every request.
At the risk of asking the obvious, are you sure that
-Original Message-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: Friday 05 November 2004 18:34
To: Steve Kirk
Cc: Tomcat Users List
Subject: Re: connection pooling
Steve, I am trying to use DBCP(hence the subject of the thread) and I
believe I have a driver that supports
The docs under 'JDBC Data Sources' at
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-resources-howto.html
say, The J2EE Platform Specification requires J2EE Application Servers to
make available a DataSource implementation (that is, a connection pool for
JDBC connections).
Now, I'm
problem' and it
was two things - we had to update some driver for the intel
NIC cards in our
server (for RedHat ES) and had to change some settings to get
better NIC
throughput.
Hope it helps.
- Original Message -
From: Steve Kirk [EMAIL PROTECTED]
Date: Monday, November 8, 2004 4
Quick guess: check that you have the default JSP servlet and mapping
enabled. by default this is generally found in two separate chunks within
the web.xml of your tomcat's conf directory and looks a bit like this:
servlet
servlet-namejsp/servlet-name
You don't say what version. I am aware that things are changing in this
area in 5.5.x so what I'm saying possibly applies to 5.0.x only. Check the
docs if you have a different version.
In 5.0.x, you have to put resource-ref in web.xml if you want to be
compliant with the servlet spec.
If you do
I've considered something like this in the past. However, I'd be interested
to know how you plan to have the failover website at the second take over
when the first website dies. In other words, how will a user's browser know
to access the website at the failover IP address rather than the
? (hot failover)
You need your fail over to be higher up in your network stack
Filip
- Original Message -
From: Steve Kirk [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, November 10, 2004 9:35 AM
Subject: RE: Multi-Site Clustering
OK that's roughly what I thought. But IME this does not switch things over
fast enough to count as a hot failover. Maybe I'm not aware of a premium
service that's available, but my experience has been that DNS updates don't
propagate fast enough for this. There are often customers that cannot
Interesting.
I had a quick browse of the servlet spec and it doesn't seem to say either
that you can or cannot do this.
However these guys seems to reckon it works on TC:
http://archives.java.sun.com/cgi-bin/wa?A2=ind0103L=servlet-interestF=S=;
P=50479
If it is possible, your config looks
-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Tuesday 09 November 2004 00:45
To: 'Tomcat Users List'
Subject: Are all TC-managed DataSources pooled?
The docs under 'JDBC Data Sources' at
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-resources
-howto.html
say, The J2EE Platform
cheap either since we had a couple of full cabinets at two different
locations.
peter
On Wed, 10 Nov 2004 22:52:08 -, Steve Kirk
[EMAIL PROTECTED] wrote:
OK that's roughly what I thought. But IME this does not
switch things over
fast enough to count as a hot failover. Maybe
)
you don't need to run DNS to do this
Filip
- Original Message -
From: Steve Kirk [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED];
'Peter Lin' [EMAIL PROTECTED]
Sent: Wednesday, November 10, 2004 7:57 PM
Subject: RE: Multi-Site Clustering? (hot failover)
Thanks
Thanks for your comments Doug. Good point re relevance of javax.sql API
docs.
I had a search through the J2EE spec. It does not appear to me to _require_
that DataSources are provided in a pooled implementation. It seems to be
preferred. For example:
J2EE.5.4.3 (J2EE Product Provider's
is minimal and you get much better fault tolerance.
peter
On Thu, 11 Nov 2004 12:56:06 -, Steve Kirk
[EMAIL PROTECTED] wrote:
Yes that's true and I have used that feature in the past by
asking our ISP
(registrar) to enter multiple A records in the primary DNS.
However
Thanks Yoav. I see your original reply in the archive now, but I never got
it via email. Strange. I do occasionally get notifications from ezmlm that
my mailbox has been bouncing mails, but haven't had one of those for a
while. I think the bouncing is due to false positives at my ISP
OK thanks, some useful points. I'll do some more reading. :)
So I'm going to submit an enhacement suggestion for the docs
(5.0.x/5.5.x),
as they imply that DBCP is always used for datasources.
The docs give a DBCP example. If someone needs to be told another
implementation can be
My webapp has a working JDBC DataSource configured in META-INF/context.xml.
The JNDI how-to mentions that the default factory for TC-managed JDBC
DataSources (i.e. those configured as a Resource in the config files) is
org.apache.naming.factory.DbcpDataSourceFactory, but if I configure that as
From reading your post below, I'm not sure what your problem is, or what you
are trying to achieve. I must have missed your previous emails. Can you
explain in a bit more detail?
-Original Message-
From: Alex Korneyev [mailto:[EMAIL PROTECTED]
Sent: Thursday 02 December 2004 15:06
Here's one perspective based on one way I have used them. there are others.
%@ include% is useful when you know the name of the page you want to
include at coding time.
jsp:include is useful when you do not know the name of the page you want
to include until execution time, because it can
if you call request.getSession(false) this will return null if the request
is not associated with a request already. the false param turns off the
default behaviour of creating a new session when none exists.
-Original Message-
From: LAM Kwun Wa Joseph [mailto:[EMAIL PROTECTED]
Sent:
I haven't tested this, but I *think* that a request containing an expired
session will still return a non-null session object, but a different
instance to the one that would have been returned pre-timeout. But I don't
know that for a fact. why not just test it out yourself, it's not that
hard,
I'm a bit puzzled. There is something not quite right here (or maybe I'm
not quite understanding correctly). Aren't sessions created as soon as a
JSP within a ServletContext is accessed, irrespective of whether the user
authenticates or not? Thus invalid sessions vs anonymous sessions is not an
at that point.
Hope this is useful to someone else and isn't too far off the mark...?
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Wednesday 08 December 2004 16:25
To: 'Tomcat Users List'
Subject: RE: How to detect expired session vs. no session? (Solved)
I'm
By default:
1. getSession(true)!=null
2. getSession(false)!=null
But if a JSP page contains the tag %@ page session=false %, then:
1. getSession(true)!=null
2. getSession(false)==null
In the last of these 4 cases, do you mean that the implicit JSP session
object returns null, or that
:15, Steve Kirk wrote:
Following Yoav's earlier comments I've implemented a basic class
SessionLogger that implements HttpSessionListener,
HttpSessionActivationListener, HttpSessionAttributeListener,
ServletContextListener. It just writes amessages to stdout using
System.out.println
they are methods
of objects bound within the session or not.
However I'd still appreciate any help that anyone can give on the other
points below :)
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Friday 10 December 2004 05:50
To: 'Tomcat Users List'
Subject: RE
session vs. no session? (Solved)
I am curious why people spent so much time trying to figure
out whether
request.getSession(...) returns null or not but didn't bother using
request.getSession().isNew()?
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent
In the last of these 4 cases, do you mean that the implicit
JSP session
object returns null, or that request.getSession(false)
returns null? I
could understand the first behaviour but would be surprised
by the second.
actually forget I said that, I made a mistake,
,
Tomcat is not throwing that exception just because it feels
like it. An
instance of that class must be reachable in the serialization
process of
at least of the session attributes.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Steve Kirk [mailto:[EMAIL
Ben Souther said:
This is probably the bug you're talking about.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29521
Aha. Thanks Ben. That clears up most of it in one go.
So it was fixed in 5.0.29 but as far as I can see (from the Jakarta news
page and the TC download page) there
no. I've checked this by adding more debug code to my SessionLogger class
(which implements all the Listener interfaces). Every time a session event
is fired, my listener code lists all the session attribute names and values
to the log. So when I shutdown TC, the log output looks like this:
-Original Message-
From: Chris Cherrett [mailto:[EMAIL PROTECTED]
Is there a way to catch all exceptions that works in Tomcat 5
You can catch all Exceptions/Throwables and their subclasses by configuring
java.lang.Exception or java.lang.Throwable in the error-type tag. However
, and no errors were logged.
So, as far as I can tell, it seems that the include-prelude tag is being
silently ignored when placed in a 2.3 web.xml, but no errors are being
thrown.
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Thursday 07 October 2004 18:42
To: 'Tomcat Users
report. Post it in Bugzilla (probably to
the Jasper
component). I notice you said 5.0.27: does 5.0.28 work?
Yoav Shapira http://www.yoavshapira.com/
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Monday, October 11, 2004 2:50 PM
To: 'Tomcat
...
Steve Kirk wrote:
I've had similar problems myself (not fully answered yet).
Here's a
couple
of issues that I found:
1. Check the exception messages / stack traces in your browser and
logfiles
carefully to make sure that droit.jsp is not itself
throwing a second
exception
repositories.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 13, 2004 10:29 AM
To: 'Tomcat Users List'
Subject: ServletException not wrapping cause correctly
The short version is: ServletException does
As Yoav says, it works, and is very easy to use once you have it configured.
But note that lots of people seem to have trouble getting the config right.
I was one of those. You have to persevere a bit. The problem I had was
that there are lots of pages on lots of websites that describe how to
A customer is interested in licensing and developing the source code for a
servlet-based webapp that I am writing, but for maintenance and support
reasons they want it written in MS technologies (asp, asp.net, c#, etc)
rather than Java servlets. I have some experience of webapps written in ASP
I'm trying to work out how to configure web.xml to use a custom error page
when one of a list of HTTP status codes are encountered. Couldn't find any
documentation, so pure guesswork led me to try this:
error-page
error-code404,406/error-code
Thanks Matt.
This is in fact what I have been doing to date :) . The problem is, that to
configure the error page to handle several different status codes, you have
to keep repeating basically the same 4 lines of config, with just the error
code changing each time - a bit repetitive, and not good
Can anyone confirm that they have got include-prelude to work? It appears
to be ignored in my installation, in that the prelude file is not included
within any of my JSPs. No exceptions are thrown or errors logged. I can't
find any reference to a problem on the web or the archives of this
You can certainly telnet to the shutdown port and send the shutdown string.
You could do this using a scripting tool or simple Java class. For example,
telnet to localhost 8015 then send the string shutdown, or whatever string
is configured in server.xml for that port.
-Original
Subject: RE: Using shutdown script for different port
Hi,
Of course, you can only do this telnet from the local machine ;)
Otherwise we'd have a nice security hole ;)
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 29, 2004 4:22 PM
To: 'Tomcat Users List'
Subject: RE: Using shutdown script for different port
To be clear, the default setup _does_ allow shutdown using
telnet from
any
machine unless
Try turning off ip to name resolution, this can sometimes be very slow and
seemingly affect different PCs/servers differently. I'm no expert on what
might cause the slowdown in your case, but I have experienced what sound
like similar problems in the past.
From the default server.xml file for
-pattern*.jsp/url-pattern
include-prelude/WEB-INF/jsp/include/prelude.jspf/include-prelude
/jsp-property-group
/jsp-config
/web-app
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Wednesday 29 September 2004 19:45
To: [EMAIL PROTECTED]
Subject
Only just noticed this, looks like a possible bug, but maybe there's a
reason behind it?
Basically, the default web.xml files included within the standard webapps of
5.0.27 and 5.0.28 seem to be a mix of webapp v2.3 and v2.4 - anyone know if
there is a reason for this, or is this a bug?
Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Thursday 30 September 2004 17:32
To: 'Tomcat Users List'
Subject: versions 2.3 and 2.4 of web.xml
Only just noticed this, looks like a possible bug, but maybe there's a
reason behind it?
Basically, the default web.xml
I've had similar problems myself (not fully answered yet). Here's a couple
of issues that I found:
1. Check the exception messages / stack traces in your browser and logfiles
carefully to make sure that droit.jsp is not itself throwing a second
exception when trying to display the
). The
validation that tomcat does on web.xml is usually very thorough, so this
case seems to be a bit of an anomaly.
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Thursday 30 September 2004 18:03
To: 'Tomcat Users List'
Subject: RE: versions 2.3 and 2.4 of web.xml
complain, that'd be great. I don't have time
to look at
this now, there are more important issues around, but maybe
eventually... ;)
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 07, 2004 11:27 AM
Someone please correct me if I've got this wrong, but I don't think that the
try/catch or if constructs achieve anything, so the whole code that
Steffen posted could be replaced with simply:
serveResource(request, response, true);
(Maybe this is what Steffen was implying?)
So, as I am
ServletException seems to behave differently than expected when wrapping
other Throwables, and I'm wondering if there is a reason for this. A bit
more explanation: in general, since JDK 1.4, any subclass of Throwable can
be used to wrap another Throwable passed as an arg to its constructor (see
Does anyone know if there is a way to make a single error-page entry in
web.xml cover more than one error-code?
I have created a single error page which I would like to display whatever
the exception-type or error-code. Catching all the exception-types in
one go is easy - I just use:
Seems to me that browsers are inherently pull technology because at the
basic level they send a single request and await a single response to it.
You can't push stuff at them that they haven't requested. Hence why you
have to use an approach like your javascript - which, by the way, I have
used
/DataUpdateCheck which is a servlet that returns just a
simple js function - if there is new data, the function reloads it into the
visible frame, otherwise it reloads itself after a couple of seconds to
check for more data.
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED
Message-
From: Michael McGrady [mailto:[EMAIL PROTECTED]
Sent: Tuesday 19 October 2004 14:57
To: Tomcat Users List
Subject: [OT] Re: Push-Server with Tomcat
Do you have a simple sample of this Steve? If so, I would
sure like to
see it.
Michael McGrady
Steve Kirk wrote:
Not sure
as a shot in the dark, your servers might be making reverse lookups of IP to
DNS name for logging purposes (or if you call request.getRemoteHost()), and
if your DNS setup is performing slowly this might explain it. You don't
mention whether the HTML page itself is returned quickly or not. if
Not sure about using SocketWriteException. A less elegant approach might be
to put a javascript function in the page that is called when the window is
closed. That JS function could call a servlet that you can write. (This is
a bit OT though because it's really to do with HTML rather than
Steffen Heil wrote:
- Tomcat 5 uses newer specifications than 4.1.x. does. Your
App MIGHT be
incompatible.
Yes unexpected problems can happen. An example of this is the config files.
V4 supports the v2.3 of the servlet spec, V5 supports v2.4 as well as v2.3.
If you use v2.4 features, make
Scroll down to point 8 under Incompatibilities Between Java 2 Platform,
Standard Edition, v1.4.0 and v1.3, read the second bullet. This confirms
Alan's comments.
http://forum.java.sun.com/thread.jsp?thread=466368
http://forum.java.sun.com/thread.jsp?thread=466368forum=31message=2145193
Sorry - ignore my last post, it contained the wrong link.
Try this instead. Go to point 8, second bullet:
http://java.sun.com/j2se/1.4/compatibility.html#incompatibilities1.4
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Friday 22 October 2004 12:55
To: 'Tomcat
I used to use TC behind Apache but found that a bit flakey under windows
(which was my dev platform), and I found configuring the two servers
separately a bit fiddly. So when I started a new project I did a bit of
homework on TC standalone, then decided to drop Apache entirely and run TC
Sounds like it's a case where using a war file is causing the problem. I
would drop the war files altogether and just distribute their contents.
That way you can distribute just the bits of the webapp that you have
changed. Sounds to me like you own the JSP/servlet/config files and they
own the
More info here
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/default-servlet.html#secure
which refers to the servlet spec, which is here
http://jcp.org/aboutJava/communityprocess/final/jsr154/index.html
-Original Message-
From: vivek gupta [mailto:[EMAIL PROTECTED]
Sent: Friday 22
I haven't experience this myself, but as no-one else has responded yet, here
are some thoughts that come to mind in case they help :-)
Perhaps the session associated with cookie C1 has expired by the time that
Tomcat receives the request that contains C1? Then, if your code uses
If you really need to, you can wrap one exception inside the other, e.g.
throw new ServletException(new UnavailableException(my unavaiable
message));
and I think you'll find that the Tomcat error page (or your own custom error
page, if configured) will automatically strip the outer
Throwing a generic ServletException wrapping my UnavailableException
would probably get the report showing up, but it also means Tomcat won't
be
able to respond correctly to it.
Yes. Sorry, I had missed the fact that UnavailableException is a subclass
of ServletException, so unless your
Not sure that this is your actual problem, but is it correct to use
mailto:; within the to/from addresses?
-Original Message-
From: David Lee [mailto:[EMAIL PROTECTED]
Sent: October 25, 2004 3:51 PM
To: [EMAIL PROTECTED]
Subject: Why mail/session always being set to localhost even
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Monday, October 25, 2004 3:41 PM
To: 'Tomcat Users List'
Subject: RE: Why mail/session always being set to localhost even
Context.xml says otherwise?
Not sure that this is your actual problem, but is it correct
try a quick googling:
http://www.google.com/search?hl=enlr=q=tomcat+space+%22folder+name%22btnG
=Search
I always omit spaces from folder names, on the basis that it _might_ cause
an unexpected problem - why tempt fate?
If you have to use spaces in the name, you may need to enclose paths in
This type of bug crops up a lot on this list. The best answer seems to be
to make sure you follow the instructions on this page _exactly_:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-how
to.html
I assume that where you have x/y in your config file this is to hide
When you say random do you mean that accessing the same URL sometimes
gives a 500 and sometimes not, or that you can't see a pattern in the URLs
that cause the 500?
Are you looking in all the tomcat log files (under CATALINA_HOME\logs ), and
the apache httpd logs, as well as any TC log file you
This question illustrates (IMHO) probably the biggest issue of confusion
with regard to DBCP - that is, there are several XML elements that you can
potentially use, and several places that you can potentially put them.
Specifically, the Resource, ResourceParams and ResourceLink elements
can go in
I have a suggestion for an improvement to the how-to docs (a slightly
misleading instruction which I think needs correcting). Where should I send
that? Bugzilla?
Also I have a suggestion for a new how-to document that I would be prepared
to write, or contribute to, if these are written by an
1 - 100 of 200 matches
Mail list logo
