On Wed, Feb 11, 2015 at 12:00 AM, artnaseef a...@artnaseef.com wrote:
Hey Claus - we can work on a 5.10.2; this bug exists in 5.10.1?
Yes 5.10.1 and 5.11.0 are affected.
Before starting down that route, though, is it possible to clarify the
impact of this bug? It sounds like a nuisance
[
https://issues.apache.org/jira/browse/AMQ-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef reassigned AMQ-5478:
--
Assignee: Arthur Naseef
REST endpoint creates topic instead of queue
Here's the list of tickets for the 5.11.1 release:
https://issues.apache.org/jira/browse/AMQ-5565?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.11.1
--
View this message in context:
http://activemq.2283324.n4.nabble.com/DICUSS-5-11-1-patch-release-tp4691399p4691402.html
Sent from the
[
https://issues.apache.org/jira/browse/AMQCPP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Godin updated AMQCPP-560:
--
Description:
A program have one connection and may create many threads. Each of those thread
Arthur Naseef created AMQ-5579:
--
Summary: REST production of message bodies can result in
IllegalStateException: STREAMED
Key: AMQ-5579
URL: https://issues.apache.org/jira/browse/AMQ-5579
Project:
A leak is a major concern.
With that said, I have questions. First, I thought the creation of addition
mbeans was failing, is that not right? If so, then what is actually
leaking? Are the mbeans being created but not removed?
Also, can you clarify under what conditions this occurs? For
(Repeating from the 5.10.2 thread)
As per Claus, https://issues.apache.org/jira/browse/AMQ-5564, appears to
address a significant leak introduced in the 5.11.0 (as well as 5.10.1 -
that's a separate topic).
What tickets do we want to include in this release? It appears AMQ-5550 and
AMQ-5564
[
https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316711#comment-14316711
]
Mark Frazier commented on AMQ-5579:
---
I can work on this one.
REST production of message
As per Claus, https://issues.apache.org/jira/browse/AMQ-5564, appears to
address a significant leak introduced in the 5.10.1 (as well as 5.11.0 -
that's a separate topic).
I will start working on the 5.10.2 release. Are there any other tickets we
want to include in this release?
Note that is
Here's the jira list of tickets for 5.10.2:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.2
--
View this message in context:
http://activemq.2283324.n4.nabble.com/DISCUSS-5-10-2-release-tp4691398p4691400.html
Sent from the ActiveMQ - Dev
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-6/pull/95
ACTIVEMQ6-78 performance improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-6 perf
Alternatively
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316619#comment-14316619
]
ASF GitHub Bot commented on ACTIVEMQ6-78:
-
GitHub user clebertsuconic opened a
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-6/pull/91
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-6/pull/94
---
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
Re-reading the entire thread, it appears there is an mbean leak.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691397.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[
https://issues.apache.org/jira/browse/AMQ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5573:
--
Fix Version/s: 5.12.0
Configurable messages size for Stomp producer
[
https://issues.apache.org/jira/browse/AMQ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5573.
---
Resolution: Fixed
Assignee: Timothy Bish
Added option transport.maxDataLength to allow for
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-6/pull/94
Remove Geronimo version prop from JMS example pom
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-6
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316215#comment-14316215
]
ASF GitHub Bot commented on ACTIVEMQ6-7:
GitHub user andytaylor opened a pull
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-6/pull/93
ACTIVEMQ6-7 - Improve Serialization on Connection Factory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andytaylor/activemq-6 uri
[
https://issues.apache.org/jira/browse/AMQ-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316371#comment-14316371
]
Gary Tully commented on AMQ-5520:
-
seems that test failure points to a
Timothy Bish created AMQ-5580:
-
Summary: Thread unsafe operations on the PersistenceAdapters in
the mKahaDB implementation
Key: AMQ-5580
URL: https://issues.apache.org/jira/browse/AMQ-5580
Project:
[
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317023#comment-14317023
]
ASF GitHub Bot commented on AMQ-4848:
-
GitHub user zmhassan opened a pull request:
GitHub user zmhassan opened a pull request:
https://github.com/apache/activemq/pull/60
https://issues.apache.org/jira/browse/AMQ-4929 - remove old and unused
org.apache.activemq.broker.BrokerService#setSupportFailOver
I've removed the unused method
[
https://issues.apache.org/jira/browse/AMQ-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317203#comment-14317203
]
ASF GitHub Bot commented on AMQ-4929:
-
GitHub user zmhassan opened a pull request:
Brian Jackson created AMQ-5581:
--
Summary: Failover with jdbcPersistenceAdapter/PGPoolingDataSource
doesn't fail over properly when DB server changes IP
Key: AMQ-5581
URL:
GitHub user zmhassan opened a pull request:
https://github.com/apache/activemq/pull/59
https://issues.apache.org/jira/browse/AMQ-4848 - Karaf update added Netw...
This was a fix that I sent pull request #28 which was from Jun 17, 2014. I
fixed activemq:list command and it now
[
https://issues.apache.org/jira/browse/AMQ-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5580.
---
Resolution: Fixed
Fixed on master.
Thread unsafe operations on the PersistenceAdapters in the
Kyung Soo Lee created AMQCPP-563:
Summary: Process is dead with seg fault when queue has heavy load.
Key: AMQCPP-563
URL: https://issues.apache.org/jira/browse/AMQCPP-563
Project: ActiveMQ C++ Client
Given that the bug Claus discovered AMQ-5564 has now been fixed is there a
date scheduled for the 5.11.1 release?
Thanks,
Paul
On Wed, Feb 11, 2015 at 1:36 PM, artnaseef a...@artnaseef.com wrote:
Here's the list of tickets for the 5.11.1 release:
[
https://issues.apache.org/jira/browse/AMQ-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317214#comment-14317214
]
Timothy Bish commented on AMQ-4929:
---
The patch only removes the method, but the issue
[
https://issues.apache.org/jira/browse/AMQ-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317453#comment-14317453
]
Zak Hassan commented on AMQ-4929:
-
Thank you for taking the time to review. I'll rollback
[
https://issues.apache.org/jira/browse/AMQ-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317453#comment-14317453
]
Zak Hassan edited comment on AMQ-4929 at 2/12/15 3:01 AM:
--
Thank
[
https://issues.apache.org/jira/browse/AMQ-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317453#comment-14317453
]
Zak Hassan edited comment on AMQ-4929 at 2/12/15 3:08 AM:
--
Thank
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/24
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/42
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/54
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/5
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/58
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/29
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/57
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/20
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/47
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/28
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/30
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/22
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/55
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/45
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/51
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/9
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/31
---
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
Bernhard Trummer created AMQ-5575:
-
Summary: Stuck message in ActiveMQ after WebLogic (incl. MDB)
startup
Key: AMQ-5575
URL: https://issues.apache.org/jira/browse/AMQ-5575
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315932#comment-14315932
]
Bernhard Trummer commented on AMQ-5575:
---
Feel free to request any additional
[
https://issues.apache.org/jira/browse/AMQ-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315997#comment-14315997
]
ASF GitHub Bot commented on AMQ-5344:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315998#comment-14315998
]
ASF GitHub Bot commented on AMQ-5503:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315994#comment-14315994
]
ASF GitHub Bot commented on AMQ-5381:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315996#comment-14315996
]
ASF GitHub Bot commented on AMQ-5295:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315992#comment-14315992
]
ASF GitHub Bot commented on AMQ-5160:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315990#comment-14315990
]
ASF GitHub Bot commented on AMQ-3452:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315999#comment-14315999
]
ASF GitHub Bot commented on AMQ-5378:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315991#comment-14315991
]
ASF GitHub Bot commented on AMQ-4848:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315993#comment-14315993
]
ASF GitHub Bot commented on AMQ-4945:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315995#comment-14315995
]
ASF GitHub Bot commented on AMQ-5265:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315989#comment-14315989
]
ASF GitHub Bot commented on AMQ-5187:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/AMQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316080#comment-14316080
]
Sergey commented on AMQ-1940:
--
What I can see in JMX using Hawtio:
Total dequeue count 2474137
[
https://issues.apache.org/jira/browse/AMQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316127#comment-14316127
]
Sergey commented on AMQ-1940:
--
I've just created AMQ-5576, and where is a route test case.
Sergey created AMQ-5576:
Summary: Reported queue sizes are wrong in many cases
Key: AMQ-5576
URL: https://issues.apache.org/jira/browse/AMQ-5576
Project: ActiveMQ
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/AMQ-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey updated AMQ-5576:
-
Description:
Web console, JMX MBeans and Hawtio/Jolokia all reports wrong size for queues in
many cases. See my
[
https://issues.apache.org/jira/browse/AMQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316120#comment-14316120
]
Gary Tully commented on AMQ-1940:
-
@Sergey - can you make a junit test case that can
[
https://issues.apache.org/jira/browse/AMQ-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316132#comment-14316132
]
Sergey commented on AMQ-5576:
--
BTW, on *clean 5.11.0* installation, with sample route
Vladimir Kulev created AMQ-5577:
---
Summary: Web console message properties not escaped
Key: AMQ-5577
URL: https://issues.apache.org/jira/browse/AMQ-5577
Project: ActiveMQ
Issue Type: Bug
Gary Tully created AMQ-5578:
---
Summary: preallocate journal files
Key: AMQ-5578
URL: https://issues.apache.org/jira/browse/AMQ-5578
Project: ActiveMQ
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef updated AMQ-5579:
---
Description:
Attempting to post a message to AMQ using the following yields an
IllegalStateException:
[
https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317587#comment-14317587
]
Mark Frazier commented on AMQ-5579:
---
Upon closer inspection, this seems to be working as
Krishna created AMQ-5582:
Summary: Queues stop sending to consumers after a threshold
Key: AMQ-5582
URL: https://issues.apache.org/jira/browse/AMQ-5582
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef resolved AMQ-5579.
Resolution: Fixed
Thanks Mark. Looks like a good way to resolve under the circumstances.
REST
[
https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317546#comment-14317546
]
Arthur Naseef commented on AMQ-5579:
Sure thing - go for it Mark.
REST production of
77 matches
Mail list logo
