activiti stop working when refresh datasource with new properties

[shivam-ver]

Hi,

I am facing problem when we refresh the datasource in activiti. 

Initially I set my datasource from properties file on H2 and after server up I show one simple page where I ask for new datasource properties  then refresh our application datasource with new new properties bbut activiti stop working and throwing error as below.

getting exception on  java code as below.

repositoryService.createDeployementQuery().list().

ERROR-Stack

SQLSERVEREXCEPTION: 

Error may exist in org/activiti/db/mapping/entity/deployment.xml

Error involved in  org.activiti.engine.impl.persistence.entity.deploymentEntity.SelectDeploymentByQueryCriteria-inline

setting parameters * from ACT_re_deployment RES order by RES.ID asc LIMT? OFFSET ?

Cause: SQLSERVEREXCEPTION : Incorrect syntax near 'LIMIT'

PLEASE I spend lot of days on this issue.

[jearles]

In your error:

Error involved in  org.activiti.engine.impl.persistence.entity.deploymentEntity.SelectDeploymentByQueryCriteria-inline setting parameters * from ACT_re_deployment RES order by RES.ID asc LIMT? OFFSET ?

The word 'LIMIT' is spelled incorrectly. Could that be a part of the issue? Have you potentially misspelled the word?
Also in that same error, your spelling of 'LIMIT' is follow immediately by a question mark, which I believe is incorrect syntax, as there should be a space between them.

If these aren't the problem, could you please include the entire stacktrace?

-JEarles

[shivam-ver]

Thanks for your reply,

Please find my problem details as attached

[shivam-ver]

thanks for reply.

Please find my problem details as attached snapshot

[jearles]

Shivam,

It appears as thought you're using Microsoft SQL Server - is that correct? Which version of it are you using? I'm not sure if the newer versions support 'LIMIT' - but that hasn't previously been a support clause in the Microsoft SQL server dialect.

If this is custom SQL that you've written, you'll want to change it yourself.
If this is autogenerated SQL by the application, you'll want to take a look at your database configuration and verify that you have your dialect configured properly.

-JEarles