Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 51647 invoked from network); 2 Nov 2010 12:04:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 12:04:53 -0000 Received: (qmail 33012 invoked by uid 500); 2 Nov 2010 12:05:24 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 32831 invoked by uid 500); 2 Nov 2010 12:05:21 -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 32821 invoked by uid 99); 2 Nov 2010 12:05:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 12:05:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 12:05:20 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA2C50lG005888 for ; Tue, 2 Nov 2010 12:05:00 GMT Message-ID: <23726928.4531288699500155.JavaMail.jira@thor> Date: Tue, 2 Nov 2010 08:05:00 -0400 (EDT) From: "Norman Maurer (JIRA)" To: dev@activemq.apache.org Subject: [jira] Updated: (AMQ-3010) ActiveMQInputStream should allow to specify a timeout like MessageConsumer.receive() does In-Reply-To: <21964188.4511288699260611.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c [ https://issues.apache.org/activemq/browse/AMQ-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Maurer updated AMQ-3010: ------------------------------- Attachment: AMQ-3010.diff The attached patch allows to the user/dev to configure a timeout for the first chunk of data. So if the data is not received within the timeout an ReadTimeoutExecption get thrown. This allows the user/dev to handle it a custom way > ActiveMQInputStream should allow to specify a timeout like MessageConsumer.receive() does > ----------------------------------------------------------------------------------------- > > Key: AMQ-3010 > URL: https://issues.apache.org/activemq/browse/AMQ-3010 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker > Reporter: Norman Maurer > Attachments: AMQ-3010.diff > > > When using ActiveMQInputStream you are not able todo some kind of polling consuming. As soon as you call ActiveMQInputStream.read() it will block until it receive a message. So it could block forever. Sometime it would be usefull to allow some kind of polling even when using a stream. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.