Return-Path: Delivered-To: apmail-ws-sandesha-dev-archive@www.apache.org Received: (qmail 66500 invoked from network); 1 Jun 2007 13:53:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Jun 2007 13:53:37 -0000 Received: (qmail 66178 invoked by uid 500); 1 Jun 2007 13:53:40 -0000 Delivered-To: apmail-ws-sandesha-dev-archive@ws.apache.org Received: (qmail 66132 invoked by uid 500); 1 Jun 2007 13:53:40 -0000 Mailing-List: contact sandesha-dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list sandesha-dev@ws.apache.org Received: (qmail 66121 invoked by uid 99); 1 Jun 2007 13:53:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 06:53:40 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 06:53:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D1EA271418E for ; Fri, 1 Jun 2007 06:53:15 -0700 (PDT) Message-ID: <27068456.1180705995857.JavaMail.jira@brutus> Date: Fri, 1 Jun 2007 06:53:15 -0700 (PDT) From: "stefan stieglitz (JIRA)" To: sandesha-dev@ws.apache.org Subject: [jira] Updated: (SAND-13) InactivityTimeout events do not reach the application layer In-Reply-To: <25770743.1180705876158.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SAND-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stefan stieglitz updated SAND-13: --------------------------------- Description: Sandesha provides an inactivity timeout configuration for timing out sequences. Reaching this timeout results in an exception in the SenderWorker object. This exception does not reach the application layer. There should be an exception or a send result that indicates the timeout. Effect: Callback objects are not notified that the message can not be delivered. Reproduction: - use an asynchronous client setup with separate listeners and a callback as in the AsyncEchoClient sample - use a (short) inactivityTimeout - wait without timeout for the callback to receive an event - start the application offline with no connection to the RMSampleService Resolution suggestions: - let SenderWorker initiate a call of Callback.onError( Exception ) - let SenderWorker initiate a call of Callback.onComplete( AsyncResult ) with a SOAPFault result was: Sandesha provides an inactivity timeout configuration for timing out sequences. Reaching this timeout results in an exception in the SenderWorker object. This exception does not reach the application layer. There should be an exception or a send result that indicates the timeout.

Effect:

Callback objects are not notified that the message can not be delivered.

Reproduction:

  1. use an asynchronous client setup with separate listeners and a callback as in the AsyncEchoClient sample.
  2. use a (short) inactivityTimeout
  3. wait without timeout for the callback to receive an event.
  4. start the application offline with no connection to the RMSampleService

Resolution suggestions:

  • let SenderWorker initiate a call of Callback.onError( Exception )
  • let SenderWorker initiate a call of Callback.onComplete( AsyncResult ) with a SOAPFault result
> InactivityTimeout events do not reach the application layer > ----------------------------------------------------------- > > Key: SAND-13 > URL: https://issues.apache.org/jira/browse/SAND-13 > Project: Sandesha > Issue Type: Bug > Environment: Axis2 1.1 > sandesha2 1.1 > Sample AsyncEchoClient > Reporter: stefan stieglitz > Assignee: Davanum Srinivas > Priority: Minor > > Sandesha provides an inactivity timeout configuration for timing out sequences. Reaching this timeout results in an exception in the SenderWorker object. This exception does not reach the application layer. There should be an exception or a send result that indicates the timeout. > Effect: > Callback objects are not notified that the message can not be delivered. > Reproduction: > - use an asynchronous client setup with separate listeners and a callback as in the AsyncEchoClient sample > - use a (short) inactivityTimeout > - wait without timeout for the callback to receive an event > - start the application offline with no connection to the RMSampleService > Resolution suggestions: > - let SenderWorker initiate a call of Callback.onError( Exception ) > - let SenderWorker initiate a call of Callback.onComplete( AsyncResult ) with a SOAPFault result -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org For additional commands, e-mail: sandesha-dev-help@ws.apache.org