[
https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769973#action_12769973
]
Rafal Rusin commented on ODE-686:
---------------------------------
Ad. 1
This is possibly a pool configuration problem. I'll look at it.
Ad. 2
Derby supports now in-memory databases
(http://blogs.sun.com/kah/entry/derby_10_5_preview_in).
I'll try to provide a way of configuring it in ServiceMix. This should go
almost straightforward. The only problem seems to be schema creation at
startup.
> 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.
