On Mon, Jun 27, 2011 at 10:39 PM, Afkham Azeez <[email protected]> wrote: > It doesn't seem to be critical for 3.2.1 right? What modules will change?
I also dont think so. Only ldap server component is changing. Thanks AmilaJ > > On Mon, Jun 27, 2011 at 5:59 PM, Amila Jayasekara <[email protected]> wrote: >> >> Created [1]. Should this be part of 3.2.1 release ? >> >> Thanks >> AmilaJ >> >> [1] https://wso2.org/jira/browse/CARBON-10919 >> >> On Mon, Jun 27, 2011 at 4:36 PM, Isuru Suriarachchi <[email protected]> >> wrote: >> > >> > >> > On Mon, Jun 27, 2011 at 4:21 PM, Saminda Wijeratne <[email protected]> >> > wrote: >> >> >> >> IMO if the server is not behaving according to the given configurations >> >> (specially with configurations related to security), it should fail >> >> with meaningful logs. >> > >> > +1 >> > Thanks, >> > ~Isuru >> > >> >> >> >> This could be handled at the OSGi component level. >> >> Saminda >> >> >> >> On Mon, Jun 27, 2011 at 4:15 PM, Amila Jayasekara <[email protected]> >> >> 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 >> >>> [email protected] >> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> >> >> _______________________________________________ >> >> Carbon-dev mailing list >> >> [email protected] >> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> > >> > >> > >> > -- >> > Isuru Suriarachchi >> > Technical Lead & Product Manager, WSO2 Application Server >> > WSO2 Inc. http://wso2.com >> > email : [email protected] >> > blog : http://isurues.wordpress.com/ >> > >> > lean . enterprise . middleware >> > >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] >> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > -- > Afkham Azeez > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > > email: [email protected] cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > Lean . Enterprise . Middleware > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
