Let me see if I got the steps correct. Is this what you did:
1) copied server/default as server/production
2) copied the MySQL JDBC jar file to server/production/lib
3) started the server as: ./run.sh -c production
I do this all the time without any problems.
I did exactly same except rather then copying server/default folder i copied server/all folder.
Do you, by any chance, have a copy of the JDBC jar file in one of the applications you deployed? What are the contents of the *-ds.xml file for MySQL? Where did you deploy that *-ds.xml file, in the server/production/deploy directory, or within your application?
No I didn't package jdbc jar into my application, i copied it to server/production/lib and since i am using clustered jboss so i put *-ds.xml file under server/production/farm directory.
So i can be replicated across the jboss nodes.
I am using an older version of Jboss and MySQL. But when I encountered a similar problem, I made a jar of the mysql com/ files and mysql org/ files from the mysql distribution and placed them in the server/<server name>/lib folder. Seemed to work!!