95 jars in lib dir makes jboss explode

SourceForge Submitter: charris .
Came across this obscure bug since we put a lot of
stuff in the standard jboss 'lib' dir.

Take a 3.2 release, and put into server/default/lib a
number of tiny jar files (my example contained a single
text file and manifest). Keep adding copies of this jar
until the total number of jars in the directory reaches 95.

Then 'run'. Whilst trying to deploy jboss-service.xml
you get CNFE's for each MBean class mentioned in the
xml file.

I turned on a whole pile of tracing information with
-Dlog4.configuration=log4-trace.properties and
discovered that the CNFE is caused by a
StackOverFlowError where the class loader tries to load
the jar protocol handler and gets into an infinite
recursion. However this is just the symptom - I suspect
there is a hard limit somewhere in the unified class
loading structure which is causing some class loaders
to 'fall off the front'.

There are lots of workarounds to this obviously but it
looks like I'm hitting a limit somewhere.

Chris Harris