In JBoss 5.1. upon executing any OLAP View, including the sample 'Profile View', the application server hangs entirely. With INFO level loging the WEB-INF\logs\jasperserver.log indicates that the execution reaches the following log statement, but never progresses:
13:29:52,878 INFO [RendererTag] enter /performance/views/Profile_view/toolbar
Analysis in JConsole shows heap memory usage spiking and remaining high despite standard JAVA_OPT recommendations from install guide. A jmap heap dump shows that org.jboss.classloader.spi.base.BaseClassLoader has a “domains” member retaining an extraordinary amout of memory.
The problem was a classloading conflict within JBoss configuration. Modifying JBoss's jboss-classloading.xml file as follows resolved the issue:
<classloading domain="jasperserver-pro" export-all="NON_EMPTY" import-all="true" name="jasperserver-pro.war" parent-domain="DefaultDomain" xmlns="urn:jboss:classloading:1.0"> </classloading>
Ref. Case #00030563