topic Re: org.activiti.engine.impl.interceptor.CommandContext close in Alfresco Archive

org.activiti.engine.impl.interceptor.CommandContext close

sonam — Thu, 09 Oct 2014 16:03:31 GMT

I am working on BookOrderTest.java with a connection to localhost database. The following is my codeublic class BookOrderTest { private Logger logger = LoggerFactory.getLogger(getClass()); @Test public void startBookOrder() { logger.info("creating processEngine"); ProcessEngi

Re: org.activiti.engine.impl.interceptor.CommandContext close

trademak — Fri, 10 Oct 2014 09:05:17 GMT

The error already shows the solution:

### Error opening session. Cause: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-132]

Best regards,

Re: org.activiti.engine.impl.interceptor.CommandContext close

sonam — Fri, 10 Oct 2014 15:54:31 GMT

Yes, I have tried the solution as stated in the error by appending it to the jdbc-url (setJdbcUrl("jdbc:h2:tcp://localhost/activiti;DB_CLOSE_ON_EXIT=FALSE")) . However, I still see the similar error with the following stacktrace:

Oct 10, 2014 9:36:01 AM org.activiti.engine.impl.interceptor.CommandContext close
SEVERE: Error while closing command context
org.apache.ibatis.exceptions.PersistenceException:
### Error opening session. Cause: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-132]
### The error may exist in org/activiti/db/mapping/entity/EventSubscription.xml
### The error occurred while processing mapper_resultMap[compensateResultMap]
### Cause: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-132]
at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:8)
at org.apache.ibatis.session.defaults.DefaultSqlSessionFactory.openSessionFromDataSource(DefaultSqlSessionFactory.java:83)

thanks

-Sonam

Re: org.activiti.engine.impl.interceptor.CommandContext close

jbarrez — Fri, 17 Oct 2014 10:15:23 GMT

See http://www.h2database.com/html/features.html :

By default, closing the last connection to a database closes the database. For an in-memory database, this means the content is lost. To keep the database open, add ;DB_CLOSE_DELAY=-1 to the database URL. To keep the content of an in-memory database as long as the virtual machine is alive, use jdbc:h2:mem:test;DB_CLOSE_DELAY=-1.

Re: org.activiti.engine.impl.interceptor.CommandContext close

sonam — Fri, 17 Oct 2014 18:34:37 GMT

I am connecting to a standalone database not a in-memory one. I am not able to connect to a standalone database in my test case.

Re: org.activiti.engine.impl.interceptor.CommandContext close

jbarrez — Mon, 20 Oct 2014 09:15:36 GMT

hmm ok, sorry didn't read that bit.

So, are your sure the H2 standalone is running? Can you connect to it with the H2 webap tool?

Which H2 version are you using? More recent versions of H2 have a different url (see https://github.com/Activiti/Activiti/commit/5f6cee1b55ac6e8a0ce16b7698e9bc19297a73cc)

Re: org.activiti.engine.impl.interceptor.CommandContext close

sonam — Mon, 20 Oct 2014 16:03:40 GMT

Yes, my H2 Console webapp requires "jdbc:h2:tcp://localhost/~/activiti" which is as same as in the GitHub file. I still run into the same error. When I log-in to the H2 Console I see tables such as "CATALOGS, COLLATIONS,.." and so on. Do I need to manually run some external command for database setup?

I have also tried to switch within the Activiti-explorer weabpp to a standalone database and it runs into error too. For the activitii-explorer webapp I see the following:

Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Connection is broken: "unexpected status 16777216" [90067-170])
        at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
        at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)

I can start a separate thread for the activiti-explorer webapp if you want.

thanks
-Sonam
-Sonam

Re: org.activiti.engine.impl.interceptor.CommandContext close

jbarrez — Tue, 21 Oct 2014 07:21:00 GMT

If you don't see the Activiti tables in the H2 web console, then something has gone wrong.

How do you boot up your H2? Should just starting the H2 using the jar.

After that, you need to change the jdbc url in the config of Explorer to use that database.

The exception you get does point to the fact it can't reach the database, either because the db isnt up and running or if the url is wrong.

Re: org.activiti.engine.impl.interceptor.CommandContext close

sonam — Tue, 21 Oct 2014 16:45:21 GMT

I downloaded another copy of H2 (Version 1.3.176 (2014-04-05), Last Stable) and it worked. I had H2 Version 1.4.182 (2014-10-17), Beta which does not work with current Activiti 5.16.3.

-thanks

Re: org.activiti.engine.impl.interceptor.CommandContext close

jbarrez — Wed, 22 Oct 2014 11:06:48 GMT

Hmm odd. We'll double check it in our QA

Re: org.activiti.engine.impl.interceptor.CommandContext close

joanna — Mon, 09 Feb 2015 22:25:57 GMT

Hi, I had the same problem and indeed the version of H2 does matter. I installed the latest non-stable version initially and after unistalling it and installing the 1.3.176 the connection was finally established. Many thanks for help