Err. Got my mailing lists mixed up. I think this is due to
http://bugs.sun.com/view_bug.do?bug_id=6501158 The suggested workaround has
been to force initialization of your classes in main, before threads are
spawned.
On Sun, May 16, 2010 at 1:18 AM, Jason Hsueh wrote:
> I think this is http://b/
I think this is http://b/issue?id=2267627
On Sat, May 15, 2010 at 10:02 PM, Igor Gatis wrote:
> Agreed. So I guess I need to start looking for the deadlock in my code. Do
> you know any tool to help me out on that?
>
>
> On Sun, May 16, 2010 at 1:38 AM, Christopher Smith wrote:
>
>> Never seen i
Agreed. So I guess I need to start looking for the deadlock in my code. Do
you know any tool to help me out on that?
On Sun, May 16, 2010 at 1:38 AM, Christopher Smith wrote:
> Never seen it before... and the Java code is pretty extensively used.
> Surely someone would have hit this before.
>
> -
Never seen it before... and the Java code is pretty extensively used. Surely
someone would have hit this before.
--Chris
On May 15, 2010, at 9:03 PM, Igor Gatis wrote:
> Have anyone experienced deadlock problems related to Java protobuf generated
> messages static initialization?
>
> My mult
Have anyone experienced deadlock problems related to Java protobuf generated
messages static initialization?
My multithreaded app seems to be stuck around internalBuildGeneratedFileFrom
method. Workaround so far was to move first reference to one of my generated
classes to out side of a synchroniz
