wlsagent is leaking memory

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set up wlsagent to report on WebLogic multiple services and multiple 
items per server
2. Run it for a while
3. wlsagent will stop.  Looking with 'jstat' at the GC and memory usage 
behaviour, wlsagent has consumed all its heap.

Increasing the JVM heap memory for wlsagent doesn't help (unfortunately).

What is the expected output? What do you see instead?
wlsagent stops working

What version of the product are you using? On what operating system?
r1.85.  Red Hat Linux.  JDK 7.

Please provide any additional information below.
I tried to download the project in order to try and find the leak, but couldn't 
do so.  Do I need any special permissions?
Otherwise, *many thanks* for producing wlsagent - it's a very useful project 
and otherwise works very well.  Impressive stuff.

Original issue reported on code.google.com by apna...@gmail.com on 6 Aug 2014 at 6:44

[GoogleCodeExporter]

Hello,

I'm aware of this issue, you can check Issue 21 to get more details. I tried 
everything to fix this but as far as I'm concerned, it's related to the CORBA 
authentication mechanisms, so there's nothing I can do about it. We - at my 
company - don't have the right support contract (we can create SRs only for a 
server side related issue, and this is a client side related issue).

Yann

Original comment by yann.lambret@gmail.com on 6 Aug 2014 at 7:51

[GoogleCodeExporter]

Hi Yann,

Thanks for your reply.

Thinking about my options now ....

Do you have a script that you'd be willing to share that stops / starts the 
wlsagent via cron?  If you do, that would be terrific - and I'd be very 
grateful if you could post that.  If not, I'll need to write one up.

Sad about this GC issue.  I have some tooling (YourKit) so I might try and see 
if it can make any sense of what is going on.  When I was reading through your 
notes / reading the Oracle support page, you mentioned that you had a version 
that cached the JMX connections.  I'm wondering if this might be the best way 
to go, in that tests could be written around the connection and if it is bad a 
new connection is generated.

I like wlsagent - it has alot of functionality and is very useful.
It'd be great if this memory issue could be sorted.  :)

Cheers,

Adrian.

Original comment by apna...@gmail.com on 6 Aug 2014 at 10:29

[GoogleCodeExporter]

Hi again Yann,

I'm trying to checkout the 1.85 code but am having no success - I keep getting 
a 
'not found' message.  I'm using Tortoise SVN on Windows, and just plugging in 
the SVN information as you have it on the checkout page.

Could you please give me an idea about what I'm doing wrong?

Many Thanks,

Adrian.

Original comment by apna...@gmail.com on 6 Aug 2014 at 10:44

[GoogleCodeExporter]

Hi Adrian,

You should be able to checkout the code with this URL:

http://wlsagent.googlecode.com/svn/trunk/

If you do this at work, you'll probably have to use a proxy. I'm not sure of 
what I'm saying but I think Tortoise is using somme HTTP extensions and these 
may not be supported by your company's proxy.

Yann

Original comment by yann.lambret@gmail.com on 7 Aug 2014 at 8:35