CMDBuild Forum

Unknown SQLException

Old Versions
#1

I've recently setup openMAINT on one of our computers for eval., following the Technical manual instructions but I am unable to get the workflow server running correctly. When I start the program I receive error messages stating that several classes are non found. In the administration module, when I open the processes tree, errors pop up stating "ERROR: relation "shkresourcestable" does not exist". I know for a fact that it does exist in my Postgres database. I have enabled workflow modified the appropriate config files and set the appropriate passwords for the openMAINT and shark. Please advise. I have included partial text from the error message below.

I'm running on Windows 7, Tomcat 6, Postgres 9.4

------------------------------------------------------------------------------------------------------------------------

Call: services/json/workflow/xpdlversions
------------------------------------------
Error: org.cmdbuild.workflow.CMWorkflowException: org.enhydra.shark.api.internal.instancepersistence.PersistenceException: Unknown SQLException: (:ERROR: relation "shkresourcestable" does not exist
  Position: 33)
 at org.cmdbuild.workflow.service.TransactedSharkService$TransactedExecutor.initAndConnect(TransactedSharkService.java:49)
 at org.cmdbuild.workflow.service.TransactedSharkService$TransactedExecutor.execute(TransactedSharkService.java:23)
 at org.cmdbuild.workflow.service.TransactedSharkService.downloadAllPackages(TransactedSharkService.java:127)
 at org.cmdbuild.workflow.xpdl.CachedProcessDefinitionStore$LazyClassNameToPackageInfoMap.fetchProcessDefinitions(CachedProcessDefinitionStore.java:119)
 at org.cmdbuild.workflow.xpdl.CachedProcessDefinitionStore$LazyClassNameToPackageInfoMap.checkLoaded(CachedProcessDefinitionStore.java:111)
 at org.cmdbuild.workflow.xpdl.CachedProcessDefinitionStore$LazyClassNameToPackageInfoMap.getPackageInfoByClass(CachedProcessDefinitionStore.java:98)
 at org.cmdbuild.workflow.xpdl.CachedProcessDefinitionStore.getPackageId(CachedProcessDefinitionStore.java:209)
 at org.cmdbuild.workflow.xpdl.CachedProcessDefinitionStore.getPackageVersions(CachedProcessDefinitionStore.java:204)
 at org.cmdbuild.workflow.xpdl.AbstractProcessDefinitionManager.getVersions(AbstractProcessDefinitionManager.java:37)
 at org.cmdbuild.workflow.ProcessClassImpl.getDefinitionVersions(ProcessClassImpl.java:167)
 at org.cmdbuild........

 

#2
I suggest you take a look at CMDBuild Technical Manual.
CMDBuild Team
#3

Previously Tecnoteca wrote:

I suggest you take a look at CMDBuild Technical Manual.
CMDBuild Team

 

I found the solution to my problem. This may help others.

When I set up the shark context.xml file in the shark/meta-inf folder, I pointed it to the correct database but I also changed the username and password from shark to what I knew as the Superuser username and password for my Postgres database. I should have left them both as shark.