Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,366,080
Community Members
 
Community Events
168
Community Groups

Have memory allocation settings changed?

According to this article the memory settings should be set in fisheyectl.sh (linux) by doing:

FISHEYE_OPTS="-Xms128m -Xmx1024m -XX:MaxPermSize=256m -Xss512k"

However on Crucible Fisheye 3.10.3 this string looks quite different:

FISHEYE_OPTS=`$JAVACMD -cp $FISHEYE_HOME/fisheyeboot.jar com.cenqua.fisheye.boot.OptsSetter`

 

Adding memory settings here, like this:

FISHEYE_OPTS=`$JAVACMD -Xms256m -Xmx2048m -XX:MaxPermSize=512m -cp $FISHEYE_HOME/fisheyeboot.jar com.cenqua.fisheye.boot.OptsSetter`

 

Does not do anything, am i doing it wrong?

2 answers

1 accepted

0 votes
Answer accepted

Sorted it by simply adding the parameters in the FISHEYE_CMD string instead:

FISHEYE_CMD="$JAVACMD $FISHEYE_OPTS -Xms4096m -Xmx8192m -Dfisheye.library.path........

In our Fisheye instance FISHEYE_OPTS is always set to -Xmx1024m by the subcommand  construction:

FISHEYE_OPTS=`$JAVACMD -cp $FISHEYE_HOME/fisheyeboot.jar com.cenqua.fisheye.boot.OptsSetter`

So we replaced this with 

FISHEYE_OPTS=" -Xmx2048m"

After restarting Fisheye this JVM input is really changed (according to System Information). However the Total memory is exactly the same as before with Xmx1024m.

According to http://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html this should have worked.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events