[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582547#comment-13582547
 ] 

Marcus Sorensen commented on CLOUDSTACK-1339:
---------------------------------------------

Ok, that log just looks like business as usual.  I checked my dev system, which 
has been up since yesterday, and it's doing just fine, although it hasn't been 
doing a whole lot. It may be dependent on a certain level of activity.

One last thing and I'll leave this issue to someone else (maybe the guys who 
worked on Javelin), when you have an unresponsive management server, could you 
run 'cat /proc/meminfo' and post the results? I didn't see your memory/hardware 
spec in the response. Also, change /etc/cloudstack/management/tomcat6.conf, 
JAVA_OPTS back to previous settings once you get me that info, and see if you 
can trigger unresponsive server.

Old settings:
JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 
-Dcom.sun.management.jmxremote.authenticate=false 
-Dcom.sun.management.jmxremote.ssl=false -Xmx1024m 
-XX:+HeapDumpOnOutOfMemoryError 
-XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=256M"

                
> ASF 4.1: Management server becomes unresponsive
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-1339
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1339
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>            Reporter: Srikanteswararao Talluri
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> management server becomes unresponsive after running for a while and after 
> some time the process shuts down.
> This is blocking the testing 
> logs can be found @ https://citrix.sharefile.com/d/sa684d7a73fb45ba8

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to