[GitHub] activemq-artemis pull request #841: ARTEMIS-795 Tests for temporary destinat...

[tabish121]

GitHub user tabish121 opened a pull request:

https://github.com/apache/activemq-artemis/pull/841

ARTEMIS-795 Tests for temporary destinations using dynamic nodes

Tests for the management of temporary destinations using the dynamic
node feature.  Failing case, the broker return a source or target that
indicates it will honor the lifetime policy of delete on close but the
temporary destination remains in existence after the link it closed.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-795

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/841.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #841


commit 0aca7938e13e24c24bb866d57dc41cd2a147ad24
Author: Timothy Bish 
Date:   2016-10-11T22:51:07Z

ARTEMIS-795 Tests for temporary destinations using dynamic nodes

Tests for the management of temporary destinations using the dynamic
node feature.  Failing case, the broker return a source or target that
indicates it will honor the lifetime policy of delete on close but the
temporary destination remains in existence after the link it closed.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request #840: ARTEMIS-794 Add tests for handling of va...

[tabish121]

GitHub user tabish121 opened a pull request:

https://github.com/apache/activemq-artemis/pull/840

ARTEMIS-794 Add tests for handling of various outcomes for deliveries

Adds tests for handling of Rejected, Released and Modified outcomes for
a delivery sent to a receiver.  Tests show that for the Modified outcome
the broker is redelivering the message to the same receiver when the
undeliverable here value is set which violates the AMQP 1.0 specified
handling of that field.  

Small fix included to not adjust the delivery count if the Modified
outcome does not indicate that the delivery failed.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-794

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/840.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #840


commit cb994c8f6b55f494389bde267415104043e38f86
Author: Timothy Bish 
Date:   2016-10-11T22:39:46Z

ARTEMIS-794 Add tests for handling of various outcomes for deliveries

Adds tests for handling of Rejected, Released and Modified outcomes for
a delivery sent to a receiver.  Tests show that for the Modified outcome
the broker is redelivering the message to the same receiver when the
undeliverable here value is set which violates the AMQP 1.0 specified
handling of that field.  

Small fix included to not adjust the delivery count if the Modified
outcome does not indicate that the delivery failed.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request #839: ARTEMIS-793 Improvement to OSGi integrat...

[graben]

GitHub user graben opened a pull request:

https://github.com/apache/activemq-artemis/pull/839

ARTEMIS-793 Improvement to OSGi integration



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/graben/activemq-artemis master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/839.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #839


commit 021fa843cd2ccabb2be509df18ebb57c8ab260ed
Author: Benjamin Graf 
Date:   2016-10-11T19:27:52Z

ARTEMIS-793 Improvement to OSGi integration




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request #838: ARTEMIS-268 Adds tests that shows issue ...

[tabish121]

GitHub user tabish121 opened a pull request:

https://github.com/apache/activemq-artemis/pull/838

ARTEMIS-268 Adds tests that shows issue with presettled receivers

Tests added that show that a receiver attached to a queue as presettled
are not removing the messages that are dispatched to them.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-268

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/838.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #838


commit 3f3f1f4e3d7231c29606a292169a2d0766380e1f
Author: Timothy Bish 
Date:   2016-10-11T18:07:02Z

ARTEMIS-268 Adds tests that shows issue with presettled receivers

Tests added that show that a receiver attached to a queue as presettled
are not removing the messages that are dispatched to them.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request #837: ARTEMIS-792 Add additional tests for AMQ...

[tabish121]

GitHub user tabish121 opened a pull request:

https://github.com/apache/activemq-artemis/pull/837

ARTEMIS-792 Add additional tests for AMQP protocol

Adds several tests for AMQP expectations in various use cases.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-792

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/837.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #837


commit e3bda788bfbd12f43d58e52b2e0d14351960c4a6
Author: Timothy Bish 
Date:   2016-10-11T16:16:28Z

ARTEMIS-792 Add additional tests for AMQP protocol

Adds several tests for AMQP expectations in various use cases.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Please help compile the ASF board report

[John D. Ament]

It should be "Java EE 7" but other than that its good.

You may want to point out the project's description has been updated.

John

On Tue, Oct 11, 2016 at 10:23 AM Bruce Snyder 
wrote:

