1:04 a.m.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:09 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=comments#action_12365987 ]
Ron Sigal commented on JBREM-757:
---------------------------------
The test for disconnectTimeout >= 0, found in removeListener() for push callbacks, has
been added for pull callbacks.
Unit test: two new methods have been added to
org.jboss.test.remoting.timeout.QuickDisconnectClientParent. They run in
org.jboss.test.remoting.transport.http.timeout.HttpQuickDisconnectClient and
org.jboss.test.remoting.transport.socket.timeout.SocketQuickDisconnectClient.
Note: the same tests should be implemented for the RMI transport when per invocation
timeouts are implemented for RMI.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal updated JBREM-757:
----------------------------
Fix Version/s: 2.2.2.GA
Affects Version/s: 2.2.0.SP4
2.2.1.GA
Changes ported for Remoting 2.2.2.GA.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:05 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=comments#action_12374880 ]
Ron Sigal commented on JBREM-757:
---------------------------------
The test method additions did not properly test polled callbacks.
Now, testQuickRemoveListener has been split into testQuickRemovePushListener() and
testQuickRemovePullListner, and testQuickRemoveListenerZeroTimeout has been split into
testQuickRemovePushListenerZeroTimeout and testQuickRemovePullListenerZeroTimeout. For
transports that are not bidirectional, quick versions of Client.disconnect() and quick
Client.removeListener() will be tested for polled callbacks.
Also, unit tests have been added for the bisocket transport.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:12 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal updated JBREM-757:
----------------------------
Fix Version/s: (was: 2.2.2.GA)
Removing fix version 2.2.2.GA, which has been release.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:12 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=comments#action_12374881 ]
Ron Sigal commented on JBREM-757:
---------------------------------
Set log level to DEBUG for SocketQuickDisconnectTestCase in response to cruisecontrol
failure:
http://cruisecontrol.jboss.com/cc/artifacts/jboss-remoting-testsuite-1.4/....
Don't forget to reset it to INFO before closing issue.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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
8:18 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal updated JBREM-757:
----------------------------
Fix Version/s: 2.2.2.GA
(was: 2.4.0.Beta1 (Pinto))
Adding fix version 2.2.2.GA back. No more changes will be made for 2.2.2.GA. The
remaining concerns associated with this issue will be addressed in Remoting 2.4.0 in
conjunction with JBREM-798.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.GA
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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
8:20 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal closed JBREM-757.
---------------------------
Resolution: Done
All further concerns related to this issue will be addressed in Remoting 2.4.0 in
conjunction with JBREM-798.
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.GA
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:55 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal updated JBREM-757:
----------------------------
Fix Version/s: 2.4.0.Beta1 (Pinto)
Added fix version 2.4.0.Beta1 - see JBREM-975 "Make sure all fixes on 2.2 branch are
applied to 2.x branch".
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.GA, 2.4.0.Beta1 (Pinto)
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:55 p.m.
New subject: [JBoss JIRA] Reopened: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal reopened JBREM-757:
-----------------------------
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.GA, 2.4.0.Beta1 (Pinto)
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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:55 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.
[ http://jira.jboss.com/jira/browse/JBREM-757?page=all ]
Ron Sigal closed JBREM-757.
---------------------------
Resolution: Done
Implement quick Client.removeListener() for polled callbacks.
-------------------------------------------------------------
Key: JBREM-757
URL: http://jira.jboss.com/jira/browse/JBREM-757
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick
Client.removeListener() facilities were implemented which impose a per invocation timeout
on any network i/o that occurs during these methods. The per invocation timeout is set by
calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network
i/o is avoided entirely.
However, the quick version of Client.removeListener() was implemented only for push
callbacks. It should also be implemented for pull callbacks.
--
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
6076
days inactive
6415
days old
10 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)