CMDBuild Forum

CMDBuild/Shark 2.1.8 Importing of RequestForChange.xpdl running endless

Hello there, I have a trouble to connecting cmdbuild and shark. I've just started to evaluate CMDBuild and may be doing something wrong. 

I can't upload the example xpdl file provided with distribution (RequestForChange.xpdl). 

Here is the thing:

1. According to catalina.out shark is up and running, the service is available at http://localhost:8080/cmdbuild-shark-workflow/ (of course it is the one provided with 2.1.8 distribution and it is reporting "AXIS error No service is available at this URL", as it supposedly should do) :

<pre>
Shark will be configured from file /usr/share/tomcat-7/webapps/cmdbuild-shark-server/conf/Shark.conf
environmentType= tomcat
    t= org.objectweb.jotm.Current@57003d5d
        pre configure . . . . . .

Together Workflow Server 4.4-1

SharkEngineManager -> Shark engine is being initialized ...
Shark -> shark engine initialization is finished, it lasted 2 [s]
Shark -> Shark ready and waiting ...
        pre getConnection . . . . . .
        pre commit . . . . . .

</pre>

2. According to shark.log shark is up and running too:

<pre>

2014-03-30 20:22:28,123: SharkEngineManager -> Working with 'org.enhydra.shark.CallbackUtil' implementation of core CallbackUtilities API
2014-03-30 20:22:28,124: SharkEngineManager -> Working with 'org.enhydra.shark.SharkObjectFactoryExt' implementation of core SharkObjectFactory API
2014-03-30 20:22:28,124: SharkEngineManager -> Working with 'org.enhydra.shark.StandardToolActivityHandler' implementation of core ToolAgentManager API
2014-03-30 20:22:28,124: SharkEngineManager -> Working with 'org.enhydra.shark.logging.StandardLoggingManager' implementation of Logging API
2014-03-30 20:22:28,880: StandardAssignmentManager -> Working with 'org.enhydra.shark.usergroup.DODSUserGroupManagerAdmin' implementation of UserGroup API
2014-03-30 20:22:28,954: StandardAssignmentManager -> Working with 'org.enhydra.shark.partmappersistence.DODSParticipantMappingAdmin' implementation of ParticipantMapping API
2014-03-30 20:22:28,954: SharkEngineManager -> Working with 'org.enhydra.shark.assignment.StandardAssignmentManager' implementation of Assignment API
2014-03-30 20:22:28,958: Process Cache configured - max. size is 100
2014-03-30 20:22:28,959: Resource Cache configured - max. size is 100
2014-03-30 20:22:28,959: SharkEngineManager -> Working with 'org.enhydra.shark.caching.LRUCacheMgr' implementation of Caching API
2014-03-30 20:22:29,144: DODSPersistentManager -> persisting String variables into BLOB for sizes greater than 4000
2014-03-30 20:22:29,145: SharkEngineManager -> Working with 'org.enhydra.shark.instancepersistence.DODSSelectivePersistenceManager' implementation of InstancePersistence API
2014-03-30 20:22:29,155: DODSGlobalPersistenceManager -> persisting String data into BLOB for sizes greater than 4000
2014-03-30 20:22:29,155: SharkEngineManager -> Working with 'org.enhydra.shark.globalpersistence.DODSGlobalPersistenceManager' implementation of GlobalPersistence API
2014-03-30 20:22:30,690: SharkEngineManager -> Working with 'org.cmdbuild.workflow.CMDBuildEventAuditManager' implementation of EventAudit API
2014-03-30 20:22:30,776: SharkEngineManager -> Working with 'org.enhydra.shark.repositorypersistence.DODSRepositoryPersistenceManager' implementation of RepositoryPersistence API
2014-03-30 20:22:30,783: SharkEngineManager -> Working with 'org.enhydra.shark.scripting.StandardScriptingManager' implementation of Scripting API
2014-03-30 20:22:30,783: SharkEngineManager -> Working without Security API implementation - SecurityManager is not specified.
2014-03-30 20:22:30,947: StandardToolAgentManager -> Working with 'org.enhydra.shark.appmappersistence.DODSApplicationMappingAdmin' implementation of ApplicationMapPersistence API
2014-03-30 20:22:30,947: SharkEngineManager -> Working with 'org.enhydra.shark.toolagent.StandardToolAgentManager' implementation of ToolAgentManager API
2014-03-30 20:22:30,947: SharkEngineManager -> Working without wfEngineInteroperability API implementation - WfEngineInteroperability implementation is not specified.
2014-03-30 20:22:30,965: SharkUtilities -> synchronizing XPDL cache
</pre>

3. CMDBuild up and running too. The service available at http://localhost:8080/cmdbuild/

4. webapps/cmdbuild-shark-server/conf/Shark.conf has the lines required to integrate with cmdbuild:

<pre>

# CMDBuild connection settings
org.cmdbuild.ws.url=http://localhost:8080/cmdbuild/
org.cmdbuild.ws.username=admin
org.cmdbuild.ws.password=admin

</pre>

Those above are the CMDBuild administrator credentials.

5. In CMDBuild in section for wirkflow configuration i use the URL : http://localhost:8080/cmdbuild-shark-workflow/

6. I doubt i have the credentials right here. I use the the same as above user 'admin' and password 'admin'

 

So right or wrong but i get no response from CMDBuild after I starting to upload the sample  XPDL file. It is running and running and running. I waited for 2 hours then restarted tomcat. Though there is another thing: you have to kill the java process to get cmdbuild down.

 

