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

[PeterWiles]

I am sure I had a similar problem though I wasn't using a MID server. I can't 100% remember what I did to fix it but I will check my updates. Have you checked the endpoint fields actually on the REST message and adjusted them just in case?

Pete

[hpesata]

Hi Pete!

Thanx for Your reply!

Yes , I checked the fields, I added gs.log() messages and I saw, that the complete endpoint-url is added to the ecc-queue, but after it gets processed, only the 120 character limited endpoint-url is visible in the ecc-queue record.

It seems that the RESTProbe is doing the truncation ...

regards,

Hans

[hpesata]

Hi!

The solution for this is related to the fact, that the "ecc_queue" table is a rotated table and the max length for the source column has to be updated in all shared tables:

ecc_queue, ecc_queue0000, ...

regards,

Hans

[durgamittal]

Hi Hans,

I am facing a similar issue , did you get a workaround for this.

Thank you for your help !!

Regards,

Durga