Issue Details (XML | Word | Printable)

Key: OF-91
Type: Bug Bug
Status: Reopened Reopened
Priority: Blocker Blocker
Assignee: Gaston Dombiak
Reporter: Gaston Dombiak
Votes: 1
Watchers: 7
Operations

If you were logged in you would be able to see more operations.
Openfire

Client session will be terminate when receiving invalid surrogate characters

Created: 06/11/08 07:30 AM   Updated: 02/01/10 01:27 AM
Component/s: Connection Manager, Core
Affects Version/s: 3.6.4
Fix Version/s: 3.7.1

Time Tracking:
Not Specified

Issue Links:
Related to
 

Acceptance Test - Add?: No


 Description  « Hide
Client session will be terminate when receiving invalid surrogate characters

 All   Comments   Work Log   Change History   FishEye      Sort Order: Ascending order - Click to sort in descending order
Ilan Rabinovitch added a comment - 08/21/08 10:54 PM
Would it be possible to confirm if this is related to the issues mentioned in the Pidgin and AdiumX bug trackers? Both tickets reference, but indicate they were unable to confirm if this was the solution. I know that as of openfire 3.5.2 the invalid characters still terminate client sessions for Pidgin, Gajim, and Adium.

AdiumX:
http://trac.adiumx.com/ticket/10353

Pidgin: ASCII control characters cause problems with libpurple clients
http://developer.pidgin.im/ticket/6031


Thoralf Will added a comment - 10/25/08 01:41 AM
Still (again?) an issue with 3.6.0a
When sending something as simple as <ctrl>-<alt>-a in Adium the receiving side will disconnect within the next 2 seconds.

Daryl Herzmann added a comment - 04/29/09 07:22 PM
reopening.

Ilan Rabinovitch added a comment - 05/01/09 10:08 PM
So a fix was found and is available in 3.6.5?

Daryl Herzmann added a comment - 05/01/09 10:49 PM
Hi,

Unfortunately, no. The ticket was just bumped against the next unreleased release .

daryl


Steve Alligood added a comment - 10/07/09 09:52 PM
Bump. This issue is constantly causing issues with over 200 users constantly getting disconnected and auto reconnecting.

Guenther Niess added a comment - 01/07/10 09:41 AM - edited
Either this or the JM-1421 issue is invalid. I'm not sure which one.

Ilan Rabinovitch added a comment - 01/07/10 10:18 AM
@Guenther, I do not believe these 2 issues contradict each other. JM-1421 is indicating the sender of invalid XML should be disconnected. In the case of this bug OF-91, invalid XML is sent and the recipient is disconnected.