Alan,
I have upgraded my go to 1.5 and i dont see that error now.
Thanks,
Ram
On Fri, Nov 25, 2016 at 12:32 PM, Alan Conway wrote:
> On Fri, 2016-11-25 at 14:44 -0500, Alan Conway wrote:
> > On Fri, 2016-11-25 at 11:15 -0800, rammohan ganapavarapu wrote:
> > >
> > > Alan,
> > >
> > > I have th
On Fri, 2016-11-25 at 14:44 -0500, Alan Conway wrote:
> On Fri, 2016-11-25 at 11:15 -0800, rammohan ganapavarapu wrote:
> >
> > Alan,
> >
> > I have the same issue and raised a jira here "
> > https://issues.apache.org/jira/browse/PROTON-1356"; did you get
> > chance
> > to
> > take a look?
> >
On 25 November 2016 at 19:17, Alan Conway wrote:
> On Wed, 2016-11-23 at 12:40 +, Robbie Gemmell wrote:
>> I'd like to call this out more specifically following discussion in a
>> couple of recent threads, to ensure folks are clear on things before
>> they proceed. If not, shout.
>>
>> Followi
Updated JIRA, can you share your environment details may be i will try to
use same and see if it works for me.
Ram
On Fri, Nov 25, 2016 at 11:44 AM, Alan Conway wrote:
> On Fri, 2016-11-25 at 11:15 -0800, rammohan ganapavarapu wrote:
> > Alan,
> >
> > I have the same issue and raised a jira her
On Fri, 2016-11-25 at 11:15 -0800, rammohan ganapavarapu wrote:
> Alan,
>
> I have the same issue and raised a jira here "
> https://issues.apache.org/jira/browse/PROTON-1356"; did you get chance
> to
> take a look?
>
Looking now, but not sure what is happening, I can't reproduce and I
can't see
On Wed, 2016-11-23 at 03:07 +, Steve Huston wrote:
> I don't think anyone has done the work to manage availability on
> Windows so I don't think you can run a qpid cluster on Windows at
> this time.
Not out of the box, but if you can find a windows-based cluster manager
then you just need to
On Wed, 2016-11-23 at 12:40 +, Robbie Gemmell wrote:
> I'd like to call this out more specifically following discussion in a
> couple of recent threads, to ensure folks are clear on things before
> they proceed. If not, shout.
>
> Following completion of the 0.16.0 release, I will look to proc
Alan,
I have the same issue and raised a jira here "
https://issues.apache.org/jira/browse/PROTON-1356"; did you get chance to
take a look?
Ram
On Fri, Nov 25, 2016 at 11:02 AM, Alan Conway wrote:
> On Thu, 2016-11-24 at 20:26 +0100, Ulf Lilleengen wrote:
> > On 24. nov. 2016 14:34, Alex Kriti
On Thu, 2016-11-24 at 20:26 +0100, Ulf Lilleengen wrote:
> On 24. nov. 2016 14:34, Alex Kritikos wrote:
> >
> > hello all,
> >
> > i am interested in finding out more about the status of the Go
> > client, specifically level of completeness and whether it can be
> > installed as
> >
> > go get q
"I also think I see an issue with the closeTimeout handling in that in
one place it seems likely to be using the requestTimeout value
instead. Need to investigate that further."
Though in my attemps that didnt actually matter and the close
completed fine if the network dropped and no response coul
I'll try to find a way of preventing this problem from happening. (Though I'm
not sure how to do that properly at the moment.)
But how do you explain unlimited waiting for Close frame response as shown
in my previous post?
DraCzech wrote
> 2016-11-24 16:41:45.202589 [19105288:0] -> Close{error=
I had a look at this on master and though I did see a missing guard
(diff below) on the connection close that could be related, I haven't
reproduced what you are seeing even without that. It may still be
worth you giving it a try out.
Your logging snippets only include protons protocol trace, it m
Yes that looks like its trying to get a lock which the onMessage
handler is holding while firing, which is ongoing due to a send within
it.
On 25 November 2016 at 07:37, DraCzech wrote:
> When going through logs I also found this piece of thread dump. Which shows
> that my cleaning thread is wait
13 matches
Mail list logo
