Issue Details (XML | Word | Printable)

Key: XADISK-152
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Nitin Verma
Reporter: Nitin Verma
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
xadisk

When using clustering, the sessions do not close connections to the master concurrency control.

Created: 14/Oct/13 04:52 PM   Updated: 15/Oct/13 08:46 AM   Resolved: 15/Oct/13 08:46 AM
Component/s: filesystem
Affects Version/s: 1.2.2
Fix Version/s: current

Time Tracking:
Not Specified

Tags:
Participants: Nitin Verma


 Description  « Hide

When using clustering, the sessions created in the slave xadisk instances depend upon the concurrency-control of the master xadisk instance. If the master xadisk instance is a remote one, a proxy named RemoteConcurrencyControl is handed over to the sessions for the same. As this proxy object encapsulate a communication channel, so a new proxy object (hence a new channel) is needed for every such session. But sessions do not disconnect from these remote proxy objects. This leads to accumulation of channels, conversation-context (and their hosted object contexts) etc. Hence memory "leaks".

Solution is to disconnect from remote-concurrency-control as a session is done (eg in cleanup).



Nitin Verma added a comment - 15/Oct/13 08:46 AM

Checked-in the changes to trunk. Revision #557.