Hi Shariq, Agree with what you pointed out, it should have been handled. But when you upgrading the versions we expect the configurations also to be updated where in this case at least NPE was thrown. There can be situations like we use older configurations and end up with totally unusable state where we might never identified the cause as it a configuration error. Its a bit pain to change the configurations but it's the correct way we should follow.
thanks Eranda On Thu, Oct 24, 2013 at 11:20 AM, Shariq Muhammed <[email protected]> wrote: > Hi folks, > > We came across an issue where a weird NPE was thrown after upgrading to > latest RC packs, the server simply wouldn't start cz of this and there > was no helpful error logs that suggest what the issue is. > > After some debugging we manage to identify that the issue was in > registry.xml where "indexingConfiguration", which had been added > recently, was missing. While this is an issue with the setup itself, it > would be helpful if we could alert users of such issue since it is common > to externally manage configs externally with puppet etc. > > Of course this is not the only place where we could improve, just wanted > to point this out :) > > -- > Thanks, > M. S. M. Shariq. > Senior Software Engineer > Phone: +94 777 202 225 > -- *Eranda Sooriyabandara *Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
