The error you see usually doesn't relate to a Java heap limit issue, but the OS actually running out of memory. Can you try closing every other process while building these products and make sure the memory usage is low or add more swap space[1].
Are you using open-jdk? If so, can you switch to oracle jdk if the above doesn't work and try again. Best regards. [1] http://askubuntu.com/questions/178712/how-to-increase-swap-space On Wed, Apr 27, 2016 at 2:32 PM, Mahesh Dananjaya <[email protected] > wrote: > Hi suho, > Thanl you for the information. In the initial build i used mvn "mvn clean > install -Dmaven.test.skip=true", thats why i did not get errors.But this > time i built with mvn clean build and i got some errors in test stage.i > have already set up MAVEN_OPTS as MAVEN_OPTS="-Xms768m -Xms3072m > -XX:MaxPermSize=1200m". But it seems to be some memory constriant.i got > followings. > > > ERROR > [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] - > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option > MaxPermSize=256m; support was removed in 8.0 > ERROR > [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] - > Java HotSpot(TM) 64-Bit Server VM warning: INFO: > os::commit_memory(0x00000000f4000000, 157286400, 0) failed; error='Cannot > allocate memory' (errno=12) > > I have been using Ubuntu 14.04 LTS with 4GB ram.So how can i fix this > issue. And i got similar kind of error when i was trying to build the wso2 > product-ml. i have attached the detailes of the error i got in this mail. > Do i need to set up some additional environemtn variables to fix this. > BR, > Mahesh. > > > > > On Wed, Apr 27, 2016 at 1:51 PM, Maheshakya Wijewardena < > [email protected]> wrote: > >> Hi Mahesh, >> >> As Suho mentioned, if you have successfully built with tests, then there >> shouldn't be an issue. >> >> However, in the error you've stated, it seems there's problem with carbon >> home: >> >>> CARBON_HOME environment variable is set to >>> /home/mahesh/GSOC/WSO2/product-cep/modules/distribution >>> >> Can you make sure that you extract >> product-cep/modules/distribution/target/wso2cep-4.1.1-SNAPSHOT.zip and run >> the server in wso2cep-4.1.1-SNAPSHOT/bin/ with ./wso2server.sh >> >> Best regards. >> >> On Wed, Apr 27, 2016 at 12:43 PM, Sriskandarajah Suhothayan < >> [email protected]> wrote: >> >>> If your build has passed, then it should not be an issue. When building >>> the the tests should have ran. >>> Is that so? please verify. >>> During that server should have started and stopped. >>> >>> I think there is some issue in the way you have started the CEP. >>> >>> You should be able to build the products as you will be working with >>> components having snapshots versions. >>> >>> Regards >>> Suho >>> >>> On Wed, Apr 27, 2016 at 12:33 PM, Mahesh Dananjaya < >>> [email protected]> wrote: >>> >>>> Hi Maheshakya, >>>> I am trying to build the CEP by sourceas [1].it was built without >>>> errors.But when i run the ./wso2server.sh i got his error >>>> >>>> JAVA_HOME environment variable is set to /usr/local/java/jdk1.8.0_51 >>>> CARBON_HOME environment variable is set to >>>> /home/mahesh/GSOC/WSO2/product-cep/modules/distribution >>>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option >>>> MaxPermSize=256m; support was removed in 8.0 >>>> Could not load Logmanager "org.apache.juli.ClassLoaderLogManager" >>>> java.lang.ClassNotFoundException: org.apache.juli.ClassLoaderLogManager >>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:381) >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) >>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) >>>> at java.util.logging.LogManager$1.run(LogManager.java:195) >>>> at java.util.logging.LogManager$1.run(LogManager.java:181) >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> at java.util.logging.LogManager.<clinit>(LogManager.java:181) >>>> at java.util.logging.Logger.demandLogger(Logger.java:448) >>>> at java.util.logging.Logger.getLogger(Logger.java:502) >>>> at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:55) >>>> at >>>> sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:814) >>>> at sun.management.Agent.startLocalManagementAgent(Agent.java:138) >>>> at sun.management.Agent.startAgent(Agent.java:260) >>>> at sun.management.Agent.startAgent(Agent.java:447) >>>> Error: Could not find or load main class >>>> org.wso2.carbon.bootstrap.Bootstrap >>>> >>>> do i need some additional libraries there?Is it allright to go wit the >>>> [2] as we will be doing changes to source. >>>> BR, >>>> Mahesh. >>>> >>>> >>>> On Wed, Apr 27, 2016 at 12:17 PM, Maheshakya Wijewardena < >>>> [email protected]> wrote: >>>> >>>>> You don't need to build the kernel. You can build either current >>>>> master of product-cep[1] or you can download the latest release from [2]. >>>>> >>>>> Best regards. >>>>> >>>>> [1] https://github.com/wso2/product-cep >>>>> [2] http://wso2.com/products/complex-event-processor/ >>>>> >>>>> On Wed, Apr 27, 2016 at 12:09 PM, Mahesh Dananjaya < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi maheshakya, >>>>>> Do we need to build carbon kernal by source before we build CEP by >>>>>> source (https://github.com/wso2/carbon-kernel ) .Or is it inside >>>>>> those sources.i am trying to build all three sources after forked >>>>>> them.thank you. >>>>>> regards, >>>>>> Mahesh >>>>>> >>>>>> On Mon, Apr 25, 2016 at 5:49 PM, Maheshakya Wijewardena < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Mahesh, >>>>>>> >>>>>>> Congratulations and welcome to GSoC 2016. You did a great job in >>>>>>> preparing the proposal. Now it's time to dig deep and get started with >>>>>>> the >>>>>>> project. >>>>>>> >>>>>>> First of all you need to familiarize with the code base. We have >>>>>>> agreed to implement this with CEP event streams. We already have a CEP >>>>>>> extension for predictions [1][2]. Go through this implementation and >>>>>>> familiarize your self with that. You need to understand how: >>>>>>> >>>>>>> 1. Even streams are consumed >>>>>>> 2. predictions are made from individual event >>>>>>> 3. Results are sent back >>>>>>> >>>>>>> Get WSO2 ML and CEP sources (You may use latest released version of >>>>>>> CEP) and build the products. Get both carbon-ml[3] and product-ml[4] >>>>>>> masters and create new branches for your work from masters. >>>>>>> >>>>>>> After you build the products, you may need to do remote debugging[5] >>>>>>> to understand the flow. So please follow an example of real time >>>>>>> prediction >>>>>>> with ML with debugging and get some idea. The component you need to >>>>>>> debug >>>>>>> is org.wso2.carbon.ml.siddhi.extension. >>>>>>> >>>>>>> Next tasks would be implementing online learning algorithms in plain >>>>>>> java with spark ml lib and integrating those to ML. We also need to >>>>>>> come up >>>>>>> with a proper and detailed architecture to employ those algorithms in >>>>>>> ML. >>>>>>> Getting familiar with the aforementioned sections would give you some >>>>>>> insight on how this should be implemented. >>>>>>> >>>>>>> So please try to get a quick grasp then you can start the >>>>>>> implementation. Let us know if you have any questions or you get stuck >>>>>>> somewhere. >>>>>>> >>>>>>> Also, please always add WSO2 developer's list as well when you >>>>>>> communicate with us regarding the project so that you can get opinions >>>>>>> and >>>>>>> feedback from others as well. >>>>>>> >>>>>>> Best regards. >>>>>>> >>>>>>> [1] >>>>>>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension >>>>>>> >>>>>>> [2] >>>>>>> https://github.com/wso2/carbon-ml/tree/master/components/extensions/org.wso2.carbon.ml.siddhi.extension >>>>>>> >>>>>>> [3] https://github.com/wso2/carbon-ml >>>>>>> >>>>>>> [4] https://github.com/wso2/product-ml >>>>>>> >>>>>>> [5] https://dzone.com/articles/how-debug-wso2-carbon-kernel >>>>>>> >>>>>>> >>>>>>> On Mon, Apr 25, 2016 at 3:33 PM, Mahesh Dananjaya < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> thank you for accepting my GSOC 2016 proposal and i am looking >>>>>>>> forward for the further instruction and project continuation. thank you >>>>>>>> very much. >>>>>>>> regards, >>>>>>>> Mahesh. >>>>>>>> >>>>>>>> -- >>>>>>> Pruthuvi Maheshakya Wijewardena >>>>>>> [email protected] >>>>>>> +94711228855 >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Pruthuvi Maheshakya Wijewardena >>>>> [email protected] >>>>> +94711228855 >>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> *S. Suhothayan* >>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>> *WSO2 Inc. *http://wso2.com >>> * <http://wso2.com/>* >>> lean . enterprise . middleware >>> >>> >>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >>> >> >> >> >> -- >> Pruthuvi Maheshakya Wijewardena >> [email protected] >> +94711228855 >> >> >> > -- Pruthuvi Maheshakya Wijewardena [email protected] +94711228855
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
