[
https://issues.apache.org/jira/browse/QPID-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676702#comment-13676702
]
Minmin Ren commented on QPID-4903:
--
Then will someone to fix it?
> python
James Belch created QPID-4910:
-
Summary: Python, Ruby, and C++ clients automatically connect to
replica server when master fails
Key: QPID-4910
URL: https://issues.apache.org/jira/browse/QPID-4910
Project
[
https://issues.apache.org/jira/browse/QPID-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676623#comment-13676623
]
Steve Huston commented on QPID-4909:
Review board for diffs to resolve this issue:
htt
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11665/
---
Review request for qpid.
Description
---
Allow QMF to build on Windows usi
Steve Huston created QPID-4909:
--
Summary: QMF doesn't build correctly on Windows
Key: QPID-4909
URL: https://issues.apache.org/jira/browse/QPID-4909
Project: Qpid
Issue Type: Bug
Compo
The poller handles I/O on all connected sockets. Multiple threads can run the
poller to increase the I/O concurrency but there's no correlation between the
number of threads running the poller and the number of sockets.
> -Original Message-
> From: Subramaniam, Ganapathy [mailto:ganapath
[
https://issues.apache.org/jira/browse/QPID-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved QPID-2616.
---
Resolution: Duplicate
I'm not sure if this bug has always been the same bug as qpid-2518, but
[
https://issues.apache.org/jira/browse/QPID-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676174#comment-13676174
]
ASF subversion and git services commented on QPID-4854:
---
Commit 14899
On 06/05/2013 05:04 PM, Phil Harvey wrote:
On 5 June 2013 16:54, Gordon Sim wrote:
On 06/05/2013 03:27 PM, Phil Harvey wrote:
To recap, Rob, Rajith, Rafi and Gordon have expressed a desire for Proton
and the new JMS client to use a custom logging facade, rather than
directly
calling log4j, s
On 5 June 2013 16:54, Gordon Sim wrote:
> On 06/05/2013 03:27 PM, Phil Harvey wrote:
>
>> To recap, Rob, Rajith, Rafi and Gordon have expressed a desire for Proton
>> and the new JMS client to use a custom logging facade, rather than
>> directly
>> calling log4j, slf4j etc.
>>
>
> Just to clarify
I don't think it's worth retaining any JMS Client coding standards so I've
removed the page.
I did however tweak the main coding standards [1] to briefly mention TODO
comments, made a couple of draconian rules "recommended" rather than
mandatory, and touched on documenting the thread-safety of cla
On 06/05/2013 03:27 PM, Phil Harvey wrote:
To recap, Rob, Rajith, Rafi and Gordon have expressed a desire for Proton
and the new JMS client to use a custom logging facade, rather than directly
calling log4j, slf4j etc.
Just to clarify, I merely said that having some way to better integrate
the
[
https://issues.apache.org/jira/browse/QPID-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-4908:
Assignee: Robbie Gemmell (was: Alex Rudyy)
Robbie,
I changed the description text to the one you h
[
https://issues.apache.org/jira/browse/QPID-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-4908:
-
Status: Ready To Review (was: In Progress)
> [Java Broker] Expose queue attributes MessageGroupKey an
[
https://issues.apache.org/jira/browse/QPID-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned QPID-4908:
Assignee: Alex Rudyy (was: Robbie Gemmell)
> [Java Broker] Expose queue attributes Mess
[
https://issues.apache.org/jira/browse/QPID-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675968#comment-13675968
]
Robbie Gemmell commented on QPID-4908:
--
{code}
+@MBeanAttribute(name="MessageGroup
An interesting discussion about logging has emerged from the mailing thread
"AMQP 1.0 JMS client - supplementary coding standards". I'm starting a new
thread for this specific topic and am including the proton list.
To recap, Rob, Rajith, Rafi and Gordon have expressed a desire for Proton
and the
[
https://issues.apache.org/jira/browse/QPID-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-4908:
Assignee: Robbie Gemmell (was: Alex Rudyy)
Robbie,
Could you please review the changes in revision
Alex Rudyy created QPID-4908:
Summary: [Java Broker] Expose queue attributes MessageGroupKey and
MessageGroupSharedGroups via queue MBean
Key: QPID-4908
URL: https://issues.apache.org/jira/browse/QPID-4908
[
https://issues.apache.org/jira/browse/QPID-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675876#comment-13675876
]
Rob Godfrey commented on QPID-4837:
---
Hi Michael... we definitely want to add connection p
[
https://issues.apache.org/jira/browse/QPID-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-4837:
--
Fix Version/s: (was: Future)
0.23
> JDBC store should use connection pooler
>
On 06/05/2013 12:00 PM, Rafael Schloming wrote:
I think this approach is probably where we will end up going with proton
with the further step of having the facade actually wrap a configurable
logging callback so we don't need to build in any logging dependency at all
and it becomes easy to integ
On 5 June 2013 13:00, Rafael Schloming wrote:
> On the logging topic I think the JMS client (or any project really) should
> actually have an internal logging interface that wraps what it actually
> uses for logging. I've done this in the past a lot and found it very useful
> for a number of reas
On 06/05/2013 12:00 PM, Subramaniam, Ganapathy wrote:
Can you give me more details ? I am confused between the poller and
the socket.
There will typically be many clients connected to the broker, each using
its own socket. At any one time there may be nothing to read on a given
socket. The po
On the logging topic I think the JMS client (or any project really) should
actually have an internal logging interface that wraps what it actually
uses for logging. I've done this in the past a lot and found it very useful
for a number of reasons. For one thing the internal interface can actually
r
Can you give me more details ? I am confused between the poller and the socket.
The poller is waiting for messages on a pipe. I don’t understand how these two
work together. When the broker object is created, only n threads of the poller
are started. I am confused. So can you give me an brief o
For TODOs, I usually just consider them all roughly equally (in that there
should be a comment saying what needs changed and why) without any special
classification. I tend to closely examine all my changes prior to commit so
if I mean to change something I have added a TODO for before commiting th
On 06/05/2013 09:42 AM, Subramaniam, Ganapathy wrote:
I am trying to understand the flow of a message from the client to
the broker. From the broker code, I see that there are two entry
points to access the broker functions. One is when the socket
receives a message, it is decoded and finally th
Hello everyone,
I am trying to understand the flow of a message from the client to the broker.
From the broker code, I see that there are two entry points to access the
broker functions. One is when the socket receives a message, it is decoded and
finally the session adapter converts the amqp
Hello everyone,
I am trying to understand the flow of a message from the client to the broker.
From the broker code, I see that there are two entry points to access the
broker functions. One is when the socket receives a message, it is decoded and
finally the session adapter converts the amqp
30 matches
Mail list logo
