Good catch and one I thought of earlier. Unfortunately that would
generate a java.security.AccessControlException, not a
java.net.ConnectionException.
The OPs exception comes from a failure to connection to the port mysql
is supposed to be listening on.
--David
Martin Gainty wrote:
Sorry
Most implementations work fine with using /dev/urandom as a seed for the
sessionid generator for Tomcat (class ManagerBase), but I have 2 instances
that seem to cause Tomcat to hang on open of /dev/urandom. I have been
unsuccessful in finding any overrides that would get the session manager to
use
Hi Rainer
a very big thanks for your help, and also for your work in the
connector project.
My work and passion depends on your work: I will never thank enough
you and the many people working on opensource projects like tomcat.
I will test the new version as soon as it's released.
Best regards
E
I didn't see auth="container" parameter for your
I did'nt see type="org.apache.catalina.UserDatabase" parameter for your
Anyone else?
M-
This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
designated recipients named above.
Sorry for jumping in late in the thread but I assume you covered the basics as
in granting your Socket the ability to connect as in
$CATALINA_HOME/conf/catalina.policy
grant
{
permission java.net.SocketPermission "NameOfDBGoesHere:PortNumberGoesHere",
"accept,connect,listen,resolve";
}
?
Martin
Hi Enrico,
I think we will have fixed your original problem, and also the
sendfull/another log lines in 1.2.20. They don't mean anything bad, so
please ignore them for the moment. Watch the list, we will have a 1.2.20
release ready for testing next week.
Concerning the client write error, this us
