[JIRA] (COMETD-370) connectTimeout not working and closing an opened connection

7 views
Skip to first unread message

Mathieu Carbou (Created) (JIRA)

unread,
May 7, 2012, 12:15:25 PM5/7/12
to comet...@googlegroups.com
connectTimeout not working and closing an opened connection
-----------------------------------------------------------

Key: COMETD-370
URL: http://bugs.cometd.org/browse/COMETD-370
Project: CometD
Issue Type: Bug
Components: websocket-javascript
Affects Versions: 2.4.1
Reporter: Mathieu Carbou
Priority: Blocker
Attachments: connectTimeout-fix.patch

The code which supports the connectTimeout miss some checks thus it closes the webcocket connection event if it is successfully opened.

To reproduce, just put a connectTimeout of 2 seconds for example and you'll see the connnection closing after 2 seconds.

Here is an attached patch which fixes the issue.

Mat'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: http://bugs.cometd.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Mathieu Carbou (Commented) (JIRA)

unread,
May 7, 2012, 12:15:25 PM5/7/12
to comet...@googlegroups.com

Simone Bordet (Resolved) (JIRA)

unread,
May 15, 2012, 9:10:25 AM5/15/12
to comet...@googlegroups.com

[ http://bugs.cometd.org/browse/COMETD-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simone Bordet resolved COMETD-370.
----------------------------------

Assignee: Simone Bordet
Fix Version/s: 2.4.2
2.5.0
Resolution: Fixed

Fixed as suggested (plus some additions), thanks for the patch.

> connectTimeout not working and closing an opened connection
> -----------------------------------------------------------
>
> Key: COMETD-370
> URL: http://bugs.cometd.org/browse/COMETD-370
> Project: CometD
> Issue Type: Bug
> Components: websocket-javascript
> Affects Versions: 2.4.1
> Reporter: Mathieu Carbou
> Assignee: Simone Bordet
> Priority: Blocker
> Fix For: 2.4.2, 2.5.0
Reply all
Reply to author
Forward
0 new messages