Apama 10.15.0 | Other Resolved Issues | Release 10.3.1.5 | Cumulocity IoT Transport
 
Cumulocity IoT Transport
*PAM-30514
Attempt to update objects in Cumulocity fails if creationTime and lastUpdated are present.
The Cumulocity IoT transport fails to update a managed object/event/operation that contains creationTime or lastUpdated in the params dictionary. This is because Cumulocity IoT does not accept these fields while making a REST request.
This is fixed now.
*PAM-30400
Missing timestamps of ManagedObject within com.apama.cumulocity.Timestamps fields such as creationTime and lastUpdated were missing from the com.apama.cumulocity.ManagedObject object when using the query interface (requestAllDevice=true or FindManagedObject) to retrieve managed objects from Cumulocity IoT. creationTime and lastUpdated are now added to the params dictionary of the ManagedObject event.
*PAM-30265
SocketTimeout if sending a response after 10 minutes of nothing.The Cumulocity IoT transport fails to send a message to Cumulocity IoT in scenarios where the transport is idle (that is, no messages are being sent from the transport to Cumulocity IoT) for a long duration (more than 10 minutes).
This is fixed now.