Il giorno 12/nov/09, alle ore 17:54, gustav trede ha scritto:
>
>
> 2009/11/12 rama.rama_at_tiscali.it <rama.rama_at_tiscali.it>
> Hi all,
>
> i am doing some test with 1.9.18-f gws.
>
>
> I have configured it
> as follow
> maxThread = 24
> jdk 1.6_13
> use of 1 asyncfilter
> use of 1
> grizzllyresadapter
>
>
> basically after a stress test, i have found that
> all the workerTread lock on a common point (forever) and GWS stop to
> serve requests.
>
> This is where the lock happen
>
>
> ----WAITING THREAD
> (uin this case workerthread(2))--------
> com.sun.grizzly.util.
> SyncThreadPool$SyncThreadWorker.getTask()
> com.sun.grizzly.util.
> AbstractThreadPool$Worker.doWork()
> com.sun.grizzly.util.
> AbstractThreadPool$Worker.run()
>
> -------owning thread (in this case
> workerthread(95)---
> java.util.Queue.offer(java.lang.Object)
> com.sun.
> grizzly.util.SyncThreadPool.execute(java.lang.Runnable)
> java.util.
> concurrent.ExecutorService.execute(java.lang.Runnable)
> com.sun.grizzly.
> http.TaskBase.execute()
> com.sun.grizzly.arp.DefaultAsyncHandler.handle
> (com.sun.grizzly.http.Task)
> com.sun.grizzly.arp.AsyncProtocolFilter.
> execute(com.sun.grizzly.Context)
> com.sun.grizzly.DefaultProtocolChain.
> executeProtocolFilter(com.sun.grizzly.Context, int)
> com.sun.grizzly.
> DefaultProtocolChain.execute(com.sun.grizzly.Context, int)
> com.sun.
> grizzly.DefaultProtocolChain.execute(com.sun.grizzly.Context)
> com.sun.
> grizzly.http.HttpProtocolChain.execute(com.sun.grizzly.Context)
> com.sun.
> grizzly.ProtocolChainContextTask.doCall()
> com.sun.grizzly.
> SelectionKeyContextTask.call()
> com.sun.grizzly.ContextTask.run()
> java.
> lang.Runnable.run()
> com.sun.grizzly.util.AbstractThreadPool$Worker.
> doWork()
> com.sun.grizzly.util.AbstractThreadPool$Worker.run()
>
>
> that's
> quite strange, right now the thread are locked for 456s :)
>
> some other
> information
> os = win
> n*cpu core = 4
> ram = 4gb heap = 1gb
>
>
>
> any
> suggestion is appreciated :)
>
> Does it help to use latest jdk6 and 7 builds ?.
> In older jdks, some problems with concurrent datastructures are not
> fixed.
>
> --
> regards
> gustav trede
>
>
Unfortunatly note, use tle latest jdk cause jit compiler to crash on
my app (on linux, i have already forwarded the hs_error_log to this ml
and to the jdk support).
In any case, using the latest jdk on win doesn't cause the crash, but
the lock is still present :S
This kind of lock is only present under high load, if this can be of
any help!
Warm Regards
Rama