Another + 1 (4x performance improvement over 1.3.4 for us)
-cj
On Wed, Feb 2, 2011 at 11:17 AM, Nowakowski, Mateusz
wrote:
> We've tested the ODE 1.3.5 RC2 as well and it went smoothly.
> So +1
>
> --
> Regards,
> Mateusz Nowakowski
>
>
> -Original Message-
> From: Jeff Yu [mailto:jeff.yu
quite quick
~10 minutes, but most of the time need to rake clean, then rake package.
My CPU is fully max'd out on the ruby process (not the javac process!). Is
this normal? (Never really used rake/buildr before)
--
- Ciaran
On Tue, May 27, 2008 at 10:51 PM, Matthieu Riou <[EMAIL PROTECTED]>
wrote:
> On Tue, May 27, 2008 at 2:41 PM, Ciaran <[EMAIL PROTECTED]> wrote:
>
> > Hi All,
> > Am I doing something badly wrong, the ODE build times are prohibitively
> bad
> > for me at th
ght be worth putitng that on the
'building ODE' page ( I tried to edit it, but without a login it appears not
to be editable :) ) in case others come this way later !:)
- Ciaran
Fwiw that problem has existed in trunk head for the last couple of days,
since the global package rename, it seems to compile ok from the command
line, but shows errors in eclipse, ;)
- ciaran
On Wed, May 28, 2008 at 8:58 AM, Nowakowski, Mateusz <
[EMAIL PROTECTED]> wrote:
> > There
namespace of the 'from' variable, rather than previously where it left the
namespace of the root element alone. I hope this makes sense :)
--
- Ciaran
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2336
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2217
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2221
- ciaran
On Fri, Jun 6, 2008 at 9:15 PM, Tammo van Lessen <[EMAIL PROTECTED]>
wrote:
> Hi,
&g
On Fri, Jun 6, 2008 at 10:06 PM, Matthieu Riou <[EMAIL PROTECTED]>
wrote:
> Jaxen is fairly safe. Did you give Xalan a try? Usually Xalan an Xerces
> have
> to hold each other hand in hand to work nicely... until you run in an
> environment that has a different Xerces version that is.
I've given
On Fri, Jun 6, 2008 at 10:29 PM, Matthieu Riou <[EMAIL PROTECTED]>
wrote:
> On Fri, Jun 6, 2008 at 2:09 PM, Ciaran <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Jun 6, 2008 at 10:06 PM, Matthieu Riou <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Jaxen is f
+1 for 1.2 now :)
- ciaran.
On Wed, Jun 25, 2008 at 5:53 PM, Alex Boisvert <[EMAIL PROTECTED]> wrote:
> I'd go for 1.2 now, and plan to do a minor release within a few weeks.
>
> alex
>
>
> On Wed, Jun 25, 2008 at 9:16 AM, Matthieu Riou <[EMAIL PROTECTED]>
>
ces/1.2/apache-ode-sources-1.2.zip>
> <
> http://people.apache.org/%7Emriou/ode-1.2/org/apache/ode/apache-ode-sources/1.2/apache-ode-sources-1.2.zip
> >
> > <
> >
> http://people.apache.org/%7Emriou/ode-1.2/org/apache/ode/apache-ode-sources/1.2/apache-ode-sources-1.2.zip
> > >
> > > <
> > >
> >
> http://people.apache.org/%7Emriou/ode-1.2/org/apache/ode/apache-ode-sources/1.2/apache-ode-sources-1.2.zip
> > > >
> > >
> > > Please cast your votes to approve (or not) this release. Here's my +1.
> > >
> > > Cheers,
> > > Matthieu
> > >
> >
>
--
- Ciaran
On Mon, Jul 7, 2008 at 6:35 PM, Matthieu Riou <[EMAIL PROTECTED]>
wrote:
> Hi guys,
>
> Following up on our 1.2, I think it'd be nice to post a release
> announcement
> here and there (and on [EMAIL PROTECTED] first of all). Here is what I
> came up with:
>
> http://cwiki.apache.org/confluence/dis
On Mon, Feb 9, 2009 at 5:09 PM, Matthieu Riou wrote:
> Hi ODEers,
>
> I've cut two potential releases of ODE: 1.3 from the 1.x branch and
> 2.0-beta1 from the trunk. Please have a look, try them and let me know if
> you see anything wrong. If it looks good enough, I'll start votes in a
> couple of
> FYI there are several issues that are currently affecting us, in order of
> least important first
> i) The shipped eclipse .classpath files refer to invalid project names (
> can get a patch for this easily enough )
> ii) The default .war file thats created doesn't have an empty 'processes'
> fo
On Wed, Feb 18, 2009 at 7:00 PM, Alex Boisvert wrote:
> On Wed, Feb 18, 2009 at 10:50 AM, Ciaran wrote:
>
> > > FYI there are several issues that are currently affecting us, in order
> of
> > > least important first
> > > i) The shipped eclipse .classpath
On Thu, Feb 19, 2009 at 4:54 PM, Assaf Arkin wrote:
> On Thu, Feb 19, 2009 at 8:43 AM, Alex Boisvert
> wrote:
>
> > The confusion comes from the fact that we pseudo-released 1.3. It should
> > have been a RC1.
> >
> > I don't think it's a good idea to use version number without qualifiers
> if
>
> > the
>> > > answer is 1.3, which 1.3 does that mean? Version numbers are cheap.
>> > >
>> > > I remember we had a similar discussion some time ago on this ML about
>> 1.2
>> > > or 1.1, we re-released the same version but the consensus back then
>> was
>> > that
>> > > it was "wrong" :)
>> > >
Matthie
> >
> >
> >>
> >> Assaf
> >>
> >> [1] <
> http://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate
> >
> >>
> http://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate
> >>
On Mon, Feb 23, 2009 at 7:09 PM, Matthieu Riou wrote:
> A quick update: I'm preparing to release 2.0-beta1. For 1.3.1 I'll wait a
> bit until we completely solve the deployment service WSDL issue (it's
> breaking some test cases at this point and responses might change).
>
> Cheers,
> Matthieu
Hm
On Tue, Feb 24, 2009 at 2:47 AM, Alexis Midon wrote:
> from the top level directory of ODE, you can do:
> buildr ode:axis2-war:test
thank you :)
- Cj.
>
>
>
> Alexis
>
>
> On Mon, Feb 23, 2009 at 1:23 PM, Ciaran wrote:
>
> > On Mon, Feb 23, 2009
Fwiw it still doesn't work for us under load :( Still looks like race-issues
in axis web service calls, and we're still seeing memory issues when
un/re-deploying :( We've been unable to produce a test-case of either
issues yet either .
- Cj.
On Mon, Mar 9, 2009 at 2:27 PM, Matthieu Riou wrote:
On Thu, Mar 12, 2009 at 7:16 PM, phan huy wrote:
> Hi Gero,
>
> As I introduced in the "Hello Email", I'm going to participate in GSoC 2009
> with the "Web-based BPEL debugger for Apache ODE" project. So, I have
> something to say about your suggestion.
>
> First, I tried Oryx and found it's a ex
On Thu, Mar 12, 2009 at 7:51 PM, Alex Boisvert wrote:
> On Thu, Mar 12, 2009 at 12:39 PM, Ciaran wrote:
>
> > I don't believe that EXTJS' license is compatible with the existing ODE
> > licenses? Would this not cause
> > you some issues ?
>
>
> It de
Hi Folk,
I've compiled (cleanly I believe, although having spoken to others, I'll
check again in the morning when at the keyboard) the SVN HEAD of the 1.xx
branch, and on deployment of ODE I'm currently seeing the following
exception trace:
DEBUG - GeronimoLog.debug(66) | Loading properties
WARN -
lated to the xml beans generated code then
> it's
> > almost certain that you didn't do a clean.
> >
> >
> > On 3/16/09 3:41 PM, "Ciaran" wrote:
> >
> > Hi Folk,
> > I've compiled (cleanly I believe, although having spoken
Hiyah, I've heard good things about your progress on the CBP memory
footprints, the memory usage of the workflows for us is a current concern
and I'm interested in any progress that you've managed to make so far ?
I hope you don't mind, but because the memory was looking to be an issue to
me, I di
On Mon, Mar 30, 2009 at 10:38 PM, Karthick Sankarachary <
sankarach...@intalio.com> wrote:
> Hi Ciaran,
>
> The issue <http://issues.apache.org/jira/browse/ODE-561> you're referring
> to aims to limit the total number and/or size of processes in the server'
Hi folks,
I notice that Alexis references an 'enableSharing' element in deploy.xml in
this issue comment, but I can't find any definition in the documentation as
to what this element actually means, can anyone explain why I might want
this on or off for my deployments ?
Sorry folks! :)
-cj.
On W
Thanks chaps :)
- cj.
On Thu, Apr 2, 2009 at 6:05 PM, Karthick Sankarachary <
sankarach...@intalio.com> wrote:
> Hi Ciaran,
>
> For more details on 'enableSharing', please take a look at
> this<http://issues.apache.org/jira/browse/ODE-364>issue. I will updat
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-
Sorry guys, I'm currently unable to deploy to ODE I receive the following
exception:
WARN - GeronimoLog.warn(96) | Invocation of operation deploy failed
org.apache.ode.axis2.OdeFault: Your message should contain an element named
'package' with a 'zip' element
at
org.apache.ode.axis2.service.De
Need to understand why my Dynamic invokes no longer work before I can vote
positively :(
- cj.
On Thu, Apr 30, 2009 at 2:31 AM, Assaf Arkin wrote:
> +1
>
> Assaf
>
> On Wed, Apr 29, 2009 at 3:00 PM, Alexis Midon wrote:
>
> > Here we go again,
> >
> > I cut another ODE release, ODE-1.3.2. Since
I get this too, it doesn't seem to matter fwiw and I put it down to a build
environment issue on my part (the wrong version of buildr or some such!)
- cj.
On Wed, May 13, 2009 at 11:28 AM, Nowakowski, Mateusz <
mateusz.nowakow...@sabre-holdings.com> wrote:
> I'll make a build today as fast as po
Hi Folks,Has anyone had a chance to look at this issue at all? I still
cannot use ODE with this issue in the code (or in my BPEL wherever the fault
is), which is a shame :(
-cj.
On Tue, May 12, 2009 at 4:47 PM, Ciaran Jessup (JIRA) wrote:
> *MY* dynamic endpoint references have sudde
I would really appreciate some feedback, just anything really on this issue
I *cannot* use ODE currently, and I would rather like to given the time I've
invested in investigating the memory issues previously :(
Many thanks.
-cj.
On Thu, May 14, 2009 at 8:27 PM, Ciaran wrote:
> Hi F
ad-rush/
>
> http://www.intalio.com/news/press-releases/intalio-acquires-bpm-and-crm-companies-launches-intalio-cloud/
>
> We'll get back to your issue soon after we land back on terra firma.
>
> alex
>
>
> On Tue, May 19, 2009 at 2:58 AM, Ciaran wrote:
>
> > I woul
d any
un-neccessary fluff from the BPEL (for example I've removed all the fault
handling code etc.)
Many thanks
- Cj.
On Wed, May 20, 2009 at 12:16 AM, Karthick Sankarachary <
sankarach...@intalio.com> wrote:
> Ciaran,
>
> There appears to be something missing in the proje
Fwiw, I use the following command to build ode_1xx branch:
buildr TEST=no JAVADOC=off ode:package
Hope that helps :)
- cj.
On Mon, Jun 1, 2009 at 10:12 AM, Ian Harrigan wrote:
> Hi all,
>
> Im having a real problem trying to build the ODE distribution. Im pretty
> sure I installed ruby cor
Hi Guys,
I just recently updated our SVN working copy of the ODE 1_X branch. It
seems that changeset 790694 (
http://svn.apache.org/viewvc?view=rev&revision=790694) has broken our
worklfows.
Effectively we now see (at random, as this is I believe an introduced race)
:
ERROR - GeronimoLog.error(10
On Tue, Dec 8, 2009 at 8:28 PM, Rafal Rusin wrote:
> I personally think that we should stay with 1.X and drop trunk for
> now. In future, we could
> integrate in smaller steps features from trunk into 1.X, for example
> in versions 1.4, 1.5,...
> Doing so huge leap into 2.0 now will do no good for
Ciaran Jessup created ODE-991:
-
Summary: ode:delete fails when removing multiple elements
Key: ODE-991
URL: https://issues.apache.org/jira/browse/ODE-991
Project: ODE
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ODE-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-991:
--
Attachment: FixDeleteForMultipleElements.patch
> ode:delete fails when removing multiple eleme
Versions: 1.1.1
Environment: Java6u6, Tomcat 6.0.16
Reporter: Ciaran Jessup
Priority: Minor
The AXIS SOAP responses I'm getting back from ODE within soapui show a worrying
proliferation of namespace prefixes. The same namespace is receiving a new
prefix everytime
Support XSLT's document() function
--
Key: ODE-296
URL: https://issues.apache.org/jira/browse/ODE-296
Project: ODE
Issue Type: New Feature
Components: BPEL Runtime
Reporter: C
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-296:
--
Attachment: HelloWorld2.zip
This is an example test-case that uses the 'document()' sy
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-296:
--
Attachment: AddDocumentSupport.patch
Initial patch to provide document() support.
Solves test-case
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600393#action_12600393
]
Ciaran Jessup commented on ODE-296:
---
Ok, this makes sense, I was unhappy with where I
se/ODE-296
> Project: ODE
> Issue Type: New Feature
> Components: BPEL Runtime
>Reporter: Ciaran Jessup
> Fix For: 1.2
>
> Attachments: AddDocumentSupport.patch, HelloWorld2.zip
>
>
> Currently the BPEL runtime d
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-296:
--
Attachment: AddDocumentSupportv2.patch
Ammended approach taking into account the above comments. Removed
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600602#action_12600602
]
Ciaran Jessup commented on ODE-296:
---
Ok, thanks for applying the patch, I hit the
[
https://issues.apache.org/jira/browse/ODE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-297:
--
Attachment: AddDOMtoStringCustomFunction.patch
This patch provides a custom function declared in the
Issue Type: New Feature
Components: BPEL Compilation/Parsing, BPEL Runtime
Affects Versions: 1.2
Reporter: Ciaran Jessup
Priority: Minor
Fix For: 1.2
Attachments: AddDOMtoStringCustomFunction.patch
I have a requirement to pass an XML
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-296:
--
Attachment: FixUnneccessaryConstructorArgs.patch
When looking over the code I noticed I was passing an
[
https://issues.apache.org/jira/browse/ODE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-192:
--
Attachment: FixDeleteInstances.patch
This patch should resolve issues 1 & 3 but issue 2 is relate
[
https://issues.apache.org/jira/browse/ODE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-192:
--
Attachment: DeleteByInstanceId.patch
A patch to fix Issue 2 ;)
As far as I can tell the
[
https://issues.apache.org/jira/browse/ODE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-296:
--
Attachment: HelloWorld2.zip
I'm not totally sure this is a micro-optimization, I use the doc
: ODE
Issue Type: Bug
Affects Versions: 1.2
Reporter: Ciaran Jessup
During BPEL Assign's in certain scenarios namespace prefix declarations which
are required to maintain valid qnames in attribute values are dropped. This is
a bit of a problem for me as it renders my XML
[
https://issues.apache.org/jira/browse/ODE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-343:
--
Attachment: HelloWorld2.zip
Sample echo process that loses namespace prefix declarations required by
[
https://issues.apache.org/jira/browse/ODE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-352:
--
Attachment:
PatchToSupportMultipleAttributesWithTheSameLocalNameButDifferentNamespaces.patch
This
[
https://issues.apache.org/jira/browse/ODE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-352:
--
Attachment: HelloWorld2.zip
The attached process should accept requests like:
http://www.w3.org/2001
[
https://issues.apache.org/jira/browse/ODE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674745#action_12674745
]
Ciaran Jessup commented on ODE-522:
---
Yup, you're quite correct that was indeed
[
https://issues.apache.org/jira/browse/ODE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674754#action_12674754
]
Ciaran Jessup commented on ODE-522:
---
Thats very strange, we were opening the war file
[
https://issues.apache.org/jira/browse/ODE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678443#action_12678443
]
Ciaran Jessup commented on ODE-533:
---
Sorry about ODE-537 Matthieu asked for a new bug t
[
https://issues.apache.org/jira/browse/ODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678686#action_12678686
]
Ciaran Jessup commented on ODE-536:
---
These changes *appear* to have broken our BPEL f
[
https://issues.apache.org/jira/browse/ODE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678843#action_12678843
]
Ciaran Jessup commented on ODE-422:
---
We're only using in-memory processes (just
[
https://issues.apache.org/jira/browse/ODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678845#action_12678845
]
Ciaran Jessup commented on ODE-536:
---
Not easily, our processes are quite complex/large,
[
https://issues.apache.org/jira/browse/ODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678852#action_12678852
]
Ciaran Jessup commented on ODE-536:
---
Unfortunately I won't be able to do t
[
https://issues.apache.org/jira/browse/ODE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683523#action_12683523
]
Ciaran Jessup commented on ODE-557:
---
We raised ODE-422, our concern was that the
[
https://issues.apache.org/jira/browse/ODE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689393#action_12689393
]
Ciaran Jessup commented on ODE-422:
---
We've not seen any failures since that fix :)
Components: BPEL Compilation/Parsing, BPEL Runtime
Environment: N/A
Reporter: Ciaran Jessup
Currently if the BPEL process contains any XSL stylesheets it will not free up
*all* the memory that was allocated during the compilation/dehydration of the
process. This seems to
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Attachment: StyleSheetCache.patch
This patch should now allow any OProcess instances that happen to be
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Attachment: StopListenersHangingAbout.patch
The attached patch (I think, will confirm in the morning [GMT
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696772#action_12696772
]
Ciaran Jessup commented on ODE-574:
---
Your proposal makes sense, the only reason I di
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Comment: was deleted
(was: Your proposal makes sense, the only reason I didn't want to do something
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696776#action_12696776
]
Ciaran Jessup commented on ODE-574:
---
That patch certainly is a lot simpler from
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696944#action_12696944
]
Ciaran Jessup commented on ODE-574:
---
I've reviewed the cleanup-xsl-ca
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Attachment: memory-leak-all-in-one.patch
Iv'e merged my previous two patches into a single patch
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Attachment: (was: StopListenersHangingAbout.patch)
> Memory leak when Un-deploying processes t
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Attachment: (was: StyleSheetCache.patch)
> Memory leak when Un-deploying processes that contain
Components: BPEL Runtime
Environment: n/a
Reporter: Ciaran Jessup
Our BPEL workflows contain a large number of literal assigns, these are stored
as Document instances in the BPEL runtime, which are cloned each time they are
referenced, this appears to consume an immense amount
[
https://issues.apache.org/jira/browse/ODE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-575:
--
Attachment: AssignLiteralMemoryRedux.patch
The attached patch attempts to reduce the memory footprint of
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697403#action_12697403
]
Ciaran Jessup commented on ODE-574:
---
If you don't clear the cache after the com
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697489#action_12697489
]
Ciaran Jessup commented on ODE-574:
---
After applying your patch, it seems that yo
[
https://issues.apache.org/jira/browse/ODE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-574:
--
Attachment: memory-leak-all-in-one-2.patch
This patch has been re-generated against the latest SVN HEAD
Components: BPEL Runtime
Environment: n/a
Reporter: Ciaran Jessup
It seems that when I deploy and un-deploy in-memory processes ProcessDaoImpl
objects stored in the __StateStore field of the BpelDAOConnectionFactoryImpl
object are being left around.
Over the course of several tens
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-576:
--
Attachment: InMemoryProcessesLeakMemory.patch
This patch contains a 'fix' (I could completel
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697651#action_12697651
]
Ciaran Jessup commented on ODE-576:
---
Ok, with the patch I have no memory leaks, without
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697651#action_12697651
]
Ciaran Jessup edited comment on ODE-576 at 4/9/09 2:32 PM:
---
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup reopened ODE-576:
---
Based on my comments above, the BpelConnectionDaoImpl instance that the
'delete' occurs on, is
[
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-deploym
Reporter: Ciaran Jessup
When un-deploying a DeploymentUnitDir object instance is kept in memory, this
is a direct consequence of this Axis bug ( ) which has been resolved in Axis2
1.4 (I know there's an ODE fork running that version out there...)
There follows a *HORRIBLE* &#x
[
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
[
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
[
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 flagge
[
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
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699579#action_12699579
]
Ciaran Jessup commented on ODE-576:
---
Hi Karthick,
Unfortunately your patch doesn'
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699792#action_12699792
]
Ciaran Jessup commented on ODE-576:
---
Thanks Karthick, I appreciate your quick turnaroun
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700162#action_12700162
]
Ciaran Jessup commented on ODE-576:
---
Hi Karthick,
Unfortunately this patch also doe
[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701129#action_12701129
]
Ciaran Jessup commented on ODE-576:
---
Hi Karthick,
I'm happy to report that yo
Environment: n/a
Reporter: Ciaran Jessup
Priority: Blocker
Fix For: 1.3.1
As of the changes that went into https://issues.apache.org/jira/browse/ODE-591
the deployment web service appears to be broken, any attemp to deploy will
probably result in an
1 - 100 of 112 matches
Mail list logo
