Keith Chalk
2007-08-30 17:58:33 UTC
Hi,
we've recently upgraded from OmniORB 3.0.4 to 4.1 (Windows builds), as
we needed to specify EndPoints to get round firewall issues. Since
upgrading, we're seeing a marsalling error on connecting to the naming
service (MARSHAL_PassEndOfMessage) shown in a trace below.
This works fine on a similar set up with firewalls; the main difference
is that WebSphere 5.1.1.11 is running on a Unix box on the site that is
failing, but running on a windows box where it is working.
Has anyone seen anything like this before or have any ideas? It looks
like the message recieved from the WebSphere Naming service is of an
unexpected length; I can only think there's some kind of
interoperability problem. Any thoughts appreciated.
Thanks,
Keith.
(I've been asked to XX out the Ip address...)
omniORB: Initial reference `NameService' resolved from configuration
file.
omniORB: Client attempt to connect to giop:tcp:XX.XX.XX.XX:9811
omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 2
omniORB: Scavenger task execute.
omniORB: Client opened connection to giop:tcp:XX.XX.XX.XX:9811
omniORB: sendChunk: to giop:tcp:XX.XX.XX.XX:9811 100 bytes
omniORB:
4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
0200 0000 0175 6363 0b00 0000 4e61 6d65 .....ucc....Name
5365 7276 6963 6500 0600 0000 5f69 735f Service....._is_
6100 0000 0000 0000 2800 0000 4944 4c3a a.......(...IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
312e 3000 1.0.
omniORB: inputMessage: from giop:tcp:XX.XX.XX.XX:9811 724 bytes
omniORB:
4749 4f50 0100 0001 0000 02c8 0000 0002 GIOP............
4942 4d12 0000 0008 0000 0001 1420 0001 IBM.......... ..
0000 0006 0000 00f8 0000 0000 0000 0028 ...............(
4944 4c3a 6f6d 672e 6f72 672f 5365 6e64 IDL:omg.org/Send
696e 6743 6f6e 7465 7874 2f43 6f64 6542 ingContext/CodeB
6173 653a 312e 3000 0000 0001 0000 0000 ase:1.0.........
0000 00bc 0001 0200 0000 000f 6672 6370 ............frcp
7065 3335 6b61 5f61 7070 0000 265c 0000 pe35ka_app..&\..
0000 002c 4a4d 4249 0000 0010 69cc 8111 ...,JMBI....i...
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 0024 0000 0008 0000 0005 0000 0002 ...$............
0000 0007 0000 0001 0000 0014 0000 0000 ................
0501 0001 0000 0000 0001 0100 0000 0000 ................
4942 4d0a 0000 0008 0000 0001 1420 0001 IBM.......... ..
0000 0026 0000 0002 0002 0000 4942 4d04 ...&........IBM.
0000 0005 0005 0101 0200 0000 0000 001f ................
0000 0004 0000 0003 0000 0020 0000 0004 ........... ....
0000 0001 0000 0025 0000 0004 0000 0003 .......%........
0000 0002 0000 0003 0000 0031 4944 4c3a ...........1IDL:
636f 6d2e 6962 6d2f 5773 6e4f 7074 696d com.ibm/WsnOptim
697a 6564 4e61 6d69 6e67 2f4e 616d 696e izedNaming/Namin
6743 6f6e 7465 7874 3a31 2e30 0000 0000 gContext:1.0....
0000 0001 0000 0000 0000 0168 0001 0200 ...........h....
0000 000f 6672 6370 7065 3335 6b61 5f61 ....frcppe35ka_a
7070 0000 265c 0000 0000 006b 4a4d 4249 pp..&\.....kJMBI
0000 0012 69cc 8111 3562 3835 6539 6363 ....i...5b85e9cc
3831 3131 3463 3131 0000 0024 0000 0047 81114c11...$...G
4945 4a50 0101 1743 444c 5374 7261 7461 IEJP...CDLStrata
4d6f 6e69 746f 7243 6c75 7374 6572 1a57 MonitorCluster.W
736e 4469 7374 436f 734f 626a 6563 7441 snDistCosObjectA
6461 7074 6572 574c 4d00 0000 0a70 7065 dapterWLM....ppe
6365 6c6c 3031 3500 0000 0009 0000 0001 cell015.........
0000 0014 0000 0000 0501 0001 0000 0000 ................
0001 0100 0000 0000 4942 4d0a 0000 0008 ........IBM.....
0000 0001 1420 0001 0000 0026 0000 0002 ..... .....&....
0002 0000 4942 4d0b 0000 0043 0000 0001 ....IBM....C....
000a 7070 6563 656c 6c30 3135 0017 4344 ..ppecell015..CD
4c53 7472 6174 614d 6f6e 6974 6f72 436c LStrataMonitorCl
7573 7465 7200 0000 0123 f123 8d00 0e66 uster....#.#...f
7263 7070 6533 356b 615f 6170 7026 ac00 rcppe35ka_app&..
0000 0003 0000 0016 0000 000f 6672 6370 ............frcp
7065 3335 6b61 5f61 7070 0000 26ac 0000 pe35ka_app..&...
4942 4d04 0000 0005 0005 0101 0200 0000 IBM.............
0000 001f 0000 0004 0000 0003 0000 0020 ...............
0000 0004 0000 0001 0000 0025 0000 0004 ...........%....
0000 0003 ....
omniORB: throw MARSHAL from corbaString.cc:200
(NO,MARSHAL_PassEndOfMessage)
omniORB: Unexpected error encountered in talking to the server
giop:tcp:XX.XX.XX.XX:9811 . The connection is closed immediately.
********************************************************************************
This email is intended only for the person(s) named above and may contain private and confidential information. If it has come to you in error, please destroy and permanently delete any copy in your possession and contact us on +44 (0) 161 480 4420. The information in this email is copyright ? CDL Group Holdings Limited. We cannot accept any liability for any loss or damage sustained as a result of software viruses. It is your responsibility to carry out such virus checking as is necessary before opening any attachment.
Cheshire Datasystems Limited uses software which automatically screens incoming emails for inappropriate content and attachments. If the software identifies such content or attachment, the email will be forwarded to our Technology Department for checking. You should be aware that any email which you send to Cheshire Datasystems Limited is subject to this procedure.
Cheshire Datasystems Limited, Strata House, Kings Reach Road, Stockport SK4 2HD
Registered in England and Wales with Company Number 3991057
VAT registration : 727 1188 33
******************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070830/3f835d9c/attachment.htm
we've recently upgraded from OmniORB 3.0.4 to 4.1 (Windows builds), as
we needed to specify EndPoints to get round firewall issues. Since
upgrading, we're seeing a marsalling error on connecting to the naming
service (MARSHAL_PassEndOfMessage) shown in a trace below.
This works fine on a similar set up with firewalls; the main difference
is that WebSphere 5.1.1.11 is running on a Unix box on the site that is
failing, but running on a windows box where it is working.
Has anyone seen anything like this before or have any ideas? It looks
like the message recieved from the WebSphere Naming service is of an
unexpected length; I can only think there's some kind of
interoperability problem. Any thoughts appreciated.
Thanks,
Keith.
(I've been asked to XX out the Ip address...)
omniORB: Initial reference `NameService' resolved from configuration
file.
omniORB: Client attempt to connect to giop:tcp:XX.XX.XX.XX:9811
omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 2
omniORB: Scavenger task execute.
omniORB: Client opened connection to giop:tcp:XX.XX.XX.XX:9811
omniORB: sendChunk: to giop:tcp:XX.XX.XX.XX:9811 100 bytes
omniORB:
4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
0200 0000 0175 6363 0b00 0000 4e61 6d65 .....ucc....Name
5365 7276 6963 6500 0600 0000 5f69 735f Service....._is_
6100 0000 0000 0000 2800 0000 4944 4c3a a.......(...IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
312e 3000 1.0.
omniORB: inputMessage: from giop:tcp:XX.XX.XX.XX:9811 724 bytes
omniORB:
4749 4f50 0100 0001 0000 02c8 0000 0002 GIOP............
4942 4d12 0000 0008 0000 0001 1420 0001 IBM.......... ..
0000 0006 0000 00f8 0000 0000 0000 0028 ...............(
4944 4c3a 6f6d 672e 6f72 672f 5365 6e64 IDL:omg.org/Send
696e 6743 6f6e 7465 7874 2f43 6f64 6542 ingContext/CodeB
6173 653a 312e 3000 0000 0001 0000 0000 ase:1.0.........
0000 00bc 0001 0200 0000 000f 6672 6370 ............frcp
7065 3335 6b61 5f61 7070 0000 265c 0000 pe35ka_app..&\..
0000 002c 4a4d 4249 0000 0010 69cc 8111 ...,JMBI....i...
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 0024 0000 0008 0000 0005 0000 0002 ...$............
0000 0007 0000 0001 0000 0014 0000 0000 ................
0501 0001 0000 0000 0001 0100 0000 0000 ................
4942 4d0a 0000 0008 0000 0001 1420 0001 IBM.......... ..
0000 0026 0000 0002 0002 0000 4942 4d04 ...&........IBM.
0000 0005 0005 0101 0200 0000 0000 001f ................
0000 0004 0000 0003 0000 0020 0000 0004 ........... ....
0000 0001 0000 0025 0000 0004 0000 0003 .......%........
0000 0002 0000 0003 0000 0031 4944 4c3a ...........1IDL:
636f 6d2e 6962 6d2f 5773 6e4f 7074 696d com.ibm/WsnOptim
697a 6564 4e61 6d69 6e67 2f4e 616d 696e izedNaming/Namin
6743 6f6e 7465 7874 3a31 2e30 0000 0000 gContext:1.0....
0000 0001 0000 0000 0000 0168 0001 0200 ...........h....
0000 000f 6672 6370 7065 3335 6b61 5f61 ....frcppe35ka_a
7070 0000 265c 0000 0000 006b 4a4d 4249 pp..&\.....kJMBI
0000 0012 69cc 8111 3562 3835 6539 6363 ....i...5b85e9cc
3831 3131 3463 3131 0000 0024 0000 0047 81114c11...$...G
4945 4a50 0101 1743 444c 5374 7261 7461 IEJP...CDLStrata
4d6f 6e69 746f 7243 6c75 7374 6572 1a57 MonitorCluster.W
736e 4469 7374 436f 734f 626a 6563 7441 snDistCosObjectA
6461 7074 6572 574c 4d00 0000 0a70 7065 dapterWLM....ppe
6365 6c6c 3031 3500 0000 0009 0000 0001 cell015.........
0000 0014 0000 0000 0501 0001 0000 0000 ................
0001 0100 0000 0000 4942 4d0a 0000 0008 ........IBM.....
0000 0001 1420 0001 0000 0026 0000 0002 ..... .....&....
0002 0000 4942 4d0b 0000 0043 0000 0001 ....IBM....C....
000a 7070 6563 656c 6c30 3135 0017 4344 ..ppecell015..CD
4c53 7472 6174 614d 6f6e 6974 6f72 436c LStrataMonitorCl
7573 7465 7200 0000 0123 f123 8d00 0e66 uster....#.#...f
7263 7070 6533 356b 615f 6170 7026 ac00 rcppe35ka_app&..
0000 0003 0000 0016 0000 000f 6672 6370 ............frcp
7065 3335 6b61 5f61 7070 0000 26ac 0000 pe35ka_app..&...
4942 4d04 0000 0005 0005 0101 0200 0000 IBM.............
0000 001f 0000 0004 0000 0003 0000 0020 ...............
0000 0004 0000 0001 0000 0025 0000 0004 ...........%....
0000 0003 ....
omniORB: throw MARSHAL from corbaString.cc:200
(NO,MARSHAL_PassEndOfMessage)
omniORB: Unexpected error encountered in talking to the server
giop:tcp:XX.XX.XX.XX:9811 . The connection is closed immediately.
********************************************************************************
This email is intended only for the person(s) named above and may contain private and confidential information. If it has come to you in error, please destroy and permanently delete any copy in your possession and contact us on +44 (0) 161 480 4420. The information in this email is copyright ? CDL Group Holdings Limited. We cannot accept any liability for any loss or damage sustained as a result of software viruses. It is your responsibility to carry out such virus checking as is necessary before opening any attachment.
Cheshire Datasystems Limited uses software which automatically screens incoming emails for inappropriate content and attachments. If the software identifies such content or attachment, the email will be forwarded to our Technology Department for checking. You should be aware that any email which you send to Cheshire Datasystems Limited is subject to this procedure.
Cheshire Datasystems Limited, Strata House, Kings Reach Road, Stockport SK4 2HD
Registered in England and Wales with Company Number 3991057
VAT registration : 727 1188 33
******************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070830/3f835d9c/attachment.htm