New install, couple of quick questions(wierd screen attachment)

[Korny]

First of all, I'd like to thank all the posters in this forum for the large amount of information provided. I have 2 questions however
First off, I know I've read it somewhere, but how do I increase the JVM heap size again, I know in windows it a reg edit. I could have sworn it was a property file in sage that did it in linux but I am unable to find the post I read it on. So any help would be appreciated.
Secondly I used to have Jetty installed on port 8082 all was working well until I started getting screen that I have attached, anyone know what its about. I changed jetty to 8083 and its working fine, but I perfere to move it back to 8082 if possible. Thanks

Aaron

[KeithAbbott]

Originally Posted by Korny

First off, I know I've read it somewhere, but how do I increase the JVM heap size again, I know in windows it a reg edit. I could have sworn it was a property file in sage that did it in linux but I am unable to find the post I read it on. So any help would be appreciated.

Check out this thread: http://forums.sagetv.com/forums/show...istry+settings

[Korny]

Keith, sorry if I'm missing something but that program you posted looked as though it was for windows based Sage installs as it references registery entries. Again sorry if I'm missing something

[KeithAbbott]

Sorry, I missed that this was in the Linux forum. Please ignore...

[tmiranda]

Port 8082 is used by the H2 database and what you are seeing is the H2 console. If you want Jetty to use 8082 you have to move H2 to another port.

In linux the JVM heap size is set in the startup script. I don't have my linux box on right now but it's something like -XsmHHH where HHH is the heap size.

Tom

[drewg]

Originally Posted by Korny

First of all, I'd like to thank all the posters in this forum for the large amount of information provided. I have 2 questions however
First off, I know I've read it somewhere, but how do I increase the JVM heap size again, I know in windows it a reg edit. I could have sworn it was a property file in sage that did it in linux but I am unable to find the post I read it on. So any help would be appreciated.

In V6, you edit startsage.sh and change the -Xmx384m argument to java (might be -Xmx256m, I forget what the default was).

In V7, you edit (create?) a sagesettings file with the correct memory size exported in JAVAMEM. Eg:

% cat /opt/sagetv/server/sagesettings 
export PATH=/opt/jre/bin:$PATH
mkdir -p /var/tmp/sage
PIDFILE=/var/run/sagetv/sagetv.pid
JAVAMEM=-Xmx512m
JAVAOPTS="-Djava.io.tmpdir=/var/tmp/sage -XX:ThreadPriorityPolicy=42"

Drew