CORBA problem

• 报告人: freebeans
• 属主: freebeans
• 类型: Bugs
• 状态: 开启 [Owner assigned]
• 组件: v0.3.2
• 里程碑: (无)
• 优先: 5 - Medium
• 严重性: 5 - Medium
• 处理结果: 无
• 文件: 无

Details

I'm running a corba application made of:
1- A name server running on a desktop (JRE 1.5)
2- A corba server application running on a desktop
(JRE 1.5 developped
with JBuilder2005 and JDK 1.5)
3- A corba application running on PPC 2003 (JVM
Mysaifu developped with
JBuilder2005 and JDK 1.5)

The ppc application is run quite well but I get the
following
INTERMITANT error:
org.omg.CORBA.MARSHAL: Not a GIOP message: Immediate
EOF Minor: 0 (0).
Completed: not completed
at gnu.CORBA.GIOP.MessageHeader.read
(MessageHeader.java:305)
at gnu.CORBA.gnuRequest.submit(gnuRequest.java:841)
at gnu.CORBA.IorDelegate.invoke
(IorDelegate.java:184)
at org.omg.CORBA.portable.ObjectImpl._invoke
(ObjectImpl.java:201)
at
idl.com.eva.mrtms.objectManager.decoder._iDecoderStub.
GetName(_iDecoderS
tub.java:45)
at com.eva.ppc.MainFrame.connect(MainFrame.java)
at com.eva.ppc.MainFrame.access$000
(MainFrame.java:39)
at com.eva.ppc.MainFrame$2.actionPerformed
(MainFrame.java:79)
at java.awt.Button.processActionEvent
(Button.java:409)
at java.awt.Button.processEvent(Button.java:392)
at java.awt.Button.dispatchEventImpl
(Button.java:419)
at java.awt.Component.dispatchEvent
(Component.java:2670)
at java.awt.EventQueue.dispatchEvent
(EventQueue.java)
at java.awt.EventDispatchThread.run
(EventDispatchThread.java)
at java.lang.VMThread.run(VMThread.java:120)

Inspecting the GNU classpath code the exception occur
if the socket.read
function return empty after the connection of the
socket.

This communication error is not "moving". The
application is sending
several CORBA request to the server and the exception
is not always
raised on the same request:
I tested the application in several configuration:
1- On IPAQ with bluetooth connection: The exception
occur each 5 or 6
CORBA request.
2- On IPAQ on cradle: It goes well
3- Window mobile CE emulator 1.0 on the desktion: The
exception may
occure every 3 or 4 application launche.

I saw in the restriction that timeout is not
implemented on
java.net.socket, Could it be the source of my problem.

任务单历史 (1/1 Histories)

2006-12-12 22:35 Updated by: freebeans

• 属主 Update from (无) to freebeans
• (组 change on Tracker)
• (类别 change on Tracker)

评论

Logged In: YES
user_id=14530

It seems Mysaifu JVM has some problems with networking.

1. Socket timeout is not supported.
Pocket PC does not have "SO_RCVTIMEO" or "SO_SNDTIMEO".
http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/wcecomm5/html/wce50lrfsetsockoptwindowssockets.asp
> The following list shows BSD options that are not
supported for setsockopt .
>
> SO_ACCEPTCONN
> SO_RCVLOWAT
> SO_RCVTIMEO
> SO_SNDLOWAT
> SO_SNDTIMEO
> SO_TYPE

Socket.getSoTimeout() does nothing in currrent version of
Mysaifu JVM.

2. Native implementation does not throw SocketException
correctly.
I port GNU Classpath implementation (it is based on
Linux) to Pocket PC
(WinSock), but error handling code does not work correctly
yet.

I'll fix those problems in the future version.