On Wed, Apr 25, 2012 at 8:37 AM, Prabath Abeysekera <praba...@wso2.com>wrote:
> Hi SupunM, > > On Wed, Apr 25, 2012 at 2:55 AM, Supun Malinga <sup...@wso2.com> wrote: > >> Hi PrabathA, >> >> Added a comment to the jira with the error I got in stratos AS. I believe >> its the same issue, hence didn't reopen. Please have a look. >> Also I can confirm that the issue is fixed with manager. >> > > As the stacktrace suggests, it looks likes the issue is originated from > the user core in this occasion. Root cause could be the same (therefore the > fix could be the same) but I don't think it has something to do with the > changes we've done for dataservices. > In a way there's a possibility that both the two reported issues are correlated. For example, there might be some functionality which depends on dataservices running in AS (BAM data agents?) occupying the maximum number of connections allowed in the MySQL instance thereby triggering this issue from somewhere else. Better if we profile the connections (via SHOW PROCESSLIST command in MySQL) in AS and double check whether it's the same issue that triggers the exceptions in both occasions. > > >> >> thanks, >> >> >> On Tue, Apr 24, 2012 at 3:54 PM, Muhammed Shariq <sha...@wso2.com> wrote: >> >>> On Tue, Apr 24, 2012 at 2:31 PM, Prabath Abeysekera >>> <praba...@wso2.com>wrote: >>> >>>> Hi, >>>> >>>> On Mon, Apr 23, 2012 at 8:14 PM, Sumedha Rubasinghe >>>> <sume...@wso2.com>wrote: >>>> >>>>> But if a connection leak has occurred, it has to come from DS code. >>>>> Are all data services using the same connection pool or are there >>>>> separate ones? >>>>> >>>> >>>> The reason behind this issue is that multiple datasource references are >>>> getting created (thereby creating multiple connection pools) at run time >>>> whenever we look up for a particular carbon datasource. I've done a >>>> temporary fix upon this by enabling sharing of the same datasource per >>>> dataservice configuration, when used with carbon datasources(This option is >>>> already there for inline datasources). However, this fix too would have a >>>> few issues such as whenever the properties of a particular carbon >>>> datasource are updated, those updates will not be reflected until the >>>> dataservice is redeployed, etc. But we're hoping to fix all the >>>> aforementioned limitations (together with some other limitations that were >>>> already reported) in the new datasource component that we'll be implemented >>>> targeting the upcoming release. >>>> >>> >>> Thanks for the detailed update :-) >>> >>>> >>>> >>>>> >>>>> >>>>> >>>>> On Mon, Apr 23, 2012 at 4:51 PM, Prabath Abeysekera <praba...@wso2.com >>>>> > wrote: >>>>> >>>>>> >>>>>> >>>>>> On Mon, Apr 23, 2012 at 4:40 PM, Anjana Fernando <anj...@wso2.com>wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> On Mon, Apr 23, 2012 at 4:29 PM, Muhammed Shariq <sha...@wso2.com>wrote: >>>>>>> >>>>>>>> Hi Anjana, >>>>>>>> >>>>>>>> IIRC there was an issue in Alpha2 packs where there was an NPE >>>>>>>> thrown when deploying .dbs files, so this issue did not surface. By >>>>>>>> monitoring via SHOW PROCESSLIST, there seem a burst of processes >>>>>>>> trying to connect to the billing database (that's the DB all the .dbs >>>>>>>> files >>>>>>>> access). Basically there are a numer of .dbs files deployed during the >>>>>>>> server startup, hence the sudden increase. >>>>>>>> >>>>>>>> However by increasing the max_connections to 1000 I was able to get >>>>>>>> rid of this issue, (hope 1000 is an acceptable number ?), previously >>>>>>>> it was >>>>>>>> set to 150. So if 1000 as max_connections is acceptable, we can >>>>>>>> consider >>>>>>>> this issue fixed. >>>>>>>> >>>>>>> >>>>>>> 1000 is too much, there is no reason for that much of connections to >>>>>>> be created and persisted. Anyways, does the connections get released >>>>>>> after >>>>>>> the startup, which can be observed by SHOW PROCESSLIST. >>>>>>> >>>>>> >>>>>> I too have a feeling that you would probably need to double check the >>>>>> database access implementation and see whether the connections are >>>>>> properly >>>>>> closed after the interactions with the database. Though it's not >>>>>> something >>>>>> unusual to see this parameter being increased to higher values in a >>>>>> production level MySQL instances to allow higher number of connections, I >>>>>> don't really think it's the best option we have upon the reported issue >>>>>> as >>>>>> ideally there shouldn't be that many connections opened at the server >>>>>> startup. >>>>>> >>>>>> >>>>>>> >>>>>>> Cheers, >>>>>>> Anjana. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Apr 23, 2012 at 3:25 PM, Anjana Fernando >>>>>>>> <anj...@wso2.com>wrote: >>>>>>>> >>>>>>>>> Hi Shariq, >>>>>>>>> >>>>>>>>> On Mon, Apr 23, 2012 at 2:27 PM, Muhammed Shariq >>>>>>>>> <sha...@wso2.com>wrote: >>>>>>>>> >>>>>>>>>> This issue is there in Alpha4 packs as well. I had a chat with >>>>>>>>>> PrabathA about this learnt that increasing the number connections >>>>>>>>>> could >>>>>>>>>> resolve the issue. I tried increasing the connection properties as >>>>>>>>>> follows, >>>>>>>>>> but still no luck >>>>>>>>>> >>>>>>>>> >>>>>>>>> Did this properly work in Alpha2? .. if so, can you please check >>>>>>>>> if there any configuration related changes happen between builds. >>>>>>>>> Basically >>>>>>>>> run Alpha2 again, against the same MySQL instance and see if it >>>>>>>>> works. And >>>>>>>>> also as Prabath said, run "SHOW PROCESSLIST" and monitor the number of >>>>>>>>> connections being created. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Anjana. >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> synapse.datasources.stratos_ds.maxActive=*300* >>>>>>>>>> synapse.datasources.stratos_ds.minIdle=*50* >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Apr 23, 2012 at 2:14 PM, Dimuthu Leelarathne < >>>>>>>>>> dimut...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Sumedha, >>>>>>>>>>> >>>>>>>>>>> The server is up because the mysql-query-browser connects. >>>>>>>>>>> >>>>>>>>>>> thanks, >>>>>>>>>>> dimuthu >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Apr 23, 2012 at 2:08 PM, Sumedha Rubasinghe < >>>>>>>>>>> sume...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> MySQL service is not available when the server boots up. >>>>>>>>>>>> Try connecting to MySQL from command line. >>>>>>>>>>>> >>>>>>>>>>>> Another thing is to observe the time to connect (if the MySQL >>>>>>>>>>>> is responding too slow). >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Apr 23, 2012 at 2:04 PM, Dimuthu Leelarathne < >>>>>>>>>>>> dimut...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Anjana, >>>>>>>>>>>>> >>>>>>>>>>>>> Any idea how to overcome this issue we are facing? >>>>>>>>>>>>> >>>>>>>>>>>>> https://wso2.org/jira/browse/STRATOS-2021 >>>>>>>>>>>>> >>>>>>>>>>>>> According to stack overflow, this seems to be a timeout issue. >>>>>>>>>>>>> But this error comes on the first startup of the server. >>>>>>>>>>>>> >>>>>>>>>>>>> thanks, >>>>>>>>>>>>> dimuthu >>>>>>>>>>>>> -- >>>>>>>>>>>>> Dimuthu Leelarathne >>>>>>>>>>>>> Technical Lead >>>>>>>>>>>>> >>>>>>>>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>>>>>>>> email: dimut...@wso2.com >>>>>>>>>>>>> >>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> /sumedha >>>>>>>>>>>> +94 773017743 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Dimuthu Leelarathne >>>>>>>>>>> Technical Lead >>>>>>>>>>> >>>>>>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>>>>>> email: dimut...@wso2.com >>>>>>>>>>> >>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Thanks, >>>>>>>>>> Shariq. >>>>>>>>>> Phone: +94 777 202 225 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Anjana Fernando* >>>>>>>>> Senior Software Engineer >>>>>>>>> WSO2 Inc. | http://wso2.com >>>>>>>>> lean . enterprise . middleware >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks, >>>>>>>> Shariq. >>>>>>>> Phone: +94 777 202 225 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Anjana Fernando* >>>>>>> Senior Software Engineer >>>>>>> WSO2 Inc. | http://wso2.com >>>>>>> lean . enterprise . middleware >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Prabath Abeysekara >>>>>> Software Engineer >>>>>> WSO2 Inc. >>>>>> Email: praba...@wso2.com <harsha...@wso2.com> >>>>>> Mobile: +94774171471 >>>>>> >>>>>> <http://harshana05.blogspot.com/> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> /sumedha >>>>> +94 773017743 >>>>> >>>> >>>> >>>> Regards, >>>> Prabath >>>> -- >>>> Prabath Abeysekara >>>> Software Engineer >>>> WSO2 Inc. >>>> Email: praba...@wso2.com <harsha...@wso2.com> >>>> Mobile: +94774171471 >>>> >>>> <http://harshana05.blogspot.com/> >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Thanks, >>> Shariq. >>> Phone: +94 777 202 225 >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Supun Malinga, >> >> Software Engineer, >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> email - sup...@wso2.com <sup...@wso2.com> >> mobile - 071 56 91 321 >> >> > > Regards, > Prabath > -- > Prabath Abeysekara > Software Engineer > WSO2 Inc. > Email: praba...@wso2.com <harsha...@wso2.com> > Mobile: +94774171471 > > <http://harshana05.blogspot.com/> > > -- Prabath Abeysekara Software Engineer WSO2 Inc. Email: praba...@wso2.com <harsha...@wso2.com> Mobile: +94774171471 <http://harshana05.blogspot.com/>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
