On Oct 6, 2006, at 11:10 AM, sksamuel wrote:

> My resin installation is going into deadlock at least once a day.
>
> I have a thread dump that shows the TCP threads are waiting on for  
> a lock at
> com.caucho.log.StreamHandler.publish(StreamHandler.java:112).
>
> Is that normal? Is that just Resin waiting to lock the log file for  
> output
> and I can rule this out? Or is there something more serious going on?

Which version?

Also, try to find the thread that owns that lock and send it so we  
can see what it's doing.  Deadlocks are important.

-- Scott

>
>
>
> "resin-tcp-connection-*:80-39" daemon prio=1 tid=0x09e12430 nid=0x340e
> waiting for monitor entry [0xa624a000..0xa624af30]
>  at com.caucho.log.StreamHandler.publish(StreamHandler.java:112)
>  - waiting to lock <0x67f80098> (a com.caucho.vfs.WriteStream)
>  at com.caucho.log.SubHandler.publish(SubHandler.java:73)
>  at java.util.logging.Logger.log(Logger.java:452)
>  at com.caucho.log.EnvironmentLogger.log(EnvironmentLogger.java:323)
>  at java.util.logging.Logger.doLog(Logger.java:474)
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest


_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to