topic Re: Activiti tables creation issue in Alfresco Archive

Activiti tables creation issue

frequentcrasher — Wed, 25 Jan 2012 21:14:22 GMT

Hi,I am trying to use Activiti 5.7 inside of a Spring webapp on Tomcat 6 and Oracle 10g database. When I deploy the webapp, I thought the way it should work is the process engine configuration spring bean will check and see that the tables do not exist in the new user schema and proceed to create th

Re: Activiti tables creation issue

trademak — Thu, 26 Jan 2012 07:35:25 GMT

Hi,

Is there a specific reason why you are using lazy-init="true" ?
When you look in the database, can you see that no tables are created?
Are there any error messages before the log messages you already included?

Best regards,

Re: Activiti tables creation issue

frequentcrasher — Fri, 27 Jan 2012 19:45:04 GMT

Thanks for taking the time to look at my question. I got a chance to download and debug through the source code and here's what I realized I was doing that was slightly different. We were setting up a test environment so we created a second oracle user/schema on the same database to have a second environment.

Here's my interpretation of what's going on so please take it with a grain of salt since I'm no expert at this. When the process engine configuration bean is created by Spring, the app eventually find its way to DbSqlSession.dbSchemaCreate() where there's a call to isEngineTablePresent() followed by a call to getDbVersion(). I think the DbSqlSession object created for the isEngineTablePresent call might be instantiated using the constructor that doesn't pass schema so the app thinks the engine tables exists at this point because the call to fetch database meta data indeed find a table named ACT_RU_EXECUTION from the first user/schema and proceed to query the ACT_GE_PROPERTY table for the schema.version property which bombs. I see a DbSqlSession constructor that takes schema but it was used by something else and I didn't find a property I could set that will pass the schema along to the schema check/create piece.

I created a test user schema and started up the app in debug mode pointing to this test database and updated the schema property of the DbSqlSession object on the fly and everything ran great as a test.

On the lazy-init, I don't think I consciously picked it as a choice. Either I copied it from an example or one of the other developers chose it. Since you pointed it out, I assume it is not the recommeded practice and will look in the documentation to see what it does exactly.

I verified that no database tables are created when it errors out each time (we tried multiple times on a couple different developer's local databases). The errors I pasted in the original post were the first error messages to show up each time.

Re: Activiti tables creation issue

pgadecki — Tue, 15 Jan 2013 10:21:33 GMT

I have noticed the same problem in 5.10, with two user schemas in oracle - first with activiti tables and second with no tables. When trying to start process engine with db config set to use second user schema
method isTablePresent returns true as it was checking for any table in the db.

Is this issue fixed in the current release?

Re: Activiti tables creation issue

frederikherema1 — Tue, 15 Jan 2013 10:58:04 GMT

Did you specify the "databaseSchema" property on the process-engine-configuration?

Re: Activiti tables creation issue

pgadecki — Tue, 15 Jan 2013 12:06:21 GMT

No, but now I used your advice. I don't have direct access to the db user name, but I was able to plug into process engine configuration initialization and managed to get use of patch https://jira.codehaus.org/secure/attachment/58549/ACT-1062.patch from jira issue https://jira.codehaus.org/browse/ACT-1062 so the code looks like this:

this.databaseSchema = this.dataSource.getConnection().getMetaData().getUserName();
this.dbSqlSessionFactory.setDatabaseSchema(this.databaseSchema);

thanks