i think it when i have a lot of t:buffer..
most operation to render a page are read-only..
t:buffer seems to be a write operation..
the write operation causes the lock..
is this so?
can anyone confirm this?
the more t:buffer i use the more locks i have, causing a serious
performance penalty.
Ok the synchronized collection is necessary, but my question goes
towards along the lines of thinking around the box, could it be
that you have something serious going on in one of the setter or getter
methods of a bean which causes a hang or lock on the server side?
Maybe a database related proble
hello to all..
i'm using myfaces 1.1.5 and tomahawak 1.1.5
my application hang frequently
here is a stack on one of my threads
"TP-Processor280" daemon prio=1 tid=0x0889b1e0 nid=0xab2 waiting for
monitor entry [0x2c658000..0x2c659f30]
at java.util.Collections$SynchronizedMap.get(Collection
3 matches
Mail list logo