This content has been marked as final. Show 2 replies
The answer to your question about CPU usage is a little difficult. It is largely going to depend upon the complexity/size of the SOAP request and to a lesser extent the complexity/size of the SOAP response. XML processing is EXPENSIVE! This is why we see so few Tuxedo applications using XML because the parsing time for the XML is often greater than the processing time of the service.
The solution for LIBTUX_CAT:582 is as the documentation says, increase the MAXACCESSERS value in the UBBCONFIG.
The solution for LIBTUX_CAT:1285 is to increase the size of the IPC queues on the underlying OS, if possible. Basically what happened was a server called by the GWWS tried to place a reply message on the GWWS reply queue and found that it would have made the queue more than 75% full. So to ensure that message can still be returned to the GWWS, Tuxedo spools the message to disk and then places a much smaller message in the reply queue indicating where the message can be read on disk. Obviously this can cause a huge performance hit and should be avoided if at all possible.
For the GWWS_CAT:109 error, I would open a support case as that sounds like either a problem with the GWWS SSL code or an undocumented limitation, although these are just guesses. Oracle Customer Support should be able to give you better answers.
Oracle Tuxedo Chief Architect
PS If you are dealing with 300kb messages, the SOAP/XML processing is going to be significant.