Hi Jeanfrancois,
I see some api changes related to worker thread impl in Grizzly v1.7.3
Basically I think they are incompatible with applications that were
built on v1.7.2. Are we going to adhere to v1.7.2 for Glassfish for
now? (For example, please take a look at attach and detach api calls
which are public in both 1.7.2 and 1.7.3. They have change in signature
:-( ..)
Also, on a different topic, did you / anyone noticed a spurious wake up
from Grizzly worker threads wait for task?? Quite often I see 2
Grizzly worker threads entering almost near the same time into the
ProtocolFitler to read data and thereby causing a race for reading data
while in the ReadFilter. So, it leads to partial data read b/w 2 threads
and hence, causes parsing errors.
Another request is, to strictly give Grizzly based names (conventions)
to threads that are getting started from within Grizzly. This approach
helps in identifying Grizzly generated threads to user generated threads.
thanks,
Harsha