IMO if the server is not behaving according to the given configurations (specially with configurations related to security), it should fail with meaningful logs. This could be handled at the OSGi component level.
Saminda On Mon, Jun 27, 2011 at 4:15 PM, Amila Jayasekara <ami...@wso2.com> wrote: > Hi All, > > We have following behaviour within carbon products. > > Say we need to start 2 carbon servers in the same machine. Both > servers use embedded LDAP server. User forgets to change LDAP server > port in user-mgt.xml configuration for second server. > Still user will be able to start 2nd server with few error messages in > the console. Error messages are due to LDAP address already used by > first carbon server. The second server still, starts because user > manager is able to connect to first carbon server's embedded LDAP > server. > > After a chat with Saminda and Milinda, we realised that this could > lead to erroneous situations as user is under the impression that > second carbon server is connected to embedded-ldap server running > within second server. > > One way to resolve this issue is to stop starting carbon server if > embedded-ldap server cannot start successfully. > Are there any other better solutions to get rid of this behaviour ? > > Feedback appreciated. > > Thanks > AmilaJ > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
