CDV ❯ On client reconnect: com.tc.exception.TCRuntimeException: com.tc.net.protocol.TCProtocolException: Bad magic number: 16908316 != -1145324613

• Type: Bug
• Status: Closed
• Priority: 2 Major
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee:
• Reporter:
• Created: December 04, 2007
• Votes: 0
• Watchers: 1
• Updated:

  July 27, 2012
• Resolved:

  April 16, 2008

Description

This is from http://forums.terracotta.org/forums/posts/list/647.page

User reports that it works on 2.4.8

Comments

orion 2007-12-05

I accidentally closed this issue instead of the CRT one.

Fiona OShea 2008-02-20

Kunal I think you worked on this, and that everything is OK there now. Can you confirm and mark resolved if this is the case?

Saravanan Subbiah 2008-02-21

We think this is due to the fact that OOO was configured on one end and not configured on the other.

To avoid such situation, we should get any stack configuration from the server during handshake.

Manoj Govindassamy 2008-02-25

I can think of 2 solutions for this.

1. We should be able to bypass a layer and its processing (here OOO) if the layer is optional based on the sender’s comm stack.

2. During handshaking, the OOO should look for its parallel layer in the peer’s comm stack and if it is not present drop the connection request with proper error messages.

Fiona OShea 2008-02-25

Could be part of Big Giant config re-org. L1 reconnect settings can cause this if different on client/server

Saravanan Subbiah 2008-02-25

Manoj and Raghu are looking at some alternate approaches that we discussed.

Manoj Govindassamy 2008-02-25

will come up with the plan and estimate soon.

Raghvendra Singh 2008-07-21

fixed this issue long back :)