Connector Exception 7: Thing Not Found on the ThingWorx Platform
This exception appears in the Connector log if a Thing is configured in the ThingWorx Platform for an asset running an Axeda agent. For more information, refer to
Observation 2: The lastConnection property of the Thing does not update and
Observation 3: Asset was communicating earlier, but now it does not communicate.
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Create a Thing on the ThingWorx Platform, using the AxedaStandaloneModel Thing Template, leaving the modelNumber and serialNumber properties blank.
4. Start an Axeda Connector agent that sends a registration message and data item messages to the Connector.
|
This scenario can also occur with a Thing created using the AxedaEmessageGatewayModel or AxedaManagedModel Thing Template and an asset running Axeda Gateway or managed by Gateway.
|
In this scenario, eMessage Connector cannot determine the ThingName of the agent using the modelNumber/serialNumber service call on the ThingWorx Platform. When the agent sends its registration message, the following warning messages appear in the Connector log:
... [vert.x-worker-thread-1]
WARN c.t.p.e.c.TokenAuthenticationConverter -
Token authentication failure detected
for Thing=null modelNumber=WeatherModel serialNumber=Weather2
failureMessage=Thing Name was not supplied
... [vert.x-worker-thread-1]
WARN c.t.p.e.c.TokenAuthenticationConverter -
Token authentication failure detected for Thing=null
modelNumber=WeatherModel serialNumber=Weather2
failureMessage=Thing Name was not supplied
...[vert.x-worker-thread-1]
WARN c.t.p.e.c.TokenAuthenticationConverter -
Token authentication failure detected for Thing=null
modelNumber=WeatherModel serialNumber=Weather2
failureMessage=Thing Mame was not supplied
|
If the agent sends data item messages and NOT a registration message, no warning messages are generated.
|