[ 
https://issues.apache.org/jira/browse/CAY-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753880#comment-15753880
 ] 

ASF GitHub Bot commented on CAY-2162:
-------------------------------------

GitHub user stariy95 opened a pull request:

    https://github.com/apache/cayenne/pull/162

    CAY-2162 Set max connection pool size in tests

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/stariy95/cayenne CAY-2162

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cayenne/pull/162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #162
    
----
commit 25d673df4c42639d5b48b29582f82175e828a5d2
Author: Nikita Timofeev <stari...@gmail.com>
Date:   2016-12-12T08:17:21Z

    CAY-2162
    Set connection pool size for all test connections

----


> Integration Tests. Setting connection pool size in test with command line 
> parameters
> ------------------------------------------------------------------------------------
>
>                 Key: CAY-2162
>                 URL: https://issues.apache.org/jira/browse/CAY-2162
>             Project: Cayenne
>          Issue Type: Task
>            Reporter: Nikita Timofeev
>            Priority: Minor
>
> Currently there is two options for setting connection properties for 
> integration tests [1]:
>  1. via command line parameters
>  2. via connection.properties in ~/.cayenne directory
> When connection.properties is used connection pool size by default has max 
> size 2. 
> In case properties set directly in command line max size remains 1 and there 
> is no way to set max pool size.
> That behavior leads to some test failure where passing connection parameters 
> via command line (e.g. travis build fails with mysql-docker and 
> postgres-docker test profiles)
> [1] 
> http://cayenne.apache.org/dev/running-unit-tests.html#running-against-a-specific-database



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to