A nightmare caused by a mismatch between MySQL server and the Mysql-connector version

Plot restore

Today, the original plan to show the leader a small demo, yesterday in their own machine to increase the OK after the off-duty ...

This morning after the meeting, the leader said, "Yesterday, I let our IT colleagues to set up a new test environment, XXX you have to demonstrate the demo deployed to the above, and then set up a conference room, we have a look ... ”。

After that, I hurried to the IT colleague to confirm the information of the new environment, because he had something to ask for leave, so simply give me to say the next flash people, so left me a person to open the crawl pit trip ...

Crawl Pit Start

From their own machine login to the new environment, looked at the environment, the outfit seems to be a lot of things ... Heart secretly happy (it colleagues really to force), so the demo program package deployed to Tomcat, perfect boot!!

Open the browser, enter the URL, a huge 404 I almost did not put in the mouth of the as water spray out ... Nani? Open Tomcat's log and see,

'  $ ' received from server ...

What kind of stuff? Hurriedly Search Online | Pressure yajing, really glad that the network is really good, enter the keyword after a variety of solutions. No way, try it out. At this time the leader came, said XX, I am a bit of a thing in the morning, your demo put to the afternoon demo it ... I hastened to say "no problem, lead you first busy." Oh "It is unfortunate in the lucky Ah, heaven help me also (in the heart secretly lucky escaped a robbery).

Then climb

Hurry back to God to solve the problem, if this thing is not good, not ready to find a batch!! As time goes by, the online solution has tried one after another, with little effect. In a blink of an eye to lunch time, but I still helpless ... Torment!! Lunch at noon is also tasteless, casual Palawan two quickly come back and then solve the problem. The strangest thing is that there is no problem deploying tests in your environment, but putting them in a new environment is an error. Think carefully, first of all to eliminate the problem of the program, then will the environmental differences?

End Crawl Pit

Then opened the Pom to see the next Mysql-connector version, their own use is

<dependency>      <groupId>mysql</groupId>      <artifactid>mysql-connector-java</ artifactid>      <version>5.1.  </version></dependency>

Looks good, did not go the non-mainstream road, why would it be wrong ... Is it a problem with MySQL server? Open the tool to check the next version, almost no one let me inorder (seemingly noon also did not eat).

> SELECT VERSION (); 6.0. -alpha-community

What is this version of autumn? Alpha is not bright blind my eyes ~ ~ ITX Small handsome pot, we both have no revenge?! Oneself in the online simple search, now can not find the download address, really is no language ah ...

No way, can not re-install MySQL server bar, then try to use the old Mysql-connector bar, in the Maven warehouse to find a use of the highest 5.1.6, from the new packaging deployment, problem resolution:

---

PS. This afternoon because the leadership thing did not finish, the demonstration of things temporarily stranded, is a false alarm. It's also a bit of fun to be here for a dull life:)

A nightmare caused by a mismatch between MySQL server and the Mysql-connector version