Why do we get an error "Arguments Conflict", after we destroy a transport and recreate another network transport on the same service with different network parameter
Article ID: KB0079013
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Why do we get an error "Arguments Conflict", sometimes after we destroy a transport and subsequently recreate another network transport on the same service with different network parameter (i.e different multicast group)? When is it safe to create a new transport on the same service/daemon with different network parameters?
Issue/Introduction
Why do we get an error "Arguments Conflict", after we destroy a transport and recreate another network transport on the same service with different network parameter
Environment
Product: TIBCO Rendezvous
Version:
OS:
--------------------
Resolution
You will need to wait for 60 seconds after stopping the old transport and before starting a new transport on same service/daemon port but different network parameter. Otherwise you will get "argument conflict" error. This is because RVD will remember the network parameters bound to the service port even after the application using it is closed. However, if you restart RVD, then you will not need to wait for 60 seconds. So in your application, you can try to put some waiting time before creating a new transport.
Feedback
Yes
No
Powered by
