<< Back to previous view

[GLASSFISH-4074] New connection cache for ORB Created: 05/Feb/08  Updated: 18/Oct/12

Status: Open
Project: glassfish
Component/s: orb
Affects Version/s: 4.0
Fix Version/s: future release

Type: New Feature Priority: Blocker
Reporter: Ken Cavanaugh Assignee: Harshad Vilekar
Resolution: Unresolved Votes: 3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,074
Tags: 3_1-exclude
Participants: Harshad Vilekar and Ken Cavanaugh

 Description   

Modify the ORB connection management to use the connection cache
in Grizzly. This fixes a number of race conditions in the current
code that can occur when a busy system is using a large number of
connections.



 Comments   
Comment by Ken Cavanaugh [ 05/Feb/08 02:32 PM ]

Fixed target milestone

Comment by Ken Cavanaugh [ 07/Feb/08 09:24 PM ]

V3 PRD

Comment by Ken Cavanaugh [ 22/Sep/09 04:54 PM ]

Not for v3.

Comment by Ken Cavanaugh [ 19/Jan/10 10:47 AM ]

Work in progress for V3.1. Note that the connection caches will be used from
the ORB workspace, not grizzly, as we still don't have sufficient resources
to do the grizzly integration.

Comment by Ken Cavanaugh [ 19/Jan/10 10:48 AM ]
      • Issue 7062 has been marked as a duplicate of this issue. ***
Comment by Ken Cavanaugh [ 19/Jan/10 10:49 AM ]
      • Issue 952 has been marked as a duplicate of this issue. ***
Comment by Ken Cavanaugh [ 14/Sep/10 10:07 AM ]

Moved out of release 3.1.

Comment by Ken Cavanaugh [ 06/Oct/10 04:59 PM ]

Some notes from Some notes from bug 6854220:

  • Would like option to periodically force connections to be closed
    after some period of inactivity (that is already present somewhere
    in the new connection design, I think).
  • Would like option to ALWAYS use fresh connection (this is available in
    HWLB plugin, but better integration would be useful).
    :
  • Would like option to periodically force connections to be closed
    after some period of inactivity (that is already present somewhere
    in the new connection design, I think).
  • Would like option to ALWAYS use fresh connection (this is available in
    HWLB plugin, but better integration would be useful).
Generated at Sat Apr 19 13:25:38 UTC 2014 using JIRA 4.0.2#472.