[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687215#comment-16687215
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user franz1981 commented on the
Github user franz1981 commented on the issue:
https://github.com/apache/qpid-jms/pull/26
I have TBH that I'm not getting such a big boost as I was expecting, but
probably because there are other bottlenecks (the consumer side on the broker)
that are not' helping to measure it correctl
[
https://issues.apache.org/jira/browse/PROTON-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1964:
Description:
The bug PROTON-1586 had events returned after a connection was
TRANSPORT_CLOSED and
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687209#comment-16687209
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user tabish121 commented on the
[
https://issues.apache.org/jira/browse/PROTON-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1964:
Description:
The bug PROTON-1586 had events returned after a connection was
TRANSPORT_CLOSED and
Github user tabish121 commented on the issue:
https://github.com/apache/qpid-jms/pull/26
Yes, that test is exposing some issues in the 5.x broker which is unrelated
to this change.
---
-
To unsubscribe, e-mail: dev-
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687204#comment-16687204
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user franz1981 commented on the
Github user franz1981 commented on the issue:
https://github.com/apache/qpid-jms/pull/26
The failing test
`JmsConnectionCloseVariationsTest.testCloseBeforeBrokerStoppedRepeated` seems
that is not allocating any `FifoMessageQueue`: i suppose its failure is
indipendent by this PR.
--
[
https://issues.apache.org/jira/browse/PROTON-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1964:
Description:
The original but
Run the send examples code with an invalid hostname like shown
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687185#comment-16687185
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user franz1981 commented on the
Github user franz1981 commented on the issue:
https://github.com/apache/qpid-jms/pull/26
Just as a reference: I'm getting about 80 M msg/sec with the new
`FifoMessageQueue` while near 2.5 M msg/sec with the original one.
On a end-to-end test I'm getting a 20% more throughput with m
Alan Conway created PROTON-1964:
---
Summary: [c] pn_proactor_wait() can return empty event batches.
Key: PROTON-1964
URL: https://issues.apache.org/jira/browse/PROTON-1964
Project: Qpid Proton
Is
[
https://issues.apache.org/jira/browse/DISPATCH-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687116#comment-16687116
]
ASF GitHub Bot commented on DISPATCH-1177:
--
Github user ganeshmurthy commente
Github user ganeshmurthy commented on the issue:
https://github.com/apache/qpid-dispatch/pull/420
Should it say "Router is Standalone or Edge - No Router List".
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.ap
Chuck Rolke created DISPATCH-1186:
-
Summary: qdstat to include csv output format
Key: DISPATCH-1186
URL: https://issues.apache.org/jira/browse/DISPATCH-1186
Project: Qpid Dispatch
Issue Type:
[
https://issues.apache.org/jira/browse/DISPATCH-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687024#comment-16687024
]
ASF GitHub Bot commented on DISPATCH-1177:
--
Github user fgiorgetti commented
Github user fgiorgetti commented on the issue:
https://github.com/apache/qpid-dispatch/pull/420
@ganeshmurthy I have executed qdstat with -e on a formed network here and I
see the "edge" routers from an interior router, and the "interior" router when
executed against edge. It makes se
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686991#comment-16686991
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user jdanekrh commented on the i
Github user jdanekrh commented on the issue:
https://github.com/apache/qpid-jms/pull/26
Won't work with JDK < 8 is fine with qpid-jms, I think
https://github.com/apache/qpid-jms/blob/master/pom.xml#L37-L39
I'll check tomorrow if IBM JDK supports this. I am fairly sure
[
https://issues.apache.org/jira/browse/QPIDJMS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686988#comment-16686988
]
ASF subversion and git services commented on QPIDJMS-431:
-
Commi
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686954#comment-16686954
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user franz1981 commented on the
Github user franz1981 commented on the issue:
https://github.com/apache/qpid-jms/pull/26
It won't work with JDK < 8 and is specific of oracle AFAIK (I could be
wrong of course!)
---
-
To unsubscribe, e-mail: dev-uns
Github user jdanekrh commented on the issue:
https://github.com/apache/qpid-jms/pull/26
Wouldn't `@Contended` annotation work just as well?
http://mail.openjdk.java.net/pipermail/hotspot-dev/2012-November/007309.html (I
just googled it...)
---
--
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686944#comment-16686944
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user jdanekrh commented on the i
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686859#comment-16686859
]
ASF GitHub Bot commented on QPIDJMS-430:
Github user franz1981 commented on the
Github user franz1981 commented on the issue:
https://github.com/apache/qpid-jms/pull/26
The reason behind the abstract classes for padding between fields to avoid
false sharing (that could lead to a 1/10 of performance):
```
OFFSET SIZE
Timothy Bish created QPIDJMS-431:
Summary: Refactor the Failover provider to improve performance
Key: QPIDJMS-431
URL: https://issues.apache.org/jira/browse/QPIDJMS-431
Project: Qpid JMS
Issu
[
https://issues.apache.org/jira/browse/QPIDJMS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686794#comment-16686794
]
ASF GitHub Bot commented on QPIDJMS-430:
GitHub user franz1981 opened a pull req
Francesco Nigro created QPIDJMS-430:
---
Summary: Lock-Free FifoMessageQueue
Key: QPIDJMS-430
URL: https://issues.apache.org/jira/browse/QPIDJMS-430
Project: Qpid JMS
Issue Type: Improvement
GitHub user franz1981 opened a pull request:
https://github.com/apache/qpid-jms/pull/26
QPIDJMS-430 Lock-Free FifoMessageQueue
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/franz1981/qpid-jms lock_free_fifo_q
Alternatively you
[
https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686480#comment-16686480
]
ASF GitHub Bot commented on QPID-7541:
--
GitHub user alex-rufous opened a pull request
[
https://issues.apache.org/jira/browse/QPID-7372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686487#comment-16686487
]
ASF GitHub Bot commented on QPID-7372:
--
Github user alex-rufous commented on the issu
Github user alex-rufous commented on the issue:
https://github.com/apache/qpid-broker-j/pull/13
Hi nitin1706,
com.sleepycat:je::7.4.5 is compiled with java8 whilst Qpid 6.x is java 7
compatible. In order to keep Qpid 6.x java7 compatible, we cannot upgrade JE
to version 7.4.5. Pl
GitHub user alex-rufous opened a pull request:
https://github.com/apache/qpid-broker-j/pull/17
QPID-7541: [Broker-J] Close consumers when a Queue is deleted
The proposed changes allow to close queue sending and receiving links and
mark all in-progress queue transactions as read-only
34 matches
Mail list logo
