You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by oshafi <om...@shafi.org> on 2012/02/14 22:25:39 UTC
Conduit Error on CXF 2.1.4
Hello, I have a service set up that uses a conduit for SSL. This was working
fine with both applications running locally on my development enviornment
but when I moved to test enviornment with both applications running on
separate machines i get the following error
Caused by: java.lang.NullPointerException
at
org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactory.java:228)
at
org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:81)
at
org.apache.cxf.endpoint.UpfrontConduitSelector.prepare(UpfrontConduitSelector.java:61)
at
org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector(ClientImpl.java:809)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:505)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:440)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:295)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 36 more
The following is my conduit. The name has the target URL in it.
<http-conf:conduit name="https://10.101.255.135/.*">
<http-conf:tlsClientParameters secureSocketProtocol="SSL"
disableCNCheck="true">
<sec:keyManagers keyPassword="password">
<sec:keyStore type="JKS" password="${ws.keystorePassword}"
file="${ws.keystoreLocation}" />
</sec:keyManagers>
<sec:trustManagers>
<sec:keyStore type="JKS" password="${ws.truststorePassword}"
file="${ws.truststoreLocation}" />
</sec:trustManagers>
<sec:cipherSuitesFilter>
<sec:include>.*_EXPORT_.*</sec:include>
<sec:include>.*_EXPORT1024_.*</sec:include>
<sec:include>.*_WITH_DES_.*</sec:include>
<sec:include>.*_WITH_NULL_.*</sec:include>
<sec:exclude>.*_DH_anon_.*</sec:exclude>
</sec:cipherSuitesFilter>
</http-conf:tlsClientParameters>
</http-conf:conduit>
Any ideas?
--
View this message in context: http://cxf.547215.n5.nabble.com/Conduit-Error-on-CXF-2-1-4-tp5483971p5483971.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Conduit Error on CXF 2.1.4
Posted by Daniel Kulp <dk...@apache.org>.
This stack trace shows that the server is sending back a fault of some sort.
You may need to check the server side to see what is happening there.
Dan
On Tuesday, February 14, 2012 2:38:34 PM oshafi wrote:
> I changed the conduit name to look like this
> <http-conf:conduit name="*.http-conduit">
>
>
> and now I get the following error
>
> Caused by: org.apache.cxf.binding.soap.SoapFault: Fault occurred while
> processing.
> at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFa
> ult(Soap11FaultInInterceptor.java:75) at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessa
> ge(Soap11FaultInInterceptor.java:46) at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessa
> ge(Soap11FaultInInterceptor.java:35) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain
> .java:263) at
> org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(Abs
> tractFaultChainInitiatorObserver.java:104) at
> org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(
> CheckFaultInterceptor.java:69) at
> org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(
> CheckFaultInterceptor.java:34) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain
> .java:263) at
> org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:762) at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse
> Internal(HTTPConduit.java:1582) at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse
> (HTTPConduit.java:1467) at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPCond
> uit.java:1375) at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) at
> org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:623) at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInter
> ceptor.handleMessage(MessageSenderInterceptor.java:62) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain
> .java:263) at
> org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:510) at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:440) at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343) at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:295) at
> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124) ...
> 36 more
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Conduit-Error-on-CXF-2-4-1-tp5483971p548417
> 7.html Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
RE: Conduit Error on CXF 2.1.4
Posted by oshafi <om...@shafi.org>.
I changed the conduit name to look like this
<http-conf:conduit name="*.http-conduit">
and now I get the following error
Caused by: org.apache.cxf.binding.soap.SoapFault: Fault occurred while
processing.
at
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:75)
at
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:46)
at
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:104)
at
org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
at
org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:762)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1582)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1467)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1375)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:623)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:510)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:440)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:295)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 36 more
--
View this message in context: http://cxf.547215.n5.nabble.com/Conduit-Error-on-CXF-2-4-1-tp5483971p5484177.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: Conduit Error on CXF 2.1.4
Posted by oshafi <om...@shafi.org>.
In the wiki they have this listed
Another option for the name attribute is a reg-ex expression for the
ORIGINAL URL of the endpoint. The configuration is matched at conduit
creation so the address used in the WSDL or used for the JAX-WS
Service.create(...) call can be used for the name. For example, you can do:
<http:conduit name="http://localhost:8080/.*">
......
</http:conduit>
so If my client is set up as follows:
<jaxws:client
id="dataCallScheduleService"
serviceClass="com.test.stars.ws.DataCallScheduleService"
address="https://1.1.255.135/starst/s/dataCallSchedule">
</jaxws:client>
Should my conduit not be set up as follows: <http:conduit
name=https://1.1.255.135/.*">
--
View this message in context: http://cxf.547215.n5.nabble.com/Conduit-Error-on-CXF-2-4-1-tp5483971p5484106.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: Conduit Error on CXF 2.1.4
Posted by Omar Atia <om...@its.ws>.
Dear omer,
Well the target URL shouldn't be on http conduit , Please check below example :
<http:conduit name="{pcrf:soap}ScfPccSoapServiceEndpointPort.http-conduit"> (Name space and port binding from WSDL).
<http:tlsClientParameters disableCNCheck="true">
<sec:trustManagers>
<sec:keyStore type="JKS" password="123456"
file="/test1/appl/ocs/OCS-PCRF/OCS-router/src/main/resources/certs/UPCC_client.store"></sec:keyStore>
</sec:trustManagers>
<sec:keyManagers keyPassword="123456">
<sec:keyStore type="JKS" password="123456"
file="/test1/appl/ocs/OCS-PCRF/OCS-router/src/main/resources/certs/UPCC_client.store"/>
</sec:keyManagers>
<sec:cipherSuitesFilter>
<sec:include>.*_EXPORT_.*</sec:include>
<sec:include>.*_EXPORT1024_.*</sec:include>
<sec:include>.*_WITH_DES_.*</sec:include>
<sec:include>.*_WITH_NULL_.*</sec:include>
<sec:exclude>.*_DH_anon_.*</sec:exclude>
</sec:cipherSuitesFilter>
</http:tlsClientParameters>
</http:conduit>
And the main URL will be in the following :
<cxf:cxfEndpoint
address="https://10.87.87.8:8080/axis/services/ScfPccSoapServiceEndpointPort"
id="Masterpcrf" serviceClass="pcrf.soap.ScfPccSoapServiceEndpoint"
wsdlURL="etc/UPCCProvisionsing.wsdl">
<cxf:inInterceptors>
<ref bean="logginginInterceptor"/>
</cxf:inInterceptors >
<cxf:outInterceptors>
<ref bean="loggingOutInterceptor"/>
</cxf:outInterceptors>
<!-- address="https://10.100.184.193:8080/axis/services/ScfPccSoapServiceEndpointPort"-->
</cxf:cxfEndpoint>
Thanks,
Omar Atia
-----Original Message-----
From: oshafi [mailto:omer@shafi.org]
Sent: Tuesday, February 14, 2012 11:26 PM
To: users@cxf.apache.org
Subject: Conduit Error on CXF 2.1.4
Hello, I have a service set up that uses a conduit for SSL. This was working
fine with both applications running locally on my development enviornment
but when I moved to test enviornment with both applications running on
separate machines i get the following error
Caused by: java.lang.NullPointerException
at
org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactory.java:228)
at
org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:81)
at
org.apache.cxf.endpoint.UpfrontConduitSelector.prepare(UpfrontConduitSelector.java:61)
at
org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector(ClientImpl.java:809)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:505)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:440)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:295)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 36 more
The following is my conduit. The name has the target URL in it.
<http-conf:conduit name="https://10.101.255.135/.*">
<http-conf:tlsClientParameters secureSocketProtocol="SSL"
disableCNCheck="true">
<sec:keyManagers keyPassword="password">
<sec:keyStore type="JKS" password="${ws.keystorePassword}"
file="${ws.keystoreLocation}" />
</sec:keyManagers>
<sec:trustManagers>
<sec:keyStore type="JKS" password="${ws.truststorePassword}"
file="${ws.truststoreLocation}" />
</sec:trustManagers>
<sec:cipherSuitesFilter>
<sec:include>.*_EXPORT_.*</sec:include>
<sec:include>.*_EXPORT1024_.*</sec:include>
<sec:include>.*_WITH_DES_.*</sec:include>
<sec:include>.*_WITH_NULL_.*</sec:include>
<sec:exclude>.*_DH_anon_.*</sec:exclude>
</sec:cipherSuitesFilter>
</http-conf:tlsClientParameters>
</http-conf:conduit>
Any ideas?
--
View this message in context: http://cxf.547215.n5.nabble.com/Conduit-Error-on-CXF-2-1-4-tp5483971p5483971.html
Sent from the cxf-user mailing list archive at Nabble.com.