You mention monitoring JVM memory usage. How are you doing that, using system tools? Unfortunately, that is not very helpful. You really need to monitory garbage collection data (e.g., -verbose:gc and similar JVM options) and examine that. That is the only thing that will tell you what is really going on.
Be aware that there will often be unused heap memory - the JVM will rarely use all of the memory that it asks for. For example, with a 1GB heap and a 200MB you generation, you will typically have at least 200MB of unused heap memory (unless you have a memory leak). The unused memory is a side0effect of the algorithm the JVM uses to determine when to do a full garbage collection.
See my presentation at http://www.cecmg.de/doc/tagung_2007/agenda07/24-mai/2b3-peter-johnson/ind...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144886#4144886
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144886
"claudio_br" wrote : Completing the my last post, I am using a Windows machine and you a Unix machine. The default file-encoding are different. Because of this you can got error 500.
| Please read my last post too.
| Thanks
I don't think the problem is related to unix vs. windows.
Maybe it's related to the machine default encoding.
Please, try to specify -Dfile.encoding=utf-8 on client side when executing the client via java command
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144883#4144883
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144883