We are developping an EntireX Application using Java Wrapper (and also XML Wrapper, but in order to understand the error i make some test with java wrapper) under EntireX 7.1.1 and using Natural 6.1.1 under AIX 5.2 64 Bit (Also the EntireX Broker is running on the AIX Box).
The parameter of the Natural Wrapped subprogram is contained in the attached “nat_para.txt” .
I generated the IDL and , using the WorkBench i generated the java Classes and i run the test. After some time i got " Broker error 0074 0074:WAIT Timeout Occurred".
The natural server (Running on AIX) is started with a MAXBUFF=40000 and from the rpc trace (activated after getting this error) i get the following:
***** USER-ID: BC677E1086DEA000 LIB : SYSTEM
BC *** Reply to client BIGTEST failed at 14:35:00
FUNCTION: R RC: 7 SERVER: ENGSRV02
00200218 API: SEND or RECEIVE-LENGTH exceeds max
SEND-LEN: 32048 REC-LEN: 32048
0 31313430 30303030 30323033 30303030 * 1140000002030000 *
16 30303030 30202020 20202020 20203030 * 00000 00 *
32 57454241 4E532020 42494754 45535420 * WEBANS BIGTEST *
48 41646D69 6E697374 7261746F 72202020 * Administrator *
64 3230204E 43303030 30322020 20303030 * 20 NC00002 000 *
80 30303030 30303030 30303030 30303020 * 000000000000000 *
96 20202020 20202020 20202020 20202020 * *
NEXT 5 LINES SAME AS ABOVE…
Now, as I know , using TCP transport that’s no more the 32K limit in the receive and send buffer also using RPC call. Where’s the problem? Is there any parameter i’ve to set in order to let it works ?
Attached in the file “nat_trace.txt” you can find the rpc trace generated on the aix machine. In the file “etbfile” you can find the broker parameters.
All the atached file in a zip archive.
Thanks in advance
All_File.zip (8.78 KB)
The problem was solved increasing the MAX-MSG parameter in the etbfile of the broker.
Starting Natural with MAXBUFF=40 (In the previous mail i make a mistake writing 40000) and broker with MAX-MSG=100000 solved