Re: Difficult Performance Problem

I don't think I can easily post enough material to duplicate the issue at this time.  The process in question involves quite a lot of code, including a service on an IIS server, in C#, and SAs on remote Glassfish servers.  I've got quite a large application here...

I did realize that I should have added a few points to my original post.  1) The EJB driving the process is in a different SA from the BPEL it is calling (but on the same server).  And 2) the amount of data is relatively large.  The BPEL is being called with an image of about one MB, that has been marshaled into a string field (a string, for reasons having to do with the other servers it goes on to from the BPEL).  The large data block seems to be key.  I have not seen this in other places in the application.

3) Only restarting Glassfish seems to clear it up, reloading the SAs does not help.

What I'm wondering about is perhaps some resource being consumed in the HTTP BC maybe?  I'm not sure how to go about collecting more information, or on the impacts of increasing any of the default cache and pool settings for HTTP or EJBs.

Murali Pottlapelli wrote:

I am not aware of this issue. Will you please an issue at
https://open-esb.dev.java.net/servlets/ProjectIssues and attach the
project to reproduce the issue?

Regards
Murali

jsexton0 wrote:
> I have a system of BPELs and EJBs that perform a task.  Most of the task is
> driven by an EJB, which invokes a few BPEL processes.  One of the BPELs
> takes about 2 seconds to run.
>
> The problem is that if for any reason the client (I'm using SoapUI and
> Netbeans unit tests) goes away, such as a timeout, then the next time the
> process is run, the same process that took 2 seconds to run takes more like
> seven seconds.
>
> Let the client time out again, and that becomes more like 2-3 minutes.  Do
> this 3-5 times and the system becomes unusable, the delay becomes several
> hours.
>
> I have used logging to isolate the time being consumed to be just between
> the Java/EJB's call to the BPEL's web service, and the start of the initial
> receive action in the BPEL.
>
> How can I avoid this problem?
> Thanks
>