java memory issues since update

[sacrament055]

I've now received system messages that I'm out of memory where that never happened with the previous build. I know phoenix core services was updated as well so I can't say its gemstone for sure.

[jorton]

On your server or client(s)?

How many extenders?

What other plugins are you running?

Any details will help.

J

[sacrament055]

5 extenders and 2 clients but only 3 of the extenders have been on since the last reset.
I have comskip, webserver, play on, sagetv restart, sagex api.

Since the latest gemstone update I also updated phoenix core and play on. Prior to that all was well .

[jusjoken]

You will need to dig into your issue a little more for us to provide any help. The best bet is usually to get back to base Sage, add in Gemstone and then other plugins to see what may be causing the issue.

My system has run "excellent" from a heap perspective since the first public beta. I run 1 client and 2 extenders and my Heap goes between 260 and 550 and consistently cleans itself up back to around 260 without having to restart the server.

So something is obviously different with your setup and we will need more details, logs etc to narrow it down.

k

[sacrament055]

Sounds good, I'll do that. That's one of the odd things for me is the last time I got the message about memory I looked at the system information and it showed the heap was under 600MB at the time but somehow Sage was saying it was out of memory.

Is it worthwhile to also manually delete all files from the JAR folder just in case there's something in there that wasn't registered with the sage plugin system?

[jusjoken]

A clean install is always the cleanest option to find an issue but not always needed. But if you have just Sage and Gemstone installed and the heap is filling up then make sure the log is set to DEBUG and create an issue on the issues site with the logs attached (gemstone.log and the sagetv logs).

k

[uberpixel]

Originally Posted by sacrament055

I've now received system messages that I'm out of memory where that never happened with the previous build. I know phoenix core services was updated as well so I can't say its gemstone for sure.

I had the same error after the same updates.

I've never seen it before.

I did a full restart and haven't seen a repeat of the problem since.

-uberpixel