[
https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on JGRP-1345:
---------------------------------------
yes that's the code to initialize the table. But it's not the code writing to it
;)
The error should be logger in
{code}org.jgroups.protocols.JDBC_PING.writeToFile(PingData, String){code}
There's no point in failing if we couldn't initialize the table, as most databases
don't support the _IF NOT EXISTS_ clause, so everyone but the first fill fail. In fact
in most environments the applications are not allowed at all to change the schema, so the
DBA should create the table and define the SQL fragments he wants JGroups to use.. so
_attemptSchemaInitialization_ is really just a temptative to make your life easier, but an
error is not critical at all.
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