I can only agree with Marcio that it is hardly possible to provide a detailed report or the error log as the server shuts itself down after running for a while for no obvious reason. It does not look like it is in a panic or having a problem with the memory - it seems it has just met some condition and now starts evacuating. For this is our production environment we cannot increase the logging level for all the org.jboss package tree. Can you perhaps recommend a sub-package that is worth setting to DEBUG to get a better idea on what is going on underneath ? Also, to may be give you a clue, I can admit that we started the performance tuning project on JBoss instance when this started to happen. All we did so far was to set Sun JVM to use -server, -Xms512m and -Xmx1024m. We are running Jboss 3.2.1 on Solaris 2.6 with applied patches for J2SDK 1.3+ and J2SDK 1.4.2_04.
Thanks, Nikolay. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850076#3850076 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850076 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
