• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOWorkerThread deadlocks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOWorkerThread deadlocks


  • Subject: Re: WOWorkerThread deadlocks
  • From: Miguel Arroz <email@hidden>
  • Date: Mon, 10 Sep 2012 10:13:40 -0700

Hi,

  Isn't that normal? Only one thread can be accepting at any time, when it accepts, it releases the lock for the next one to enter the accept state. I think those are not the threads you are looking for…

  Regards,

Miguel Arroz

On 2012-09-10, at 8:03 AM, Maik Musall <email@hidden> wrote:

> Hi,
>
> in an app with high concurrency, the app sometimes becomes unresponsive to everything but DirectActions at the time of day with the most concurrency. All users aren't seeing responses any more. In jstack I see hundreds of these:
>
>> "WorkerThread207" prio=5 tid=131e0a800 nid=0x151aa2000 waiting for monitor entry [151aa1000]
>>   java.lang.Thread.State: BLOCKED (on object monitor)
>> 	at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
>> 	- waiting to lock <20d3da450> (a java.net.SocksSocketImpl)
>> 	at java.net.ServerSocket.implAccept(ServerSocket.java:462)
>> 	at java.net.ServerSocket.accept(ServerSocket.java:430)
>> 	at com.webobjects.appserver._private.WOWorkerThread.run(WOWorkerThread.java:210)
>> 	at java.lang.Thread.run(Thread.java:680)
>
> all waiting on the same lock 20d3da450, and one thread holding that lock:
>
>> "WorkerThread206" prio=5 tid=131d79800 nid=0x15199f000 runnable [15199e000]
>>   java.lang.Thread.State: RUNNABLE
>> 	at java.net.PlainSocketImpl.socketAccept(Native Method)
>> 	at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
>> 	- locked <20d3da450> (a java.net.SocksSocketImpl)
>> 	at java.net.ServerSocket.implAccept(ServerSocket.java:462)
>> 	at java.net.ServerSocket.accept(ServerSocket.java:430)
>> 	at com.webobjects.appserver._private.WOWorkerThread.run(WOWorkerThread.java:210)
>> 	at java.lang.Thread.run(Thread.java:680)
>
> Anyone familiar with this problem?
>
> Maik
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >WOWorkerThread deadlocks (From: Maik Musall <email@hidden>)

  • Prev by Date: Re: Community "bounties"
  • Next by Date: Re: Eclipse source of problems?
  • Previous by thread: WOWorkerThread deadlocks
  • Next by thread: Re: WOWorkerThread deadlocks
  • Index(es):
    • Date
    • Thread