[ 
https://issues.apache.org/jira/browse/OFBIZ-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-4794:
-----------------------------------

    Attachment: OFBIZ-4794 - test port - R11.04.patch
                OFBIZ-4794 - test port - R12.04.patch
                OFBIZ-4794 - test port - R13.07.patch
                OFBIZ-4794 - test port - trunk.patch

After unsuccesfully trying to understand why I get a Transaction Timeout error 
with testSOAPSimpleService when running trunk tests with concurrently one 
release instance tests, I decided to attach the patch again. 

I did not get this error when I run 2 releases instances tests (R11.04 and 
R12.04) but maybe R13.07 with another one. Since R13.07 is not much different 
than trunk I guess I will get the same error, which is quite obvcure to me. I 
can't relate to my changes though it must be related.

If someone could also test it and have a look it would be great.
                
> set different ports for testing in a CI environment (e.g. Jenkins)
> ------------------------------------------------------------------
>
>                 Key: OFBIZ-4794
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4794
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>    Affects Versions: Release Branch 11.04, SVN trunk, Release Branch 12.04, 
> Release Branch 13.07
>            Reporter: Pierre Smits
>            Assignee: Jacques Le Roux
>             Fix For: SVN trunk
>
>         Attachments: OFBIZ-4794 - test port - R11.04.patch, OFBIZ-4794 - test 
> port - R12.04.patch, OFBIZ-4794 - test port - R13.07.patch, OFBIZ-4794 - test 
> port - trunk.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In order to run test targets in Jenkins we need to change ports for at least 
> ajp, http and https in test-containers.xml as these ports are most likely to 
> be already in use by the CI server.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to