|

»

»

[jira] Created: (ODE-686) ODE on Derby cannot recover from out of space error

View: New views

10 Messages — Rating Filter: Alert me

	[jira] Created: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 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 Fix For: 1.3.4 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.
	[jira] Updated: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mateusz Nowakowski updated ODE-686: ----------------------------------- Attachment: stacktraces.txt > 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 > 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.
	[jira] Assigned: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafal Rusin reassigned ODE-686: ------------------------------- Assignee: Rafal Rusin > 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770475#action_12770475 ] Alex Boisvert commented on ODE-686: ----------------------------------- And from the stacktrace, it appears you are using a <bpel:wait> activity which are not supported by in-memory processes. (Granted, it would be better if the engine would report this during deployment/activation). > 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770542#action_12770542 ] Alex Boisvert commented on ODE-686: ----------------------------------- I was under the impression we had decided to not support <bpel:wait> but apparently we do it in a somewhat broken way. If we support it, the schedule created should be in-memory instead of persistent. We should open a separate issue for this. The two dangers of long-running in-memory processes are 1) memory consumption since we don't do hydration/dehydration of in-memory instances and 2) increased exposure to a node failure. Nothing inherently wrong here except that those are important design considerations. > 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770544#action_12770544 ] Alex Boisvert commented on ODE-686: ----------------------------------- Created issue ODE-688 to track the schedule job persistence issue. > 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ 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.
	[jira] Commented: (ODE-686) ODE on Derby cannot recover from out of space error by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/ODE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770962#action_12770962 ] Mateusz Nowakowski commented on ODE-686: ---------------------------------------- Our in-memory processes are very short processes and we don't need hydration/dehydration feature for it. Thanks for the clarification and the example. We need to ask Fuse team to upgrade Derby first. > 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.