Bug 260817 - [tml][protocol] Connection is stopped unexpectedly
Summary: [tml][protocol] Connection is stopped unexpectedly
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sequoyah (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Daniel Barboza Franco CLA
QA Contact:
URL:
Whiteboard: released_0.3M6
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2009-01-13 03:38 EST by petr CLA
Modified: 2016-11-08 14:46 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description petr CLA 2009-01-13 03:38:36 EST 
Build ID: M20080911-1700

Steps To Reproduce:
1. Connect to a server
2. Hold a keyboard key which does not cause any visual change. 
3. Connection is stopper with error message in the console: "Message not found. Stopping protocol..."


More information:
The problem is easily solved by modifying org.eclipse.tml.protocol.lib.internal.engine.ProtocolEngine:
swap line 1450 and 1451. move "code=0;" outside if statement. This change should be verified that it does not cause other problems.
Comment 1 Daniel Barboza Franco CLA 2009-02-12 10:22:45 EST 
The problem was that the vnc client implementation was not handling the Bell message. It is a 1 byte long message, sent by the server when a system beep happens.

That is the reason why your fix worked. Now the Bell message handling is implemented and this workaround in ProtocolEngine is not necessary.

Tks,
Daniel.

branch: branch_dsdp_tml_bug_260817
integrated to: HEAD
Comment 2 Fabio Fantato CLA 2009-03-11 11:48:52 EDT 
released_0.3M6