[
https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin....
]
Raúl Raja Martínez commented on JGRP-1345:
------------------------------------------
Bela, I will keep that in mind for next time. Sanne, I know my workaround is MYSQL
specific and I understand you use standard SQL, I thought this issue was only on MYSQL
that's why I commented about the workaround. Any standard MySQL installs on Mac like
mine are potentially suffering the same issue. In any case I think this should be looked
into as this prevents discovery from working and the only way to find out is to have trace
turned on. The app silently fails later when it tries to insert data in tables that do not
exist.
Thanks for looking into it and getting back to me.
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