Currently, when calling DataStreamService.openDataStreams, a IllegalStateException is thrown when data streams for the same studyDeploymentId have already been configured.
Currently, there is no state held in StudyDeployment to keep track of previous deployments, which could conditionally call openDataStreams. This would be one solution to preventing this exception.
Alternatively, possibly openDataStreams should simply succeed if the requested DataStreamsConfiguration matches those of the already opened data streams for the given studyDeploymentID?
Currently, when calling
DataStreamService.openDataStreams
, aIllegalStateException
is thrown when data streams for the samestudyDeploymentId
have already been configured.This exception currently is caught and ignored in
DeploymentService
when deploying a device, since when a device is re-deployed, the data streams have already been opened as part of the previous deployment.Currently, there is no state held in
StudyDeployment
to keep track of previous deployments, which could conditionally callopenDataStreams
. This would be one solution to preventing this exception.Alternatively, possibly
openDataStreams
should simply succeed if the requestedDataStreamsConfiguration
matches those of the already opened data streams for the givenstudyDeploymentID
?