transportConnector using multicast ---------------------------------- Key: AMQ-944 URL: https://issues.apache.org/activemq/browse/AMQ-944 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0.2, 4.0.1 Environment: A network that supports multicast Reporter: Gabriel Kastenbaum Priority: Blocker It seems that one can nto use multicast in a transportConnector. Description of the test: In the distribution, go into /example Edit the build.xml in order to use multicast. for instance Change the URL in the build.xml to : Start the producer: ant producer Here is the output: [echo] Running producer against server at $url = multicast://225.0.0.1:61620 for subject $subject = Syntheses [java] Connecting to URL: multicast://225.0.0.1:61620 [java] Publishing a Message with size 1000 to queue: Syntheses [java] Using non-durable publishing [java] Sleeping between publish 0 ms [java] DEBUG MulticastTransport - Joining multicast address: /225.0.0.1 [java] DEBUG UdpTransport - Consumer thread starting for: multicast://225.0.0.1:61620@0 [java] DEBUG UdpTransport - Sending oneway from: multicast://225.0.0.1:61620@0 to target: /225.0. 0.1:61620 command: ConnectionInfo {commandId = 1, responseRequired = true, connectionId = ID:ZOZMA-2042-1159347487015-0: 0, clientId = ID:ZOZMA-2042-1159347487015-1:0, userName = null, password = null, brokerPath = null, brokerMasterConnecto r = false, manageable = true} [java] DEBUG DefaultReplayBuffer - Adding command ID: 1 to replay buffer: org.apache.activemq.transport. reliable.DefaultReplayBuffer@1b3f829 object: [B@698403 [java] DEBUG CommandDatagramSocket - Channel: multicast://225.0.0.1:61620@0 sending datagram: 1 to: /225.0 .0.1:61620 [java] DEBUG CommandDatagramSocket - Channel: multicast://225.0.0.1:61620@0 about to process: ConnectionIn fo {commandId = 1, responseRequired = true, connectionId = ID:ZOZMA-2042-1159347487015-0:0, clientId = ID:ZOZMA-2042-115 9347487015-1:0, userName = null, password = null, brokerPath = null, brokerMasterConnector = false, manageable = true} [java] DEBUG ReliableTransport - Still waiting for response on: multicast://225.0.0.1:61620@0 to comma nd: ConnectionInfo {commandId = 1, responseRequired = true, connectionId = ID:ZOZMA-2042-1159347487015-0:0, clientId = I D:ZOZMA-2042-1159347487015-1:0, userName = null, password = null, brokerPath = null, brokerMasterConnector = false, mana geable = true} sending replay message [java] DEBUG UdpTransport - Sending oneway from: multicast://225.0.0.1:61620@0 to target: /192.9. 211.39:61620 command: ReplayCommand {commandId = 2, firstNakNumber = 1, lastNakNumber = 1} [java] DEBUG DefaultReplayBuffer - Adding command ID: 2 to replay buffer: org.apache.activemq.transport. reliable.DefaultReplayBuffer@1b3f829 object: [B@d02b51 [java] DEBUG CommandDatagramSocket - Channel: multicast://225.0.0.1:61620@0 sending datagram: 2 to: /192.9 .211.39:61620 [java] DEBUG CommandDatagramSocket - Channel: multicast://225.0.0.1:61620@0 about to process: ReplayComman d {commandId = 2, firstNakNumber = 1, lastNakNumber = 1} [java] DEBUG ReliableTransport - Processing replay command: ReplayCommand {commandId = 2, firstNakNumb er = 1, lastNakNumber = 1} [java] DEBUG DefaultReplayBuffer - Buffer: org.apache.activemq.transport.reliable.DefaultReplayBuffer@1b 3f829 replaying messages from: 1 to: 1 * [java] DEBUG CommandDatagramSocket - Channel: multicast://225.0.0.1:61620@0 REDELIVERING datagram: 1 to: / 225.0.0.1:61620* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira