/*)
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Robert Jacobson robert.c.jacob...@nasa.gov
Lead System Admin Solar Dynamics Observatory (SDO)
Bldg 14, E222 (301) 286-1591
-
To unsubscribe, e-mail: users-unsubscr
Chuck wrote:
Not sure what else is going on, but the above is incorrect for your webapp - the
context name is *not* part of the url-pattern.
Oops! You're right of course. Thank you! I'm a little confused as to
why having an incorrect url-pattern would cause the SQL to fail.
About the
Hi,
I'm running Tomcat 6.0.20 on Windows 2003 Server, with JRE 1.6.0_14.
I have a working Tomcat configuration using MySQL authentication to access to
ROOT webapp. I'm using DataSourceRealm just like the one in the Tomcat docs
Hi,
I have a Tomcat 4.1.37 server running on Windows Server 2003. I have SSL setup
and working.
The network admins scanned my machine and requested that I reduced the
supported SSL ciphers so that only 128-bit ciphers were allowed.
So, I added the following setting to my Factory for the SSL
Robert Jacobson wrote:
So, what cipher(s) do I need to add to make sure that IE6 can connect?
Answering my own question...
I searched Google for one of the ciphers I'm already using, and the
first link was:
http://www-306.ibm.com/software/webservers/httpservers/doc/v2047/manual/ibm/en_US
Christopher Schultz wrote:
Yes, using DataSourceRealm is the preferred configuration.
Thank you for confirming that :)
[...] By the way, there's no reason not
to upgrade to the most recent Connector/J, either.
Sorry.. are you referring to the mysql-connector JAR file? In my
Hi,
I have an existing Tomcat configuration that is working well. However,
it is running version 4.1.31. We are updating the platform, so I
thought I'd take the opportunity to update Tomcat. Unfortunately (??) I
must stick with the Tomcat 4.1 release.
I have a test machine on which I
