Java 多播接收错误消息

我正在研究多播套接字。在AIX7上使用WebSphere8.0.0.5进行测试。问题是从发件人处收到错误的消息。测试场景为： 1.运行sendMulticast（新线程） 2.运行receiveMulticast（新线程） 3.运行receiveMulticast（新线程）

第一个接收方线程总是接收正确的消息。辅助接收器线程接收到错误消息

但有趣的是，我在同一台机器（AIX7）上使用Java6作为控制台应用程序进行了尝试，一切都正常

代码如下：

    static final int port = 9999;
    static final String multicastAddress = "224.2.2.3";


    public static void sendMulticast()  {
        MulticastSocket socket = null;
        DatagramPacket outPacket = null;
        byte[] outBuf;

        long t= System.currentTimeMillis();

        //run 60 seconds
        long end = t+60000;

        try {
            socket = new MulticastSocket();
            String msg;

            while(System.currentTimeMillis() < end) {
                msg = "//172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA";
                outBuf = msg.getBytes();

                InetAddress address = InetAddress.getByName(multicastAddress);
                outPacket = new DatagramPacket(outBuf, outBuf.length, address, port);

                socket.setTimeToLive(32);
                socket.send(outPacket);


                System.out.println("Server sends : " + msg);
                try {
                    Thread.sleep(500);
                } catch (InterruptedException ie) {
                }
            }
        } catch (IOException ioe) {
            ioe.printStackTrace();
        }
        socket.close();
    }


    public static void receiveMulticast() {
        MulticastSocket socket = null;
        DatagramPacket packet = null;
        byte[] inBuf = new byte[1500];

        long t= System.currentTimeMillis();

        //run 60 seconds
        long end = t+60000;

        try {
            // Prepare to join multicast group
            socket = new MulticastSocket(port);
            InetAddress address = InetAddress.getByName(multicastAddress);
            socket.joinGroup(address);

            while(System.currentTimeMillis() < end) {
                packet = new DatagramPacket(inBuf, inBuf.length);
                socket.receive(packet);
                byte[] payload = packet.getData();
                String msg = new String(payload);
                System.out.println("From " + packet.getAddress() + " Msg : " + msg);
            }
        } catch (IOException ioe) {
            ioe.printStackTrace();
        }

        socket.close();
    }

---

网络上似乎有另一个发送者，无论如何，您不应该在websphere中打开任何线程。对于套接字，您可能应该使用JCA资源适配器。我确信我是网络上唯一的发送者（在这个多播地址和端口上），并且我不会在websphere中打开新线程。每个线程都是一个web服务请求，这是什么IP 46.50.52.50？是发送方计算机的另一个IP吗？否此IP地址上没有任何内容。我认为数据报包被破坏了。同时，我在监控网络，只有一个发送者，它是172.21.131.242在包被发送后，你有没有可能开始监听？

[2/20/13 10:39:45:162 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:45:163 EET] 0000003b SystemOut     O From /172.21.131.242 Msg : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:45:665 EET] 0000003b SystemOut     O From /172.21.131.242 Msg : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:45:665 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:46:167 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:46:168 EET] 0000003b SystemOut     O From /172.21.131.242 Msg : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:46:672 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:46:673 EET] 0000003b SystemOut     O From /172.21.131.242 Msg : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:47:173 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:47:174 EET] 0000003b SystemOut     O From /172.21.131.242 Msg : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:47:674 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:47:675 EET] 0000003b SystemOut     O From /46.50.52.50 Msg : CE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA131.242:51860/REFERENCE_DATA
[2/20/13 10:39:47:676 EET] 0000003c SystemOut     O From /172.21.131.242 Msg : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:48:176 EET] 0000003a SystemOut     O Server sends : //172.21.131.242:51860/SERVICE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA
[2/20/13 10:39:48:177 EET] 0000003b SystemOut     O From /46.50.52.50 Msg : CE_EXECUTION_CACHE|//172.21.131.242:51860/ERROR_CODES_CACHE|//172.21.131.242:51860/ACCOUNTING_CACHE|//172.21.131.242:51860/CONFIGURATION_ITEMS_CACHE|//172.21.131.242:51860/REFERENCE_DATA131.242:51860/REFERENCE_DATA