如果您的应用程序相对较小并且没有任何 Java EE 5 模块，那么本文可能不适用。您可能可以调整一些其他 WAS 或操作系统配置来稍微提高部署性能，但如果所有这些因素都相同，则 WAS 7 部署实际上可能比 WAS 6.1 慢。如果您怀疑性能大幅下降，而本文没有帮助并且没有其他变量，您可以考虑联系 IBM 支持人员。
It suggests the following (seemingly in order of preference):
downgrade to J2EE 1.4 modules
utilizing the "metadata-complete" attribute in EE 5 module deployment descriptors
moving utility jars to shared libs
moving utility jars from WEB-INF/lib to the root of the EAR
If your application is relatively small and doesn't have any Java EE 5 modules, then this article might not be as applicable. It's possible that there may be some other WAS or OS configuration you could tune to help deployment performance slightly, but if all these factors are identical, it may just be possible that WAS 7 deployment is in fact slower than WAS 6.1. If you suspect a major downgrade in performance, the article doesn't help and there are no other variables, you might consider contacting IBM support.
Here is the description of the fix pack: “For very large applications with a large number of files and directories, application startup time has increased by a significant amount when moving from v5.0 to v5.1/v6.x. This is due to new code in later versions of WebSphere that search the application installation directories for TLD (taglib descriptor) files.”
Add the following property to WebContainer custom properties com.ibm.wsspi.jsp.disableTldSearch true
On my machine the statup time of Websphere 7 server was reduced from 1 min 30 secs to 45 seconds!
发布评论
评论（2）
这是来自 IBM 的一篇文章，标题为 “具有多个 Java 类的应用程序部署缓慢可能发生在 WebSphere Application Server Version 7.0 上”，它描述了您可以采取的一些方法来帮助减少应用程序的部署时间。本文主要关注 WAS 7 中对 Java EE 5 的新支持，该支持要求 WAS 在部署期间扫描所有模块、jar 和类以获取注释。
它建议进行以下操作（似乎按优先顺序排列）：
如果您的应用程序相对较小并且没有任何 Java EE 5 模块，那么本文可能不适用。您可能可以调整一些其他 WAS 或操作系统配置来稍微提高部署性能，但如果所有这些因素都相同，则 WAS 7 部署实际上可能比 WAS 6.1 慢。如果您怀疑性能大幅下降，而本文没有帮助并且没有其他变量，您可以考虑联系 IBM 支持人员。
Here is an article from IBM entitled "Slow Deployment of Applications with Multiple Java Classes Might Occur on WebSphere Application Server Version 7.0" that describes some approaches that you can take to help reduce the deployment time of your application. The article focuses primarily on the new support in WAS 7 for Java EE 5, which requires WAS to scan all modules, jars, and classes for annotations during deployment.
It suggests the following (seemingly in order of preference):
If your application is relatively small and doesn't have any Java EE 5 modules, then this article might not be as applicable. It's possible that there may be some other WAS or OS configuration you could tune to help deployment performance slightly, but if all these factors are identical, it may just be possible that WAS 7 deployment is in fact slower than WAS 6.1. If you suspect a major downgrade in performance, the article doesn't help and there are no other variables, you might consider contacting IBM support.
我刚刚发现有一个修复可以减少启动时间。该修复适用于版本 6.1.x 和版本 7.0.x
修复详细信息< /a>
以下是修复包的说明：
“对于具有大量文件和目录的大型应用程序，从 v5.0 迁移到 v5.1/v6.x 时，应用程序启动时间显着增加。这是由于 WebSphere 更高版本中的新代码在应用程序安装目录中搜索 TLD（标签库描述符）文件。”
将以下属性添加到 WebContainer 自定义属性
com.ibm.wsspi.jsp.disableTldSearch true
在我的机器上，Websphere 7 服务器的启动时间从 1 分 30 秒减少到 45 秒！
I just found that there is fix that reduces the startup time. The fix is available for Version 6.1.x and Version 7.0.x
Fix Details
Here is the description of the fix pack:
“For very large applications with a large number of files and directories, application startup time has increased by a significant amount when moving from v5.0 to v5.1/v6.x. This is due to new code in later versions of WebSphere that search the application installation directories for TLD (taglib descriptor) files.”
Add the following property to WebContainer custom properties
com.ibm.wsspi.jsp.disableTldSearch true
On my machine the statup time of Websphere 7 server was reduced from 1 min 30 secs to 45 seconds!