[Design of JBoss Labs] - Wrong headers slowing www.jboss.org down
by Tobias
Hi!
Pages from www.jboss.org are served with unoptimized response headers. Is there a reason for this or is this just an oversight?
Firebug shows me this for http://www.jboss.org/projects/:
http://www.jboss.org/projects/
Content-Type: text/html;charset=UTF-8
| Connection: close
| Transfer-Encoding: chunked
|
Ok, no keep-alice it seems. That's a bit weird, but ok.
http://www.jboss.org/file-access/default/theme/images/common/bkgheader_le...
Last-Modified: Fri, 01 Jun 2007 01:41:08 GMT
| Expires: Fri, 01 Jun 2007 01:41:08 GMT
| Content-Type: image/gif
| Connection: close
|
Again no keep-alive, ok. But Expires set to Last-Modified for a static gif?
Either set Expires to the future or better include a Cache-Control: max-age header.
http://www.jboss.org/file-access/default/theme/images/common/bkgheader_no...
Last-Modified: Fri, 01 Jun 2007 01:41:08 GMT
| Expires: Fri, 01 Jun 2007 01:41:08 GMT
| Content-Type: image/gif
| Connection: close
|
Again, no proper caching for static gifs.
For me fetching 10-30 static resources again and again for each page makes the whole thing really slow.
If you look into this, please also check the headers for the MIME-types for PNGs, JPG/jpegs and CSS.
Ciao,
Tobias
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143469#4143469
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143469
17 years, 12 months
[Deployers on JBoss (Deployers/JBoss)] - Re: jee module's alt-dd (Repost)
by adrian@jboss.org
"alex.loubyansky(a)jboss.com" wrote : I don't have strong preferences here. If it looks more logical then I'll do it that way.
|
| Except as it is done now, getOutput() is available only in the module deployer. The deployer that is attaching the altDD value (AppParsingDeployer in this case) has to use class names explicitly? I did it that way because the key construction was identical everywhere and that looked easier to me.
Yes, but in the standard EAR metadata you have to know the type anyway.
| <module>
| <ejb>ejb.jar</ejb> // Implies EjbJarMetaData.class.getName().altdd
| <alt-dd>altDD_ejb.xml</alt-dd>
| </module>
|
But the real point is that In JBoss there can be other files in META-INF.
e.g. an altDD_jboss.xml for the same module
which could be specified in jboss-app.xml or could be specified by the deployer
programmatically.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143445#4143445
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143445
17 years, 12 months
[Design of AOP on JBoss (Aspects/JBoss)] - Error during undeploy GeneratedClassAdvisor
by adrian@jboss.org
The following test in JBoss 5
| ./build.sh one-test -Dtest=org.jboss.test.aop.test.MicrocontainerJMXUnitTestCase
|
is giving the following error at undeploy
| 15:13:18,430 ERROR [AspectDeployer] Error during undeploy: vfsfile:/home/ejort/jboss-head/testsuite/output/lib/aop-mc-jmxtest-has-dependency.jar
| java.lang.IllegalStateException
| at java.util.WeakHashMap$HashIterator.remove(WeakHashMap.java:757)
| at org.jboss.aop.GeneratedClassAdvisor.cleanup(GeneratedClassAdvisor.java:133)
| at org.jboss.aop.classpool.AOPClassPoolRepository.doUnregisterClassLoader(AOPClassPoolRepository.java:206)
| at org.jboss.aop.classpool.AOPClassPoolRepository.access$000(AOPClassPoolRepository.java:51)
| at org.jboss.aop.classpool.AOPClassPoolRepository$UnregisterClassLoaderAction$2.unregister(AOPClassPoolRepository.java:267)
| at org.jboss.aop.classpool.AOPClassPoolRepository.perfomUnregisterClassLoader(AOPClassPoolRepository.java:180)
| at org.jboss.aop.classpool.AOPClassPool.close(AOPClassPool.java:84)
| at org.jboss.aop.asintegration.jboss5.JBoss5ClassPool.close(JBoss5ClassPool.java:73)
| at javassist.scopedpool.ScopedClassPoolRepositoryImpl.unregisterClassLoader(ScopedClassPoolRepositoryImpl.java:172)
| at org.jboss.aop.classpool.AOPClassPoolRepository.unregisterClassLoader(AOPClassPoolRepository.java:162)
| at org.jboss.aop.AspectManager.unregisterClassLoader(AspectManager.java:754)
| at org.jboss.aop.deployers.AspectDeployer.undeploy(AspectDeployer.java:141)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalUndeploy(AbstractVFSRealDeployer.java:54)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.undeploy(AbstractRealDeployer.java:112)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.undeploy(DeployerWrapper.java:197)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:1189)
|
The test now passes after I fixed the xml, but there's obviously some problem
with the aop cleanup of deployments.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143434#4143434
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143434
17 years, 12 months