Re: 100s of threads stuck in map

OK so I think I found my issue

https://issues.apache.org/jira/browse/VELOCITY-718

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422


On Fri, Jul 20, 2012 at 8:40 AM, Jason Tesser <[email protected]> wrote:
> So I guess the code in question is this
>
>         private final Map cache = new HashMap();
>
> ........
>
>         public Method get(final String name, final Object [] params)
>                 throws MethodMap.AmbiguousException
>         {
>             String methodKey = makeMethodKey(name, params);
>
>             Object cacheEntry = cache.get(methodKey);
>
> Maybe this should be a concurrentMap?
>
> Thanks,
> Jason Tesser
> dotCMS Director, Support Services
> 1-305-858-1422
>
>
> On Fri, Jul 20, 2012 at 8:37 AM, Jason Tesser <[email protected]> wrote:
>> correction we are running 1.6.3
>>
>> Thanks,
>> Jason Tesser
>> dotCMS Director, Support Services
>> 1-305-858-1422
>>
>>
>> On Fri, Jul 20, 2012 at 7:49 AM, Jason Tesser <[email protected]> wrote:
>>> Is Velocity not using a ConcurrentMap here
>>>
>>> "TP-Processor28" daemon prio=10 tid=0x00007fa0ac027bd0 nid=0x44f4
>>> runnable [0x00007fa0f9368000]
>>>    java.lang.Thread.State: RUNNABLE
>>>         at java.util.HashMap.get(HashMap.java:303)
>>>         at org.apache.velocity.util.introspection.ClassMap$MethodCache.get(ClassMap.java:249)
>>>         at org.apache.velocity.util.introspection.ClassMap.findMethod(ClassMap.java:102)
>>>         at org.apache.velocity.util.introspection.IntrospectorBase.getMethod(IntrospectorBase.java:105)
>>>         at org.apache.velocity.util.introspection.Introspector.getMethod(Introspector.java:94)
>>>
>>> I see 100s of threads on a fresh start stuck here. This is 1.7
>>>
>>> Thanks,
>>> Jason Tesser
>>> dotCMS Director, Support Services
>>> 1-305-858-1422