Hudson build became unstable: ODE-trunk-jdk6 #149

See http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/149/changes

[jira] Resolved: (ODE-577) No separate threads for ExternalServices replies

[ https://issues.apache.org/jira/browse/ODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Midon resolved ODE-577. -- Resolution: Fixed Fix Version/s: (was: 2.0) The issue is not relevant in trunk. > No separate

[jira] Commented: (ODE-577) No separate threads for ExternalServices replies

[ https://issues.apache.org/jira/browse/ODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699018#action_12699018 ] Alexis Midon commented on ODE-577: -- committed in 1.X r765029 > No separate threads for Exter

[jira] Work started: (ODE-577) No separate threads for ExternalServices replies

[ https://issues.apache.org/jira/browse/ODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ODE-577 started by Alexis Midon. > No separate threads for ExternalServices replies > > > Key: ODE-5

[jira] Issue Comment Edited: (ODE-578) Better error reporting for WS clients

[ https://issues.apache.org/jira/browse/ODE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698989#action_12698989 ] Alexis Midon edited comment on ODE-578 at 4/14/09 5:07 PM: --- Now, in

[jira] Issue Comment Edited: (ODE-578) Better error reporting for WS clients

[ https://issues.apache.org/jira/browse/ODE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698989#action_12698989 ] Alexis Midon edited comment on ODE-578 at 4/14/09 5:00 PM: --- Now, in

[jira] Commented: (ODE-578) Better error reporting for WS clients

[ https://issues.apache.org/jira/browse/ODE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698990#action_12698990 ] Alexis Midon commented on ODE-578: -- committed in 1.X r765012 > Better error reporting for WS

[jira] Commented: (ODE-578) Better error reporting for WS clients

[ https://issues.apache.org/jira/browse/ODE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698989#action_12698989 ] Alexis Midon commented on ODE-578: -- Now, in case of failure, the details passed to MessageExc

[jira] Resolved: (ODE-575) oAssign$Literal seems to consume an excessive volume of memory

[ https://issues.apache.org/jira/browse/ODE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Sankarachary resolved ODE-575. --- Resolution: Fixed Ciaran, I have applied the patch based on your proposal at revision 76

[jira] Resolved: (ODE-574) Memory leak when Un-deploying processes that contain XSL stylesheets

[ https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Sankarachary resolved ODE-574. --- Resolution: Fixed The patch from 2009-04-08 04:07 AM has been applied at revision 765005

[jira] Updated: (ODE-236) Add support for from-spec inside a variable declaration to initialize it. . This is a standard BPEL 2.0 construct

[ https://issues.apache.org/jira/browse/ODE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madars Vitolins updated ODE-236: Attachment: inline-var-init-trunk-rev-764976-20090415.patch Hello Oders! I have attached patch for in

[jira] Commented: (ODE-575) oAssign$Literal seems to consume an excessive volume of memory

[ https://issues.apache.org/jira/browse/ODE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698960#action_12698960 ] Ciaran Jessup commented on ODE-575: --- I agree totally, the only reason I didn't do this was b

[jira] Commented: (ODE-575) oAssign$Literal seems to consume an excessive volume of memory

[ https://issues.apache.org/jira/browse/ODE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698958#action_12698958 ] Karthick Sankarachary commented on ODE-575: --- Ciaran, Thanks for bringing this issue

[jira] Commented: (ODE-573) Reuse And Reduce Process Memory

[ https://issues.apache.org/jira/browse/ODE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698957#action_12698957 ] Ciaran Jessup commented on ODE-573: --- This patch looks excellent, my profiler had flagged up

[jira] Updated: (ODE-575) oAssign$Literal seems to consume an excessive volume of memory

[ https://issues.apache.org/jira/browse/ODE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Sankarachary updated ODE-575: -- Attachment: reduce-xml-literal-size.patch > oAssign$Literal seems to consume an excessive

[jira] Commented: (ODE-573) Reuse And Reduce Process Memory

[ https://issues.apache.org/jira/browse/ODE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698954#action_12698954 ] Karthick Sankarachary commented on ODE-573: --- There are a number of immutable objects

[jira] Updated: (ODE-573) Reuse And Reduce Process Memory

[ https://issues.apache.org/jira/browse/ODE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Sankarachary updated ODE-573: -- Attachment: interning-mechanism-for-processes.patch > Reuse And Reduce Process Memory > --

Output of investigation into memory usage on BPEL Redeployments

Hi Folks, I think I've completed my investigation into memory leaks when doing re-deployments of in-memory processes. At the start of this process I was leaking several tens, to hundreds of megabytes (depending on the workflow size,) I was unable to deploy the largest of my flows and couldn't re-

[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked after un-deployment.

[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ciaran Jessup updated ODE-580: -- Description: When un-deploying a DeploymentUnitDir object instance is kept in memory, this is a direct c

[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked after un-deployment.

[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ciaran Jessup updated ODE-580: -- Attachment: FixForAxisBug.patch This patch uses reflection to properly clear down the endpoints hashmap wh

[jira] Created: (ODE-580) DeploymentUnitDir object gets leaked after un-deployment.

DeploymentUnitDir object gets leaked after un-deployment. - Key: ODE-580 URL: https://issues.apache.org/jira/browse/ODE-580 Project: ODE Issue Type: Bug Environment: na

[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked after un-deployment.

[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ciaran Jessup updated ODE-580: -- Priority: Minor (was: Major) > DeploymentUnitDir object gets leaked after un-deployment. > --

Concurrent execution of extension activities (RE: Problem with flow and extension activities)

Hi Tammo, > -Original Message- > From: Tammo van Lessen [mailto:tvanles...@gmail.com] > Sent: Thursday, April 02, 2009 4:17 PM > Subject: Re: AW: Problem with flow and extension activities > > That's true. If you need a concurrent execution of extension activities > you'd need to implement

[jira] Created: (ODE-579) Ode 2.0 beta problem while using pathner service - corresponding method not implemented

Ode 2.0 beta problem while using pathner service - corresponding method not implemented --- Key: ODE-579 URL: https://issues.apache.org/jira/browse/ODE-579 Project: O

[jira] Commented: (ODE-561) Process hydration/dehydration improvements to better control memory footprint

[ https://issues.apache.org/jira/browse/ODE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698697#action_12698697 ] Jim Swainston commented on ODE-561: --- Thanks Karthick, Have been away this last week, but wi