+1
On 03/30/2016 06:25 AM, Robbie Gemmell wrote:
Hello folks,
Many moons ago, a seperate mailing list was established for Proton,
back when it was purely a protocol engine other components would use.
Its scope has since expanded beyond that and the separate mailing list
has I feel been an
On 03/24/2016 10:04 PM, arkain wrote:
Hello,
I have a question about connecting to ActiveMQ. I'm trying to connect
multiple consumers to a queue, by changing the session id. I'm not sure how
to do that with qpid-proton
According to
Timothy Bish created PROTON-1147:
Summary: Add OSGi bundle metadata to the proton-j jar manifest
Key: PROTON-1147
URL: https://issues.apache.org/jira/browse/PROTON-1147
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved PROTON-1145.
--
Resolution: Fixed
> Move the python shim code to the test module where it is u
Timothy Bish created PROTON-1145:
Summary: Move the python shim code to the test module where it is
used.
Key: PROTON-1145
URL: https://issues.apache.org/jira/browse/PROTON-1145
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved PROTON-1141.
--
Resolution: Fixed
> Update JUnit Dependency and fix some warnings in the te
Timothy Bish created PROTON-1141:
Summary: Update JUnit Dependency and fix some warnings in the
tests.
Key: PROTON-1141
URL: https://issues.apache.org/jira/browse/PROTON-1141
Project: Qpid Proton
On 02/19/2016 12:39 PM, Flores, Paul A. wrote:
> Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0
> Release to work.
>
>
>
> When I go to run it I am seeing the following.
>
>
>
> Can some one point me to a resolution? I am running out of hair to pull!
>
Try changing
On 02/10/2016 09:04 AM, Justin Ross wrote:
> Hi, everyone. RC 2 had some embedded build output, which this RC removes.
> Apart from that removal, it has the same content as RC 2.
>
> The proposed release artifacts:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-rc3/
>
> Please
+1
* Built and ran tests.
* validated signatures and sums
* Built ActiveMQ using the staged maven artifacts and ran all AMQP tests
* Built Qpid-JMS using the staged maven artifacts and ran all the tests.
On 02/03/2016 10:10 AM, Justin Ross wrote:
> The artifacts proposed for release:
>
>
On 11/11/2015 07:53 AM, Justin Ross wrote:
> The artifacts proposed for release are here:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-rc2/
>
> Please indicate your vote below. If you favor releasing the 0.11.0 RC 2
> bits as 0.11.0 GA, vote +1. If you have reason to think
[
https://issues.apache.org/jira/browse/PROTON-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14987428#comment-14987428
]
Timothy Bish commented on PROTON-971:
-
Reviewed the changes, fix seems valid.
> [proton-j] mu
+1 for dropping Java 6 from future releases.
On 07/08/2015 09:59 AM, Robbie Gemmell wrote:
Epic bump.
As per https://issues.apache.org/jira/browse/PROTON-935 the build is
currently broken again on Java 6. We need to either update it to
compile on Java 6, since that is still the builds
On 06/10/2015 10:18 AM, Kritikos, Alex wrote:
Hi Alan,
thanks for your response. We also use an engine per connection however there
are different read and write threads interacting with it and the issues only
occur under load.
I guess we should try to create a repro case.
Thanks,
Alex
On 04/29/2015 03:34 PM, Rafael Schloming wrote:
Hi Everyone,
I've put out an RC for 0.9.1 in the usual places.
Source artifacts are here:
https://people.apache.org/~rhs/qpid-proton-0.9.1-rc1/
Java binaries are here:
On 04/23/2015 06:39 AM, Robbie Gemmell wrote:
Hi folks,
I would like to propose doing a new release. There have been quite a
few important fixes or changes since 0.9, mainly in proton-j, that I
would like to see made available for use in dependent projects such as
the JMS client. These
[
https://issues.apache.org/jira/browse/PROTON-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved PROTON-845.
-
Resolution: Fixed
Fix Version/s: 0.10
Added check and create of Header instance if none
Timothy Bish created PROTON-845:
---
Summary: Proton-J: Potential NPE in proton-jms outbound native
transformer
Key: PROTON-845
URL: https://issues.apache.org/jira/browse/PROTON-845
Project: Qpid Proton
On 03/16/2015 04:42 PM, Rafael Schloming wrote:
[ ] Yes, release Proton 0.9-rc-3 as 0.9 final
[X] Yes, release Proton 0.9-rc-3 as 0.9 final
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog:
On 02/16/2015 03:02 PM, Rafael Schloming wrote:
I'm not much of a git expert, so I don't know what the preferred option
would be, but I'm +1 for killing it in one form or another.
--Rafael
You can submit a request to INFRA to drop it, the only caveat is that
there is no enforcement to
[ X ] Yes, migrate the proton repo over to git.
On 10/30/2014 06:59 AM, Rafael Schloming wrote:
Hi Everyone,
I'm planning on updating the release script for 0.9 to automate the last
few details of the release process and to do proper branching. Given that
the release script must make use of
[X] Yes, release Proton 0.8 RC5 as 0.8 final
Proton-J side still works for AMQ.
On 10/27/2014 09:51 PM, Rafael Schloming wrote:
Hi Everyone,
Sorry for the delay, there seemed to be some kind of Nexus outage today, so
I was unable to generate the java binaries until just now.
I've posted RC5
[ X ] Yes, release Proton 0.8 RC4 as 0.8 final.
Tested Proton-J with ActiveMQ and the new JMS client and found no issues,
On 10/23/2014 12:21 PM, Rafael Schloming wrote:
Hi Everyone,
I've put together RC4. This is pretty much the same as RC3 with a number of
fixes to disable those SSL
[
https://issues.apache.org/jira/browse/PROTON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated PROTON-508:
Attachment: (was: PROTON-508.txt)
Use of Sasl auth results in a large performance hit
[
https://issues.apache.org/jira/browse/PROTON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated PROTON-508:
Attachment: PROTON-508.txt
New patch that resolves the issue and keeps tests passing. Problem
[
https://issues.apache.org/jira/browse/PROTON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated PROTON-508:
Attachment: PROTON-508.txt
Use of Sasl auth results in a large performance hit
[
https://issues.apache.org/jira/browse/PROTON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated PROTON-508:
Attachment: (was: PROTON-508.txt)
Use of Sasl auth results in a large performance hit
Timothy Bish created PROTON-508:
---
Summary: Use of Sasl auth results in a large performance hit.
Key: PROTON-508
URL: https://issues.apache.org/jira/browse/PROTON-508
Project: Qpid Proton
Issue
Timothy Bish created PROTON-474:
---
Summary: Incorrect mapping of TTL to JMSExpiration in JMS
InboundTransformer
Key: PROTON-474
URL: https://issues.apache.org/jira/browse/PROTON-474
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated PROTON-474:
Attachment: JMSExpiration-patch.txt
Proposed patch for this issue.
Incorrect mapping of TTL
30 matches
Mail list logo
