Hi Harsha, On Mon, Feb 20, 2017 at 10:52 AM, Harsha Thirimanna <hars...@wso2.com> wrote:
> What do you mean by properly ? Is that possible to happen these issues > intermittently if it is not defined properly ? > This is happening intermittently since the order in which components are resolved in OSGi varies. AFAIR this issue was there in Kernel 5.1.0, but this was fixed in the startup order resolver to catch this issue (if the component such as number of expected and actual being registered vary [2]). In order to identify this issue, you need to narrow down which component is causing this issue. > > Yes I am using maven 3.0.5 and you are saying still it can be happened > intermittently because of this ? Because of some others using same maven > but never seen this issue. > For C5, the maven should be 3.3.x and JDK should be 1.8.x (Oracle / OpenJDK). This is mentioned in the [1]. We need to added in the Github Readme as well. If your components are compiled using maven 3.0.5 then it is not compatible with C5. > And I have seen another issue that OSGi services not register > intermittently. Is that the same issue as you suggested ? > > *Harsha Thirimanna* > *Associate Tech Lead | WSO2* > > Email: hars...@wso2.com > Mob: +94715186770 <+94%2071%20518%206770> > Blog: http://harshathirimanna.blogspot.com/ > Twitter: http://twitter.com/harshathirimann > Linked-In: linked-in: http://www.linkedin.com/pub/ > harsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Mon, Feb 20, 2017 at 10:33 AM, Niranjan Karunanandham < > niran...@wso2.com> wrote: > >> Hi Harsha, >> >> On Mon, Feb 20, 2017 at 9:23 AM, Harsha Thirimanna <hars...@wso2.com> >> wrote: >> >>> Hi, >>> >>> When the IS server get start, we can see this error log intermittently. >>> Any idea about this ? >>> >>> Exception in thread "Timer-0" java.lang.NullPointerException >>> at org.wso2.carbon.kernel.internal.startupresolver.StartupOrder >>> Resolver$1.run(StartupOrderResolver.java:170) >>> at java.util.TimerThread.mainLoop(Timer.java:555) >>> at java.util.TimerThread.run(Timer.java:505) >>> >> This issue happens when you have not defined your components properly. In >> C5, we have introduced startup order resolver. This is introduced when a >> components need to wait till other components are initialized (refer [1]). >> >> Btw I have noticed that for C5 components some are using Java 1.8 and >> maven 3.0.5. Please note for C5, you need to have maven 3.3.x. >> >> >>> >>> thanks >>> >>> *Harsha Thirimanna* >>> *Associate Tech Lead | WSO2* >>> >>> Email: hars...@wso2.com >>> Mob: +94715186770 <+94%2071%20518%206770> >>> Blog: http://harshathirimanna.blogspot.com/ >>> Twitter: http://twitter.com/harshathirimann >>> Linked-In: linked-in: http://www.linkedin.com/pub/ha >>> rsha-thirimanna/10/ab8/122 >>> <http://wso2.com/signature> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> [1] - https://github.com/wso2/carbon-kernel/blob/v5.2.0-m3/docs/ >> KernelFeatures/ResolvingtheComponentStartupOrder.md >> >> Regards, >> Nira >> >> -- >> >> >> *Niranjan Karunanandham* >> Associate Technical Lead - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com >> >> > [1] - https://docs.wso2.com/display/Carbon500/Installation+Prerequisites [2] - https://github.com/wso2/carbon-kernel/blob/v5.2.0-m3/ docs/KernelFeatures/ResolvingtheComponentStartupOrder.md Regards, Nira -- *Niranjan Karunanandham* Associate Technical Lead - WSO2 Inc. WSO2 Inc.: http://www.wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
