web stats
Download | Support | Contact
Mirth Corporation
  • Home
  • Products
    • Mirth Connect
    • Mirth Results
    • Mirth Match
    • Mirth Mail
    • Mirth Care
    • Mirth Appliances
    • Mirth Virtual Appliances
    • Mirth Hosted Appliances
  • Services
    • Support
    • Training
    • Consulting
  • Solutions
    • HIEs
    • Hospitals
    • Clinics
    • Laboratories
    • Radiology
    • Vendors
    • Government
  • Community
    • Forums
    • Wiki
    • Issues
    • Source Code
    • Mirth Exchange
    • IRC
    • FAQs
    • Contribute
    • Registration
    • Downloads
  • Company
    • About
    • Mission and Vision
    • Testimonials
    • News
    • Employment Opportunities
    • Contact

Mirth Project

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile
  • Mirth Connect
  • MIRTH-1975

Add timeout setting for HTTP Listener

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.1.1
  • Fix Version/s: 2.2.0 RC 1, 2.2.0
  • Component/s: Administrator, Server
  • Labels:
    None

Description

Add a receiver timeout setting to the HTTP Listener. One possible setting can be found in the Jetty configuration documentation:

"maxIdleTime: Set the maximum Idle time for a connection, which roughly translates to the Socket.setSoTimeout(int) call, although with NIO implementations other mechanisms may be used to implement the timeout. The max idle time is applied: when waiting for a new request to be received on a connection; when reading the headers and content of a request; when writing the headers and content of a response. Jetty interprets this value as the maximum time between some progress being made on the connection. So if a single byte is read or written, then the timeout (if implemented by Jetty) is reset. However, in many instances, the reading/writing is delegated to the JVM, and the semantic is more strictly enforced as the maximum time a single read/write operation can take. Note that as Jetty supports writes of memory-mapped file buffers, a write may take many 10s of seconds for large content written to a slow device."

http://wiki.eclipse.org/Jetty/Howto/Configure_Connectors

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Source
Hide
Permalink
Gerald Bortis added a comment - 03/Nov/11 9:33 AM
Added "Receive Timeout" on connector that corresponds to maxIdleTime on HTTP server.
Show
Gerald Bortis added a comment - 03/Nov/11 9:33 AM Added "Receive Timeout" on connector that corresponds to maxIdleTime on HTTP server.

People

  • Assignee:
    Gerald Bortis
    Reporter:
    Gerald Bortis
Vote (0)
Watch (0)

Dates

  • Created:
    07/Oct/11 9:51 AM
    Updated:
    19/Jan/12 4:49 PM
    Resolved:
    19/Jan/12 4:49 PM
  • Atlassian JIRA (v5.0.3#729-sha1:bf569e4)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Mirth Corporation. Try JIRA - bug tracking software for your team.