0 Replies Latest reply on May 12, 2006 4:52 AM by Christian Becker

    Deployment Problem - SQL Exception while Deployment

    Christian Becker Newbie

      We´ve running locally a jBPM Server to Test the New Version. The installation Package was "jbpm-starters-kit-3.1.1".
      The Server is running with a MySQL Database.
      Every thing is running fine, but if i try to Deploy any Process i get some errors like these:

      =========================

      Caused by: java.sql.SQLException: Syntax error or access violation message from server: "You have an error in your SQL syntax; check the manual that c
      orresponds to your MySQL server version for the right syntax to use near '1 processdef0_.ID_ as ID1_4_, processdef0_.NAME_ as NAME2_4_, processdef0_.V
      ERSI' at line 1"
      at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2001)
      at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1168)
      at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1279)
      at com.mysql.jdbc.Connection.execSQL(Connection.java:2281)
      at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1634)
      at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:211)
      at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:137)
      at org.hibernate.loader.Loader.getResultSet(Loader.java:1676)
      at org.hibernate.loader.Loader.doQuery(Loader.java:662)
      at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
      at org.hibernate.loader.Loader.doList(Loader.java:2147)
      ... 41 more
      10:51:21,427 ERROR [GraphSession] org.hibernate.exception.SQLGrammarException: could not execute query
      10:51:21,427 INFO [STDOUT] org.jbpm.JbpmException: couldn't find process definition 'beck'

      =========================

      I don´t know why this Error Appears, this error occours even with a Process that perfectly runs on an older version
      Is this a Bug of the new version? if yes, is there already a workaround?