my understanding of the gfv3 sample -- async-request-war -- is that in its init(sc) which is being called for each browser request,
it creates a new Thread -- which seems like should only be done one time -- the code -- on my crashed drive needing repair --
i am trying to remember here -- perhaps? only has 1 instance of each queue (messages and AsyncContexts)-- think
was declared static to the servlet -- so i guess could still work -- buts definitely does not for me!!!
i had tried separated browsers, also different browsers; firefox, chrome, IE
the grizzly sample which the gfv3 sample was derived from worked just fine -- even with the same browser with multiple tabs open???
so i cannot see how it can work for you -- it not only failed with the gfv3 sample -- but with the sample in the netbeans dev build
bundled EE6 servlet example with the same code.
gary
----- Original Message -----
From: Shing Wai Chan
To: users_at_glassfish.dev.java.net
Sent: Wednesday, April 14, 2010 1:57 PM
Subject: Re: servlet 3.0 async, gvf3
Hi,
I have just tried the GlassFish async sample. It is working fine for me.
You may like to restart your browser. Also, you may like to have two different browsers to run the chat.
As mentioned by Jan, there is an bug in the sample.
That bug should not affect the functionality described above.
I have just fixed the sample in glassfish-sample svn repository.
Regards,
Shing Wai Chan