[jboss-jira] [JBoss JIRA] Issue Comment Edited: (JGRP-1345) JDBC_PING fails to initialize table in mysql
[
https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin....
]
Sanne Grinovero edited comment on JGRP-1345 at 7/14/11 4:22 AM:
----------------------------------------------------------------
I've updated this with your settings: http://community.jboss.org/wiki/JDBCPING
And I'm going to mark this as "won't solve" as it's not a bug, still
I agree it could be easier to get started. If you have suggestions about how to improve
user experience with this I'll be glad to hear about it; we could make a custom
extension "MYSQL_PING" which hardcodes all what's needed for MySQL, or have
an ENUM like parameter which selects SQL statements among a set of tested configurations.
was (Author: sannegrinovero):
I've updated this with your settings: http://community.jboss.org/wiki/JDBCPING
And I'm going to mark this as "won't solve", still if you have
suggestions about how to improve user experience with this I'll be glad to hear about
it; we could make a custom extension "MYSQL_PING" which hardcodes all what's
needed for MySQL, or have an ENUM like parameter which selects SQL statements among a set
of tested configurations.
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