Harikrishnan P created AMQ-5700:
---
Summary: Invalid TLS Padding data Error
Key: AMQ-5700
URL: https://issues.apache.org/jira/browse/AMQ-5700
Project: ActiveMQ
Issue Type: Bug
Harikrishnan P created AMQ-5701:
---
Summary: Invalid TLS Padding data Error
Key: AMQ-5701
URL: https://issues.apache.org/jira/browse/AMQ-5701
Project: ActiveMQ
Issue Type: Bug
I agree with Jim. If there is not (near) 100% consensus among committers,
then HQ should become its own project, and there is nothing wrong with
that. ASF are ridden with competing implementations and that is fully
embraced here.
ยข2 from peanut gallery
On Sat, Mar 28, 2015 at 9:28 PM, Jim
J G created AMQ-5702:
Summary: REST production of message bodies can result in
IllegalStateException: STREAMED (same as AMQ-5579)
Key: AMQ-5702
URL: https://issues.apache.org/jira/browse/AMQ-5702
Project:
On 28 March 2015 at 19:02, artnaseef a...@artnaseef.com wrote:
Hey Gary - in all the discussion, I missed this response, so forgive my slow
response.
ditto :-)
First, let me apologize for my use of the word take - it sounds it was
read as an attack or accusation, and that was not my intent.
On Wed, Apr 1, 2015 at 7:23 AM, Gary Tully gary.tu...@gmail.com wrote:
Would version 10 allow you to pause and be happy with 5.x for the next
few years, till 10.x gets a chance to bed in?
A higher number isn't the answer. HQ needs to go to the incubator.
Gary Tully created AMQ-5703:
---
Summary: kahadb - index recovery - corrupt journal records cannot
be skipped
Key: AMQ-5703
URL: https://issues.apache.org/jira/browse/AMQ-5703
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5701.
-
Resolution: Duplicate
Invalid TLS Padding data Error
--
[
https://issues.apache.org/jira/browse/AMQ-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390515#comment-14390515
]
Timothy Bish commented on AMQ-5700:
---
Are you trying to connect from a client of the than
[
https://issues.apache.org/jira/browse/AMQ-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390513#comment-14390513
]
Timothy Bish commented on AMQ-5701:
---
Are you trying to connect from a client of the than
[
https://issues.apache.org/jira/browse/AMQ-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5680.
---
Resolution: Fixed
Fix Version/s: 5.12.0
Fixed, thanks for pointing that out.
Timothy Bish created AMQ-5704:
-
Summary: AMQP: SASL Mechanisms sent in the wrong order.
Key: AMQ-5704
URL: https://issues.apache.org/jira/browse/AMQ-5704
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5704.
---
Resolution: Fixed
now sending in correct order of preference.
AMQP: SASL Mechanisms sent in the
Just a quick FYI:
I have reached out to Red Hat (w/ my ASF hat one) via Mark Little
and Dave Ingham. Both have been *extremely* open, eager and honest
w/ me. I plan on writing up a quick summary of my thoughts and
our conversations and maybe suggest some ways of moving forward.
Sometimes our
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390648#comment-14390648
]
Christian Posta commented on AMQ-5082:
--
Thanks Jim for digging into this. I've
[
https://issues.apache.org/jira/browse/AMQ-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5703.
-
Resolution: Fixed
fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/a7178a46
kahadb
Github user jimrobinson closed the pull request at:
https://github.com/apache/activemq/pull/76
---
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
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390730#comment-14390730
]
anselme dewavrin commented on AMQ-5082:
---
A big Thank you Jim, we were truly annoyed by
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390671#comment-14390671
]
ASF GitHub Bot commented on AMQ-5082:
-
Github user jimrobinson closed the pull request
[
https://issues.apache.org/jira/browse/AMQ-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J G updated AMQ-5702:
-
Description:
I am working on a project to use Apache ActiveMQ with a RESTful interface. It's
a cross platform error
[
https://issues.apache.org/jira/browse/AMQ-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392103#comment-14392103
]
Harikrishnan P commented on AMQ-5701:
-
No, am using an Mqtt paho C client to connect to
[
https://issues.apache.org/jira/browse/AMQ-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392118#comment-14392118
]
Harikrishnan P commented on AMQ-5700:
-
No, am using an Mqtt paho C client to connect to
GitHub user dfj opened a pull request:
https://github.com/apache/activemq/pull/79
Improved filename sanitization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dfj/activemq activemq-5.10.x
Alternatively you can review and
GitHub user dfj opened a pull request:
https://github.com/apache/activemq/pull/78
Improved filename sanitization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dfj/activemq activemq-5.11.x
Alternatively you can review and
GitHub user dfj opened a pull request:
https://github.com/apache/activemq/pull/77
Improved filename sanitization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dfj/activemq master
Alternatively you can review and apply these
[
https://issues.apache.org/jira/browse/AMQ-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14391551#comment-14391551
]
Chuck Rolke commented on AMQ-5684:
--
Snapshot 5.12-20150331 looks good. The test case
[
https://issues.apache.org/jira/browse/AMQ-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5684.
---
Resolution: Fixed
Fix Version/s: 5.12.0
Fix confirmed by Chuck, thanks!
AMQP: messages get
I have decided to not draft any email. There really is
no need.
The PMC is on task to provide a board report. It is
expected that the report will be open and honest
and present the board with the current projected
roadmap for AMQ5 and AMQ6 going forward. It is
expected that this report will be
For every Pull Request sent (e.g: https://github.com/apache/activemq-6/pull/197)
There will be a build with a considerable sized testsuite running..
which we call fast-test
https://builds.apache.org/job/ActiveMQ6-PR-Build/223/
This will validate tests, CheckStyle and Licensing.
This will run
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-6/pull/200
Docs and settings updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-6 master
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-6/pull/200
---
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
Vu Le created AMQ-5705:
--
Summary: originBrokerURL incorrectly set in advisory messages
Key: AMQ-5705
URL: https://issues.apache.org/jira/browse/AMQ-5705
Project: ActiveMQ
Issue Type: Bug
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/1290/changes
The board will not, and does not, tolerate outside
influences impacting our internal decision making
and development methods.
PUH-LEASE do not read ANYTHING into the above. It is a simple
catch-all reminder.
nip-conspiracy-theory-paranoia-in-the-bud
34 matches
Mail list logo