Hi Rama,
I think this bug is not related to spinning, but to [1].
Gustav has commited the fix to the 1.9.15 workspace. Can you pls. try
to build it from sources and check if you still see the problem?
Thank you.
WBR,
Alexey.
[1]
https://grizzly.dev.java.net/issues/show_bug.cgi?id=547
On Apr 26, 2009, at 23:02 , rama wrote:
>
> Hi again,
>
> i am reply to myself, sorry.
>
> After a bit of crawling about this issue, for me it could be related
> to
> "SPINNING PROBLEM"
> or something like that (i have read mailing list quite a bit in this
> hours, so sorry if i wrote a wrong name)
>
> Anyway, Jeanfrancois in one of his messages report that this issue
> can be related to java 1.6.
>
> The problem is that unfortunatly under debian etch, upgrading to 1.7
> isn't really easy (it require glibc 2.4, that isn't included on etch
> and upgrading glibc by hand is quite a long task) also, i don't
> think that 1.7 is production ready, i am right?
>
> So, i have try an early access to 1.6 (to 1.6 v 14b05 dated
> 23-04-09), but unfortunatly the problem persist :(
>
> At this point the question are
> 1) do you think that the issue can be related to SPINNING PROBLEM?
> 2) there is something that i can do as a dirty workaround for this
> issue?
>
>
> Sorry to write 2 msg in a row, but i am a bit worried since this bug
> will block the production setup of monday :(
>
>
>
>> Hello,
>>
>> i am having some issue with gws vers 1.9.14, on linux (seems
>> that on win i haven't that issue)
>> i am using 1.6.0 b13.
>>
>> let me give to
>> you more information and explain what's up.
>>
>>
>> after a while, without
>> any apparent error on logging, gws became very slow.
>>
>> after a bit of
>> profiling i have get some of this line
>>
>> 12:08.653 30 s Blocked 428
>> java.lang.Object GrizzlySelectorRunner-TCP [Grizzly] http5480-
>> WorkerThread(39) [Grizzly]
>> 12:05.843 33 s Blocked 427 java.lang.Object
>> GrizzlySelectorRunner-TCP [Grizzly] http5480-WorkerThread(24)
>> [Grizzly]
>>
>>
>> that say that
>> GrizzlySelectorRunner-TCP [Grizzly] THREAD
>> WorkerThread
>> (24) [Grizzly] TCP
>>
>> also some other like
>> 12:50.186 84 s Blocked 116
>> java.util.HashSet http5480-WorkerThread(44) [Grizzly]
>> GrizzlySelectorRunner-TCP [Grizzly]
>>
>> the problem isn't that there are
>> some lock, but that the lock last for 84Seconds!!
>>
>> i'll also add a
>> stacktrace (sorry, it's very big, i add a zip, i have try to put 6
>> reader, many worker threads, to do a work around, but without
>> successs)
>>
>>
>> if someone can give to me some idea, i'll really appreciate
>>
>>
>> <
>> putty
>> .zip
>> >
>> <
>> putty
>> .zip
>> >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>