[
https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770683#action_12770683
]
Rafal Rusin commented on ODE-686:
---------------------------------
As for running fully in memory, you can use following config (substitute
target/test/smx/ode/jpadb with path to db from ode-jbi zip) for EXTERNAL db
connection:
<bean id="odeMCF" class="org.jencks.tranql.DataSourceMCF">
<property name="driverName"
value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="url"
value="jdbc:derby:memory:MyDB;createFrom=target/test/smx/ode/jpadb"/>
<property name="user" value="sa"/>
<property name="password" value=""/>
</bean>
> ODE on Derby cannot recover from out of space error
> ---------------------------------------------------
>
> Key: ODE-686
> URL: https://issues.apache.org/jira/browse/ODE-686
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime, JBI Integration
> Affects Versions: 1.2
> Environment: Linux, Fuse 3.4.0.4+ ODE 1.2 JBI
> Reporter: Mateusz Nowakowski
> Assignee: Rafal Rusin
> Fix For: 1.3.4
>
> Attachments: stacktraces.txt
>
>
> When the free space on disk is running out, ODE fails on SQLs, but when the
> free space on disk increases, ODE cannot recover.
> (attached stack traces)
> PS. All the processes are "in memory", why is database used for saving
> "persistent jobs"?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
