[jboss-jira] [JBoss JIRA] Commented: (JBREM-657) Implement versions of Client.removeListener() and Client.disconnect() which do not write to a broken server.
[ http://jira.jboss.com/jira/browse/JBREM-657?page=comments#action_12353369 ]
Tom Elrod commented on JBREM-657:
----------------------------------
Ok. I understand what the root issue is now. Thanks.
The problem with the previous change that resolved this problem is it introduced an API
change that wasn't really needed (as can be fixed without having to add new disconnect
methods). Since that change is only visible between one alpha release (think was made in
the last alpha 7 release), I think it would be better to roll back to the original API
before beta, cr, or ga releases go out.
Implement versions of Client.removeListener() and Client.disconnect()
which do not write to a broken server.
------------------------------------------------------------------------------------------------------------
Key: JBREM-657
URL: http://jira.jboss.com/jira/browse/JBREM-657
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
From Clebert Suconic:
When a server is killed and failover is processed, we don't have at this
point a way to disconnect a client from a dead server. I tried to call
disconnect on those clients after failover and remoting does a socket
communication.
It looks we would need a new feature/new method such as
client.removeLeases or client.disconnect(false); false means = send data
or any other similar way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira