Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Atlassian JIRA by Brian Fox, 2 years ago
Invalid SQL statement or JDBC escape, terminating ''' not found.
via Atlassian JIRA by Brian Fox, 1 year ago
Invalid SQL statement or JDBC escape, terminating ''' not found.
via Stack Overflow by Unknown author, 2 years ago
Invalid SQL statement or JDBC escape, terminating ']' not found.
via Stack Overflow by user3428736
, 1 year ago
Invalid SQL statement or JDBC escape, terminating ']' not found.
via jtds by ickzon
, 1 year ago
Invalid SQL statement or JDBC escape, terminating '}' not found.
java.sql.SQLException: Invalid SQL statement or JDBC escape, terminating ''' not found. at net.sourceforge.jtds.jdbc.SQLParser.parse(SQLParser.java:1155) at net.sourceforge.jtds.jdbc.SQLParser.parse(SQLParser.java:156) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.<init>(JtdsPreparedStatement.java:104) at net.sourceforge.jtds.jdbc.ConnectionJDBC2.prepareStatement(ConnectionJDBC2.java:2221) at net.sourceforge.jtds.jdbc.ConnectionJDBC2.prepareStatement(ConnectionJDBC2.java:2179) at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:185) at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:278) at org.ofbiz.core.entity.jdbc.SQLProcessor.prepareStatement(SQLProcessor.java:327) at org.ofbiz.core.entity.jdbc.SQLProcessor.prepareStatement(SQLProcessor.java:302) at com.atlassian.jira.toolkit.customfield.ParticipantsDAO.getCommenterNames(ParticipantsDAO.java:110) at com.atlassian.jira.toolkit.customfield.ParticipantsCFType.getValueFromIssue(ParticipantsCFType.java:84) at com.atlassian.jira.issue.fields.CustomFieldImpl.getValue(CustomFieldImpl.java:212)