调用 EJB 方法时出现 CORBA.COMM_FAILURE

发布于 2024-12-14 23:16:58 字数 845 浏览 2 评论 0原文

我们运行一个带有几个使用不同 EJB 的客户端的 WebSphere 服务器。其中一个客户端有时会在一个特定方法调用（每分钟运行一次 KeepAlive 方法）上失败。我们看到以下异常：

...
Caused by: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079696 Maybe; nested exception is: org.omg.CORBA.COMM_FAILURE: vmcid: SUN  minor code: 208 completed: Maybe
at com.sun.corba...
at...
...
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN  minor code: 208 completed: Maybe
at com.sun.corba... connectionAbort...
at...
...
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN  minor code: 215 completed: No
at com.sun.corba... transportReadTimeoutExceeded...
at...
...

我们所知道的是：

该客户端应用程序是唯一一个因该异常而失败的应用程序，并且它使用了其他人未使用的 EJB。
问题似乎是某种超时，但它发生得非常快，我们还没有找到可能的配置来更改。
在 WebSphere 控制台中，我们看到这个特定 EJB 的响应时间约为 360 毫秒，比其他 EJB 长大约 10 倍（但仍然可以？如果这是问题所在 - WAS 代码？）

提前谢谢。

原文

We run a WebSphere server with a few clients using different EJBs. One of the clients SOMETIMES fails on one specific method call (a KeepAlive method running every minute). We see the following exception:

...
Caused by: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079696 Maybe; nested exception is: org.omg.CORBA.COMM_FAILURE: vmcid: SUN  minor code: 208 completed: Maybe
at com.sun.corba...
at...
...
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN  minor code: 208 completed: Maybe
at com.sun.corba... connectionAbort...
at...
...
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN  minor code: 215 completed: No
at com.sun.corba... transportReadTimeoutExceeded...
at...
...

What we do know is:

This client application is the only one failing on this exception, and it uses an EJB that nobody else is using.
The problem appears to be some kind of timeout, but it happens very quickly and we haven't found a possible configuration to change.
In the WebSphere console we see that the response time of this specific EJB is about 360 millisec which is about 10 times more than other EJBs (but still OK? if that's the problem what might cause this - the WAS code?)
Thnx in advance.

分享到QQ

分享到微博