Any advise here ?

 

 

 

So guys, no any advises? No any clue here ?

 

Previously Paul wrote:

Hello there, I have a trouble to connecting cmdbuild and shark. I've just started to evaluate CMDBuild and may be doing something wrong. 

I can't upload the example xpdl file provided with distribution (RequestForChange.xpdl). 

Here is the thing:

1. According to catalina.out shark is up and running, the service is available at http://localhost:8080/cmdbuild-shark-workflow/ (of course it is the one provided with 2.1.8 distribution and it is reporting "AXIS error No service is available at this URL", as it supposedly should do) :

<pre>
Shark will be configured from file /usr/share/tomcat-7/webapps/cmdbuild-shark-server/conf/Shark.conf
environmentType= tomcat
    t= org.objectweb.jotm.Current@57003d5d
        pre configure . . . . . .

Together Workflow Server 4.4-1

SharkEngineManager -> Shark engine is being initialized ...
Shark -> shark engine initialization is finished, it lasted 2 [s]
Shark -> Shark ready and waiting ...
        pre getConnection . . . . . .
        pre commit . . . . . .

</pre>

2. According to shark.log shark is up and running too:

<pre>

2014-03-30 20:22:28,123: SharkEngineManager -> Working with 'org.enhydra.shark.CallbackUtil' implementation of core CallbackUtilities API
2014-03-30 20:22:28,124: SharkEngineManager -> Working with 'org.enhydra.shark.SharkObjectFactoryExt' implementation of core SharkObjectFactory API
2014-03-30 20:22:28,124: SharkEngineManager -> Working with 'org.enhydra.shark.StandardToolActivityHandler' implementation of core ToolAgentManager API
2014-03-30 20:22:28,124: SharkEngineManager -> Working with 'org.enhydra.shark.logging.StandardLoggingManager' implementation of Logging API
2014-03-30 20:22:28,880: StandardAssignmentManager -> Working with 'org.enhydra.shark.usergroup.DODSUserGroupManagerAdmin' implementation of UserGroup API
2014-03-30 20:22:28,954: StandardAssignmentManager -> Working with 'org.enhydra.shark.partmappersistence.DODSParticipantMappingAdmin' implementation of ParticipantMapping API
2014-03-30 20:22:28,954: SharkEngineManager -> Working with 'org.enhydra.shark.assignment.StandardAssignmentManager' implementation of Assignment API
2014-03-30 20:22:28,958: Process Cache configured - max. size is 100
2014-03-30 20:22:28,959: Resource Cache configured - max. size is 100
2014-03-30 20:22:28,959: SharkEngineManager -> Working with 'org.enhydra.shark.caching.LRUCacheMgr' implementation of Caching API
2014-03-30 20:22:29,144: DODSPersistentManager -> persisting String variables into BLOB for sizes greater than 4000
2014-03-30 20:22:29,145: SharkEngineManager -> Working with 'org.enhydra.shark.instancepersistence.DODSSelectivePersistenceManager' implementation of InstancePersistence API
2014-03-30 20:22:29,155: DODSGlobalPersistenceManager -> persisting String data into BLOB for sizes greater than 4000
2014-03-30 20:22:29,155: SharkEngineManager -> Working with 'org.enhydra.shark.globalpersistence.DODSGlobalPersistenceManager' implementation of GlobalPersistence API
2014-03-30 20:22:30,690: SharkEngineManager -> Working with 'org.cmdbuild.workflow.CMDBuildEventAuditManager' implementation of EventAudit API
2014-03-30 20:22:30,776: SharkEngineManager -> Working with 'org.enhydra.shark.repositorypersistence.DODSRepositoryPersistenceManager' implementation of RepositoryPersistence API
2014-03-30 20:22:30,783: SharkEngineManager -> Working with 'org.enhydra.shark.scripting.StandardScriptingManager' implementation of Scripting API
2014-03-30 20:22:30,783: SharkEngineManager -> Working without Security API implementation - SecurityManager is not specified.
2014-03-30 20:22:30,947: StandardToolAgentManager -> Working with 'org.enhydra.shark.appmappersistence.DODSApplicationMappingAdmin' implementation of ApplicationMapPersistence API
2014-03-30 20:22:30,947: SharkEngineManager -> Working with 'org.enhydra.shark.toolagent.StandardToolAgentManager' implementation of ToolAgentManager API
2014-03-30 20:22:30,947: SharkEngineManager -> Working without wfEngineInteroperability API implementation - WfEngineInteroperability implementation is not specified.
2014-03-30 20:22:30,965: SharkUtilities -> synchronizing XPDL cache
</pre>

3. CMDBuild up and running too. The service available at http://localhost:8080/cmdbuild/

4. webapps/cmdbuild-shark-server/conf/Shark.conf has the lines required to integrate with cmdbuild:

<pre>

# CMDBuild connection settings
org.cmdbuild.ws.url=http://localhost:8080/cmdbuild/
org.cmdbuild.ws.username=admin
org.cmdbuild.ws.password=admin

</pre>

Those above are the CMDBuild administrator credentials.

5. In CMDBuild in section for wirkflow configuration i use the URL : http://localhost:8080/cmdbuild-shark-workflow/

6. I doubt i have the credentials right here. I use the the same as above user 'admin' and password 'admin'

 

So right or wrong but i get no response from CMDBuild after I starting to upload the sample  XPDL file. It is running and running and running. I waited for 2 hours then restarted tomcat. Though there is another thing: you have to kill the java process to get cmdbuild down.

 

Any advise here ?