If see the following messages (related to the DACS mount configuration), where is the 127.0.0.1 from? e.g., the DACS host or the (docker with real ip) host running the application?
State: Closed/Suspect/Maximum logins reached - text: "Access Denied-already using position 127.0.0.1"
Hi @Frederic
When the code sends a LOGIN request message, they should specify the IP Address/hostname of the PC/server where the application is running. If they do not provide the actual details, it defaults to 127.0.0.1 (localhost). So, they need to change their code to send the correct details - then the error will show that address.
e.g.
OmmConsumer consumer( OmmConsumerConfig().host( "yourads:14002" )
.username( "user" ).position("129.121.1.2/net") );
where 129.121.1.2 is the local IP address or hostname.
NOTE: just to clarify EMA sends a LOGIN behind the scenes and the above call changes the position attribute in that Login. If the developer is explicitly sending an MMT_LOGIN, they should change the Position in that (e.g. consumer example 420_MP_AdminDomainCfg)
Hi @Frederic
This means that an application is already logged in using the same DACS ID on a different PC/server.
There is a limit set in the DACS system regards how many mounts can be made with a DACS ID - by default, this is set to 1.
This can be increased using the DACS admin system - however, there is often additional data usage cost associated with allowing multiple mounts with a single ID.
The developer should speak to their local DACS admin team.
