[
https://issues.apache.org/jira/browse/CXF-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brent Verner updated CXF-2437:
------------------------------
Comment: was deleted
(was: Patch to add support for host attribute on jetty engine....If host is not
supplied, the previous behaviour is retained (listen on all local addresses).
<httpj:engine host="10.0.20.10" port="19001">
<httpj:tlsServerParametersRef id="secure" />
<httpj:sessionSupport>true</httpj:sessionSupport>
</httpj:engine>
This patch is against 2.2.3, but it applies cleanly to 2.2.4. I've only tested
in the context of my very limited use of cxf...
)
> Host not set CXFJettySslSocketConnector
> ---------------------------------------
>
> Key: CXF-2437
> URL: https://issues.apache.org/jira/browse/CXF-2437
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.2.2
> Environment: Suse Linux, ActiveMQ 5.2, Camel 2.0-M3
> Reporter: Didier Gutacker
> Attachments: cxf-jetty-host-support.diff
>
>
> Host is not set on
> org.apache.cxf.transport.https_jetty.JettySslConnectorFactory so
> org.mortbay.jetty.bio.SocketConnector tries to use all available ip
> addresses. This causes problems on multi-homed systems. In our environment
> ip2:8443 is used by our JBoss server. We want to run a CXF-Endpoint within
> activemq 5.2 (camel-cxf-2.0-M3) on ip1:8443. The result is:
> "java.net.BindException: Address already in use".
> Config sample:
> <cxf:cxfEndpoint id="cxfEndpoint"
> serviceClass="xxxxx"
> wsdlURL="abc.wsdl"
> serviceName="abc:ABC"
> endpointName="abc:ABC_Port"
> address="https://server:8443/abc/service";>
> </cxf:cxfEndpoint>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
