Yes I have. After some more investigation I think the problem is this: the entry in server.xml is like this user=ken;password=ken. But mySQL wants a "&" and xml parser demands a ";". With a ";" mySQL thinks no password was sent and so denies me with 'password: no'. With "&" debug=99 comes into play and tells me "The reference to entity 'password' must end with the ';' delimiter". But as soon as I do that then mySQL no longer sees the password!!
I have read about the need to change the ";" to "&" while investigating on google so I know some people have found that necessary. My problem is that I then get the parser error. So it seems to me I'm sitting on the horns of a dilemma from which I hope someone can remove me. Thanks! -----Original Message----- From: Rick Fincher [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 2:14 PM To: Tomcat Users List Subject: Re: JDBC realm problems Hi Ken, Have you tried setting the debug level to 99 in the realm tag in server.xml? You may have already done this, but it will add a lot more info to the log about the process of getting into the realm. Rick > Hi, > > I've spent many hours last week and a few more today trying to get JDBC > security realm to work and keep stumbling on this error: > java.sql.SQLException: General error: Access denied for user: > 'localhost.localdomain' to database 'tomcatusers'; > > I'm sure many people have problems getting this to work right off and I've > read a fair amount about various solutions. But what I can't figure out is > why the access denied error doesn't include a user name but only > localhost.localdomain. I've put user and password in server.xm; there is a > tomcatusers table with what i believe are the correct entries. In fact > they're copied/modified from the Goodwill book. I wouldn't be surprised by a > bad username or bad password error but this indicates that the user name > just isn't being passed along. Anyway I assume that I'll find the answer to > the authentication problem if I can find out why the user name doesn't seem > to be passed along to the database call. > > Does anyone have any clues? > > Thanks, > > Ken > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
