The Mux e*Way header is becoming corrupted in Java collaboration (Doc ID 1027900.1)

Last updated on SEPTEMBER 13, 2004

Applies to:

Sun SeeBeyond e*Gate - Version: 4.5.3 and later
Microsoft Windows (32-bit)

Symptoms

The 24 byte Mux e*Way header is becoming corrupted by a collaboration running in the JCS. The collaboration copies the header from an inbound ETD to a outbound ETD.

If MSGV is switched on at TRACE level, the 'Got message' and 'Putting message' trace shows that characters in the Mux header with ascii values greater than 0x7f (ie > 127 decimal) are being set to the question mark character "?" (ie 0x3F).

17:13:04.049 MSGV T 1960 (queuelayer.cxx:416): Got message [etMux]. Body follows: Data Follows (bytes 90):
00 00 00 01 00 00 00 01 00 1E 8D A9 44 D0 E3 80 | ............D...
00 00 00 00 00 00 00 42 54 68 69 73 20 69 73 20 | .......BThis is
74 68 65 20 4A 43 53 20 63 6F 6C 6C 61 62 20 73 | the JCS collab s
65 72 76 69 63 65 20 77 69 74 68 20 61 20 73 69 | ervice with a si
6D 70 6C 65 20 67 65 74 2F 73 65 74 20 6F 66 20 | mple get/set of
74 68 65 20 68 65 61 64 65 72 | the header


17:13:05.080 MSGV T 1960 (queuelayer.cxx:120): Putting message [etMux] with [1] parents. Body follows: Data Follows (bytes 90):
00 00 00 01 00 00 00 01 00 1E 3F 3F 44 3F 3F 3F | ..........??D???
00 00 00 00 00 00 00 42 54 68 69 73 20 69 73 20 | .......BThis is
74 68 65 20 4A 43 53 20 63 6F 6C 6C 61 62 20 73 | the JCS collab s
65 72 76 69 63 65 20 77 69 74 68 20 61 20 73 69 | ervice with a si
6D 70 6C 65 20 67 65 74 2F 73 65 74 20 6F 66 20 | mple get/set of
74 68 65 20 68 65 61 64 65 72 | the header

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms