You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/05/26 17:36:03 UTC

[jira] Commented: (AXIS-1369) Deadlock in Axis when using HttpClient

The following comment has been added to this issue:

     Author: Daniel Marchant
    Created: Wed, 26 May 2004 8:35 AM
       Body:
Looks like this is related to http://nagoya.apache.org/jira/browse/AXIS-238 so this seems like it is a duplicate.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1369?page=comments#action_35728

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1369

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1369
    Summary: Deadlock in Axis when using HttpClient
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Daniel Marchant

    Created: Tue, 25 May 2004 12:35 PM
    Updated: Wed, 26 May 2004 8:35 AM
Environment: Solaris 2.8; jdk 1.3.1; httpclient 2.0 rc2

Description:
After running some tests against the Axis client, came across an issue with monitor locking in HttpClient. Researched the issue with the HttpClient and deadlocks and the resolution was to releaseConnection. (reference http://issues.apache.org/bugzilla/show_bug.cgi?id=27434)

While looking through the Axis 1.2 Beta code I couldn't find where it released the connection. 

Possible resolution could be in (org.apache.axis.transport.http.CommonsHTTPSender) line 203 ish to add a wrapper to the Message that would contain the Connection Manager, this way down the chain some other handler can release the connection manager. I'll let you guys work out that kind of detail though :)


"Thread-266" daemon prio=5 tid=0x58b4d0 nid=0x1aa waiting on monitor 
[0xcef7f000
..0xcef7fc68]
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
        at 
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$Refe
renceQueueThread.run(MultiThreadedHttpConnectionManager.java:732)

"Thread-257" daemon prio=5 tid=0x63c1b0 nid=0x1a1 waiting on monitor 
[0xcf07f000
..0xcf07fc68]
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira