Solaris 上的 Websphere 6.1.0.23 的 jvm 版本
您好，我在大型金融机构，我们有一个在 Websphere 6.1 上运行的应用程序。在 Solaris 上。由于 MQ Connectivity，我们必须安装修复包 6.1.0.23。不幸的是，这破坏了 ejb (1.1)，它仍然作为遗产存在（测试错过了它）。
[3/23/10 11:33:18:703 CET] 00000055 EJBContainerI E WSVR0068E: Attempt to start EnterpriseBean EventRisk_1.0.0#EventRiskEJB.jar#PolicyDataManager failed with exception: java.lang.NoSuchMethodError: com.ibm.ejs.csi.ResRefListImpl.(Lorg/eclipse/jst/j2ee/ejb/EnterpriseBean;Lcom/ibm/ejs/models/base/bindings/ejbbnd/EnterpriseBeanBinding;Lcom/ibm/ejs/models/base/extensions/ejbext/EnterpriseBeanExtension;)V
at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.finishBMDInit(EJBMDOrchestrator.java:1364)
at com.ibm.ws.runtime.component.EJBContainerImpl.finishDeferredBeanMetaData(EJBContainerImpl.java:4829)
at com.ibm.ws.runtime.component.EJBContainerImpl$3.run(EJBContainerImpl.java:4631)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:125)
at com.ibm.ws.runtime.component.EJBContainerImpl.initializeDeferredEJB(EJBContainerImpl.java:4627)
at com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:390)
at com.ibm.ejs.container.HomeOfHomes.internalCreateWrapper(HomeOfHomes.java:938)
at com.ibm.ejs.container.EJSContainer.createWrapper(EJSContainer.java:4783)
at com.ibm.ejs.container.WrapperManager.faultOnKey(WrapperManager.java:545)
at com.ibm.ejs.util.cache.Cache.findAndFault(Cache.java:498)
at com.ibm.ejs.container.WrapperManager.keyToObject(WrapperManager.java:489)
我们无法在台式机上重现该问题（在那里一切正常），并且我们无法直接访问 Solaris 计算机（取决于部署部门），我们确实怀疑 jvm 上存在差异，但我们不确定。
我的问题有两个：
- 您能否确认 IBM 的 声明 修复包 6.1 .0.23 for Solaris 确实在 jvm 1.5.0_17b04 上运行，我们的安装告诉我们 ./java -version java version "1.5.0_13" 但部署部门并不急于调查。
- 除了聘请蓝色巨人的顾问之外，您还看到其他解决方案吗？
亲切的问候，
杰罗恩.
Hi I'm at big financial institute and we've an application running on Websphere 6.1. on Solaris. Due to MQ Connectivity we had to install fixpack 6.1.0.23. Unfortunately this broke an ejb (1.1) which is still there as legacy (Test missed it).
[3/23/10 11:33:18:703 CET] 00000055 EJBContainerI E WSVR0068E: Attempt to start EnterpriseBean EventRisk_1.0.0#EventRiskEJB.jar#PolicyDataManager failed with exception: java.lang.NoSuchMethodError: com.ibm.ejs.csi.ResRefListImpl.(Lorg/eclipse/jst/j2ee/ejb/EnterpriseBean;Lcom/ibm/ejs/models/base/bindings/ejbbnd/EnterpriseBeanBinding;Lcom/ibm/ejs/models/base/extensions/ejbext/EnterpriseBeanExtension;)V
at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.finishBMDInit(EJBMDOrchestrator.java:1364)
at com.ibm.ws.runtime.component.EJBContainerImpl.finishDeferredBeanMetaData(EJBContainerImpl.java:4829)
at com.ibm.ws.runtime.component.EJBContainerImpl$3.run(EJBContainerImpl.java:4631)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:125)
at com.ibm.ws.runtime.component.EJBContainerImpl.initializeDeferredEJB(EJBContainerImpl.java:4627)
at com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:390)
at com.ibm.ejs.container.HomeOfHomes.internalCreateWrapper(HomeOfHomes.java:938)
at com.ibm.ejs.container.EJSContainer.createWrapper(EJSContainer.java:4783)
at com.ibm.ejs.container.WrapperManager.faultOnKey(WrapperManager.java:545)
at com.ibm.ejs.util.cache.Cache.findAndFault(Cache.java:498)
at com.ibm.ejs.container.WrapperManager.keyToObject(WrapperManager.java:489)
We cannot reproduce the issue on our desktop boxes (it all works fine there) and we do not have direct access to our the Solaris machines (dependent on the deployment department) we do suspect a discrepancy on the jvm but we're not sure.
My question is two fold:
- can you confirm IBM's statement that fixpack 6.1.0.23 for solaris indeed runs on jvm 1.5.0_17b04 our installation tells us ./java -version java version "1.5.0_13" But deploy department is not eager to investigate.
- Do you see some other solution, apart from hiring big blue's con$ultancy?
kind regards,
Jeroen.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我建议打开 PMR，这是确认您所引用的注释可能存在的任何问题的官方方式。
我想借此机会澄清一些术语。 6.1.0.23 是完整的版本信息，修复包在这里是“23”。
您的注释中明确指出“Java SDK 1.5.0 SR9 累积修复已使用 WebSphere Application Server V6.1.0.23 进行了全面测试。”。它确实指出此 CF 将导致“Solaris 的累积修复将升级到 1.5.0_17-b04”。
这些声明暗示 IBM 将支持 WAS 6.1.0.23 的这个 JDK 版本，该版本是通过正式支持流程提供支持的。
这个 JDK 能否为您解决 EJB 问题是另一个问题？ java.lang.NoSuchMethodError 错误听起来不像 JDK 累积修复会修复的错误。不过我还没有详细查看该错误。
警告：我在 IBM 工作，但此观点仅是我的观点，并不以任何方式反映我雇主的观点。
华泰
曼鲁
I would suggest open up a PMR and that is the official way to confirm any issue that you may have with respect to the note that you had referenced.
I would take this opportunity to clarify some terminology. 6.1.0.23 is the complete version info and the fixpack is "23" here.
And this note that you had states clearly that "Java SDK 1.5.0 SR9 Cumulative Fix was fully tested with WebSphere Application Server V6.1.0.23.". It does states that this CF would result in "The cumulative fix for Solaris will upgrade to 1.5.0_17-b04".
The statements imply that IBM would support this JDK version for WAS 6.1.0.23 that it is supported via the formal support process.
Would this JDK fix the EJB issues for you is another question all-together? The error java.lang.NoSuchMethodError doesn't sound like one which is going to fixed as a result of this JDK Cumulative fix. I haven't looked at the error in detail though.
Caveat: I work for IBM but this opinion is mine and does not in any way reflects that of my employer.
HTH
Manglu