Blocking service

Question

Hello,
I have a service, that reads and returns the contents of a database table
specified as input parameter. In the case of a specific table, the service,
when returning, produces the following message:
111303.boss!srv.21028: LIBTUX_CAT:1285: WARN: tpreturn message send blocked,
will try file transfer
In this case the return message is not very big:
*********************** Start of FML buffer dump
checksum = 256118252
size = 2097152
bytes used (index excluded) = 74908
bytes used by index = 4576
bytes unused = 2017668
number of field occurrences = 4555
There are several cases where the service returns more data without
warnings.
Does anybody have a good suggestion where to start looking for the problem?
We are using Tuxedo 6.5 on Solaris 2.6 with the following kernel parameters:
msgsys:msginfo_msgmap=4003
msgsys:msginfo_msgmax=262144
msgsys:msginfo_msgmnb=524288
msgsys:msginfo_msgmni=4000
msgsys:msginfo_msgseg=32767
msgsys:msginfo_msgtql=4000
Thank you,
Lara

Answer 1

Lara,
The message indicates that the server is unable to put the message on
the queue. If the server and the client are on the same machine, then it
is the case that there is some system resource preventing the message
from going onto the client's reply queue. There may be unread replies
filling the queue, or the system itself may be out of message headers or
segments.
If the processes are on different machines, then it could be the Bridge,
WSH or Domain gateway queue that is temporarily out of space. If the
machines are different types, depending on the datatypes in the FML
buffer, the buffer could get four times larger when it is encoded. If
you run truss on your server, you will see the actual sizes in the
msgsnd calls.
Also note that you should really have MSGMAX set to at least 3/4 of
MSGMNB, because TUXEDO assumes that a queue can handle a message as
large as 3/4 of MSGMNB. For messages between your MSGMAX of 262144, and
393216 bytes (3/4 of 524288), TUXEDO will have to an extra msgsnd before
it discovers that the message is too big to be sent.
     Scott Orshan
     BEA Systems
Lara Faiazza wrote:
>
Hello,
I have a service, that reads and returns the contents of a database table
specified as input parameter. In the case of a specific table, the service,
when returning, produces the following message:
111303.boss!srv.21028: LIBTUX_CAT:1285: WARN: tpreturn message send blocked,
will try file transfer
In this case the return message is not very big:
*********************** Start of FML buffer dump
checksum = 256118252
size = 2097152
bytes used (index excluded) = 74908
bytes used by index = 4576
bytes unused = 2017668
number of field occurrences = 4555
There are several cases where the service returns more data without
warnings.
Does anybody have a good suggestion where to start looking for the problem?
We are using Tuxedo 6.5 on Solaris 2.6 with the following kernel parameters:
msgsys:msginfo_msgmap=4003
msgsys:msginfo_msgmax=262144
msgsys:msginfo_msgmnb=524288
msgsys:msginfo_msgmni=4000
msgsys:msginfo_msgseg=32767
msgsys:msginfo_msgtql=4000
Thank you,
Lara