This content has been marked as final. Show 2 replies
after upgrading our ethereal monitor (there was a "malformed frame" bug discussion
on the list :-) we found:
- JNDI :
IPv6 based request-reply (GIOP) exchange between client and server (probably correct)
- "the rest of J2EE":
After the JNDI exchanges suddenly an IPv4 based IIOP based request was issued from
the client and from then on all traffic was IPv4 based -
so, I guess, this is more a question for Sun about the capabilities of the latest J2EE
All the best
I believe here, that you have a good understanding of networks and their parts.
A Frame in a network is a packet structure. It includes headers, data, and optionally trailers that are processed by the protocol stack on the source and destination nodes. The protocol used is determined by the incomming structure of a frame. If that frame is not of a known type, the protocol sends an error code. This is most likely causing the Mailformed Frame exception.
Answer: For some reason, somewhere along the way from the source to the destination, the frame was either "damaged" by the sending node, receiveing node, or an intermediate node.
Do a test run on a small 3-4 node network, see if the error occurs again. If so, it's probably the source node causing the error. If not, then talk to the network engineer and see about possible protocol errors or abnormalities that may be encounterd along the way.
I have found the biggest error-producing node to be a Bridge between two vary different networks.