Rakesh Midha wrote:
Hello Chris,
Is there some specific scenerio where you are getting java heap space
error.
What I am guessing is that there can be a scenerio where classloaders
are cyclic. Is it possible, that
Classloader C1 is a parent of Classloader C2
Classloader C2 is a parent of Classloader C3
Classloader C3 is a parent of Classloader C1
As David Jencks pointed out this is not allowed. I was wondering if our
implementation enforces this. There are no specific steps to replicate
the problem but I usually get it after reloading Classloader viewer
portlet and doing searches a couple of times. So I’m guessing something
is not being garbage collected or there’s a memory leak somewhere. I'll
try to rebuild and see if it makes any difference.
BTW, I found another problem with the JNDI viewer portlet. After
deploying a standalone ejb jar I get a NullPointerException when viewing
the portlet. My guess is you forgot to consider the case where an ejb
module is deployed and it’s not inside an ear file resulting to a null
J2EE application.
Best wishes,
chris
If it is a possible, I need to figure out a way to know it and make
changes in tree, else it will continue filling the tree in cyclic order.
Anyone please let me know if the above scenerio is allowed or not. (If
it is allowed how is classes loaded, it will continue looking for
class in cyclic order forever and never load it.)
Thanks
Rakesh
On 1/11/07, *Rakesh Midha* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Oh I didnt see the JavaHeap space error about, let me check it out.
thanks
Rakesh
On 1/11/07, * Christopher M. Cardona* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Kevan,
FYI, I updated
https://issues.apache.org/jira/browse/GERONIMO-2689 to
include a patch that will fix the javascript error. You should
be able
to view the new portlets at least. Please let me know if you
still get
problems.
Best wishes,
chris
Kevan Miller wrote:
>
> On Jan 10, 2007, at 2:37 PM, Christopher M. Cardona wrote:
>
>> Hi Rakesh,
>>
>> I was able to run the new portlets using trunk rev494034 but
needed
>> to change all view.jsps because I get javascript errors
related to
>> your calls to dojo.require(). The console uses Dojo 0.4.1
right now
>> and I'm guessing you used a different version during
development.
>> Some widget names changed in 0.4.1.
>>
>> I'm getting a different problem this time using the ClassLoader
>> viewer. I get javax.servlet.ServletException: Java heap space:
>
> I've seen this error, also. None of the views were working
for me.
> Wasn't sure if it was a Safari issue or something else.
Rakesh, can
> you take a look at these issues (javascript errors and memory
> consumption by ClassLoader viewer)?
>
> Paul,
> Are you suggesting that we should start architecting the
console to be
> more pluggable? Or suggesting that Rakesh rewrite these viewers?
>
> --kevan
>
