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/25 21:36:01 UTC
[jira] Created: (AXIS-1369) Deadlock in Axis when using HttpClient
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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: Tue, 25 May 2004 12:35 PM
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
[jira] Closed: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Eric Friedman
Date: Tue, 1 Jun 2004 11:07 AM
Added releaseConnection calls in two places: (1) after message is read as string when raising a fault; and (2) in an InputStream wrapper's close() method, in a try {} finally {} block.
---------------------------------------------------------------------
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: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Components:
Basic Architecture
Fix Fors:
current (nightly)
Versions:
1.2 Beta
Assignee: Eric Friedman
Reporter: Daniel Marchant
Created: Tue, 25 May 2004 12:35 PM
Updated: Tue, 1 Jun 2004 11:07 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
[jira] Assigned: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
Message:
The following issue has been re-assigned.
Assignee: Eric Friedman (mailto:ericf@apache.org)
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee: Eric Friedman
Reporter: Daniel Marchant
Created: Tue, 25 May 2004 12:35 PM
Updated: Tue, 1 Jun 2004 11:06 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
[jira] Updated: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Daniel Marchant (mailto:dan@driedtoast.com)
Date: Wed, 26 May 2004 9:16 AM
Comment:
Original File for reference.
Changes:
Attachment changed to CommonsHTTPSender.java.axis-1_2beta
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1369?page=history
---------------------------------------------------------------------
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 9:16 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
[jira] Updated: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Daniel Marchant (mailto:dan@driedtoast.com)
Date: Wed, 26 May 2004 9:15 AM
Comment:
Source file
Changes:
Attachment changed to CommonsHTTPSender.java.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1369?page=history
---------------------------------------------------------------------
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 9:15 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
[jira] Commented: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
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
[jira] Commented: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Daniel Marchant
Created: Wed, 26 May 2004 9:43 AM
Body:
Actually the .axis-beta file is the patch and the
.patch is the original. Oops, sorry about the confusion.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1369?page=comments#action_35736
---------------------------------------------------------------------
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 9:43 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
[jira] Commented: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Daniel Marchant
Created: Wed, 26 May 2004 9:19 AM
Body:
I added a patch to fix the deadlock issue.
I used the same type of approach as Brian Ewins did with his patch.
So the addition of some of his concepts could be applied to fix them both at the same time.
Reference of his patch suggestion: http://nagoya.apache.org/jira/browse/AXIS-238?page=history
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1369?page=comments#action_35735
---------------------------------------------------------------------
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 9:19 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
[jira] Updated: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Daniel Marchant (mailto:dan@driedtoast.com)
Date: Wed, 26 May 2004 9:48 AM
Comment:
Add a onStreamClose method to allow for subclasses to have access to this event. Will help other developers to clean connections and such :)
Changes:
Attachment changed to CommonsHTTPSender.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1369?page=history
---------------------------------------------------------------------
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 9:48 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
[jira] Updated: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Daniel Marchant (mailto:dan@driedtoast.com)
Date: Wed, 26 May 2004 9:15 AM
Comment:
patch unix diff of old an new for the bug change
Changes:
Attachment changed to httpclient_patch.diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1369?page=history
---------------------------------------------------------------------
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 9:15 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
[jira] Updated: (AXIS-1369) Deadlock in Axis when using HttpClient
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Daniel Marchant (mailto:dan@driedtoast.com)
Date: Wed, 26 May 2004 11:15 AM
Comment:
Would help is the message was using the FilterInputStream :)
Changes:
Attachment changed to CommonsHTTPSender.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1369?page=history
---------------------------------------------------------------------
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 11:15 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