Project

General

Profile

Bug #634

Simple chat bug

Added by Thim Anneessens almost 12 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Pieter Libin
Category:
-
Target version:
Start date:
12/09/2010
Due date:
% Done:

0%

Estimated time:

Description

Hello,

I am having an issue with the Simple chat exemple. I am running it on Windows/JBoss/Firefox 3.6 with a JWt 3.1.7a library slitly modified to enable url based ressource files (see previous issue :) ).

When the server is running, I start one session (guest1), send a message, open a new tab, start a session (guest2) and send a message.

At this point I get a javascript alert saying the following:

"Wt internal error: TypeError: j10 is undefined, code: undefined, description: undefined"

Here is the console output of that little experience:

01:27:23,478 ERROR [STDERR] Using servlet API 3

01:27:23,549 ERROR [STDERR] Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12

01:32:30,096 ERROR [STDERR] Grabbing update lock

01:32:30,098 ERROR [STDERR] Releasing update lock

01:32:43,803 ERROR [STDERR] Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12

01:32:47,739 ERROR [STDERR] Grabbing update lock

01:32:47,739 ERROR [STDERR] Creating new handler for app: app.sessionId()

01:32:47,743 ERROR [STDERR] Releasing update lock

01:32:47,744 ERROR [STDERR] Releasing handler

01:32:51,922 ERROR [STDERR] Grabbing update lock

01:32:51,923 ERROR [STDERR] Creating new handler for app: app.sessionId()

01:32:51,926 ERROR [STDERR] Exception occurred when flushing the writer

01:32:51,927 ERROR [STDERR] Releasing update lock

01:32:51,928 ERROR [STDERR] Releasing handler

01:32:51,928 ERROR [STDERR] Grabbing update lock

01:32:51,929 ERROR [STDERR] Releasing update lock

Thats it for... this morning :).

Best regards,

Thim.

#1

Updated by Pieter Libin about 11 years ago

  • Status changed from New to InProgress
  • Assignee set to Pieter Libin
#2

Updated by Pieter Libin about 11 years ago

test with jwt-3.1.11

#3

Updated by Pieter Libin about 11 years ago

Hey,

There are problems with most Servlet 3.0 implementations with respect to asynchronous I/O, which is used for server push and how it is implemented in JWt. We have the best experience with Tomcat v7.0.4 as a Servlet v3 implementation, this is the one we use to host the simplechat example on our website (http://www.webtoolkit.eu/jwt/examples/chat).

If you consider 2 sessions A and B, after a while JBoss will send data that is to be received by session A to session B, resulting in the Javascript error you described in your report.

We continue to follow up the status of containers implementing the Servlet 3 specification, but until everything works properly, you can deploy your server push applications on a Servlet v2.5 servlet container. On such Servlet containers JWt will use synchronous input/output to execute server push operations, but it is otherwise functionally equivalent.

#4

Updated by Pieter Libin almost 11 years ago

  • Status changed from InProgress to Resolved
#5

Updated by Koen Deforche over 10 years ago

  • Status changed from Resolved to Closed
  • Target version set to 3.2.1

Also available in: Atom PDF