> Thank you for providing some info for the board report, John. I have added
>
> this info, but please read through to see if there's more to be added.
>
>
>
> Bruce
>
>
>
> On Thu, Oct 6, 2016 at 5:52 PM, John D. Ament 
>
> wrote:
>
>
>
> > Bruce,
>
> >
>
> > I can't edit the wiki page (not sure if I should be able to or not).
> But a
>
> > couple of things:
>
> >
>
> > - The project description is a bit out of date.  Might be good to include
>
> > things like JMS 2 support, STOMP, REST, MQTT, etc.  I would say update
> the
>
> > doap file, but it seems the description isn't sourced from doap for
>
> > ActiveMQ.
>
> > - New releases like 5.13.4, 5.14.0, 5.14.1, Artemis 1.4.0 as well as a
>
> > planned Artemis 1.4.1/1.5 release soon
>
> > - Active Discussions around a new web console
>
> > - Project's a little stuck on the docker issues pending infra and legal
>
> > resolution
>
> >
>
> > John
>
> >
>
> > On Thu, Oct 6, 2016 at 6:49 PM Bruce Snyder 
>
> > wrote:
>
> >
>
> > > Only six more days to update the board report!
>
> > >
>
> > > Please take a few minutes to contribute regarding the ActiveMQ and
>
> > Artemis
>
> > > development activity.
>
> > >
>
> > > Thank you!
>
> > >
>
> > > Bruce
>
> > >
>
> > > On Mon, Oct 3, 2016 at 3:47 PM, Bruce Snyder 
>
> > > wrote:
>
> > >
>
> > > > Hi All,
>
> > > >
>
> > > > It is time again to provide a report to the ASF board. Please take a
>
> > few
>
> > > > moments to help compile the development activity within the project
>
> > over
>
> > > > the last three months at the following URL:
>
> > > >
>
> > > >
>
> > > https://cwiki.apache.org/confluence/pages/viewpage.
>
> > action?pageId=65873416
>
> > > >
>
> > > > I've put two placeholders into the report, one for ActiveMQ and one
> for
>
> > > > ActiveMQ Artemis. Please flesh out the development activity from the
>
> > last
>
> > > > 90 days accordingly.
>
> > > >
>
> > > > As always, your assistance is greatly appreciated,
>
> > > >
>
> > > > Bruce
>
> > > >
>
> > > > --
>
> > > > perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&
>
> > > > 5R\"F)R=6-E+G-N>61E
> > > >
>
> > > > ActiveMQ in Action: http://bit.ly/2je6cQ
>
> > > > Blog: http://bsnyder.org/ 
>
> > > > Twitter: http://twitter.com/brucesnyder
>
> > > >
>
> > >
>
> > >
>
> > >
>
> > > --
>
> > > perl -e 'print
>
> > > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E );'
>
> > >
>
> > > ActiveMQ in Action: http://bit.ly/2je6cQ
>
> > > Blog: http://bsnyder.org/ 
>
> > > Twitter: http://twitter.com/brucesnyder
>
> > >
>
> >
>
>
>
>
>
>
>
> --
>
> perl -e 'print
>
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E
>
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
>
> Blog: http://bsnyder.org/ 
>
> Twitter: http://twitter.com/brucesnyder
>
>

Re: Please help compile the ASF board report

[Bruce Snyder]

Thank you for the updates to the report, Clebert. I'm happy to hear that
you are safe!

Bruce

On Thu, Oct 6, 2016 at 5:21 PM, Clebert Suconic 
wrote:

> I intended to do it between yesterday and today. But I had to duck for the
> hurricane.  :)
>
> It's all good here.  Just didn't have enough focus to do anything beyond
> secure my house.
>
> I will pick it up on the next few days.
>
> On Thursday, October 6, 2016, Bruce Snyder  wrote:
>
> > Only six more days to update the board report!
> >
> > Please take a few minutes to contribute regarding the ActiveMQ and
> Artemis
> > development activity.
> >
> > Thank you!
> >
> > Bruce
> >
> > On Mon, Oct 3, 2016 at 3:47 PM, Bruce Snyder  > > wrote:
> >
> > > Hi All,
> > >
> > > It is time again to provide a report to the ASF board. Please take a
> few
> > > moments to help compile the development activity within the project
> over
> > > the last three months at the following URL:
> > >
> > > https://cwiki.apache.org/confluence/pages/viewpage.
> > action?pageId=65873416
> > >
> > > I've put two placeholders into the report, one for ActiveMQ and one for
> > > ActiveMQ Artemis. Please flesh out the development activity from the
> last
> > > 90 days accordingly.
> > >
> > > As always, your assistance is greatly appreciated,
> > >
> > > Bruce
> > >
> > > --
> > > perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&
> > > 5R\"F)R=6-E+G-N>61E > >
> > > ActiveMQ in Action: http://bit.ly/2je6cQ
> > > Blog: http://bsnyder.org/ 
> > > Twitter: http://twitter.com/brucesnyder
> > >
> >
> >
> >
> > --
> > perl -e 'print
> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E >
> > ActiveMQ in Action: http://bit.ly/2je6cQ
> > Blog: http://bsnyder.org/ 
> > Twitter: http://twitter.com/brucesnyder
> >
>
>
> --
> Clebert Suconic
>



-- 
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E
Twitter: http://twitter.com/brucesnyder

[GitHub] activemq-artemis issue #835: ARTEMIS-786 Store user's password in hash form ...

[gaohoward]

Github user gaohoward commented on the issue:

https://github.com/apache/activemq-artemis/pull/835
  
hmm, sth wrong with Jenkins I think. My local run is ok. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis issue #835: ARTEMIS-786 Store user's password in hash form ...

[gaohoward]

Github user gaohoward commented on the issue:

https://github.com/apache/activemq-artemis/pull/835
  
@jbertram I move the hash factory api into the same PasswordMaskingUtil to 
reduce confusion, so that both 2-way encryption and one-way hashing APIs are in 
the same util class. But I'm not sure what's the benefit of bring in Jasypt. 
The PasswordMaskingUtil provides a general API which enables user to use 
customized password encoder/decoder like Jasypt, if he really want it. What do 
you think?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis issue #833: Change netty version to 4.1.5.Final

[clebertsuconic]

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/833
  
@paulgallagher75  it still didn't work actually... I will ask @dejanb 's 
help :)


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---