# Is it possible to disable the use of a database for the modeler? **URL:** \ **Category:** Flowable Engine\ **Created:** [November 14, 2017, 10:45am UTC](https://forum.flowable.org/t/is-it-possible-to-disable-the-use-of-a-database-for-the-modeler/1193 "2017-11-14T10:45:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jhbu](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jhbu](https://forum.flowable.org/u/jhbu)\ **Post date:** [November 14, 2017, 10:45am UTC](https://forum.flowable.org/t/is-it-possible-to-disable-the-use-of-a-database-for-the-modeler/1193/1 "2017-11-14T10:45:00Z")
Hello everyone, I am tasked to integrate the Flowable modeler into an existing architecture. We only need the modeler and the finished modeled processes will be stored in a temporary directory. Therefore I do not need a database to begin with. So I configured the modeler and the sub-modules for this task. But after trying to deploy the modeler-app, the app is trying to set up a database. Is there a way to disable the start of this? Because I get the following log message and the service is not deployed: 2017-11-14 10:29:16,851 WARN [org.jboss.modules] Failed to define class org.h2.table.RangeTable in Module “deployment.flowable-ui-modeler-app-6.2.1-SNAPSHOT.war:main” from Service Module Loader: java.lang.OutOfMemoryError: Metaspace at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.8.0\_131] at java.lang.ClassLoader.defineClass(ClassLoader.java:763) [rt.jar:1.8.0\_131] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:358) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:78) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:605) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] at org.h2.engine.DbObjectBase.getSQL(DbObjectBase.java:104) [h2-1.4.196.jar:1.4.196] at org.h2.schema.SchemaObjectBase.getSQL(SchemaObjectBase.java:39) [h2-1.4.196.jar:1.4.196] at org.h2.index.BaseIndex.getCreateSQL(BaseIndex.java:417) [h2-1.4.196.jar:1.4.196] at org.h2.mvstore.db.MVTable.addIndex(MVTable.java:511) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Database.open(Database.java:748) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Database.openDatabase(Database.java:276) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Database.(Database.java:270) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Engine.openSession(Engine.java:64) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Engine.openSession(Engine.java:176) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Engine.createSession(Engine.java:137) [h2-1.4.196.jar:1.4.196] at org.h2.engine.Engine.createSession(Engine.java:27) [h2-1.4.196.jar:1.4.196] at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354) [h2-1.4.196.jar:1.4.196] at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:116) [h2-1.4.196.jar:1.4.196] at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:100) [h2-1.4.196.jar:1.4.196] at org.h2.Driver.connect(Driver.java:69) [h2-1.4.196.jar:1.4.196] at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175) [c3p0-0.9.5.2.jar:0.9.5.2] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220) [c3p0-0.9.5.2.jar:0.9.5.2] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206) [c3p0-0.9.5.2.jar:0.9.5.2] at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203) [c3p0-0.9.5.2.jar:0.9.5.2] at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1138) [c3p0-0.9.5.2.jar:0.9.5.2] ---
**Author:** ![PHH](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/phh/32/94_2.png) [@PHH](https://forum.flowable.org/u/PHH)\ **Post date:** [November 14, 2017, 10:51am UTC](https://forum.flowable.org/t/is-it-possible-to-disable-the-use-of-a-database-for-the-modeler/1193/2 "2017-11-14T10:51:35Z")
Hi, The DB is used to hold the state of the model as it is designed (potentially over multiple sessions), so a DB is needed, even if it isn’t used for the final model deployment. Once a model is ready for deployment, there’s APIs you can use to export it as BPMN XML, so you can customize how it is handled from there. Cheers Paul.