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 ejbca by enchufe
, 2 years ago
Table already exists: JMS_MESSAGES in statement [CREATE CACHED TABLE JMS_MESSAGES]
via ejbca by zjl6
, 2 years ago
Table already exists: JMS\_MESSAGES in statement \[CREATE CACHED TABLE JMS\_MESSAGES\]
via Coderanch by John Kimathi, 1 year ago
Table already exists: JMS_MESSAGES in statement [CREATE CACHED TABLE JMS_MESSAGES]
via Coderanch by Liz Costello, 1 year ago
Table already exists: JMS_TRANSACTIONS in statement [CREATE CACHED TABLE JMS_TRANSACTIONS]
via Stack Overflow by LeoLozes
, 2 years ago
Wrong data type: BLOB in statement [CREATE TABLE TSHT_SALEPLAN ( SALEPLANCODE INTEGER, VENDORCODE VARCHAR(10), HOTELCODE INTEGER, SALEPLAN BLOB]
java.sql.SQLException: Table already exists: JMS_MESSAGES in statement [CREATE CACHED TABLE JMS_MESSAGES] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:95)