WildFly 8 can't connect to MySQL after restart - mysql

My enviroment has the following servers: WildFly 8.0 and MySQL 5.5.32.
The database server is stopped and started every night for backup procedures. After that, I'm getting the following error in my WildFly Log:
09:52:38,136 ERROR [stderr] (default task-11) gate.error.APPLError: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
I have five configured datasources between these servers, but only one has this problem.
I'm not using JPA.

Related

Can't connect mysql workbench to mysql even though I can connect normally through the terminal

I recently installed mysql and mysql workbench on my manjaro machine. As for mysql itself, it works perfectly. I can start the service, connect using terminal and do my usual work without any trouble.
The problem is that mysql workbench can't, for the life of me, connect to mysql. Always returning the same your connection attempt failed for user 'root' to the mysql server at 127.0.0.1:3306: SSL connection error: SSL is required but the server doesn't support it error.
Even when I try the Rescan servers option on mysql workbench it returns No servers were found.

MySQL server has gone away and can't connect to local MySQL server from Rails application

I have a Rails application which has a huge database. It uses the gem mysql2 to connect to MySQL. It was working fine until yesterday. Today when I started the application I am getting these errors while trying to connect to that specific database.
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR:
Can't connect to the server
Mysql connection is established to other databases well but not to this one database. It was perfectly fine even with this database until yesterday. Why did it change suddenly?
I also checked and made changes as per the answer in this link:
MySQL error 2006: mysql server has gone away
but I am still getting the same error. How can I rectify this error?

Liquibase can't connect to the SQL Server [duplicate]

This question already has answers here:
Connect Java to a MySQL database
(14 answers)
Closed 5 years ago.
I am fairly new to liquibase and try to set it up on my own computer, running Windows 7 with a local MySQL Server. I have installed the JDBC driver (4.2), opened the TCP/IP Port 3306 on my Firewall and the Server, installed liquibase and added it as a PATH in the environment variables.
As a first command i tried using this:
C:\Users\Marius>H:\Liquibase\Liquibase \
--driver=com.microsoft.sqlserver.jdbc.SQLServerDriver \
--classpath="C:\\Program Files\\Microsoft JDBC Driver 6.2 for SQL Server\\sqljdbc_6.2\\enu\\mssql-jdbc-6.2.2.jre7.jar" \
--url="jdbc:sqlserver://localhost:3306; databaseName=Test" \
--changeLogFile="H:\Liquibase\dbchangelog.xml" \
--username=liquibase \
--password=liquibase \
Update
But when executing I only get:
Unexpected error running Liquibase:
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection
to the host localhost, port 3306 has failed. Error: "Connection
refused: connect. Verify the connection properties. Make sure that an
instance of SQL Server is running on the host and accepting TCP/IP
connections at the port. Make sure that TCP connections to the port
are not blocked by a firewall.".
The Server is definitely running since I am able to connect to it with telnet, mySQLWorkbench and several other tools.
When running the command with --url="jdbc:sqlserver:localhost:3306; databaseName=Test", I get a different error code.
Unexpected error running Liquibase:
liquibase.exception.DatabaseException: Connection could not be created
to jdbc:sqlserver:localhost:3306; databaseName=Test with driver
com.microsoft.sqlserver.jdbc.SQLServerDriver. Possibly the wrong
driver for the given database URL
I tried this again on another computer with a SQL Server 2017, a different JDBC driver (6.0 and 6.2) and Windows 10 as the OS.
Deactivating the Firewall doesn't do anything, neither does a clean install of everything.
Any help is appreciated.
MySQL is a different product to Microsoft SQL Server. Given you have said you can connect using MySQL workbench, this is probably the product you have installed.
Instead of trying to connect to the non-existent Microsoft SQL Server, try using a MySQL driver instead.

MySQL Workbench: Unable to Connect to Table

I am working on a MySQL database having around 12 tables and it is on remote server. The connection is established via SSH. I have setup the client with MySQL Workbench and SqlYog. The connections are setup properly and database operations are getting performed well, except for one table. Whenever I am trying to access that table in workbench by directly clicking on the icon or by writing query, it is saying-
Error Code: 2013 Lost connection to MySQL server at
'waiting for initial communication packet', system error: 10060
But the same table can be accessed from SqlYog. This is something become really messy. How can this problem be sort out?
Info:
MySQL v5.6
MySQL Workbench v6.3.4
If you are working on MAC/Linux then
check if MYSQL is UP by using following
ps ax | grep sql
if it is down, try to boot is manually, using following if its linux
service mysql restart
if its mac and you have macport installed, use following
sudo port load mysql56-server

com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Unknown command

I'm trying to create datasource for connection pooling mysql database in Websphere Application Server.
I've set the JDBC Provider, I set the
Implementation class name : com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
my mysql driver version is 5.1.6.
but I got this error while I try to connect the datasource:
The test connection operation failed for data source btn_itb_ds on server server1 at node qnode with the following exception: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Unknown command. View JVM logs for further details.
I have read this http://bugs.mysql.com/bug.php?id=38388 trouble shooting. But they just suggest to upgrade mysql driver version 5.1.X and I have do that. but I've got the same error.