Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 37280 invoked from network); 20 Nov 2009 18:46:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Nov 2009 18:46:17 -0000 Received: (qmail 93911 invoked by uid 500); 20 Nov 2009 18:46:17 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 93881 invoked by uid 500); 20 Nov 2009 18:46:17 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 93871 invoked by uid 99); 20 Nov 2009 18:46:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 18:46:17 +0000 X-ASF-Spam-Status: No, hits=-1998.5 required=10.0 tests=ALL_TRUSTED,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 18:46:14 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id ACFDB234C052 for ; Fri, 20 Nov 2009 10:45:52 -0800 (PST) Message-ID: <1200609316.1258742752701.JavaMail.jira@brutus> Date: Fri, 20 Nov 2009 10:45:52 -0800 (PST) From: "Bruce Snyder (JIRA)" To: dev@activemq.apache.org Subject: [jira] Updated: (AMQ-1359) ActiveMQ 4.1.1 client can write to but not read from ActiveMQ 5.0 server In-Reply-To: <10624877.1186599901886.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder updated AMQ-1359: ------------------------------ Description: I have some code that worked fairly well with the release version of ActiveMQ 4.1 using OpenWire. One of my colleagues upgraded the server to the latest snapshot of ActiveMQ 5, and suddenly while I could still write to the queues on that server I could no longer read from them. Upgrading my client's jar to 5.0 cured the problem. The client was now able to read from and write to the 5.0 server. However the client and server versions should not need to be in such close sync. For example, this simple program to write a couple of messages and then read them back fails until I change the jar archive to match the server's: {code} import javax.jms.*; import org.apache.activemq.*; import org.apache.activemq.command.*; public class CompletedRead { private static String url = "tcp://queue.example.com:61616"; private static String queue = "foo"; public static void main(String[] args) throws JMSException { ConnectionFactory out = new ActiveMQConnectionFactory(url); Connection connection = out.createConnection(); Destination destination = new ActiveMQQueue( queue ); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageProducer producer = session.createProducer(destination); TextMessage message = session.createTextMessage(); message.setText("118652"); producer.send(message); message.setText("118653"); producer.send(message); producer.close(); session.close(); connection.close(); receive(); } private static void receive() throws JMSException { ConnectionFactory in = new ActiveMQConnectionFactory(url); Connection connection = in.createConnection(); Destination destination = new ActiveMQQueue( queue ); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageConsumer consumer = session.createConsumer(destination); TextMessage message = (TextMessage) consumer.receive(10000); System.out.println(message.getText()); message = (TextMessage) consumer.receive(10000); System.out.println (message.getText()); consumer.close(); session.close(); connection.close(); } {code} was: I have some code that worked fairly well with the release version of ActiveMQ 4.1 using OpenWire. One of my colleagues upgraded the server to the latest snapshot of ActiveMQ 5, and suddenly while I could still write to the queues on that server I could no longer read from them. Upgrading my client's jar to 5.0 cured the problem. The client was now able to read from and write to the 5.0 server. However the client and server versions should not need to be in such close sync. For example, this simple program to write a couple of messages and then read them back fails until I change the jar archive to match the server's: import javax.jms.*; import org.apache.activemq.*; import org.apache.activemq.command.*; public class CompletedRead { private static String url = "tcp://queue.example.com:61616"; private static String queue = "foo"; public static void main(String[] args) throws JMSException { ConnectionFactory out = new ActiveMQConnectionFactory(url); Connection connection = out.createConnection(); Destination destination = new ActiveMQQueue( queue ); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageProducer producer = session.createProducer(destination); TextMessage message = session.createTextMessage(); message.setText("118652"); producer.send(message); message.setText("118653"); producer.send(message); producer.close(); session.close(); connection.close(); receive(); } private static void receive() throws JMSException { ConnectionFactory in = new ActiveMQConnectionFactory(url); Connection connection = in.createConnection(); Destination destination = new ActiveMQQueue( queue ); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageConsumer consumer = session.createConsumer(destination); TextMessage message = (TextMessage) consumer.receive(10000); System.out.println(message.getText()); message = (TextMessage) consumer.receive(10000); System.out.println (message.getText()); consumer.close(); session.close(); connection.close(); } > ActiveMQ 4.1.1 client can write to but not read from ActiveMQ 5.0 server > ------------------------------------------------------------------------ > > Key: AMQ-1359 > URL: https://issues.apache.org/activemq/browse/AMQ-1359 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.0.0 > Reporter: Elliotte Rusty Harold > Fix For: AGING_TO_DIE > > > I have some code that worked fairly well with the release version of ActiveMQ 4.1 using OpenWire. One of my colleagues upgraded the server to the latest snapshot of ActiveMQ 5, and suddenly while I could still write to the queues on that server I could no longer read from them. > Upgrading my client's jar to 5.0 cured the problem. The client was now able to read from and write to the 5.0 server. However the client and server versions should not need to be in such close sync. > For example, this simple program to write a couple of messages and then read them back fails until I change the jar archive to match the server's: > {code} > import javax.jms.*; > import org.apache.activemq.*; > import org.apache.activemq.command.*; > public class CompletedRead { > > private static String url = "tcp://queue.example.com:61616"; > private static String queue = "foo"; > public static void main(String[] args) throws JMSException { > > ConnectionFactory out = new ActiveMQConnectionFactory(url); > Connection connection = out.createConnection(); > Destination destination = new ActiveMQQueue( queue ); > connection.start(); > Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > MessageProducer producer = session.createProducer(destination); > TextMessage message = session.createTextMessage(); > message.setText("118652"); > producer.send(message); > message.setText("118653"); > producer.send(message); > > producer.close(); > session.close(); > connection.close(); > > receive(); > } > private static void receive() throws JMSException { > ConnectionFactory in = new ActiveMQConnectionFactory(url); > Connection connection = in.createConnection(); > Destination destination = new ActiveMQQueue( queue ); > connection.start(); > Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > > MessageConsumer consumer = session.createConsumer(destination); > TextMessage message = (TextMessage) consumer.receive(10000); > System.out.println(message.getText()); > message = (TextMessage) consumer.receive(10000); > System.out.println (message.getText()); > > consumer.close(); > session.close(); > connection.close(); > > } > {code} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.