• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates
  • Administration
  • Log in to participate

▼ Tags

 

▼ Similar Entries

ACEv11 Creating an I...

Blog: Enterprise Po...
Adi H 270007GRFR
Updated
0 people like thisLikes 0
No CommentsComments 0

IBM WCS V9 : Benefit...

Blog: IBM Websphere...
Puneet_Jain 310002WTFA
Updated
1 people likes thisLikes 1
No CommentsComments 0

IBM WCS REST Caching...

Blog: IBM Websphere...
Puneet_Jain 310002WTFA
Updated
0 people like thisLikes 0
No CommentsComments 0

How to Secure Your D...

Blog: The Tech Park
PhilipP. 310002RC19
Updated
0 people like thisLikes 0
No CommentsComments 0

Tips and Tricks in C...

Blog: developerWork...
Gadde_Radhika 50J9GYTSQP
Updated
0 people like thisLikes 0
No CommentsComments 0

▼ Similar Ideas

Global configuration...

Ideation Blog: WebSphere App...
m.fatih 3100001ATT
Updated
No Votes 0 No CommentsComments 0

▼ Archive

  • November 2014
  • September 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010

▼ Links

  • Welcome & Product List
  • Disclaimer & Trademark
  • IBM Business Process Managemen...
  • IBM Adapters on Twitter
  • WebSphere on Facebook
  • WebSphere & CICS Support blog
  • IBM BPM Good Practices Communi...
  • IBM Technical Content Blog

▼ Blog Authors

IBM Business Process Management Products Support Blog

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

HTTP Import Binding Timeout Behavior

RayTseng 100000KB37 | | Tags:  wps process httpbindings server websphere ‎ | 4 Comments ‎ | 11,059 Views
image image

Recently, I have run across some interesting information with how the WebSphere Process Server Version 7 HTTP Import Binding handles timeouts. The WebSphere Process Server HTTP Import Binding has 2 properties for handling timeouts and retries:

  • Read Timeout :  Specifies the time, in seconds, that the binding waits to read data while receiving a response message. Setting this field to 0 causes the binding to wait indefinitely.
  • Number of Retries:  Specifies the number of times the request is retried when the system receives an error response.
 
Source: WebSphere Process Server Information Center

image
1) Read timeout=0 behavior
In WebSphere Process Server v7 there has been an addendum made to the read ReadTimeout description.
Note: The HTTP transport channel has its own Read timeout value, which is the amount of time that the channel waits for a read request to complete on a socket after the first read request occurs. This setting is described in HTTP transport channel settings in the WebSphere Application Server Information Center.

As a result, a setting of 0 in Version7 will actually fall through and timeout on the HTTP Transport channel settings (typically a default of 60 seconds). If you require a long timeout value, you will need to use an arbitrary large number for this property instead of 0. Currently there is no setting that truly represents an indefinite wait.


2) Number of Retries behavior

The description for retries can be misleading. 
Note that the description of this property is specifically describes retrying when the system receives an error response.
In a scenario where instead the HTTP Service does not respond, or the response is late, you may observe some unexpected behavior.



No Response Scenario
Retry: 5
Read Timeout: 30
Behavior of the service:  The service does not respond.

Expectation: In this case, 6 total requests (original+5 retries) are sent out in 30 second intervals.
Actual behavior: The current behavior of the binding is that only 1 request is sent as no error is returned.  This particular invocation will wait 180 seconds then return an error.

Late Response Scenario
Retry: 5
Read Timeout: 30
Behavior of the service: Return after 45 seconds

Expectation: 2 requests are sent out.  Unknown. The proper behavior to handle a late response or responses can be arbitrary.
Actual Behavior: The current behavior is that only 1 request is sent out.  When the response comes in late at 45 seconds, it causes an error as it has exceeded the timeout value. The first retry is then submitted at the 45 second mark.  Depending on the timing of the 2nd response;  this might lead to additional unexpected behavior.

In summary, the retry mechanism currently is geared towards handling errors rather than no responses.  You might encounter unexpected behavior when dealing with late or no response. If you have a service that might be slow to respond, you might set the high timeout values to avoid running into these problems. 

We have submitted this issue and further work to create more meaningful retry behavior logic in these two situations.
  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry