Hi all, Thanks for accepting my project proposal. :) Thank you very much on helping me to prepare a good proposal. I am looking forward to get started with the project ASAP
On Sat, Mar 26, 2016 at 12:16 PM, Isuru Udana <[email protected]> wrote: > Hi Dinanjana, > > > > On Sat, Mar 26, 2016 at 8:31 AM, Dinanjana Gunaratne < > [email protected]> wrote: > >> Hi Kasun, >> So shall I update the draft ? What do you think. I think the best >> approach is to make this a separate application. Otherwise it will anyways >> have an effect on the performance of ESB. Because this tool includes some >> serious IO operations >> > Even though we built it as a separate application while we are taking > thread-dumps, etc, can lead to a degrade in performance to a great extent, > that's why we need to design it carefully. > > Thanks. > >> >> On Sat, Mar 26, 2016 at 8:25 AM, Kasun Indrasiri <[email protected]> wrote: >> >>> It's fine. But just want to make sure this is added to the project plan >>> as we move forward. >>> >>> On Sat, Mar 26, 2016 at 8:01 AM, Dinanjana Gunaratne < >>> [email protected]> wrote: >>> >>>> Hi Kasun , >>>> It's now I saw this mail. Can I do the change now ? I guess it's too >>>> late now. Anyway on your second point I have said that making flight >>>> recorder a separate application will stop applying any performance >>>> degradation on ESB. Anyway it would have been better if I have added the >>>> comparison.Can I do those changes now ?And i am really sorry for the late >>>> reply. >>>> >>>> On Fri, Mar 25, 2016 at 11:54 PM, Kasun Indrasiri <[email protected]> >>>> wrote: >>>> >>>>> Dinanjana, can you please include several use cases related to >>>>> possible production issues in an ESB (such as out of memory, CPU spinning, >>>>> deadlock etc.). Also, running the ESB flight recorder should have minimal >>>>> impact on the ESB performance. Hence your proposal should include an ESB >>>>> performance comparison with and without flight recorder. >>>>> >>>>> The proposal looks good. >>>>> >>>>> Thanks, >>>>> Kasun >>>>> >>>>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Isuru , >>>>>> Thanks for the input :) >>>>>> >>>>>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Isuru , >>>>>>> Thanks for the input :) >>>>>>> >>>>>>> On Fri, Mar 25, 2016 at 6:34 PM, Isuru Udana <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Dinanjana, >>>>>>>> >>>>>>>> Proposal looks really good to me. Added several comments as well. >>>>>>>> >>>>>>>> On Fri, Mar 25, 2016 at 8:21 AM, Dinanjana Gunaratne < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hello all, >>>>>>>>> I submitted my proposal to gsoc site and shared the draft with >>>>>>>>> WSO2 earlier this week. Any thoughts on my proposal ? >>>>>>>>> >>>>>>>>> On Sun, Mar 20, 2016 at 7:04 PM, Dinanjana Gunaratne < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> Can i have the location of source of carbondump tool ? >>>>>>>>>> >>>>>>>>>> On Wed, Mar 9, 2016 at 12:05 PM, Dinanjana Gunaratne < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> I went through webinar and actually through the code of ESB. I >>>>>>>>>>> couldn't grasped much with the code though. Now I have a high level >>>>>>>>>>> understanding on what ESB does. I assumed that the esb is built on >>>>>>>>>>> carbon >>>>>>>>>>> kernel. So we can have our monitoring service there inside the >>>>>>>>>>> carbon or >>>>>>>>>>> else we can have a seperate microservice which can remotely monitor >>>>>>>>>>> the >>>>>>>>>>> mbean server of the relevant JVM and extract metrics we require >>>>>>>>>>> >>>>>>>>>>> On Thu, Mar 3, 2016 at 5:35 PM, Isuru Ranawaka <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Dinanjana, >>>>>>>>>>>> >>>>>>>>>>>> While you are reading the documentation you can figure out >>>>>>>>>>>> important features that needs to be included and come up with a >>>>>>>>>>>> set of >>>>>>>>>>>> features.Then we can finalize the scope of the project and start >>>>>>>>>>>> working on >>>>>>>>>>>> it. Since you have already worked on this kind of project can you >>>>>>>>>>>> propose >>>>>>>>>>>> set of features and informations that will be helpfull to >>>>>>>>>>>> implement them. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> thanks >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Mar 3, 2016 at 9:56 AM, Dinanjana Gunaratne < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi all, >>>>>>>>>>>>> Not currently. I am going through the documentation :) Thanks >>>>>>>>>>>>> for the help :) >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Mar 3, 2016 at 9:52 AM, Isuru Udana <[email protected]> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Dinanjana, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Do you need further help to understand the ESB architecture ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Feb 29, 2016 at 6:01 PM, Nadeeshaan Gunasinghe < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Dinanjana, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> In order to have a better understanding about the underlying >>>>>>>>>>>>>>> functionalities of WSO2 ESB, it would be better if you take a >>>>>>>>>>>>>>> look at the >>>>>>>>>>>>>>> architecture first. Please find [1] which is a very informative >>>>>>>>>>>>>>> webinar >>>>>>>>>>>>>>> about WSO2 ESB's architecture as well as the message flow. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Also if you are trying to get familiar how ESB handles the >>>>>>>>>>>>>>> mediation at the core level, I would like to suggest going >>>>>>>>>>>>>>> through [2] >>>>>>>>>>>>>>> which covers the transport level functionality mapping to the >>>>>>>>>>>>>>> ESB core >>>>>>>>>>>>>>> level. This contains three parts and it would be great if you >>>>>>>>>>>>>>> go through >>>>>>>>>>>>>>> them :) . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Additionally try to deploy a simple synapse configuration >>>>>>>>>>>>>>> and debug the code base to identify how the message flows >>>>>>>>>>>>>>> through synapse. >>>>>>>>>>>>>>> If you do so you will be able to get a firm grasp of the >>>>>>>>>>>>>>> message flow >>>>>>>>>>>>>>> mentioned at [2]. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>> http://wso2.com/library/webinars/2014/09/understanding-wso2-esb-introduction-to-esb-architecture-and-message-flow/ >>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>> http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Nadeeshaan Gunasinghe* >>>>>>>>>>>>>>> Software Engineer, WSO2 Inc. http://wso2.com >>>>>>>>>>>>>>> +94770596754 | [email protected] | Skype: >>>>>>>>>>>>>>> nadeeshaan.gunasinghe >>>>>>>>>>>>>>> <#m_-488055444625272468_m_-8776032907468064948_m_-7768434574235180537_m_-7235778947164465931_m_7232211748715967048_m_-3757373977837873170_m_-8283982100572052979_m_1362338246273110367_m_-1442751731575898940_m_6485817575745999246_m_265559619745955743_3779151517627746345_-555366748_-88362740_816856320_1348862296_-537557168_478758164_> >>>>>>>>>>>>>>> <http://www.facebook.com/nadeeshaan.gunasinghe> >>>>>>>>>>>>>>> <http://lk.linkedin.com/in/nadeeshaan> >>>>>>>>>>>>>>> <http://twitter.com/Nadeeshaan> >>>>>>>>>>>>>>> <http://nadeeshaan.blogspot.com/> >>>>>>>>>>>>>>> Get a signature like this: Click here! >>>>>>>>>>>>>>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=&u=987873371783644> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Feb 29, 2016 at 1:09 PM, Dinanjana Gunaratne < >>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>>>> As Nadeeshan has suggested earlier i built all 3 projects >>>>>>>>>>>>>>>> from the source. Many of the details of JVM Isuru suggested >>>>>>>>>>>>>>>> can be gained >>>>>>>>>>>>>>>> from java.lang.management. Other specific data i think can be >>>>>>>>>>>>>>>> gained from >>>>>>>>>>>>>>>> management package of carbon. I still have a very little >>>>>>>>>>>>>>>> understanding >>>>>>>>>>>>>>>> about the architecture of ESB. So what I can't understand is >>>>>>>>>>>>>>>> where to do >>>>>>>>>>>>>>>> the implementation?Are we talking about a "feature" to ESB ? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Feb 29, 2016 at 9:32 AM, Isuru Udana < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Dinanjana, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Intention of this project is to build a tool which ease >>>>>>>>>>>>>>>>> production incident analysis. >>>>>>>>>>>>>>>>> Some of the common production incidents are, >>>>>>>>>>>>>>>>> - Server goes OOM >>>>>>>>>>>>>>>>> - Increase of CPU usage >>>>>>>>>>>>>>>>> - Server goes to an unresponsive state >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> We need to detect those situations and need to extract >>>>>>>>>>>>>>>>> useful information to debug the issue before the server goes >>>>>>>>>>>>>>>>> to a >>>>>>>>>>>>>>>>> catastrophic state. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> For an example, when the server goes OOM, it will >>>>>>>>>>>>>>>>> automatically generate the heap dump. However heap dump is >>>>>>>>>>>>>>>>> not sufficient >>>>>>>>>>>>>>>>> to analyse the incident. We need to see what causes the >>>>>>>>>>>>>>>>> increase of heap. >>>>>>>>>>>>>>>>> That may be due to increase of load (requests) or may be due >>>>>>>>>>>>>>>>> to a bug. So >>>>>>>>>>>>>>>>> we need to extract information like TPS of the server, thread >>>>>>>>>>>>>>>>> dumps to do >>>>>>>>>>>>>>>>> the further analysis. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Fri, Feb 26, 2016 at 1:38 PM, Nadeeshaan Gunasinghe < >>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Dinanjana, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> First let's try to build WSO2 ESB from source and then >>>>>>>>>>>>>>>>>> dig in deep to the source. In order to do so you will need >>>>>>>>>>>>>>>>>> build the >>>>>>>>>>>>>>>>>> following repositories in the order. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> [1] https://github.com/wso2/wso2-synapse >>>>>>>>>>>>>>>>>> [2] https://github.com/wso2/carbon-mediation >>>>>>>>>>>>>>>>>> [3] https://github.com/wso2/product-esb >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> *Nadeeshaan Gunasinghe* >>>>>>>>>>>>>>>>>> Software Engineer, WSO2 Inc. http://wso2.com >>>>>>>>>>>>>>>>>> +94770596754 | [email protected] | Skype: >>>>>>>>>>>>>>>>>> nadeeshaan.gunasinghe >>>>>>>>>>>>>>>>>> <#m_-488055444625272468_m_-8776032907468064948_m_-7768434574235180537_m_-7235778947164465931_m_7232211748715967048_m_-3757373977837873170_m_-8283982100572052979_m_1362338246273110367_m_-1442751731575898940_m_6485817575745999246_m_265559619745955743_3779151517627746345_-555366748_-88362740_816856320_1348862296_-537557168_478758164_1912754997_-722133546_-1073985791_> >>>>>>>>>>>>>>>>>> <http://www.facebook.com/nadeeshaan.gunasinghe> >>>>>>>>>>>>>>>>>> <http://lk.linkedin.com/in/nadeeshaan> >>>>>>>>>>>>>>>>>> <http://twitter.com/Nadeeshaan> >>>>>>>>>>>>>>>>>> <http://nadeeshaan.blogspot.com/> >>>>>>>>>>>>>>>>>> Get a signature like this: Click here! >>>>>>>>>>>>>>>>>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=&u=153303653327748> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, Feb 25, 2016 at 6:24 AM, Dinanjana Gunaratne < >>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Dear Isuru, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Can you send me a link of api documentation of >>>>>>>>>>>>>>>>>>> management package of ESB ? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Sun, Feb 21, 2016 at 2:34 PM, Dinanjana Gunaratne < >>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Dear Isuru, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Sorry for bothering you again. I created a sample >>>>>>>>>>>>>>>>>>>> module with some of the requirements you mentioned in gsoc >>>>>>>>>>>>>>>>>>>> project page. >>>>>>>>>>>>>>>>>>>> Those requirements are creating thread dumps when >>>>>>>>>>>>>>>>>>>> resources usage increased >>>>>>>>>>>>>>>>>>>> unexpectedly. Now I like to know how to integrate this in >>>>>>>>>>>>>>>>>>>> to ESB and test >>>>>>>>>>>>>>>>>>>> the functionality. I couldn't find the location of ESB >>>>>>>>>>>>>>>>>>>> source. >>>>>>>>>>>>>>>>>>>> On Feb 20, 2016 9:33 AM, "Dinanjana Gunaratne" < >>>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Dear Isuru, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Are we looking at an implementation like this ? >>>>>>>>>>>>>>>>>>>>> "Dashboard is a remote monitoring system which was >>>>>>>>>>>>>>>>>>>>> developed to monitor the status(server's aliveness and >>>>>>>>>>>>>>>>>>>>> management details) >>>>>>>>>>>>>>>>>>>>> of software deployed remotely. This monitoring system is >>>>>>>>>>>>>>>>>>>>> highly scalable >>>>>>>>>>>>>>>>>>>>> and does not depend on any component which is being >>>>>>>>>>>>>>>>>>>>> monitored. With >>>>>>>>>>>>>>>>>>>>> Dashboard comes a Java library called >>>>>>>>>>>>>>>>>>>>> "HeartBeat".HeartBeat is a client >>>>>>>>>>>>>>>>>>>>> which was developed by us for connects to Dashboard and >>>>>>>>>>>>>>>>>>>>> share information. >>>>>>>>>>>>>>>>>>>>> So any component wish to register with Dashboard >>>>>>>>>>>>>>>>>>>>> monitoring system must >>>>>>>>>>>>>>>>>>>>> implement that Java library." >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I did this during my internship. I think we are >>>>>>>>>>>>>>>>>>>>> looking at an implementation within esb for debugging and >>>>>>>>>>>>>>>>>>>>> monitoring. am i >>>>>>>>>>>>>>>>>>>>> correct ? :) >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Sat, Feb 20, 2016 at 9:12 AM, Isuru Udana < >>>>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Great...! >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> btw, don't call me "Sir" :) >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Sat, Feb 20, 2016 at 8:58 AM, Dinanjana Gunaratne >>>>>>>>>>>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Dear Isuru, >>>>>>>>>>>>>>>>>>>>>>> Found the solution :) >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Sat, Feb 20, 2016 at 8:49 AM, Dinanjana Gunaratne >>>>>>>>>>>>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Dear Isuru, >>>>>>>>>>>>>>>>>>>>>>>> Sorry for bothering you. Found the solution for >>>>>>>>>>>>>>>>>>>>>>>> earlier problem from here [1 >>>>>>>>>>>>>>>>>>>>>>>> <http://stackoverflow.com/questions/32866263/axis2server-packed-with-esb-4-9-0-doesnt-start-while-it-works-fine-4-8-0>]. >>>>>>>>>>>>>>>>>>>>>>>> Now i am facing a new problem. axis2 server looking >>>>>>>>>>>>>>>>>>>>>>>> for axis2.xml on wrong >>>>>>>>>>>>>>>>>>>>>>>> directory. below is the stack trace >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> [2016-02-20 08:41:21,491] FATAL >>>>>>>>>>>>>>>>>>>>>>>> {samples.util.SampleAxis2ServerManager} - >>>>>>>>>>>>>>>>>>>>>>>> [SimpleAxisServer] Shutti >>>>>>>>>>>>>>>>>>>>>>>> ng down. Error starting SimpleAxisServer >>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis2.AxisFault: System can not find the >>>>>>>>>>>>>>>>>>>>>>>> given axis2.xml E:\Project\wso2esb-4.9.0\samples >>>>>>>>>>>>>>>>>>>>>>>> \axis2Serverrepository\conf\axis2.xml >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigu >>>>>>>>>>>>>>>>>>>>>>>> rator.java:118) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura >>>>>>>>>>>>>>>>>>>>>>>> tionContextFactory.java:64) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSy >>>>>>>>>>>>>>>>>>>>>>>> stem(ConfigurationContextFactory.java:210) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> samples.util.SampleAxis2ServerManager.start(SampleAxis2ServerManager.java:93) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> samples.util.SampleAxis2Server.startServer(SampleAxis2Server.java:61) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>>>>>>>>>>>>>>>>>>>>>>> Method) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> java.lang.reflect.Method.invoke(Method.java:483) >>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>> samples.util.Bootstrap.main(Bootstrap.java:132) >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> I have defined AXIS2_HOME correctly >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>> http://stackoverflow.com/questions/32866263/axis2server-packed-with-esb-4-9-0-doesnt-start-while-it-works-fine-4-8-0 >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> On Sat, Feb 20, 2016 at 7:55 AM, Dinanjana >>>>>>>>>>>>>>>>>>>>>>>> Gunaratne <[email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Dear sir, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> When i tried to run axis2server.bat came bundled >>>>>>>>>>>>>>>>>>>>>>>>> with wso2esb i am getting this >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Usage: java [-options] class [args...] >>>>>>>>>>>>>>>>>>>>>>>>> (to execute a class) >>>>>>>>>>>>>>>>>>>>>>>>> or java [-options] -jar jarfile [args...] >>>>>>>>>>>>>>>>>>>>>>>>> (to execute a jar file) >>>>>>>>>>>>>>>>>>>>>>>>> where options include: >>>>>>>>>>>>>>>>>>>>>>>>> -d32 use a 32-bit data model if >>>>>>>>>>>>>>>>>>>>>>>>> available >>>>>>>>>>>>>>>>>>>>>>>>> -d64 use a 64-bit data model if >>>>>>>>>>>>>>>>>>>>>>>>> available >>>>>>>>>>>>>>>>>>>>>>>>> -server to select the "server" VM >>>>>>>>>>>>>>>>>>>>>>>>> The default VM is server. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> -cp <class search path of directories and >>>>>>>>>>>>>>>>>>>>>>>>> zip/jar files> >>>>>>>>>>>>>>>>>>>>>>>>> -classpath <class search path of directories >>>>>>>>>>>>>>>>>>>>>>>>> and zip/jar files> >>>>>>>>>>>>>>>>>>>>>>>>> A ; separated list of >>>>>>>>>>>>>>>>>>>>>>>>> directories, JAR archives, >>>>>>>>>>>>>>>>>>>>>>>>> and ZIP archives to search for >>>>>>>>>>>>>>>>>>>>>>>>> class files. >>>>>>>>>>>>>>>>>>>>>>>>> -D<name>=<value> >>>>>>>>>>>>>>>>>>>>>>>>> set a system property >>>>>>>>>>>>>>>>>>>>>>>>> -verbose:[class|gc|jni] >>>>>>>>>>>>>>>>>>>>>>>>> enable verbose output >>>>>>>>>>>>>>>>>>>>>>>>> -version print product version and exit >>>>>>>>>>>>>>>>>>>>>>>>> -version:<value> >>>>>>>>>>>>>>>>>>>>>>>>> require the specified version to >>>>>>>>>>>>>>>>>>>>>>>>> run >>>>>>>>>>>>>>>>>>>>>>>>> -showversion print product version and >>>>>>>>>>>>>>>>>>>>>>>>> continue >>>>>>>>>>>>>>>>>>>>>>>>> -jre-restrict-search | -no-jre-restrict-search >>>>>>>>>>>>>>>>>>>>>>>>> include/exclude user private >>>>>>>>>>>>>>>>>>>>>>>>> JREs in the version search >>>>>>>>>>>>>>>>>>>>>>>>> -? -help print this help message >>>>>>>>>>>>>>>>>>>>>>>>> -X print help on non-standard >>>>>>>>>>>>>>>>>>>>>>>>> options >>>>>>>>>>>>>>>>>>>>>>>>> -ea[:<packagename>...|:<classname>] >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> -enableassertions[:<packagename>...|:<classname>] >>>>>>>>>>>>>>>>>>>>>>>>> enable assertions with specified >>>>>>>>>>>>>>>>>>>>>>>>> granularity >>>>>>>>>>>>>>>>>>>>>>>>> -da[:<packagename>...|:<classname>] >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> -disableassertions[:<packagename>...|:<classname>] >>>>>>>>>>>>>>>>>>>>>>>>> disable assertions with >>>>>>>>>>>>>>>>>>>>>>>>> specified granularity >>>>>>>>>>>>>>>>>>>>>>>>> -esa | -enablesystemassertions >>>>>>>>>>>>>>>>>>>>>>>>> enable system assertions >>>>>>>>>>>>>>>>>>>>>>>>> -dsa | -disablesystemassertions >>>>>>>>>>>>>>>>>>>>>>>>> disable system assertions >>>>>>>>>>>>>>>>>>>>>>>>> -agentlib:<libname>[=<options>] >>>>>>>>>>>>>>>>>>>>>>>>> load native agent library >>>>>>>>>>>>>>>>>>>>>>>>> <libname>, e.g. -agentlib:hprof >>>>>>>>>>>>>>>>>>>>>>>>> see also, -agentlib:jdwp=help >>>>>>>>>>>>>>>>>>>>>>>>> and -agentlib:hprof=help >>>>>>>>>>>>>>>>>>>>>>>>> -agentpath:<pathname>[=<options>] >>>>>>>>>>>>>>>>>>>>>>>>> load native agent library by >>>>>>>>>>>>>>>>>>>>>>>>> full pathname >>>>>>>>>>>>>>>>>>>>>>>>> -javaagent:<jarpath>[=<options>] >>>>>>>>>>>>>>>>>>>>>>>>> load Java programming language >>>>>>>>>>>>>>>>>>>>>>>>> agent, see java.lang.instrument >>>>>>>>>>>>>>>>>>>>>>>>> -splash:<imagepath> >>>>>>>>>>>>>>>>>>>>>>>>> show splash screen with >>>>>>>>>>>>>>>>>>>>>>>>> specified image >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Any reason for it ? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Then I downloaded axis2 server and started it.It >>>>>>>>>>>>>>>>>>>>>>>>> started correctly. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Thu, Feb 18, 2016 at 7:04 AM, Dinanjana >>>>>>>>>>>>>>>>>>>>>>>>> Gunaratne <[email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for the info :) i will look at it >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Feb 17, 2016 at 10:10 AM, Isuru Udana < >>>>>>>>>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Dinanjana, >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> Thank you for your interest in this project. >>>>>>>>>>>>>>>>>>>>>>>>>>> As a starting point, you can download WSO2 >>>>>>>>>>>>>>>>>>>>>>>>>>> ESB[1] and start play with it. >>>>>>>>>>>>>>>>>>>>>>>>>>> You may run few samples[2] to get familiar with >>>>>>>>>>>>>>>>>>>>>>>>>>> the product first. >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.com/products/enterprise-service-bus/ >>>>>>>>>>>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>>>>>>>>>>>>> http://docs.wso2.org/wiki/display/ESB490/Samples >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Feb 15, 2016 at 9:31 PM, Dinanjana >>>>>>>>>>>>>>>>>>>>>>>>>>> Gunaratne <[email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> From: Dinanjana Gunaratne < >>>>>>>>>>>>>>>>>>>>>>>>>>>> [email protected]> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Date: Mon, Feb 15, 2016 at 9:27 PM >>>>>>>>>>>>>>>>>>>>>>>>>>>> Subject: [Dev]GSOC 2016: Proposal 7 >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Dear Sir, >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> I m a 3rd year Computer Engineering >>>>>>>>>>>>>>>>>>>>>>>>>>>> undergraduate at University of Peradeniya. I would >>>>>>>>>>>>>>>>>>>>>>>>>>>> like to contribute to >>>>>>>>>>>>>>>>>>>>>>>>>>>> open source community by taking part in GSOC 2016. >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Recently i developed a remote monitoring system >>>>>>>>>>>>>>>>>>>>>>>>>>>> for an organization which had some of those >>>>>>>>>>>>>>>>>>>>>>>>>>>> mentioned features. Such as >>>>>>>>>>>>>>>>>>>>>>>>>>>> alerting when resources are over used and alerting >>>>>>>>>>>>>>>>>>>>>>>>>>>> when server stop >>>>>>>>>>>>>>>>>>>>>>>>>>>> responding. The monitoring system developed in >>>>>>>>>>>>>>>>>>>>>>>>>>>> such a manner that the >>>>>>>>>>>>>>>>>>>>>>>>>>>> implementation of monitoring system does not >>>>>>>>>>>>>>>>>>>>>>>>>>>> depend on components that are >>>>>>>>>>>>>>>>>>>>>>>>>>>> been monitored. The solution is built using Java >>>>>>>>>>>>>>>>>>>>>>>>>>>> and Spring framework. >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> So i wold like to know how to proceed on this >>>>>>>>>>>>>>>>>>>>>>>>>>>> project. >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>>>>>> *Isuru Udana* >>>>>>>>>>>>>>>>>>>>>>>>>>> Associate Technical Lead >>>>>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>>>>>>>>>>>>>>>>>> email: [email protected] cell: +94 77 3791887 >>>>>>>>>>>>>>>>>>>>>>>>>>> blog: http://mytecheye.blogspot.com/ >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>> *Isuru Udana* >>>>>>>>>>>>>>>>>>>>>> Associate Technical Lead >>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>>>>>>>>>>>>> email: [email protected] cell: +94 77 3791887 >>>>>>>>>>>>>>>>>>>>>> blog: http://mytecheye.blogspot.com/ >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> *Isuru Udana* >>>>>>>>>>>>>>>>> Associate Technical Lead >>>>>>>>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>>>>>>>> email: [email protected] cell: +94 77 3791887 >>>>>>>>>>>>>>>>> blog: http://mytecheye.blogspot.com/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> *Isuru Udana* >>>>>>>>>>>>>> Associate Technical Lead >>>>>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>>>>> email: [email protected] cell: +94 77 3791887 >>>>>>>>>>>>>> blog: http://mytecheye.blogspot.com/ >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Best Regards >>>>>>>>>>>> Isuru Ranawaka >>>>>>>>>>>> M: +94714629880 >>>>>>>>>>>> Blog : http://isurur.blogspot.com/ >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Isuru Udana* >>>>>>>> Associate Technical Lead >>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>> email: [email protected] cell: +94 77 3791887 >>>>>>>> blog: http://mytecheye.blogspot.com/ >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Kasun Indrasiri >>>>> Software Architect >>>>> WSO2, Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> cell: +94 77 556 5206 >>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>> >>>> >>>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: [email protected] cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
