Digital Media Suite API Forums

« Back to Digital Signs API Forum

Limit on number of items in playlist created via REST API?

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Hi,
 
We're creating playlists on a 5.2.2 DMM via the playlist_add service and we're running into issues if we have more than 18 elements in our playlists.
We are able to reproduce the issue both via our software submitting the XML and via the DMS API Tester (AIR application). The DMS API Tester only allows us to select 5.2.1 or 5.2 (we're running against 5.2.2) but all other methods work.
 
The following XML file consists of 20 identical items (assetID of 550) with 10 second durations: http://pastebin.com/QW8gYTYP
Submitting the XML via the DMS API Tester results in a 500 error with no additional information provided.
 
If two Items are removed (18 total items down from 20) then the playlist addition submits successfully with a 200 return code.
The playlist can then be increased in size via the DMM web interface to have 20+ items, so the error is not a function of the playlist created, but rather the API.
 
If the same XML is submitted by our application then we get the following Apache Tomcat error back: http://pastebin.com/rMGv3WBP
 
Is this a known issue? If so, is there a plan to address in the upcoming release?
 
Thanks very much.

Just as an aside... If the same XML (or even larger) is submitted via command line curl then it works as expected. No idea why libcurl and the DMS API Tester both fail in Tomcat.

# curl -v
curl 7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

# curl -d @test.xml -0 https://USERNAMEemoticonASSWORD@DMMIPADDRESS:8443/xTAS-core/api/rest/playlist --insecure -H "Content-Type: application/xml;charset=UTF-8" --verbose

I was wondering if this limitation is still a known issue in version 5.3+. I have tried to this API call with a Rest client and I seem to experience the same issue. Any workaround in order to integrate this API with a Java custom development
Thanks
Marc