Release Notes > Release Notes for ThingWorx Axeda Compatibility Package 2.4.0 > Fixed Issues in eMessage Connector 2.4.0
Fixed Issues in eMessage Connector 2.4.0
Security
Potential security issues, including items identified by vulnerability scanning software and PTC Quality Assurance testing, have been fixed. To take advantage of these important improvements, upgrade as soon as possible. For more information, see this PTC technical support article for important recommendations regarding using and updating regarding the use and update of third-party software for ThingWorx.
AlarmProperty Values Stored in Scientific Notation
Fixed an issue where the DataItem value related to an Agent Alarm was being saved in scientific notation inside the AlarmProperty of the Thing in cases where the data item value contained a significant number of decimal digits.
Gateway Re-registration due to unavailable Managed Thing in Platform
A new configuration option registration-failure-status-enabled has been added to emessage.conf. When set to true, the eMessage Connector will send the failure SOAP status, <status>1<status> message if registration fails. This may occur in cases where a Thing is not found in ThingWorx with the correct model number and serial number to process the registration.
* 
When a registration failure is received by the Agent, it will continue retrying the registration. Generally, this is desirable behavior, as it prevents the Agent from sending telemetry data to the platform after receiving the incorrect successful registration response. Any telemetry data sent after receiving the incorrect successful registration response will be ignored by the eMessage Connector. However, in some cases, it may be desirable to disable sending the registration failure message if this causes issues with Agents rapidly attempting re-registration.
By default, the registration-failure-status-enabled is set to true.
To configure this in emessage.conf, set the following :
emessage {
registration-failure-status-enabled = "false"
}
Improved handling of invalid Agent Tokens
Updated the default behavior of the TokenPropertyAuthenticator, which is part of the Remote Access Extension (RAE) and is used to perform token authentication for Axeda eMessage Agent assets and Global Access Server (GAS) Things. When an invalid token is received, the authenticator now disables communication with remote Things by setting the tokenInvalid Thing property to true. Any new tokens are rejected until the invalid token is reset manually using the ClearToken service on the remote Thing. For more information on how Agent tokens are validated along with when and how you may need to reset the tokenInvalid property, refer TokenPropertyAuthenticator Behavior (eMessage Connector).
Was this helpful?