You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Didier Gutacker (JIRA)" <ji...@apache.org> on 2009/09/14 17:44:57 UTC
[jira] Created: (CXF-2437) Host not set CXFJettySslSocketConnector
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
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.
[jira] Updated: (CXF-2437) Host not set CXFJettySslSocketConnector
Posted by "Brent Verner (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (CXF-2437) Host not set CXFJettySslSocketConnector
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2437.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.5
2.1.8
Applied patch with modifications. Thanks!
Basically, I left the method on the interface that just takes the port for compatibility sake. For the impls, just forwarded that into the new method with "null" for host.
> 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
> Assignee: Daniel Kulp
> Fix For: 2.1.8, 2.2.5
>
> 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.
[jira] Assigned: (CXF-2437) Host not set CXFJettySslSocketConnector
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-2437:
--------------------------------
Assignee: Daniel Kulp
> 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
> Assignee: Daniel Kulp
> 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.
[jira] Updated: (CXF-2437) Host not set CXFJettySslSocketConnector
Posted by "Brent Verner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brent Verner updated CXF-2437:
------------------------------
Attachment: cxf-jetty-host-support.diff
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.
[jira] Commented: (CXF-2437) Host not set
CXFJettySslSocketConnector
Posted by "Didier Gutacker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757859#action_12757859 ]
Didier Gutacker commented on CXF-2437:
--------------------------------------
I missed to attach cxf.xml contents:
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:http="http://cxf.apache.org/transports/http/configuration"
xmlns:httpj="http://cxf.apache.org/transports/http-jetty/configuration"
xmlns:sec="http://cxf.apache.org/configuration/security"
xsi:schemaLocation="
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/transports/http-jetty/configuration http://cxf.apache.org/schemas/configuration/http-jetty.xsd
http://cxf.apache.org/configuration/security http://cxf.apache.org/schemas/configuration/security.xsd">
<http:destination name="{http://www.server.com/abc}ABC_Port.http-destination" />
<httpj:engine-factory bus="cxf">
<httpj:engine port="8443">
<httpj:tlsServerParameters>
<sec:keyManagers keyPassword="pwd">
<sec:keyStore file="${activemq-home}/conf/server-keystore.jks" password="pwd" type="JKS" />
</sec:keyManagers>
<sec:trustManagers>
<sec:keyStore file="${activemq-home}/conf/trust-keystore.jks" password="pwd" type="JKS"/>
</sec:trustManagers>
<sec:clientAuthentication required="true" want="true"/>
</httpj:tlsServerParameters>
</httpj:engine>
</httpj:engine-factory>
</beans>
> 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
>
> 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.
[jira] Commented: (CXF-2437) Host not set
CXFJettySslSocketConnector
Posted by "Brent Verner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765856#action_12765856 ]
Brent Verner commented on CXF-2437:
-----------------------------------
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.