HttpBinding semaphore causes a memory leak

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 3.2.3, 3.3.0 Alpha 1, 3.3.0 Beta 1, 3.2.4
  • Fix Version/s: 3.3.0
  • Component/s: None
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

Several users are reporting memory leak issues with HttpBinding and the new Semaphore that is being used to forward packets. I have been unable to reproduce this issue locally.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. JM-1001 Http-binding deadlock

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Guus der Kinderen added a comment -

The current implement of the HttpBinding (including the Semaphores) seems to be triggering: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6460501. Maybe the java Semaphore class should be avoided completely, and use standard Java synchornization instead.

Show
Guus der Kinderen added a comment - The current implement of the HttpBinding (including the Semaphores) seems to be triggering: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6460501. Maybe the java Semaphore class should be avoided completely, and use standard Java synchornization instead.
Hide
Permalink
Alex Wenckus added a comment -

Switched over to using synchronized

Show
Alex Wenckus added a comment - Switched over to using synchronized

People

  • Assignee:
    Alex Wenckus
    Reporter:
    Alex Wenckus
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: