ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mateusz Nowakowski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error
Date Tue, 27 Oct 2009 14:07:59 GMT

    [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770514#action_12770514
] 

Mateusz Nowakowski commented on ODE-686:
----------------------------------------

Yes, one of our in-memory processes have a wait activity, but it works as expected..
Is there any limitation for bpel:wait activity for in-memory processes?

We have only in-memory processes, what are other restrictions for these processes?
There is only "one receive" restriction described on the documentation site.



> 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.


Mime
View raw message