RESTMessage endpoint max string length ?

[hpesata]

Hi!

I created a RESTMessage which enables our Calgary-SN application to talk to he JIRA Rest API, I am using a MID-server.

I am not able to successfully use the "get" function, I always get an error 400.

After digging around, I found out, that the RESTMessage-endpoint URL gets cut off after 120 characters which causes the 400 error.

I found the information about this fact within RESTprobe entries in the ECC Queue.

The source field of the "ecc_queue" table was indeed set to 120, I raised it up to 1024 and restarted the MID-server,

but still the endpoint url gets cut of after 120 characters...

Where can I find the real 120 character limit and raise it up ?

Thanx in advance!

regards,

Hans

[PradeepPanwar]

Yes,

the Rest Post call URI is truncated in the ECC queue source field which has field length of 120.

Right, You don't only have to increase the max_length property of the ecc_queue table but also of ALL rotated tables ecc_queue0000, 01,02...

Then it's work as expected. And if you are using MID servers, some times you have to restart your instance mid servers also to make it work.

Thanks

[Shrinil]

I tested the Table API endpoint, by providing the table names as query param that made the URL longer than 500 characters. But it worked fine and I got the expected response. I tested the same with 2 other instances and it worked fine.

Can someone confirm if it will work for all the ServiceNow instances?

Has the default limit increased for all the instances?

[we2]

Hi Shrinil,

My end point is more than 350 around ,is it ok like we can increase the length of end point in both table sys_rest_message and sys_rest_message_fn. Kindly let me know how you fixed your issue as well.

Can someone confirm if it will work for all the ServiceNow instances?

Has the default limit increased for all the instances?