GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/2179
NO-JIRAs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis tests
Alternatively you can review
GitHub user tadamski opened a pull request:
https://github.com/apache/activemq/pull/286
[WFLY-6597] Change org.apache.activemq.jms.pool.XaPooledConnectionFacâ¦
â¦tory#tmFromJndi parameter to Boolean for JCA validation
You can merge this pull request into a Git repository by
If concurrent access can be reproduced in a dev environment, it is possible
- with temporary code changes - to determine what two threads were
accessing the message at the same time.
An effective means to track this down is to record Exception objects (and
hence stack traces) at each point
Re-reading through my email backlog, I noticed this.
ActiveMQ already provides that type of persistence and guarantee of
delivery. Any additional implementation seems redundant - unless there are
some mitigating factors.
Art
On Fri, Jun 1, 2018 at 3:24 AM, gerardl wrote:
> Thanks Art. Some
Sorry if its redudant post . We are seeing kahadb file is growing beyond 10GB
. I have read in lot of forums that there is no way in cleaning that up .
Can you please help if there are any downside to this . We are using
activemq version 5.14.0
Appreciate your help !
--
Sent from:
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2177
---
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2178
I close this because It needs to be refined and battle tested...it is a WIP
:+1:
---
Github user franz1981 closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2178
---
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2178
I think that @clebertsuconic and @michaelandrepearce would be interested in
this :+1:
I would like to be reviewed on this: in particular given that I have target
x86_64 to define
GitHub user franz1981 opened a pull request:
https://github.com/apache/activemq-artemis/pull/2178
ARTEMIS-1977 ASYNCIO can reduce sys-calls to retrieve I/O events
On LibAIO is possible to retrieve the I/O completion
events without using io_getevents sys-calls by reading
the
10 matches
Mail list logo