|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Isn't this log message an indicator that JdbcCoordinatorImpl's HashMap "xref" may be retaining ResultSets and Statements which should have been removed (ie a memory leak)? I think this log message does deserve to be a warning, but it might be better to log it only once per session. If I am correct about the memory leak, the wording of the message should probably be more emphatic and more helpful too!
I encountered this warning when using a JDBC wrapper which returned unwrapped Statements from ResultSet.getStatement(), even though the ResultSet was created via a wrapped Statement. The fix was for the JDBC wrapper to ensure ResultSet.getStatement() returns the wrapped Statement. Without the warning message, I wouldn't have known there was a problem until much later. See http://stackoverflow.com/a/17480927/14379