Github user bayern39 closed the pull request at:
https://github.com/apache/activemq-artemis/pull/597
---
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
Github user bayern39 commented on the issue:
https://github.com/apache/activemq-artemis/pull/595
@jbertram OK,i will do it
---
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
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/601
ARTEMIS-596 fix JMS bridge example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis master_work
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/600
ARTEMIS-569 fix bridge producerWindowSize
Something bizarre happened with commit
8f52a622d0d883ca5e9f60ba7754ed51de38cc5c in April 2015. It reverted the
changes from both
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/598
---
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
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/597
Go ahead and close this PR please. Tom sent
https://github.com/apache/activemq-artemis/pull/599 which has (most of) the
appropriate changes.
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/599
---
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
GitHub user TomRoss opened a pull request:
https://github.com/apache/activemq-artemis/pull/599
ARTEMIS-596 JMS Bridge messages should be identified.
In cases where there are many JMS bridges defined on a broker it should
be possible to identify any error message by a bridge
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/595
Can you add a test to your commit which verifies the proper exception code
is returned in the case of a timeout?
---
If your project is set up for it, you can reply to this email and
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/597
Commit messages should follow the 50/72 pattern as noted in the "Commit
Messages" section on
http://activemq.apache.org/artemis/docs/1.3.0/hacking-guide/maintainers.html.
---
If your
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/598
the tests failures are not related to my changes.
---
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
GitHub user gaohoward opened a pull request:
https://github.com/apache/activemq-artemis/pull/598
ARTEMIS-594 support HTTPS access to hawtio
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gaohoward/activemq-artemis
GitHub user bayern39 opened a pull request:
https://github.com/apache/activemq-artemis/pull/597
[ARTEMIS-595] When creating JMS bridge management API should pass bridge
name to JMS broker
https://issues.apache.org/jira/browse/ARTEMIS-595
You can merge this pull request into a Git
13 matches
Mail list logo
