Hi Bryan,
Sorry that no one got back to you about this. I'm afraid that I don't
know the answer to your question, I've copied the dev list into this
email in case someone who monitors that list (but not this one) has
any ideas.
Best regards,
Tom
On Thu, Jan 12, 2012 at 2:29 PM, Bryan Thompson
Bryan,
DGC threads should not be per exported object. Generally speaking, they tend
to be per endpoint (at which there are one or more remote objects exported).
Are you using any sort of custom endpoint implementation? Problems like this
can occur when an endpoint implementation doesn't impl
Is there another way to create an Endpoint per exported object? I'm
just thinking, it seems unlikely that Brian's implemented his own
Endpoint, but are there any other error conditions or incorrect use
scenarios that could produce the same problem?
Cheers,
Peter.
Peter Jones wrote:
Bryan,
I would say, that it's very easy to just code up a configuration entry, or a
dynamic construction in code where a new endpoint is also created per each
Exporter. That can quickly turn into a problematic situation in cases like
this, where there are lots of "quick" exports followed by terminati
It looks like there may be some problems with getting past the v5.4 juniper
software release to get to v6.2 on the 5GT because of memory limitations. I
finally got the latest 5.4 release installed this afternoon after wasting a
bunch of time trying to get the web page interface to "upgrading" t
tures.
>
> Thanks,
> Bryan
>
>> -Original Message-
>> From: Peter Jones [mailto:p...@roundroom.net]
>> Sent: Friday, January 13, 2012 12:04 AM
>> To: u...@river.apache.org
>> Cc: dev@river.apache.org
>> Subject: Re: DGC threads issue
>
Which is why the Object.equals/hashCode for an endpoint implementation is
critical.
-- Peter
On Jan 13, 2012, at 2:05 AM, Gregg Wonderly wrote:
> I would say, that it's very easy to just code up a configuration entry, or a
> dynamic construction in code where a new endpoint is also created pe
uot;Proxy is " + proxy + "(" + proxy.getClass() + ")");
} catch (ExportException ex) {
fatal("Export error: "+this, ex);
}
Thanks,
Bryan
> -Original Message-
> From: Peter Jones [mailto:p...@roundroom.net]
time: 0:00
java.lang.Thread.run()
> -Original Message-
> From: Peter Jones [mailto:p...@roundroom.net]
> Sent: Friday, January 13, 2012 9:31 AM
> To: u...@river.apache.org
> Cc: dev@river.apache.org
> Subject: Re: DGC threads issue
>
> Bryan,
>
> I meant that it might
done before we start the join manager since the
> * join manager will register the proxy.
> */
>try {
>
>proxy = exporter.export(impl);
>
> if (log.isInfoEnabled())
>log.info("Proxy is "
>
>
> (JSK) DGC Lease Checker [SLEEPING] CPU time: 0:00
> java.lang.Thread.run()
>
>
>
> (JSK) DGC Lease Checker [SLEEPING] CPU time: 0:00
> java.lang.Threa
> (JSK) DGC Lease Checker [SLEEPING] CPU time: 0:00
> java.lang.Thread.run()
>
>
>
> (JS
On 13-01-12 16:08, Peter Jones wrote:
Bryan,
In your example below, I'm referring to TcpServerEndpoint and its
associated classes (it's its ListenEndpoint and Endpoint
implementations for which Object.equals/hashCode are critical),
because that's what you're using in your exporters. And the sta
e.org
> Subject: Re: DGC threads issue
>
> Bryan,
>
> DGC threads should not be per exported object. Generally
> speaking, they tend to be per endpoint (at which there are
> one or more remote objects exported). Are you using any sort
> of custom endpoint implementation
Hi Peter,
I was wondering if you had any thoughts on this post from Bryan on River
users?
Hope you don't mind me asking ;)
Best Regards,
Peter Firmstone.
--- Begin Message ---
Hi Bryan,
Sorry that no one got back to you about this. I'm afraid that I don't
know the answer to your question,
Firmstone wrote:
Hi Peter,
I was wondering if you had any thoughts on this post from Bryan on
River users?
Hope you don't mind me asking ;)
Best Regards,
Peter Firmstone.
----------------
Subject:
Re: DGC threads issue
From:
To
ing if you had any thoughts on this post from Bryan on
River users?
Hope you don't mind me asking ;)
Best Regards,
Peter Firmstone.
----------------
Subject:
Re: DGC threads issue
From:
Tom Hobbs
Date:
Thu, 12 Jan 2012
any thoughts on this post from Bryan on
River users?
Hope you don't mind me asking ;)
Best Regards,
Peter Firmstone.
Subject:
Re: DGC threads issue
From:
Tom Hobbs
Date:
Thu, 12 Jan 2012 20:45:01 +
To:
u...@river.apache.org, dev@river.apache.org
To:
u...@river.apache.or
Firmstone.
>
> From: Tom Hobbs
> Date: January 12, 2012 3:45:01 PM EST
> To: u...@river.apache.org, dev@river.apache.org
> Subject: Re: DGC threads issue
> Reply-To: dev@river.apache.org
>
>
> Hi Bryan,
>
> Sorry that no one got back to you about this. I'm af
e is filled, it blocks.
>>
>> Can you report the issue as a Bug on Jira for me, I'll fix this before the
>> next release.
>>
>> Regards,
>>
>> Peter.
>>
>> Peter Firmstone wrote:
>>> Hi Peter,
>>>
>>> I was wondering if you had any thoughts on this post from Bryan on River
>>> us
, 2012 3:45:01 PM EST
*To: *u...@river.apache.org <mailto:u...@river.apache.org>,
dev@river.apache.org <mailto:dev@river.apache.org>
*Subject: **Re: DGC threads issue*
*Reply-To: *dev@river.apache.org <mailto:dev@river.apache.org>
Hi Bryan,
Sorry that no one got back to you about
om Bryan on River users?
Hope you don't mind me asking ;)
Best Regards,
Peter Firmstone.
--------
Subject:
Re: DGC threads issue
From:
Tom Hobbs
Date:
Thu, 12 Jan 2012 20:45:01 +
To:
u...@river.apache.org, dev@river.apache.org
To:
u...@river.apache.org, dev@river.apache.o
t out this fix.
Thanks,
Bryan
-Original Message-
From: Peter Firmstone [mailto:j...@zeus.net.au]
Sent: Friday, January 13, 2012 3:21 AM
To: dev@river.apache.org
Cc: Bryan Thompson; u...@river.apache.org
Subject: Re: [Fwd: Re: DGC threads issue]
Ok, found the problem, when I fixed
2012 8:41 AM
> To: Bryan Thompson
> Cc: dev@river.apache.org; u...@river.apache.org
> Subject: Re: [Fwd: Re: DGC threads issue]
>
> Brian,
>
> Do you have a Linux / Unix build environment?
>
> River isn't building yet on Window's, FreeBSD, or OpenBSD,
> known bu
r.apache.org; u...@river.apache.org
> Subject: Re: [Fwd: Re: DGC threads issue]
>
> Brian,
>
> Do you have a Linux / Unix build environment?
>
> River isn't building yet on Window's, FreeBSD, or OpenBSD,
> known build environments that work are Ubuntu and Solaris.
>
Peter Firmstone [mailto:j...@zeus.net.au]
Sent: Friday, January 13, 2012 8:41 AM
To: Bryan Thompson
Cc: dev@river.apache.org; u...@river.apache.org
Subject: Re: [Fwd: Re: DGC threads issue]
Brian,
Do you have a Linux / Unix build environment?
River isn't building yet on Window's, Free
che.org
Subject: Re: [Fwd: Re: DGC threads issue]
Brian,
Do you have a Linux / Unix build environment?
River isn't building yet on Window's, FreeBSD, or OpenBSD,
known build environments that work are Ubuntu and Solaris.
If not, that's ok, well be able to get the necessary ja
> Sent: Saturday, January 14, 2012 7:04 AM
> To: Bryan Thompson
> Cc: dev@river.apache.org; u...@river.apache.org
> Subject: Re: [Fwd: Re: DGC threads issue]
>
> Brian,
>
> First checkout the main trunk (I've only just committed the
> fix so make sure it's updated,
> -Original Message-
> From: Peter Firmstone [mailto:j...@zeus.net.au]
> Sent: Friday, January 13, 2012 3:21 AM
> To: dev@river.apache.org
> Cc: Bryan Thompson; u...@river.apache.org
> Subject: Re: [Fwd: Re: DGC threads issue]
>
> Ok, found the problem, when I fixed R
Bryan Thompson wrote:
Peter,
Rather than testing against the trunk, I would prefer to test the change
against the 2.2 release. That will allow me to avoid validating the entire
state of the trunk and let me focus on whether the change fixes the specific
DGC problem.
It looks like [1] is the
listed as an "Unreleased Version" in Jira.
[1] https://issues.apache.org/jira/browse/RIVER-403
> -Original Message-
> From: Tom Hobbs [mailto:tvho...@googlemail.com]
> Sent: Friday, January 13, 2012 7:35 AM
> To: u...@river.apache.org
> Subject: Re: RE: [F
30 matches
Mail list logo
