[
https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on JGRP-1345:
---------------------------------------
Hi Raul, I can't fix MySQL's default configuration, so since the default SQL
fragment must be standard I see no way out other than having people need to read the
error, find the documentation and fix their configuration.
{quote}The app silently fails later when it tries to insert data in tables that do not
exist.{quote}
That is very bad!
I'm checking the JDBC_PING code, if it fails to write this is what should be
executed:
{code}log.error("Error updating JDBC_PING table", e);{code}
Don't you have this error in your log?
I'd also remind you that having a MySQL not configured for InnoDB and not using utf8
as char sets has several consequences on your Hibernate application too, you might not
have noticed yet but it's generally considered a totally broken configuration...
JDBC_PING fails to initialize table in mysql
--------------------------------------------
Key: JGRP-1345
URL:
https://issues.jboss.org/browse/JGRP-1345
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12
Reporter: Raúl Raja Martínez
Assignee: Sanne Grinovero
Fix For: 2.12.2, 3.0
JDBC_PING fails to initialize DB table for discover when executing the following SQL:
CREATE TABLE JGROUPSPING (own_addr varchar(200) NOT NULL, cluster_name varchar(200) NOT
NULL, ping_data varbinary(5000) DEFAULT NULL, PRIMARY KEY (own_addr, cluster_name) )
The statement results in "Specified key was too long; max key length is 1000
bytes"
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira