[omniORB] omniORB problem with giopServer on win32...
Thomas Zumbiehl
zumbiehl@bvassociates.fr
Wed Apr 23 09:32:02 2003
Hi guys,
I have a server based on omniORB 3.0.4 that works fine on Linux, AIX, HP-UX
and Solaris stations. I am currently performing a port of it on a WinNT
station.
At this time, I have a slight problem when the ORB is receiving a GIOP
request: It says that there is garbage at the end of message. This occurs
when I am connecting with a Java client with JacORB. I tried to make a fake
C++ client with omni with does not have this kind of problem (knowing the
Java client is ran on a WinMe, while the fake C++ client is ran on a Linux).
Anyway, I did the same operation with two servers, from the same client (to
make sure the GIOP request will be exactly the same). The one on the WinNT
server fails, while the one on the AIX server succeeds. You will find
hereafter some dumps of the messages (outgoing from JacORB and incoming on
the WinNT server - using ORBtraceLevel 42).
--- FAILURE ---
- JacORB side -
Hexdump [sendMessages()] len=119,119
47 49 4F 50 01 00 00 00 00 00 00 6B 00 00 00 00 GIOP .... ...k ....
00 00 00 00 01 00 00 00 00 00 00 0E FE CD 49 A6 .... .... .... ..I.
3E 00 00 00 4D 00 00 00 00 00 00 00 00 00 00 11 >... M... .... ....
6F 70 65 6E 41 67 65 6E 74 53 65 73 73 69 6F 6E open Agen tSes sion
00 00 00 00 00 00 00 00 00 00 00 09 30 30 30 30 .... .... .... 0000
30 34 45 36 00 00 00 00 00 00 00 03 74 7A 00 00 04E6 .... .... tz..
00 00 00 09 94 A3 C0 CF EE 11 18 1A 00 00 00 00 .... .... .... ....
00 00 00 03 66 72 00 .... fr.
[ Closed client-side TCP/IP transport to 192.0.0.42:1543 ]
[ ERROR: Abnormal connection termination. Lost 1 outstanding replie(s)! ]
- omniORB side -
omniORB: scavenger : scanning connections
omniORB: tcpSocketMTfactory Rendezvouser: unblock from accept()
omniORB: tcpSocketMTfactory Rendezvouser: accept new strand.
omniORB: tcpSocketMTfactory Rendezvouser: block on accept()
omniORB: tcpSocketMTfactory Worker: start.
ll_recv: 119 bytes
4749 4f50 0100 0000 0000 006b 0000 0000 GIOP.......k....
0000 0000 0100 0000 0000 000e fecd 49a6 ..............I.
3e00 0000 4d00 0000 0000 0000 0000 0011 >...M...........
6f70 656e 4167 656e 7453 6573 7369 6f6e openAgentSession
0000 0000 0000 0000 0000 0009 3030 3030 ............0000
3034 4536 0000 0000 0000 0003 747a 0000 04E6........tz..
0000 0009 94a3 c0cf ee11 181a 0000 0000 ................
0000 0003 6672 00 ....fr.
omniORB: GIOP_S::RequestReceived: garbage left at the end of message.
omniORB: throw omniConnectionBroken (minor 0) from giopServer.cc:246
omniORB: tcpSocketMTfactory Worker: #### Connection closed.
omniORB: tcpSocketMTfactory Worker: exit.
omniORB: tcpSocketStrand::~Strand() close socket no. 208
omniORB: scavenger : scanning connections
--- SUCCESS ---
- JacORB side -
Hexdump [sendMessages()] len=119,119
47 49 4F 50 01 00 00 00 00 00 00 6B 00 00 00 00 GIOP .... ...k ....
00 00 00 00 01 00 00 00 00 00 00 0E FE 3E 82 FA .... .... .... .>..
9B 60 47 00 00 00 00 00 00 00 00 00 00 00 00 11 .`G. .... .... ....
6F 70 65 6E 41 67 65 6E 74 53 65 73 73 69 6F 6E open Agen tSes sion
00 00 00 00 00 00 00 00 00 00 00 09 30 30 30 30 .... .... .... 0000
30 34 45 37 00 00 00 00 00 00 00 03 74 7A 00 00 04E7 .... .... tz..
00 00 00 09 94 A3 C0 CF EE 11 18 1A 00 00 00 00 .... .... .... ....
00 00 00 03 66 72 00 .... fr.
[ ConnectionManager: found conn to target 192.0.0.3:41602 ]
Does anyone have some experience of such problem ?
Any clue ?
Help will be appreciated.
Cheers,
Thomas
------------------------------------------------
Thomas Zumbiehl
Chef de Projet Développement
BV Associates
http://www.bvassociates.fr
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.473 / Virus Database: 271 - Release Date: 17/04/2003