Me again, I did luckily "solve" my problem - at least it vanished :-) Just for the ones who seem to have the same problems I'm trying to describe what I did:
Am So, 2003-08-31 um 02.28 schrieb Nikolas List: > After a reboot of the system (patched the kernel) I now get the > following error message: > > java.sql.SQLException: Server connection failure during transaction. > Attempted reconnect 3 times. Giving up. > It seems that there is no connection to the DBCP or the Connector/J as I expected. In some newsgroups I found hints (sorry - didn't save the links) that the problem could be related to name lookup problems. My guess is - and it's just a guess - that this has been true in my case. At least we had problems "relaying" mail from this host later the week, which seemed to have a related reason. What I did is the following: I changed the <url>-value to http://[hostname]/[dbname] It seems to be important to switch of the autoreconnect at least for one connect. After that it worked again and I could reactivate the autoreconnect to yes. (Remark: I think this have been the "important" steps I did - I did quite a lot things that night and the following, desperatly trying to reestablish this webapp, so I might have overseen a crucial action!) If I am right the deeper reason is a denial of connect to the mysqld which is not able to lookup the correct hostname mentioned in his mysql/user-table. But why didn't I find any log entry in mysql.log? This denial of connect seems to be hidden through the connection pool autoreconnect-feature (as I described switching this of and connecting showed the denial of connect.) Good Luck - and enlighten me, if anybody comes to a deeper insight on that problem. Bye, Niko --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
