[英]WAS 8.5.5 ejb lookup produces invalid object reference com.ibm.ws.naming.util.InvalidObjectException
com.ibm.ws.naming.util.InvalidObjectException: Some object reference in the name "MyEJB" relative to the context "path/to/myserver" is invalid.
Some possible causes include a context binding in the name which refers to a destroyed context, or an object binding which contains an invalid EJBHome reference.
[Root exception is org.omg.CORBA.INV_OBJREF: Could not resolve IOR string. vmcid: 0x0 minor code: 0 completed: No]
The lookup of other ejbs in the app is working.应用程序中其他 ejb 的查找工作正常。 The difference is the bean class of this ejb was modified and only the new class file was updated in the ear and the app was updated with this ear file in WAS admin console.
不同之处在于此 ejb 的 bean class 已修改,只有新的 class 文件在 ear 中更新,应用程序在 WAS 管理控制台中使用此 ear 文件更新。
Do I have to regenerate the deployment code(stub/tie etc) for the ejb?我是否必须为 ejb 重新生成部署代码(stub/tie 等)?
The EJB deployment code only needs to be regenerated if the bean interfaces have been modified or the signature of the bean implementation methods has changed.如果 bean 接口已被修改或 bean 实现方法的签名已更改,则仅需要重新生成 EJB 部署代码。 If those have not changed, then likely the issue is the bean failed to start.
如果这些没有改变,那么问题很可能是 bean 未能启动。 Check the logs (Systemout.log and FFDC logs) for any other errors related to that EJB.
检查日志(Systemout.log 和 FFDC 日志)以查找与该 EJB 相关的任何其他错误。 The application may have started fine, but typically EJB initialization is deferred until first use, which is often the first time the bean is looked up.
应用程序可能启动良好,但通常 EJB 初始化会延迟到第一次使用时,这通常是第一次查找 bean 时。 Finally, verify the logs contain a CNTR0167I message indicating the bean was bound in JNDI using the lookup name.
最后,验证日志是否包含一条 CNTR0167I 消息,指示该 bean 已使用查找名称绑定在 JNDI 中。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.