The vote seemed to run from 1/30 to 2/3. Three full days in there (1/31,
2/1, 2/2)
On Wed Feb 04 2015 at 12:17:18 PM artnaseef a...@artnaseef.com wrote:
Hey - any thoughts on the length of votes? Did I misunderstand?
By the way - my tests finally finished - after 17:42! almost 18 hours!
[
https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305437#comment-14305437
]
Arthur Naseef commented on AMQ-5566:
*Port 1099 Failure Exception*
{noformat}
karaf@root
Hey - any thoughts on the length of votes? Did I misunderstand?
By the way - my tests finally finished - after 17:42! almost 18 hours! Who
said they take 5 hours, or even 10?
There were a few failures, but they all passed on the second try - except
the karaf test that failed because my system
[
https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef updated AMQ-5566:
---
Priority: Minor (was: Major)
Karaf test fails when standard ports already in-use on the system
On 02/04/2015 12:10 PM, artnaseef wrote:
Hey - any thoughts on the length of votes? Did I misunderstand?
Vote went out on the 30th in the morning and ended on the 3rd in the
morning which meets the 72hr windows Gary set in the initial vote thread.
By the way - my tests finally finished -
I think the misunderstanding is the 72 business hours here. I don't
know that I've ever heard that stipulation. I've always just heard it
as 72 hours, and this vote satisfies that.
On Wed, Feb 4, 2015 at 12:10 PM, artnaseef a...@artnaseef.com wrote:
Hey - any thoughts on the length of votes?
[
https://issues.apache.org/jira/browse/AMQ-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305541#comment-14305541
]
Hadrian Zbarcea commented on AMQ-5554:
--
Turns out that [~dkulp] suggested a better
Arthur Naseef created AMQ-5566:
--
Summary: Karaf test fails when standard ports already in-use on
the system
Key: AMQ-5566
URL: https://issues.apache.org/jira/browse/AMQ-5566
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305436#comment-14305436
]
Arthur Naseef commented on AMQ-5566:
*Port 61616 Failure Exception*
{noformat}
Hi
I have done as Arthur suggested to dump the stacktrace, and also with
Gary's turn on|off the anonoymous producers.
I posted output from console as 2 gists
https://gist.github.com/davsclaus/b5fbb1287d383107e599
https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79
On Wed, Feb 4, 2015 at
Claus Ibsen created AMQ-5564:
Summary: activemq-pool - Either adds new mbeans or add/remove pair
of mbean for each producer in use
Key: AMQ-5564
URL: https://issues.apache.org/jira/browse/AMQ-5564
Hi
I logged a ticket about this. Not sure what the title it, but I
suspect its related to the activemq-pool.
I found an easier way of reproducing it using the camel-example-management.
https://issues.apache.org/jira/browse/AMQ-5564
Just change the AMQ version in its pom.xml
properties
Claus Ibsen created AMQ-5563:
Summary: activemq-camel - Wrong default value in javadoc
Key: AMQ-5563
URL: https://issues.apache.org/jira/browse/AMQ-5563
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated AMQ-5564:
-
Description:
On the AMQ dev mailing list we have talked about a new issue.
[
https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated AMQ-5564:
-
Attachment: amq-5110.png
amq-5101.png
amq-5100.png
Running the
Hi
Just upgraded Camel master branch to 5.11.0 and you can reproduce the
issue there also
cd examples/camel-example-management
mvn clean install camel:run
Connect to the JVM using jconsole.
Notice the AcitveMQ tree under dynamic producers keeps adding new
mbeans, until your JVM runs out of
I might get flamed but…. my experience is that blueprint is sort of ok for
applications built on spring that you are trying to port to osgi with minimal
changes but that it doesn't fit osgi well enough to use for anything else. Has
anyone considered making AMQ in osgi based on declarative
Ah, thanks James. I heard business days once-upon-a time. My mistake.
OpenSource never rests! ;-).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/VOTE-RESULT-Apache-ActiveMQ-5-11-0-tp4690937p4691069.html
Sent from the ActiveMQ - Dev mailing list archive at
Maybe I'm misunderstanding, but isn't the common approach to providing
plug-in support in blueprint to use the whiteboard pattern?
On Wed, Feb 4, 2015 at 1:23 PM, Daniel Kulp dk...@apache.org wrote:
Just to follow up on list about this to fully describe the issue and
potential solution…
In
Just to follow up on list about this to fully describe the issue and potential
solution…
In the ActiveMQ schema that is used for both Blueprint and Spring, we use a
bunch of:
xsd:any namespace=“##other”/
in places where the user may want to add custom implementation of various
things.
Good work guys! The explicit only destination stuff looks cool too. I
might have to get some time to look at the plugin model.
On Wed, Feb 4, 2015 at 4:32 AM, Gary Tully gary.tu...@gmail.com wrote:
The ActiveMQ team is delighted to announce the release of ActiveMQ 5.11.0
Full details at
[
https://issues.apache.org/jira/browse/AMQ-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305148#comment-14305148
]
Hadrian Zbarcea commented on AMQ-5554:
--
The way this issue was originally formulated
[
https://issues.apache.org/jira/browse/AMQ-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305346#comment-14305346
]
Hadrian Zbarcea commented on AMQ-5554:
--
I think there are 2 separate issues, this is
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-6/pull/90
Test fix + STOMP auto-create
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-6 master_work
Alternatively you can review
The ActiveMQ team is delighted to announce the release of ActiveMQ 5.11.0
Full details at http://activemq.apache.org/activemq-5110-release.html
We look forward to your feedback.
A hearty thanks to everyone who contributed to this release.
+1 (non binding)
Regards
JB
On 01/30/2015 03:00 PM, Gary Tully wrote:
Hi folks,
I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.
-note-
this candidate includes the fix for the 'reliably' broken test case
[
https://issues.apache.org/jira/browse/AMQ-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated AMQ-5554:
-
Summary: Proper support for the blueprint namespace in activemq-blueprint
(was: Support blueprint
[
https://issues.apache.org/jira/browse/AMQ-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned AMQ-5565:
-
Assignee: Jean-Baptiste Onofré
Need to be able to start/stop brokers in karaf via
Hadrian Zbarcea created AMQ-5565:
Summary: Need to be able to start/stop brokers in karaf via
commands
Key: AMQ-5565
URL: https://issues.apache.org/jira/browse/AMQ-5565
Project: ActiveMQ
There is rather serious issue related to supporting blueprint in karaf.
In case the jira [1] and it's relevance is not immediately obvious, I am
pointing to it here to draw a bit of attention and choose among the two
proposed solutions (or throw in other options). Lazy consensus defaults
to
[
https://issues.apache.org/jira/browse/AMQ-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305018#comment-14305018
]
Hadrian Zbarcea commented on AMQ-5250:
--
[~ruralhunter] You mention that you wrote a
[
https://issues.apache.org/jira/browse/AMQ-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated AMQ-5554:
-
Attachment: broker-blueprint.xml
Proper support for the blueprint namespace in activemq-blueprint
32 matches
Mail list logo
