Actually I don't think the memory settings has anything to do with that. The profiler uses some Java classes callings from the JNI layer if you use network options, for dealing with socket connections for control its life-cycle.
Unfortunelly the JVM doesn't behaves well if "profilerConsole.jar" is not on classpath. (Not that profilerConsole.jar is needed only if you use network options at the -XrunjbossInspector:). That's why I suggested to remove the network options and use the JMX MBeans for that job. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855015#3855015 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855015 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
