[ https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1345: --------------------------- Assignee: Sanne Grinovero (was: Bela Ban) Fix Version/s: 2.12.2 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on JGRP-1345: --------------------------------------- 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin.... ] Sanne Grinovero closed JGRP-1345. --------------------------------- Resolution: Rejected As explained in the comments, it's not a bug but using a wrong database configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin.... ] Raúl Raja Martínez commented on JGRP-1345: ------------------------------------------ I agree with you, I think your SQL is correct, just pointing out that it may be a common problem for many people. Thanks for updating the docs. As for the code in 2.12.0.Final this is the code for initializing the table. protected void attemptSchemaInitialization() { if (stringIsEmpty(initialize_sql)) { log.info("Table creation step skipped: initialize_sql property is missing"); return; } Connection connection = getConnection(); if (connection != null) { try { try { PreparedStatement preparedStatement = connection.prepareStatement(initialize_sql); preparedStatement.execute(); log.info("Table created for JDBC_PING Discovery Protocol"); } catch (SQLException e) { if (log.isDebugEnabled()) { log.debug("Could not execute initialize_sql statement; not necessarily an error.", e); } else { //avoid printing out the stacktrace log.info("Could not execute initialize_sql statement; not necessarily an error. Set to debug logging level for details."); } } } finally { try { connection.close(); } catch (SQLException e) { log.error("Error closing connection", e); } } } } The catch statement does not print to error so the error is not apparent unless you have debug turned on. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira