[
https://issues.apache.org/jira/browse/AMQ-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5606:
--
Summary: AMQP: Update the AMQP 1.0 JMS client with new QPid to v0.1.0 when
released. (was: AMQP: Update
[
https://issues.apache.org/jira/browse/AMQ-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5606:
--
Description: Upon its release we should update the QPid AMQP 1.0 JMS
library to use the new QPid JMS
[
https://issues.apache.org/jira/browse/AMQ-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Endre Stølsvik updated AMQ-5681:
Description:
These are some lines from a monitor-thingy that I have:
{code}
Endre Stølsvik created AMQ-5682:
---
Summary: Documentation about Statistics-plugin regarding
ActiveMQ.Statistics.Subscription
Key: AMQ-5682
URL: https://issues.apache.org/jira/browse/AMQ-5682
Project:
[
https://issues.apache.org/jira/browse/AMQ-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQ-5503 started by Jean-Baptiste Onofré.
-
Make init script more reliable
--
[
https://issues.apache.org/jira/browse/AMQ-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned AMQ-5503:
-
Assignee: Jean-Baptiste Onofré
Make init script more reliable
[
https://issues.apache.org/jira/browse/AMQ-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Endre Stølsvik updated AMQ-5681:
Description:
These are some lines from a monitor-thingy that I have:
{code}
+1 to the -M1 naming, I think that captures intent perfectly.
On 23 March 2015 at 10:09, Andy Taylor andy.tayl...@gmail.com wrote:
So I think the consensus is to go with ActiveMQ 6.0.0-M1 so we will go
ahead and cut a new RC in the next day or so. We will also add some
content the website so
[
https://issues.apache.org/jira/browse/AMQ-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375933#comment-14375933
]
Bernhard Trummer commented on AMQ-5575:
---
Further update. The issue does not occur,
[
https://issues.apache.org/jira/browse/AMQ-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5682.
---
Resolution: Fixed
Added an additional sentence to indicate there can be more than one message,
one for
[
https://issues.apache.org/jira/browse/AMQ-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375738#comment-14375738
]
Jean-Baptiste Onofré commented on AMQ-5503:
---
Sorry for the delay Marc, I was in
[
https://issues.apache.org/jira/browse/AMQ-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376132#comment-14376132
]
Torsten Mielke commented on AMQ-5683:
-
Resolved in [version
Torsten Mielke created AMQ-5683:
---
Summary: [doc] No documentation of transport.soWriteTimeout
Key: AMQ-5683
URL: https://issues.apache.org/jira/browse/AMQ-5683
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated AMQ-5684:
-
Attachment: second-receiver-hang-20150323.html
The receiver issues a credit of 2 but receives only 1
Chuck Rolke created AMQ-5684:
Summary: AMQP: messages get stuck
Key: AMQ-5684
URL: https://issues.apache.org/jira/browse/AMQ-5684
Project: ActiveMQ
Issue Type: Bug
Components: AMQP
I already have it on my todo list to come up with a feature matrix (in
fact i have already started) which i will stick on the wiki (or where
ever is appropriate) which will be part of a migration document.
Once i do that I will engage the community on the forums and raise some
Jiras. Any other
Apologies for late reply I was on PTO, end of last week.
+1 for 6.0.0-M#
On 20/03/15 20:40, Clebert Suconic wrote:
On Fri, Mar 20, 2015 at 4:25 PM, artnaseef a...@artnaseef.com wrote:
Please help me to understand how this would go.
We would use 6.0.0-M1, 6.0.0-M2, etc until when? Until we
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-6/pull/193
added some exclusions to the RAT plugin
added some exclusions to the RAT plugin for when users build and redirect
the output to log files
You can merge this pull request into a Git
raised a PR to fix your build issue -
https://github.com/apache/activemq-6/pull/193
On 19/03/15 22:56, artnaseef wrote:
-1
First off, please start a new thread for the next vote. This is getting
confusing. (That has nothing to do with the -1).
Second, I have to -1 on this vote because
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-6/pull/193
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
So I think the consensus is to go with ActiveMQ 6.0.0-M1 so we will go
ahead and cut a new RC in the next day or so. We will also add some
content the website so users are clear that currently there isn't
feature parity between ActiveMQ 5 and ActiveMQ 6. We will then raise
JIRA to map out a
Hi,
I have a scenario that a .NET client application (Windows) need to
communicate with a remove ActiveMQ server (Linux).
Is there anyway to accomplish this?
At: André
--
View this message in context:
On 03/22/2015 11:24 AM, andrevcv wrote:
Hi,
I have a scenario that a .NET client application (Windows) need to
communicate with a remove ActiveMQ server (Linux).
Is there anyway to accomplish this?
At: André
--
View this message in context:
[
https://issues.apache.org/jira/browse/AMQ-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke resolved AMQ-5683.
-
Resolution: Fixed
Fix Version/s: 5.11.1
[doc] No documentation of transport.soWriteTimeout
Github user artnaseef commented on the pull request:
https://github.com/apache/activemq-6/pull/193#issuecomment-85133033
I think this helps, but want to see more. The copyright check here is very
aggressive and assumes that anyone working with the sources will only ever be
working
Github user andytaylor commented on the pull request:
https://github.com/apache/activemq-6/pull/193#issuecomment-85136802
I actually took tose excludes from the ActiveMQ pom however i thought
(wrongly) that it was always run. I will update this pr and add a new profile
have a manual
I see - that makes sense. It definitely would help to have an enumeration of
features and functions and their planned state so we know what the end-goal
looks like for reaching the official 6.0.0 state. However, I can see
working with the community on a feature-by-feature basis instead, if we
Github user artnaseef commented on the pull request:
https://github.com/apache/activemq-6/pull/193#issuecomment-85137830
Thanks Andy.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
I can create using Java (not xml files ) an embedded a broker instance and
setup the broker port, the broker name, the admin user, the admin password,
some queue names.
How can I store that broker configuration in hard disk and just it later
without running the configuration
again ?
I am typing
It seems to me that a different name would mean a different project. IIUC AMQ
accepted the code so not having it turn into amq-xxx seems a bit odd to me.
What is stopping all the non-jboss-employees (yes, showing my age here) from
enthusiastically digging into the code and adapting from amq 5
Now here lies the problem.
I agree that it captures the intent well. That also creates an
expectation from the users and sort of a promise from the activemq pmc,
amplified by the vendors' marketing (well, exactly one in this case).
The same promise has been made with apollo.
I am less
31 matches
Mail list logo
