You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Tim Van Steenburgh <va...@users.sf.net> on 2013/06/26 18:26:19 UTC
[allura:tickets] #6383 zarkov eventlog cannot start when webevent is running
- **status**: open --> in-progress
- **assigned_to**: Tim Van Steenburgh
---
** [tickets:#6383] zarkov eventlog cannot start when webevent is running**
**Status:** in-progress
**Labels:** zarkov stability
**Created:** Thu Jun 20, 2013 08:54 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 20, 2013 08:54 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.