cancel
Showing results for 
Search instead for 
Did you mean: 

Message stucking in R3 side itself

Former Member
0 Kudos

HI All,

when sending the data through proxy to xi but they all stuked in R3 ,i have checked this in SXMB_MONI of R3 side and it's saying it is alreay schdeule in the queue and some it is given the HTTP 500 timeout error.plz help on this...

Regards

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

solved

Former Member
0 Kudos

Hi check this forum first

but remember in PI the best practices told the message have not to larger than 5 MB.

regards.

Marco.

Former Member
0 Kudos

If your msgs are stuck in queue, it means you're using EOIO qos mode ... So each time queues encounter a pb, msgs are stuck until error is solved or whatever ! Maybe your HTTP/500 (timeout) issue is the origin of your pb ? Have you analyzed why this error is raised (msg too big ? performance or bottleneck situation at PI level ?) ?

Chris

Former Member
0 Kudos

HI Chris,

I have analyzed this error and found that may be i have to increase the timeout parameter for HTTP in SXMB_ADM , but it's not working ,the message size is very big so i have decied that append the records in file in small chunks.i have tested this with 3 lacs records but now messages are getting stuck in queue with 1lacs records.

please suggest.........