On Mon, 2016-02-01 at 12:34 -0500, Ken Giusti wrote:
> Alan:
>
> Can you review:
>
> https://issues.apache.org/jira/browse/PROTON-1118
>
> I'd like to get it included into the 0.12.0 release,
I approve this for 0.12.
Andrew
https://scan.coverity.com/projects/apache-qpid-proton?tab=overview
Detected an additional 85 "defects" since the last run. The scanner flagged a
few C++ issues, and a whole ton of Java stuff (which may all be false positives
for all I know).
Click on the "View Defects" box.
--
-K
--
Alan:
Can you review:
https://issues.apache.org/jira/browse/PROTON-1118
I'd like to get it included into the 0.12.0 release,
thanks
--
-K
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e
Robbie,
spot on, that was it! thanks! I'm up and running
On Mon, Feb 1, 2016 at 5:24 AM, Robbie Gemmell wrote:
> In Rob's earlier mail there was a typo in the example system property
> setter so if you c&p it that could be the issue, it contained
> "qpid.http.port" rather than "qpid.http_port".
In Rob's earlier mail there was a typo in the example system property
setter so if you c&p it that could be the issue, it contained
"qpid.http.port" rather than "qpid.http_port". If not that, the
suggestion that there may be some stale prior config being picked up
seems likely.
I'm not familiar wi
On 01/29/2016 11:50 PM, jjw tectec wrote:
I ran the following script to set up a dynamic exchange route from Bs to
B1.
EX=TestExchange
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bs add exchange topic $EX
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 add exchange topic $EX
~/qpid/qpid-tools
On 01/31/2016 10:19 PM, jjw tectec wrote:
I sent out the email more than 3 days ago, but it's still not appearing
in the mailing list. Has it been deleted from the archive?
I got the mail, but not the attached image. I actually thought I had
replied as well, but it appears not...
On Thu, Ja
Can you give the full stack trace... also are you cleaning up after running
this, or is there a config.json from a previous run now written somewhere
(on startup the broker will, by default, write out a config file based on
the initial config, and in subsequent runs it will use the written file
rat
