2 Replies Latest reply on Jun 5, 2002 6:58 PM by 800384

    J2EE - IPv6 - progress in error analysis - help still needed

    807596
      Dear all (not answering our cries for help :-)
      here is a liite progress in the analysis in J2EE1.3.1, JDK1.4.0 - IPv6:

      Here is the error on the remote client:

      An exception occured while testing ClinicPublisher: javax.naming.CommunicationException: Can't find SerialContextProvider
      javax.naming.CommunicationException: Can't find SerialContextProvider
      at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:63)



      Our Ethernet monitor shows nicely (on the client side) the GIOP exchange failure:

      The client sends via GIOP a locate requesrt to the server - the server replies:

      Malformed Frame: GIOP

      ==========================

      Frame 27 (121 on wire, 121 captured)
      Ethernet II
      Internet Protocol Version 6
      Transmission Control Protocol, Src Port: 32842 (32842), Dst Port: 1050 (1050), Seq: 1487334332, Ack: 1474209016
      General Inter-ORB Protocol
      Magic number: GIOP
      Version: 1.2
      Flags: 0x00 (big-endian )
      Message type: LocateRequest <===========================
      Message size: 23
      General Inter-ORB Locate Request

      Frame 28 (86 on wire, 86 captured)
      Ethernet II
      Internet Protocol Version 6
      Transmission Control Protocol, Src Port: 1050 (1050), Dst Port: 32842 (32842), Seq: 1474209016, Ack: 1487334367

      Frame 29 (418 on wire, 418 captured)
      Ethernet II
      Internet Protocol Version 6
      Transmission Control Protocol, Src Port: 1050 (1050), Dst Port: 32842 (32842), Seq: 1474209016, Ack: 1487334367
      General Inter-ORB Protocol
      Magic number: GIOP
      Version: 1.2
      Flags: 0x00 (big-endian )
      Message type: LocateReply <==================
      Message size: 320
      General Inter-ORB Locate Reply
      [Malformed Frame: GIOP] <===================



      -----------------------------------------------------


      Any ideas? (Keep in mind - the same appl. worked for v4!!!!)



      Regards


      Yongzheng Liang
      University of Stuttgart
        • 1. Re: J2EE - IPv6 - Problem analyzed -
          807596
          Dear all,


          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
          reference implementation.



          All the best



          Yongzheng Liang
          RUS
          Stuttgart University
          • 2. Re: J2EE - IPv6 - Problem analyzed -
            800384
            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.