camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6161) blueprint-cxf-test - Should use dynamic port number
Date Wed, 20 Mar 2013 16:17:15 GMT

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

Aki Yoshida updated CAMEL-6161:
-------------------------------

    Attachment: tests-camel-blueprint-cxf-test-20130320.diff

Hi Willem,
as discussed, here is the svn diff on camel/trunk. I think this is the test that is causing
this port collision issue.
regards, aki
                
> blueprint-cxf-test - Should use dynamic port number
> ---------------------------------------------------
>
>                 Key: CAMEL-6161
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6161
>             Project: Camel
>          Issue Type: Test
>          Components: tests
>    Affects Versions: 2.11.0
>            Reporter: Claus Ibsen
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 2.11.0
>
>         Attachments: tests-camel-blueprint-cxf-test-20130320.diff
>
>
> The tests/blueprint-cxf-test uses hardcoded port numbers for its unit tests. This can
cause "connection refused" errors during testing.
> We should use dynamic ports like we have done in almost all other places.

--
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

Mime
View raw message