Salut,
Harsha Godugu wrote:
> 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
> :-( ..)
Yes, we discussed those at the Wednesday meeting after
https://grizzly.dev.java.net/issues/show_bug.cgi?id=109
Alexey talked about it and we decided to have them in 1.7.3.
>
> Also, on a different topic, did you / anyone noticed a spurious wake up
> from Grizzly worker threads wait for task??
No.
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.
Hum...This is expected if your protocol chain is stateless. Is your
protocol filter stateless or statefull?
>
> 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.
File an RFE. I was under the impression the names were already easy to
discover? Any recommendations?
Thanks
-- Jeanfrancois
>
> thanks,
> Harsha