No reply got while sending a message

Question

Environment: SCO Unixware 7.1.1, Tuxedo 6.5, Windows 98(client)
While the client sends a message(photo) which size is near to or over 16K Bytes,
to the server, the client gets no reply. Seems the server can not get the request.
Does anybody know the reason.
Thanks in advance,
George

Answer 1

"George" <[email protected]> wrote:
>
Marcin Kasperski <[email protected]> wrote:
"George" <[email protected]> writes:
Environment: SCO Unixware 7.1.1, Tuxedo 6.5, Windows 98(client)
While the client sends a message(photo) which size is near to or
over 16K Bytes, to the server, the client gets no reply. Seems the
server can not get the request. Does anybody know the reason.No space in queues?
Check the ULOG* file. Sometimes it happen that Tuxedo throws the
message away (for me it was more troublesome when the server
succesfully processed the message but Tuxedo was unable to send it
back, leaving the client waiting forever on tpcall).Thanks, Marcin. But in my case, the server seems receive no request(no
information
in the ULOG*), and the client waits forever on tpcall. Do you have any
further
idea in this case.
Thanks,
GeorgeGeorge,
I would try the following troubleshooting steps:
1) On the server, go into "tmadmin" and do a "pclt" to make
sure the client is getting connected.
2) On the Win98 box, do a "set TMTRACE=on" before starting the app.
This will place trace messages in the ULOG. You can see
when a "tpcall" is executed and what arguments are passed.
3) You can find Ethereal, a freeware packet sniffer at
www.ethereal.com. You can see if the request is even leaving
the Win98 box and making it onto the network and to the server.
4) If the request is making it to the server, shutdown all your
servers, do a "export TMTRACE=on", and restart the servers.
This will place debug messages in the ULOG on the server.
You should be able to see any ATMI calls that are made.
5) Attach to the server with a debugger and set a breakpoint
in "msgrcv". This is the Unix system function call
that gets a message from a queue. If it never gets called, then
your message is not reaching the server's queue.
If it does get called, set a breakpoint in your service routine
and continue stepping through code.
6) You can also go into "tmadmin" and do a "pq" to see if there
is a request in the server's queue.
Hope that helps,
David