Hi Akila, Yes. This is a known bug. I've created the [1] to track this. Will fix this in future msf4j release. [1] - https://wso2.org/jira/browse/WMS-85
Thanks On Sat, Aug 20, 2016 at 5:06 PM, Akila Ravihansa Perera <[email protected]> wrote: > Hi, > > I tried to create multiple MicroservicesRunner objects on different ports > as follows; > > public class Application { > public static void main(String[] args) { > > new MicroservicesRunner() > .addExceptionMapper(new EntityNotFoundMapper(), new > CustomerNotFoundMapper()) > .deploy(new CustomerService()) > .start(); > > new MicroservicesRunner(8081) > .addExceptionMapper(new EntityNotFoundMapper(), new > InvoiceNotFoundMapper()) > .deploy(new InvoiceService()) > .start(); > } > } > > > Looks like this is not supported. I'm getting "Problem accessing: > /customer/XXX. Reason: Not Found" error. > > It fails because NettyTransportContextHolder is a singleton. Therefore > messing up MSF4J message handlers. Is this by design? If so shouldn't we > print a warning if a developer tries to do this? > > Thanks. > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com About http://about.me/thusithathilina <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
