Resolve port errors received when attempting to start EngageOne Digital Delivery, formerly eMessaging

Product Feature: Administration


When starting up eMessaging, errors are received that port 1199 is already in use.

Netstat -ab has shown that when eMessaging is not started, this port is not in use.


There is a port configured within e-Messaging for a RMI service.  This is by default 1199.

If multiple instances of JBoss are configured, it is likely that 'ports-01' will be tried. 

Unfortunately, this clashes with this e-Messaging port as mentioned above.


UPDATED: November 9, 2017
There are two possible solutions:
1. Don't use ports-01 in JBoss and skip to ports-02.
2. In core.war/WEB-INF/classes/, you can modify the port that e-Messaging uses (for instance, 11990).