ThreadPool deadlock

[Игорь Бахтояров]

Здравствуйте, Xmlrpc-dev.

In last release i'am found deadlock issue:

java.lang.Throwable: Deadlock Detected:
---------------------------- ThreadName    = XML-RPC-7LockName      = org.apache.xmlrpc.util.ThreadPool$Poolable@1428edfLockOwnerName = XML-RPC Weblistener
---------------------------- ThreadName    = XML-RPC WeblistenerLockName      = org.apache.xmlrpc.util.ThreadPool$Poolable$1@b1efd7LockOwnerName = XML-RPC-7
  at org.apache.xmlrpc.util.ThreadPool$Poolable.start(ThreadPool.java:107)
  at org.apache.xmlrpc.util.ThreadPool.startTask(ThreadPool.java:168)
  at org.apache.xmlrpc.webserver.WebServer.run(WebServer.java:338)
  at java.lang.Thread.run(Thread.java:619)

[Jochen Wiedmann]

It is funny. This problem has been in the code for years, but has
never been brought up by any user. Now we see it three times in a
month ...

Try the latest snapshot, as available from

   https://repository.apache.org/content/repositories/snapshots/org/apache/xmlrpc/

It should be sufficient to replace the "common" jar file.

Jochen


2009/5/18 Игорь Бахтояров <igor@...>:

> Здравствуйте, Xmlrpc-dev.
>
> In last release i'am found deadlock issue:
>
> java.lang.Throwable: Deadlock Detected:
> ---------------------------- ThreadName    = XML-RPC-7LockName      = org.apache.xmlrpc.util.ThreadPool$Poolable@1428edfLockOwnerName = XML-RPC Weblistener
> ---------------------------- ThreadName    = XML-RPC WeblistenerLockName      = org.apache.xmlrpc.util.ThreadPool$Poolable$1@b1efd7LockOwnerName = XML-RPC-7
>  at org.apache.xmlrpc.util.ThreadPool$Poolable.start(ThreadPool.java:107)
>  at org.apache.xmlrpc.util.ThreadPool.startTask(ThreadPool.java:168)
>  at org.apache.xmlrpc.webserver.WebServer.run(WebServer.java:338)
>  at java.lang.Thread.run(Thread.java:619)
>
>
>
>

--
Don't trust a government that doesn't trust you.

[Lars Schnoor]

Hi
I am using the newest snapshot and it reduced the frequency of crashes
considerably, but I still have problems with it from time to time. I did
however not get a chance to check if it is the same deadlock problem as
before.

Lars

Jochen Wiedmann wrote:

> It is funny. This problem has been in the code for years, but has
> never been brought up by any user. Now we see it three times in a
> month ...
>
> Try the latest snapshot, as available from
>
>    https://repository.apache.org/content/repositories/snapshots/org/apache/xmlrpc/
>
> It should be sufficient to replace the "common" jar file.
>
> Jochen
>
>
> 2009/5/18 Игорь Бахтояров <igor@...>:
>  
>> Здравствуйте, Xmlrpc-dev.
>>
>> In last release i'am found deadlock issue:
>>
>> java.lang.Throwable: Deadlock Detected:
>> ---------------------------- ThreadName    = XML-RPC-7LockName      = org.apache.xmlrpc.util.ThreadPool$Poolable@1428edfLockOwnerName = XML-RPC Weblistener
>> ---------------------------- ThreadName    = XML-RPC WeblistenerLockName      = org.apache.xmlrpc.util.ThreadPool$Poolable$1@b1efd7LockOwnerName = XML-RPC-7
>>  at org.apache.xmlrpc.util.ThreadPool$Poolable.start(ThreadPool.java:107)
>>  at org.apache.xmlrpc.util.ThreadPool.startTask(ThreadPool.java:168)
>>  at org.apache.xmlrpc.webserver.WebServer.run(WebServer.java:338)
>>  at java.lang.Thread.run(Thread.java:619)
>>
>>
>>
>>
>>    
>
>
>
>  

[Jochen Wiedmann]

On Mon, May 18, 2009 at 5:41 PM, Lars Schnoor <Lars.Schnoor@...> wrote:

> I am using the newest snapshot and it reduced the frequency of crashes
> considerably, but I still have problems with it from time to time. I did
> however not get a chance to check if it is the same deadlock problem as
> before.

See

  https://issues.apache.org/jira/browse/XMLRPC-168

both for a description of the issue, which is fixed in the snapshot and what we
need if you actually encounter more deadlocks.

Jochen


--
Don't trust a government that doesn't trust you.