JIRA

  • 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 Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-147

Socket closed or not

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-rc2
  • Fix Version/s: None
  • Component/s: Transport: TCP / UDP / SSL / Multicast
  • Labels:
    None
  • Similar Issues:
    None

Description

When creating a tcp receiver, it's possible to access the ResponseOutputStream from Event and write something on it.
Sometimes client disconnect and socket is closed, if we try to write on the stream, we got an error.
Is it possible to have access to the socket and test if he's closed or not ?

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
No work has yet been logged on this issue.

People

  • Assignee:
    Ross Mason
    Reporter:
    Suray Philippe
Vote (0)
Watch (0)

Dates

  • Created:
    03/Feb/05 08:33 AM
    Updated:
    21/Aug/06 09:23 PM
    Resolved:
    20/Feb/05 08:49 AM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.