[JBoss JIRA] Created: (JBREM-657) Implement versions of Client.removeListener() and Client.disconnect() which do not write to a broken server.
12:35 p.m.
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
4:54 p.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Ovidiu Feodorov updated JBREM-657:
----------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=99461
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
4:39 p.m.
New subject: [JBoss JIRA] Assigned: (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=all ]
Ovidiu Feodorov reassigned JBREM-657:
-------------------------------------
Assignee: Ovidiu Feodorov (was: Ron Sigal)
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: Ovidiu Feodorov
Fix For: 2.2.0.Alpha6
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
4:39 p.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Ovidiu Feodorov updated JBREM-657:
----------------------------------
Fix Version/s: 2.2.0.Alpha6
(was: 2.2.0.Beta1 (Bluto))
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: Ovidiu Feodorov
Fix For: 2.2.0.Alpha6
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
7:23 p.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Ron Sigal updated JBREM-657:
----------------------------
I've added methods Client.disconnectLocal() and Client.removeListenerLocal().
Unit test: org.jboss.test.remoting.shutdown.local.LocalShutdownTestCase.
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: Ovidiu Feodorov
Fix For: 2.2.0.Alpha6
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
3:54 a.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Ovidiu Feodorov updated JBREM-657:
----------------------------------
Assignee: Ron Sigal (was: Ovidiu Feodorov)
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.Alpha6
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
4:16 a.m.
New subject: [JBoss JIRA] Closed: (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=all ]
Ovidiu Feodorov closed JBREM-657.
---------------------------------
Resolution: Done
Good enough for the time being.
We're using both these methods in JMSRemotingConnection.setFailed()
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.Alpha6
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
5:15 p.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Ron Sigal updated JBREM-657:
----------------------------
Fix Version/s: 2.2.0.Beta1 (Bluto)
(was: 2.2.0.Alpha6)
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
5:15 p.m.
New subject: [JBoss JIRA] Reopened: (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=all ]
Ron Sigal reopened JBREM-657:
-----------------------------
As per a suggestion from Tom Elrod, the disconnectLocal() and RemoveListenerLocal()
methods will be eliminated in favor of setting a short timeout for network operations in
disconnect() and removeListener().
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
5:31 p.m.
New subject: [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_12353150 ]
Clebert Suconic commented on JBREM-657:
---------------------------------------
how we will disconnect a client without making a trip to the server without these
methods?
Also.. I guess you should open a new JIRA.. since this was already in a release.. (I
guess)
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
1:33 a.m.
New subject: [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_12353307 ]
Tom Elrod commented on JBREM-657:
----------------------------------
My understanding was the real issue here is that the disconnect() causes a remote call to
be made which takes a long time to actually fail (since the server is dead). Therefore
you were seeing this call taking a long time, which you obviously didn't want. So if
this is the issue, then having a fast fail in the case that the server is dead should
solve the problem, right? If this isn't the issue, maybe can restate for us?
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
9:33 a.m.
New subject: [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_12353364 ]
Clebert Suconic commented on JBREM-657:
---------------------------------------
No.. the issue is we call that method when you know the server is failed... hence we
can't have any sort of communication to server.
When a server fail, our failover aspect kicks in, open a new connection and replace
everything... if we don't close the failed connection Lease keeps sending several
alerts on console about the server can't be reached. (that also affects the
performance somehow)
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
9:47 a.m.
New subject: [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_12353366 ]
Tom Elrod commented on JBREM-657:
----------------------------------
So assume, "if we don't close the failed connection Lease keeps sending several
alerts on console about the server can't be reached" is the real problem. If you
call disconnect(), this won't happen, correct?
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
9:59 a.m.
New subject: [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_12353367 ]
Clebert Suconic commented on JBREM-657:
---------------------------------------
If I called the old version of disconnect, I would receive an exception.
(CannotConnectException) and disconnect would never complete.
That's what this method is about. A way I could call disconnect without receive the
exception.
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
10:01 a.m.
New subject: [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_12353368 ]
Clebert Suconic commented on JBREM-657:
---------------------------------------
I mean.. .for us at this point ... this JIRA was already released... Ron reopened it and
set a new version...
What means... we would loose the feature from a previous version.
(It was a solved problem for us)
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
10:19 a.m.
New subject: [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
11:13 a.m.
New subject: [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_12353381 ]
Clebert Suconic commented on JBREM-657:
---------------------------------------
what will be the API then?
How will be the API to disconnect a client without a server trip, when we know the server
is not available? (Failover)
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
11:59 a.m.
New subject: [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_12353385 ]
Tom Elrod commented on JBREM-657:
----------------------------------
The API for the Client class should be the same it has been for every release, except
Alpha7. If looking for specific cvs version, can reference 1.53.2.21.
So, if we can implement the disconnect() method so that you don't have an exception
thrown and don't have to wait a long time (i.e. under a second), would that work for
you?
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
1:32 p.m.
New subject: [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_12354125 ]
Tim Fox commented on JBREM-657:
-------------------------------
No - I am not happy with a short timeout
We don't want to make failover any slower than it needs to be.
I am now finding that our tests are failing because of this reversion.
Please put it back like it was.
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
5:19 p.m.
New subject: [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_12354224 ]
Ron Sigal commented on JBREM-657:
---------------------------------
The bodies of disconnect() and removeListener() now run in a separate thread so that they
can return immediately.
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
1:34 a.m.
New subject: [JBoss JIRA] Closed: (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=all ]
Ron Sigal closed JBREM-657.
---------------------------
Resolution: Done
The nondeterminism that resulted from putting the network i/o on a separate thread causes
too many problems, so it has been backed out.
Instead, before any network i/o is performed, the value of disconnectTImeout, set by
Client.setDisconnectTImeout(), is checked.
If (disconnectTimeout < 0) then it is ignored
else if (disconnectTimeout == 0) then no network i/o is carried out
else disconnectTimeout is use as a per invocation timeout for the network i/o.
So, if Client.disconnectTimeout == 0, disconnect() and removeListener() behave like the
no longer existent disconnectLocal() and removeListenerLocal().
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
7049
days inactive
7108
days old
20 comments
6 participants
participants (6)
-
Clebert Suconic (JIRA) -
Ovidiu Feodorov (JIRA) -
Ron Sigal (JIRA)
-
Ron Sigal (JIRA)
-
Tim Fox (JIRA)
-
Tom Elrod (JIRA)