Hi, I'm going through 'JBoss 4.0 The Official Guide' and reading LISTING 2.8 about a way to configure log4j.xml to obtain into a log file a verbose description of the Classloading mechanism. I tried that on my jboss 4.0.2 and, although it works, once the server has started there is a Thread which loads (or attempt to load) classes, and the file grows and grows in dimension. I was wondering if you know why?
Here follows the final part of the file which keeps repeating (is this due to hot deployment?)
[210093,RepositoryClassLoader,ScannerThread] Loaded class from cache, org.jboss.net.protocol.file.FileURLLister@1aacd5f<CodeSource: (file:/D:/OPENSOURCES/jboss-4.0.0/lib/jboss-common.jar <no signer certificates>)>
[210093,RepositoryClassLoader,ScannerThread] loadClass org.jboss.mx.loading.UnifiedClassLoader3@196e136{ url=file:/D:/OPENSOURCES/jboss-4.0.0/server/ports-01/tmp/deploy/tmp26094jboss-service.xml ,addedOrder=2} name=org.jboss.net.protocol.file.FileURLLister class=class org.jboss.net.protocol.file.FileURLLister cl=org.jboss.system.server.NoAnnotationURLClassLoader@139eeda
Don't take notice about the 4.0.0 part of the string, that was left in my system for commodity. The version running is 4.0.2.
