Article - CS336688
Axeda Agents are slow to connect and then proceed to disconnect in large batches when connecting to the ThingWorx Platform via eMessage Connector
Modified: 22-Sep-2021
Applies To
- ThingWorx Platform 8.5 to 9.5
Description
- Previously connected Axeda Agents will not reconnect to the ThingWorx Platform
- Cannot load persisted properties from the ThingWorx database after a ThingWorx restart when the eMessage Connector is actively connected and sending data
- Axeda Compatibility Extension leads to outages when over 1000 devices are connected to ThingWorx Platform through eMessage Connector
- Axeda Agents connecting through eMessage Connector temporarily connect and then drop
- Initial Axeda Agent connections are slow and most devices do not connect to the ThingWorx Platform
- Axeda Agents connected to ThingWorx Platform fluctuates
- High ThingWorx Platform CPU usage when the eMessage Connector is enabled and devices are transmitting data
- Axeda eMessage Connector service GetThingNameAndIdentifierByModelAndSerial is very inefficient and causes performance issues on ThingWorx Platform
- Assets are going offline and online repeatedly
- Performance issues are seen on ThingWorx Platform when the eMessage Connector is started
- See the following in the ThingWorx Platform ThingworxStorage/logs/ApplicationLog.log file:
- [L: ERROR] [O: c.t.p.p.PostgresPropertyExceptionTranslator] [I: ] [U: SuperUser] [S: ] [P: ] [T: pool-19-thread-8] [1,018] Data store unknown error: [Error occurred while accessing the property provider.]
[L: ERROR] [O: c.t.p.p.PersistentPropertyDataProcessor] [I: ] [U: SuperUser] [S: ] [P: ] [T: pool-19-thread-8] Unable to persist entries because [1,018] Data store unknown error: [Error occurred while accessing the property provider.]
- [L: ERROR] [O: c.t.p.p.PostgresPropertyExceptionTranslator] [I: ] [U: SuperUser] [S: ] [P: ] [T: pool-19-thread-8] [1,018] Data store unknown error: [Error occurred while accessing the property provider.]
- Axeda Agents which were previously connected with ThingWorx Platform through the eMessage Connector log the following in the eMessage connector/emessage.log file:
- ERROR c.t.p.e.EmessageRequestContext - converter=PingConverter contextId=61423: failure occurred: failureMessage=Unable to find Thing Name for the eMessage device with modelNumber=DirectView DRX and serialNumber=58007745.USA
java.lang.Exception: null
- ERROR c.t.p.e.EmessageRequestContext - converter=PingConverter contextId=61423: failure occurred: failureMessage=Unable to find Thing Name for the eMessage device with modelNumber=DirectView DRX and serialNumber=58007745.USA
- eMessage Connector fails to connect to ThingWorx with following error in eMessage connector/emessage.log:
- WARN c.t.f.i.AbstractManyPlatformWebSocketFabric - Lost connection to platform
This is a printer-friendly version of Article 336688 and may be out of date. For the latest version click CS336688