Re: Blocking in WeakIdentityMap

>
> against the same service method as fast as they can. Once we hit about
> 15 concurrent threads (service clients), we see (in the profiler)
> quite a lot of waiting on monitors for the server's threads. Using
>
It would be helpful to see the rest of the threads (especially the one
that owns the monitor). Could you provide a more complete stack dump?
>
> "http-8080-Processor12" daemon prio=10 tid=0xacf75400 nid=0x5605
> waiting for monitor entry [0xaca83000..0xaca84030]
>   java.lang.Thread.State: BLOCKED (on object monitor)
>        at
> net.jini.security.policy.DynamicPolicyProvider.getDomainPermissions(DynamicPolicyProvider.java:259)
>
>        - waiting to lock <0xae6ec030> (a
> com.sun.jini.collection.WeakIdentityMap)
>        at
> net.jini.security.policy.DynamicPolicyProvider.implies(DynamicPolicyProvider.java:170)
>
>        at
> com.sun.jini.start.AggregatePolicyProvider.implies(AggregatePolicyProvider.java:201)
>
>        at
> java.security.ProtectionDomain.implies(ProtectionDomain.java:213)
> --
>        at java.lang.Thread.run(Thread.java:619)
>
> --------------------------------------------------------------------------
>
> Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
> Community Web Site:  http://jini.org
> jini-users Archive:
> http://archives.java.sun.com/archives/jini-users.html
> Unsubscribing:       email "signoff JINI-USERS"  to [email protected]


--
- vinod

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]