]
Ron Sigal updated JBREM-690:
----------------------------
Fix Version/s: 2.2.0.Beta1 (Bluto)
(was: 2.2.0.Alpha7)
Affects Version/s: 2.2.0.Beta1 (Bluto)
(was: 2.2.0.Alpha6)
Once the socket of a callback server timeouts, it starts to silently
discard traffic
------------------------------------------------------------------------------------
Key: JBREM-690
URL:
http://jira.jboss.com/jira/browse/JBREM-690
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ovidiu Feodorov
Assigned To: Ron Sigal
Priority: Blocker
Fix For: 2.2.0.Beta1 (Bluto)
Please write the following test (and I actually mean it, please do, and keep it your test
suite):
Create a "socket" transport client and register a listener to it, so the push
callback server is initialized.
Send a callback to the client, to make sure a socket is created and traffic is sent over
it.
Wait enough for the callback socket to timeout (a little bit longer than
ServerInvoker.DEFAULT_TIMEOUT_PERIOD).
Send a new callback to the client.
The callback will be silently discarded, never to be heard of again.
For the Messaging version of this bug, please see
http://jira.jboss.org/jira/browse/JBMESSAGING-371 and the associated RemotingTest.test
testMessageListenerTimeout()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: