RESTMessage endpoint max string length ?

hpesata
Kilo Expert

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

12 REPLIES 12

Hi Durga!



As I have described, You dont only have to increase the max_length property of the ecc_queue table but also of ALL rotated tables ecc_queue0000, ...



This worked for me.



regards,


Hans


poyntzj
Kilo Sage

raise a request in HI and they will make it larger for you


I had this recently


Hi Julian,



Thanks for the update.


It will really help me fix my issue.



Thanks,


Durga


Jacob_Andersen
ServiceNow Employee
ServiceNow Employee

I had this same problem several months ago and banged my head against the wall until I realized it was a rotated table.   I wish that I would have seen this forum post in time to point you in the right direction .   I knew exactly what it was when I read your post.



I was told that this bug was fixed in Dubin.


nari5
Kilo Explorer

I just had this issue today (again) .. what I did and it worked for me (again) was go to table rotation and synchronize shard .. wait for a while and retry.



I guess it's a good first try before raising a ticket on HI