Client throws assertion error when attempting to reconnect to the TCServer -
(assuming l1.reconnect is turned off).
-------------------------------------------------------------------------------------------------------------------
Key: CDV-445
URL: https://jira.terracotta.org/jira//browse/CDV-445
Project: Community Development
Issue Type: Bug
Components: DSO:L1
Affects Versions: 2.4.3
Reporter: Sreenivasan Iyer
Assignee: Issue Review Board
When testing a simple app I unplugged the network cable to see how TC would
react to this.
To my surprise the only thing I noticed on the TC client side were log
statements in the client log files.
After a while I pluged the network cable back in and the client was not able te
reconnect to the server. The server actually stopped with the following mdg
java.lang.AssertionError: Client connected before disconnecting : old Client
state = ClientStateImpl[ChannelID=[3], ObjectIDSet2 [ Range(21000,21002)]]
at
com.tc.objectserver.l1.impl.ClientStateManagerImpl.startupClient(ClientStateManagerImpl.java:176)
at
com.tc.objectserver.handshakemanager.ServerClientHandshakeManager.notifyClientConnect(ServerClientHandshakeManager.java:90)
at
com.tc.objectserver.handler.ClientHandshakeHandler.handleEvent(ClienHandshakeHandler.java:22)
at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:140)
How can a client react when losing the connection with the TC server? how does
TC help?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
