Hi Daya,
Yes, I also don't think there is a linear relationship between numbers of
users and max active connections. I thought it was 50 when trying with 400
users. In this case, issue should be something else. May be not closing the
connection properly. I'm not aware of the values used in customer
deployments. May be someone can shed some light? Thanks.
Regards,
Prasad.
On Mon, Jul 7, 2014 at 12:27 PM, Daya Attapattu <d...@wso2.com> wrote:
> Hi Prasad,
>
> Thank you for the response. I have actually increased this to 250. In a
> way, it makes sense that I can run 200 threads but not 400 (with 250). I
> have previously run 100 threads with maxActive at 50 though. I was under
> the impression that this is not the upper limit of users; because all
> threads are not active at the same instance (and if they are, I was
> expecting them to queue up). May be I am wrong. I will increase this to
> 400 and run. One of my problems is that, I don't want to deviate from
> standard settings too much as that will affect performance in an irregular
> way. But if customers actually increase this when they are running many
> users, then I have no problem in doing the same.
>
> Regards, Daya
>
>
> On Mon, Jul 7, 2014 at 12:08 PM, Prasad Tissera <pras...@wso2.com> wrote:
>
>> In master-datasources.xml (wso2is-5.0.0/repository/conf/datasources) you
>> can increase the database connection pool size by
>> increasing <maxActive>50</maxActive> property.
>>
>> <datasource>
>> <name>WSO2_CARBON_DB</name>
>> <description>The datasource used for registry and user
>> manager</description>
>> <jndiConfig>
>> <name>jdbc/WSO2CarbonDB</name>
>> </jndiConfig>
>> <definition type="RDBMS">
>> <configuration>
>>
>> <url>jdbc:h2:repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=60000</url>
>> <username>wso2carbon</username>
>> <password>wso2carbon</password>
>> <driverClassName>org.h2.Driver</driverClassName>
>> <maxActive>50</maxActive>
>> <maxWait>60000</maxWait>
>> <testOnBorrow>true</testOnBorrow>
>> <validationQuery>SELECT 1</validationQuery>
>> <validationInterval>30000</validationInterval>
>> </configuration>
>> </definition>
>> </datasource>
>>
>> Hope this will help. Thanks.
>>
>>
>> On Mon, Jul 7, 2014 at 11:55 AM, Daya Attapattu <d...@wso2.com> wrote:
>>
>>> I am trying to run 400 users (400 threads on jmeter) on identity server.
>>> IS fails with the following message:
>>>
>>> ERROR {org.wso2.carbon.registry.core.dataaccess.TransactionManager} -
>>> Failed to start new registry transaction.
>>> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
>>> Data source rejected establishment of connection, message from server:
>>> "Too many connections"
>>>
>>> Is there any configuration parameter that I can use to facilitate a
>>> larger number of threads?
>>>
>>> Regards, Daya
>>>
>>> --
>>> Daya Atapattu
>>> WSO2 Inc.
>>> Phone: +94 77 047 4730, +1 203 484 7099
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Prasad Tissera
>> Software Engineer.
>> Mobile : +94777223444
>>
>
>
>
> --
> Daya Atapattu
> WSO2 Inc.
> Phone: +94 77 047 4730, +1 203 484 7099
>
>
--
Prasad Tissera
Software Engineer.
Mobile : +94777223444
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
