Changed the exception handling to get more mbeans even if some mbeans are broken.

Commit:
09a4ee9f3470dcbcd5b3fc24406134581cb377f5

I was able to reproduce the problem and it looks like this JBoss bug: https://issues.jboss.org/browse/JBAS-1955 ore one of the duplicates they have marked. Basically the MBean or what can be inside is broken (not serializable).
To double check that you can just use Java VisualVM and connect to the JBoss.
Accessing the "org.jboss.deployment.scanner.DeploymentFilter [URL]" will case the same error in Java VisualVM as in the JmxConfigTool.

To fix your problem in the JmxConfigTool i'm going to add a workaround, soon.

Thank you for your detailed bug report.

jmx configurator STDERR log

jmx configurator STDOUT run log

C:\temp>java -jar jmxconfiggenerator-0.0.1-SNAPSHOT-jar-with-dependencies.jar -jmx -host 192.168.1.27 -port 9403 -out 1.prop >1.log 2>2.log

Unfortunately, I have no idea about that mbean. specifically, it looks like a JBoss system mbean which i'm probably not interested in to begin with.

this is jboss-4.2.3 with Java 6u31 and instructing jboss to register mbeans with the system mbean server. If you want to reproduce, I suggest running a jboss instance with the factory 'all' profile.

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=9403"
JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"