Jacorb/Tao 互操作性

发布于 2024-11-18 15:55:33 字数 671 浏览 3 评论 0原文

我有 Appl A，它是 JacORB 客户端，Appl B 是 TAO 服务器。

执行细节：

a) Appl A 最初使用其 corbaloc URL 为服务器进程 (Appl B) 创建 object_reference，并在映射中维护此引用以供后续使用。这意味着相同的对象引用用于 Appl B 上的所有 corba 调用。

b) Appl A 在上面创建的 Appl B 的缩小对象引用上调用清单方法。

c) 在服务器端（TAO），仆人完成请求并发送响应。

d）经过很长一段时间（我认为在超时间隔之后），在 Jacorb 客户端上我得到了一个异常：

     org.omg.CORBA.COMM_FAILURE:   vmcid: 0x0  minor code: 0 completed: Maybe
    at org.jacorb.orb.giop.ReplyPlaceholder.getInputStream(ReplyPlaceholder.java:133)

。 e) 如果在上述请求超时之前，如果在服务器上再次进行相同的查询（使用相同的连接对象），则两个响应都会收到并正确处理，

知道在这种情况下如何继续吗？我的猜测是套接字缓冲区正在等待刷新，这就是为什么它总是第二次工作知道如何强制刷新连接对象吗？

原文

I have Appl A which is JacORB client and Appl B is the TAO server .

Details of execution:

a) Appl A initially creates the object_reference for server process (Appl B) using its corbaloc URL and maintains this reference in a map for subsequent usage.
This mean the same object reference is used for all the corba calls on Appl B.

b) Appl A calls a inventory method on the narrowed object reference of Appl B as created above.

c) On Server side (TAO), the servant completes the request and sends the reponse.

d) After a long time (I think after the timeout interval)on the Jacorb Client side I get an exception :

     org.omg.CORBA.COMM_FAILURE:   vmcid: 0x0  minor code: 0 completed: Maybe
    at org.jacorb.orb.giop.ReplyPlaceholder.getInputStream(ReplyPlaceholder.java:133)

.
e) In case, before the above request times out, if same query is again made on the server, ( uses same connection object ), both responses are received ,processed properly

Any idea how to proceed in this case ?
My guess is that socket buffer is waiting for a flush ,thats why it always works the second time
Any idea how to force the flush on the connection object ?

分享到QQ

分享到微博