Hello, Thank you very much for the link Milinda. But further investigations lead to the point that my process is called asynchronous as expected. BUT the http connection seems to be kept opened until a timeout is reached on the server. Than the connection is closed, all client threads run out and everything is fine. It does not matter if I use a selfmade soap java client, or Eclipse WebServices Explorer or SoapUI. The connections are terminated by a timeout at the server.
Perhaps this has something to do with http://issues.apache.org/jira/browse/ODE-464? Greetings Adam -----Ursprüngliche Nachricht----- Von: Milinda Pathirage [mailto:[email protected]] Gesendet: Dienstag, 22. September 2009 19:38 An: [email protected] Betreff: Re: How to design an asynchronous BPEL process? This tutorial[1] from Netbeans knowledge base will help you to some extent. Thanks Milinda http://www.netbeans.org/kb/60/soa/asynchsample.html On Tue, Sep 22, 2009 at 8:02 PM, Lucarz, Adam <[email protected]> wrote: > Hello, > > I am a newbie to the BPEL topic and I have tried and read a lot the > last days about designing BPEL processes. But I couldn't find out how > I can create an asynchronous process. I am thinking about a process > which is initalized/called by a web service client and DO NOT blocks > the client while running. > > I have attached a process which contains only a receive statement and > does nothing after all. In my imaginary beautiful world the process > would receive the message and run out to the end. But the client would > be freed just after the receiving. > > My intention is to provide an one-way process method because I do not > need any response at this point. > > I am sure that I didn't understand some aspect...so...can someone help > me with some hints? > > Greetings > Adam > ** > > > CENIT AG, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49 711 > 7825-30, > Fax: +49 711 7825-4000, Internet: www.cenit.de > Geschaeftsstellen: Berlin, Duesseldorf, Frankfurt, Hamburg, Hannover, > Muenchen, Oelsnitz, Saarbruecken > Vorstandsmitglieder: Kurt Bengel, Christian Pusch > Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des > Aufsichtsrats), Hubert Leypoldt, Andreas Karrer > Bankverbindungen: > Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070 > 0166 1040 00 SWIFT-CODE : DEUTDESS, Commerzbank (BLZ 600 400 71) Kto. > 532 015 500 IBAN : DE83 6004 0071 0532 > 0155 00 SWIFT-Code : COBADEFF600, > BW-Bank (BLZ 600 501 01) Kto. 2 403 313 IBAN : DE17 6005 0101 0002 > 4033 13 SWIFT-Code : SOLADEST > Registergericht: Amtsgericht Stuttgart > Handelsregister: HRB Nr. 19117 > Umsatzsteuer: ID-Nr. DE 147 862 777 > -- Milinda Pathirage Senior Software Engineer & Product Manager WSO2 BPS; http://wso2.org/bps WSO2 Inc.; http://wso2.com E-mail: [email protected], [email protected] Web: http://mpathirage.com Blog: http://blog.mpathirage.com CENIT AG, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49 711 7825-30, Fax: +49 711 7825-4000, Internet: www.cenit.de Geschaeftsstellen: Berlin, Duesseldorf, Frankfurt, Hamburg, Hannover, Muenchen, Oelsnitz, Saarbruecken Vorstandsmitglieder: Kurt Bengel, Christian Pusch Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des Aufsichtsrats), Hubert Leypoldt, Andreas Karrer Bankverbindungen: Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070 0166 1040 00 SWIFT-CODE : DEUTDESS, Commerzbank (BLZ 600 400 71) Kto. 532 015 500 IBAN : DE83 6004 0071 0532 0155 00 SWIFT-Code : COBADEFF600, BW-Bank (BLZ 600 501 01) Kto. 2 403 313 IBAN : DE17 6005 0101 0002 4033 13 SWIFT-Code : SOLADEST Registergericht: Amtsgericht Stuttgart Handelsregister: HRB Nr. 19117 Umsatzsteuer: ID-Nr. DE 147 862 777
