Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0ACBE1747B for ; Mon, 3 Nov 2014 21:41:22 +0000 (UTC) Received: (qmail 40573 invoked by uid 500); 3 Nov 2014 21:41:21 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 40522 invoked by uid 500); 3 Nov 2014 21:41:21 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 40508 invoked by uid 99); 3 Nov 2014 21:41:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2014 21:41:20 +0000 X-ASF-Spam-Status: No, hits=3.1 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_IMAGE_ONLY_16,HTML_MESSAGE,HTML_SHORT_LINK_IMG_2,RCVD_IN_DNSWL_LOW,SPF_PASS,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of burtonator2011@gmail.com designates 209.85.217.178 as permitted sender) Received: from [209.85.217.178] (HELO mail-lb0-f178.google.com) (209.85.217.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2014 21:41:16 +0000 Received: by mail-lb0-f178.google.com with SMTP id f15so11119601lbj.23 for ; Mon, 03 Nov 2014 13:40:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=HbCid4HjzmMm7XEsC8fiGjlwtP6T5yZb6+05Z3YeQsU=; b=cZ6wuZUvq1PA+7BThHoAlxd3Z7ILFPNrUKOfqlzXzyDjlhAmeQdx5P64FpkXciiUEH 9VeTW0PJG6Xao97RpiyURXUKHBIwcpwSdqm0BzkE1tmXzzIjAxW4R7oaZzHUVUo7//xx lcz8UuhVeyo2w66wtWC0q4niHlejuWRr7sG3kskqmDOsG0ZIy1eP/GC7jm9WSv4OtPiv 4plB/OdnsVtpDoCbFiZfChRiKuxFhU4EFOEc2lBO3+KCKfNXA+Lbdt7m4gIKzou5PGdS HQjYSfxFo7E328GKWgOqNHKXa4e6esaYFCHNSkA+qqE01mTAfvB5Z8OVEQun6bXr6jat cO7A== X-Received: by 10.112.210.100 with SMTP id mt4mr7288832lbc.31.1415050855227; Mon, 03 Nov 2014 13:40:55 -0800 (PST) MIME-Version: 1.0 Sender: burtonator2011@gmail.com Received: by 10.112.166.137 with HTTP; Mon, 3 Nov 2014 13:40:35 -0800 (PST) From: Kevin Burton Date: Mon, 3 Nov 2014 13:40:35 -0800 X-Google-Sender-Auth: kfhtEE5sFiCqhohpsB8G-kTJmZ4 Message-ID: Subject: creating a new message once all previous messages have been executed? To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001a11361db690b25f0506fb332f X-Virus-Checked: Checked by ClamAV on apache.org --001a11361db690b25f0506fb332f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I=E2=80=99m curious if there is a good pattern for creating a new messages = once all previous tasks have been properly executed. So say I have 100 A messages which are consumed by a bunch of tasks in your cluster. When all the A tasks have executed, you want to run 1 B task to compute their results. So it=E2=80=99s sort of like map-reduce in a way. I think what I could do is use JMS transactions, and then read the value of an incrementing pointer, when it hits 100, I can create the B task, and then commit() the entire session. --=20 Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com =E2=80=A6 or check out my Google+ profile --001a11361db690b25f0506fb332f--