[
https://issues.apache.org/jira/browse/QPID-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved QPID-2112.
Resolution: Fixed
Assignee: Ted Ross
> C++ Client: Facility needed for app to extract the user-ID in
[
https://issues.apache.org/jira/browse/QPID-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston reassigned QPID-2076:
--
Assignee: Steve Huston
> C++ Broker assumes it can delete a pointer passed by message store plug
[
https://issues.apache.org/jira/browse/QPID-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston updated QPID-2076:
---
Attachment: QPID-2076.diff
Diffs attached to resolve this issue. Since this requires a change to exist
On Tue, Sep 22, 2009 at 11:18 AM, Martin Ritchie wrote:
> 2009/9/22 Rajith Attapattu :
>> On Tue, Sep 22, 2009 at 8:58 AM, Martin Ritchie wrote:
>>> 2009/9/22 Rajith Attapattu :
On Tue, Sep 22, 2009 at 7:13 AM, Martin Ritchie
wrote:
> Hi Rajith,
> Will this not cause both the
Martin Ritchie wrote:
2009/9/22 Rajith Attapattu :
Martin/Marnie,
As I mentioned in one of my previous emails, I recognized the issue
with having a log4j.xml in the classpath.
Therefore I proposed to convert the log4j.xml to a log4j.properties.
The current behaviour is totally unacceptable a
[
https://issues.apache.org/jira/browse/QPID-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758275#action_12758275
]
Steve Huston commented on QPID-1868:
The problem with trying to adapt QPID_TSS is that i
2009/9/22 Rajith Attapattu :
> Martin/Marnie,
>
> As I mentioned in one of my previous emails, I recognized the issue
> with having a log4j.xml in the classpath.
> Therefore I proposed to convert the log4j.xml to a log4j.properties.
> The current behaviour is totally unacceptable and believe me the
2009/9/22 Rajith Attapattu :
> On Tue, Sep 22, 2009 at 8:58 AM, Martin Ritchie wrote:
>> 2009/9/22 Rajith Attapattu :
>>> On Tue, Sep 22, 2009 at 7:13 AM, Martin Ritchie wrote:
Hi Rajith,
Will this not cause both the 0-8 and 0-10 code path to throw a
NullPointer if none of the brok
[
https://issues.apache.org/jira/browse/QPID-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758258#action_12758258
]
Rafael H. Schloming commented on QPID-1857:
---
According to gsim, this fix is no lon
[
https://issues.apache.org/jira/browse/QPID-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved QPID-1857.
---
Resolution: Won't Fix
> Java failover not working as session attach fails
> --
Martin/Marnie,
As I mentioned in one of my previous emails, I recognized the issue
with having a log4j.xml in the classpath.
Therefore I proposed to convert the log4j.xml to a log4j.properties.
The current behaviour is totally unacceptable and believe me there is
a fair number of folks who have co
To give a little history, we had lots of users who complained about this -
they *really* don't want us to ship log4j config files with our release. It
caused them endless pain trying to sort out classpath order with a whole
bundle of 3rd party libaries.
Marnie
On Tue, Sep 22, 2009 at 2:58 PM, Ra
On Tue, Sep 22, 2009 at 9:46 AM, Martin Ritchie wrote:
> 2009/9/22 Rajith Attapattu :
>> Martin,
>>
>> IMO our releases should have a sensible default logging level and is
>> something that most users expect.
>> So I don't think we should be asking users to set
>> -Dlog4j.configuration=client.log4
2009/9/22 Rajith Attapattu :
> Martin,
>
> IMO our releases should have a sensible default logging level and is
> something that most users expect.
> So I don't think we should be asking users to set
> -Dlog4j.configuration=client.log4j
>
> However I agree we could use a log4j.properties in our cli
On Tue, Sep 22, 2009 at 8:58 AM, Martin Ritchie wrote:
> 2009/9/22 Rajith Attapattu :
>> On Tue, Sep 22, 2009 at 7:13 AM, Martin Ritchie wrote:
>>> Hi Rajith,
>>> Will this not cause both the 0-8 and 0-10 code path to throw a
>>> NullPointer if none of the brokers are available on startup.
>>> Is
Martin,
IMO our releases should have a sensible default logging level and is
something that most users expect.
So I don't think we should be asking users to set
-Dlog4j.configuration=client.log4j
However I agree we could use a log4j.properties in our client instead
of a log4j.xml (all though this
2009/9/22 Rajith Attapattu :
> On Tue, Sep 22, 2009 at 7:13 AM, Martin Ritchie wrote:
>> Hi Rajith,
>> Will this not cause both the 0-8 and 0-10 code path to throw a
>> NullPointer if none of the brokers are available on startup.
>> Is the FailoverPolicy cycle count not what stops the looping?
>>
[
https://issues.apache.org/jira/browse/QPID-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707870#action_12707870
]
Martin Ritchie edited comment on QPID-1816 at 9/22/09 5:41 AM:
---
On Tue, Sep 22, 2009 at 7:13 AM, Martin Ritchie wrote:
> Hi Rajith,
> Will this not cause both the 0-8 and 0-10 code path to throw a
> NullPointer if none of the brokers are available on startup.
> Is the FailoverPolicy cycle count not what stops the looping?
>
> Regards
Hi Martin,
If the initia
Hi Rajith,
Will this not cause both the 0-8 and 0-10 code path to throw a
NullPointer if none of the brokers are available on startup.
Is the FailoverPolicy cycle count not what stops the looping?
Regards
Martin
2009/9/22 :
> Author: rajith
> Date: Tue Sep 22 03:11:56 2009
> New Revision: 817487
... and we had *loads* of complaints about this previously ;-(
Marnie
On Tue, Sep 22, 2009 at 11:42 AM, Martin Ritchie wrote:
> Rajith,
>
> One of the reasons we do not currently have a log4j.xml file in the
> client package is that all our users will pick this up.
> As you say on QPID-2113 Log4
Hi,
thanx for replying me.
I'm interested to join to contribute to develop client in C# and I'd like to
develop Broker management feature.
these days I follow up on this idea.
And prefer to join developing this and I think I can do this.
thank you.
[
https://issues.apache.org/jira/browse/QPID-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie reassigned QPID-1816:
Assignee: Martin Ritchie
> Unable to acknowledge messages after failover
> -
Rajith,
One of the reasons we do not currently have a log4j.xml file in the
client package is that all our users will pick this up.
As you say on QPID-2113 Log4j will scan the classpath looking for
log4j.xml then log4j.properties. If it finds one then it will use it.
I'm also not convinced we shou
24 matches
Mail list logo
