Based on the location of the error immediately after the establishment of DefaultDS, I assume that the error messages concern that datasource (the portal uses PortlaDS, not DefaultDS, and it is opened much later in the console output). I therefore assume that you replaced the hsqldb-ds.xml file, which uses Hypersonic to manage DefaultDS, with another *-ds.xml file to use MySQL for DefaultDS. Could you post the contents of that *-ds.xml file.
here it is :
<!-- Datasource config for MySQL using 3.0.9 available from: http://www.mysql.com/downloads/api-jdbc-stable.html --> <datasources> <local-tx-datasource> <jndi-name>DefaultDS</jndi-name> <connection-url>jdbc:mysql://localhost:3306/jboss_appserver</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>mco</user-name> <password>TefNout</password> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name> <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name> <metadata> <type-mapping>mySQL</type-mapping> </metadata> </local-tx-datasource> </datasources>
It worked fine before stopping/starting MySQL.
It was the first time I stop/start MySQL since the JBoss installation.
Thanks for your help.
What operating system (and version) are you using? What version of mysql?
If you run the mysql command line utility, can you log into mysql with the user-name and password in you *-ds.xml file and then access the jboss_appserver database?
I have looked for a pb around modifications of MySQL variables.
And I have found that the "skip-networking" parameter has been added.
How was it added ? I suspect some MySQL administrator using and saving, but first without effect since MySQL was not restarted.
Thanks for your replies.