Troubleshooting
3DX Error: Cannot authenticate the context
If a job fails with the error message HttpError: Cannot authenticate the context.
,
most likely the problem is related to the Security Context
being used.
Some things to check:
-
What collaborative space does the object in question belong to?
-
Which agent are you using for the operation?
-
Is the user behind the agent member of the Collaborative Space?
-
What role are you using for the operation?
If the job was triggered by an event, then you can check the event mapping entity
within TIF Administration UI and check what the Security Context
value is set to.
3DX Error: URI Not Found
This error is sometimes seen when bad/invalid data is sent to the 3DEXPERIENCE™ REST endpoints. For example, trying to create an Engineering Item and setting the type value to a non-existing type gives this error.
SocketTimeoutException: timeout
This error may occur in some cases when a request to some system takes long time to respond.
There are some methods available via the HttpAPI to control various timeouts such as:
- Connect Timeout
-
The connect timeout is applied when connecting a TCP socket to the target host. Default is 20 seconds.
- Read Timeout
-
The read timeout is applied to both the TCP socket and for individual read IO operations including on Source of the Response. Default is 30 seconds.
- Write Timeout
-
The write timeout is applied for individual write IO operations. Default is 30 seconds.
These timeouts are configured like shown below. Note that the values are all in milliseconds.
context.httpAPI()
.newRequestBuilder()
.connectTimeout(40000)
.readTimeout(60000)
.writeTimeout(40000)
.url('https://service')
.method('POST');
See also this document.