Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============6133867585299353467=="
MIME-Version: 1.0
To: "[allura:tickets] " <6383@tickets.allura.p.re.sf.net>
From: "Dave Brondsema" <brondsem@users.sf.net>
Reply-To: "[allura:tickets] " <6383@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #6383 zarkov eventlog cannot start when webevent is
 running
Message-ID: 
 </p/allura/tickets/6383/d8f58511c56d58d43a7fbc30b00eeeffeb46c44e.tickets@allura.p.sourceforge.net>
Date: Mon, 15 Jul 2013 14:51:33 +0000

--===============6133867585299353467==
Content-Type: multipart/alternative;
 boundary="===============0006862360777411046=="
MIME-Version: 1.0

--===============0006862360777411046==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

- **status**: blocked --> closed


---

** [tickets:#6383] zarkov eventlog cannot start when webevent is running**

**Status:** closed
**Labels:** zarkov stability 
**Created:** Thu Jun 20, 2013 08:54 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 11, 2013 06:11 PM UTC
**Owner:** Tim Van Steenburgh

Eventlog is supposed to listen to events from any number of event producers.  Webevent talks to eventlog.  But if webevent starts up it "claims" the port that eventlog is supposed to listen on.

Consider changing .bind or .connect.  Or maybe PUSH/PULL sockets aren't the right architecture here.  See http://stackoverflow.com/a/10446493/79697

Also cleanup 'HWM' references in zarkov/command/web_event.py and eventlog.py


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============0006862360777411046==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><ul>
<li><strong>status</strong>: blocked --&gt; closed</li>
</ul>
<hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/6383/">[tickets:#6383]</a> zarkov eventlog cannot start when webevent is running</strong></p>
<p><strong>Status:</strong> closed<br />
<strong>Labels:</strong> zarkov stability <br />
<strong>Created:</strong> Thu Jun 20, 2013 08:54 PM UTC by Dave Brondsema<br />
<strong>Last Updated:</strong> Thu Jul 11, 2013 06:11 PM UTC<br />
<strong>Owner:</strong> Tim Van Steenburgh</p>
<p>Eventlog is supposed to listen to events from any number of event producers.  Webevent talks to eventlog.  But if webevent starts up it "claims" the port that eventlog is supposed to listen on.</p>
<p>Consider changing .bind or .connect.  Or maybe PUSH/PULL sockets aren't the right architecture here.  See <a href="http://stackoverflow.com/a/10446493/79697" rel="nofollow">http://stackoverflow.com/a/10446493/79697</a></p>
<p>Also cleanup 'HWM' references in zarkov/command/web_event.py and eventlog.py</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============0006862360777411046==--

--===============6133867585299353467==--