from your stacktrace it appears that this error occurs when XML is being
parsed, because TC can't find a class:
java.lang.NoClassDefFoundError: org/apache/naming/TransactionRef
in my installation (5.5.9) this class is in
%catalina_home%\common\lib\naming-factory.jar so might be worth checking
The Logger under 5.0.x uses -MM-DD format in the filename, so this
would change each day, would that give you what you need? See FileLogger
under Standard Implementation at:
http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html
PS note that Logger is deprecated in 5.5.x
-Original
windows or linux? if on windows and runing as a service, have you run the
service install command after copying across the contents of the TC root
directory?
also check:
have you set the env variables JAVA_HOME and CATALINA_HOME?
are file permissions on the jar file OK?
-Original
to behave the same way
on the two
platforms. But it looks as if this is an OS-specific difference, as I
can't see any difference in the configuration files between the two
servers.
Tom Burke
- Original Message -
From: Steve Kirk [EMAIL PROTECTED]
To: 'Tomcat Users List
by
the time contextDestroyed() is called (see
http://issues.apache.org/bugzilla/show_bug.cgi?id=37264) so you could
do the lookup and cache the datasource object in contextInitialized().
On 10/28/05, Steve Kirk [EMAIL PROTECTED] wrote:
Yes, confirmed, I get the same problem. (I used
Bob, I replied to your original post - if you did not get that, check the
archive here
http://mail-archives.apache.org/mod_mbox/tomcat-users/200510.mbox/%3c00fc01c
[EMAIL PROTECTED]
Re what xml the host tag is referring to, I assume that the xml settings in
host relate to loading all the config
(Http11Protocol.java:732)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi
nt.java:619)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:688)
at java.lang.Thread.run(Thread.java:534)
Steve Kirk wrote:
A long shot, but if you
This is a repost of a message I first posted in June that I got no replies
to.
I have a double-logging problem, by which I mean that
some of my log messages get logged to two logfiles. I have only one
logfile configured using java.util.logging, but in some cases, the
same log message gets
Not sure, but this could be it: TC saves Session objects to files when the
webapp is started/stopped. (This is a configurable feature in context.xml).
To do this, any attribute that you add to a Session object must be
serializable. Therefore I would guess that if you call
And try to use
removeAbandoned=true logAbandoned=true
removeAbandonedTimeout=120
to track which connections were not properly closed (see
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-exampl
es-howto.html)
Regards
Jan
Steve Kirk wrote:
how many concurrent requests
probably submit
the example to bugzilla. Can somebody familiar with the code suggest
which catalina object keeps a reference of the datasource (beside
being registered in JNDI)?
On 10/26/05, Steve Kirk [EMAIL PROTECTED] wrote:
Your code and config below look fine to me, conns seem
the key lines to look at more closely at these:
java.lang.ClassCastException
org.apache.jsp.errorpage_jsp._jspService(errorpage_jsp.java:103)
...
org.apache.jsp.preview_jsp._jspService(preview_jsp.java:135)
(esp the latter), and:
note The full stack trace of the root cause is
at the risk af asking the obvious, does the database myDB exist on the
remote server at the same port number, and with the same username and pw as
on the local server, and if so, does it have any IP address filters that
forbid remote mysql client connections?
-Original Message-
From:
Two things:
1. you need to deploy your webapp as the ROOT webapp on the server. there
is a standard ROOT webapp that ships with TC, you can just replace that if
you want to, examine that to see how to configure it, look especially at the
%catalina_home%/webapps/ROOT/WEB-INF/web.xml config file.
I believe (although am not 100% sure because I haven't tried it myself) that
xmlValidation=true means that TC's XML parser should check all XML against
the DTD defined in each XML source. With xmlValidation=false, it will
check that the xml is well-formed but not that it is valid.
See these
A long shot, but if you are running RHL9 you might try this, as mentioned in
the TC 5.5 release notes at
http://tomcat.apache.org/tomcat-5.5-doc/RELEASE-NOTES.txt :
Tomcat on Linux:
GLIBC 2.2 / Linux 2.4 users should define an environment variable:
export
16 matches
Mail list logo
