[jira] [Created] (CXF-6777) javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
Sebastian Krupa created CXF-6777:
Summary: javax.net.ssl.SSLKeyException: Hostname verification
failed on WLS 12.2.1
Key: CXF-6777
URL: https://issues.apache.org/jira/browse/CXF-6777
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Reporter: Sebastian Krupa
Could you help me - i have problem with Weblogic 12.2.1 when CXF 3.1.4 dynamic
client tries to invoke SSL based web services.
I have already reported it to Oracle support - but they said that it is CXF
problem not Weblogic, so here I am :) to ask you about it.
I'm putting here reported issue(number in my oracle support SR 3-11832157061),
note *2029567.1* is error that has same exception like mine by it has been
fixed(Oracle says so) in WLS 12.1.3
{panel:title=Fragments from Oracle support
page|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
{color:red}We encountered a problem that is described in this note *2029567.1*
in one of our application that will be launched on WLS 12.2.1. This error ocurs
when dynamic Apache CXF client is invoked. Exception is like follows:{color}
<2015-12-07 11:55:09 CET>
<2015-12-07 11:55:09 CET>
<2015-12-07 11:55:09 CET><[Thread[[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled
Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: No trust failure,
validateErr=0.>
<2015-12-07 11:55:09 CET>
<2015-12-07 11:55:09 CET>
<2015-12-07 11:55:09 CET>
<2015-12-07 11:55:09 CET><[Thread[[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled
Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: Exception occurred
during SSLEngine.wrap(ByteBuffer,ByteBuffer).
javax.net.ssl.SSLKeyException: Hostname verification failed:
HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
hostname=test.osb.ibis.vip.
at
weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
{color:red}Excpetion from admin server log:{color}
==AdminServer.log===
<2015-12-07 11:55:09 CET>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
(self-tuning)'> <> <>
<1449485709084>
<[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
<[Thread[[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)',5,Pooled
Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: Exception occurred
during SSLEngine.unwrap(ByteBuffer,ByteBuffer[]).
javax.net.ssl.SSLKeyException: Hostname verification failed:
HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
hostname=test.osb.ibis.vip.
at
weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
at weblogic.security.SSL.jsseadapter.JaSSLEngine.doAction(JaSSLEngine.java:748)
at weblogic.security.SSL.jsseadapter.JaSSLEngine.unwrap(JaSSLEngine.java:132)
at weblogic.socket.JSSEFilterImpl.unwrap(JSSEFilterImpl.java:611)
at
weblogic.socket.JSSEFilterImpl.unwrapAndHandleResults(JSSEFilterImpl.java:515)
at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:98)
at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:77)
at weblogic.socket.JSSESocket.startHandshake(JSSESocket.java:240)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:574)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:545)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:230)
at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:685)
at
weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:41)
at org.apache.cxf.resource.URIResolver.tryFileSystem(URIResolver.java:184)
at org.apache.cxf.resource.URIResolver.resolve(URIResolver.java:120)
at
org.apache.cxf.resource.ExtendedURIResolver.resolve(ExtendedURIResolver.java:41)
at
org.apache.cxf.transport.TransportURIResolver.resolve(TransportURIResolver.java:150)
at
org.apache.cxf.wsdl11.CatalogWSDLLocator.getBaseInputSource(CatalogWSDLLocator.java:74)
at
org.apache.cxf.wsdl11.AbstractWrapperWSDLLocator.getBaseInputSource(AbstractWrapperWSDLLocator.java:57)
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:324)
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:315)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:74)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:296)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:241)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:234)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createC
[jira] [Updated] (CXF-6777) javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
[
https://issues.apache.org/jira/browse/CXF-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Krupa updated CXF-6777:
-
Attachment: SR Oracle.zip
Full conversation on MOS about this issue
> javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
> --
>
> Key: CXF-6777
> URL: https://issues.apache.org/jira/browse/CXF-6777
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Reporter: Sebastian Krupa
> Attachments: SR Oracle.zip
>
>
> Could you help me - i have problem with Weblogic 12.2.1 when CXF 3.1.4
> dynamic client tries to invoke SSL based web services.
> I have already reported it to Oracle support - but they said that it is CXF
> problem not Weblogic, so here I am :) to ask you about it.
> I'm putting here reported issue(number in my oracle support SR
> 3-11832157061), note *2029567.1* is error that has same exception like mine
> by it has been fixed(Oracle says so) in WLS 12.1.3
> {panel:title=Fragments from Oracle support
> page|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
> {color:red}We encountered a problem that is described in this note
> *2029567.1* in one of our application that will be launched on WLS 12.2.1.
> This error ocurs when dynamic Apache CXF client is invoked. Exception is like
> follows:{color}
> <2015-12-07 11:55:09 CET> specified trustmanager validation status 0>
> <2015-12-07 11:55:09 CET>
>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: No trust failure, validateErr=0.>
> <2015-12-07 11:55:09 CET> hostname validation checks: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> chain received from test.osb.ibis.vip - 172.16.200.115 failed hostname
> verification check. Certificate contained test.osb.ibis.vip but check
> expected test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> Verification failed for certificate with CommonName 'test.osb.ibis.vip'
> against hostname: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: Exception occurred during SSLEngine.wrap(ByteBuffer,ByteBuffer).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
>
> {color:red}Excpetion from admin server log:{color}
> ==AdminServer.log===
> <2015-12-07 11:55:09 CET>
> <[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)'> <> <>
> <1449485709084>
> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)',5,Pooled
> Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: Exception occurred
> during SSLEngine.unwrap(ByteBuffer,ByteBuffer[]).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doAction(JaSSLEngine.java:748)
> at weblogic.security.SSL.jsseadapter.JaSSLEngine.unwrap(JaSSLEngine.java:132)
> at weblogic.socket.JSSEFilterImpl.unwrap(JSSEFilterImpl.java:611)
> at
> weblogic.socket.JSSEFilterImpl.unwrapAndHandleResults(JSSEFilterImpl.java:515)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:98)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:77)
> at weblogic.socket.JSSESocket.startHandshake(JSSESocket.java:240)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:574)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:545)
> at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:230)
> at
> weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:685)
> at
> weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:41)
> at org.apache.cxf.resource.URIResolver.tryFileSystem(URIResolver.java:184)
> at org.apache.cxf.resource.URIResolver.resolve(URIResolver.java:120)
> at
> org.apache.cxf.resource.ExtendedURIResolver.resolve(ExtendedURIResolver.java:41)
> at
> org.apache.cxf.transport.TransportURIResolver.resolve(TransportURIResolver.java:150)
> at
> org.apache.cxf.wsdl11.CatalogWSDLLocator.getBaseInputSource(CatalogWSDLLocator.java:74)
> at
> org.apache.cxf.wsdl11.AbstractWra
[jira] [Comment Edited] (CXF-6777) javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
[
https://issues.apache.org/jira/browse/CXF-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148373#comment-15148373
]
Sebastian Krupa edited comment on CXF-6777 at 2/16/16 9:56 AM:
---
Full conversation on MOS about this issue (in SR Oracle.zip)
was (Author: h3x0r):
Full conversation on MOS about this issue
> javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
> --
>
> Key: CXF-6777
> URL: https://issues.apache.org/jira/browse/CXF-6777
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Reporter: Sebastian Krupa
> Attachments: SR Oracle.zip
>
>
> Could you help me - i have problem with Weblogic 12.2.1 when CXF 3.1.4
> dynamic client tries to invoke SSL based web services.
> I have already reported it to Oracle support - but they said that it is CXF
> problem not Weblogic, so here I am :) to ask you about it.
> I'm putting here reported issue(number in my oracle support SR
> 3-11832157061), note *2029567.1* is error that has same exception like mine
> by it has been fixed(Oracle says so) in WLS 12.1.3
> {panel:title=Fragments from Oracle support
> page|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
> {color:red}We encountered a problem that is described in this note
> *2029567.1* in one of our application that will be launched on WLS 12.2.1.
> This error ocurs when dynamic Apache CXF client is invoked. Exception is like
> follows:{color}
> <2015-12-07 11:55:09 CET> specified trustmanager validation status 0>
> <2015-12-07 11:55:09 CET>
>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: No trust failure, validateErr=0.>
> <2015-12-07 11:55:09 CET> hostname validation checks: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> chain received from test.osb.ibis.vip - 172.16.200.115 failed hostname
> verification check. Certificate contained test.osb.ibis.vip but check
> expected test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> Verification failed for certificate with CommonName 'test.osb.ibis.vip'
> against hostname: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: Exception occurred during SSLEngine.wrap(ByteBuffer,ByteBuffer).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
>
> {color:red}Excpetion from admin server log:{color}
> ==AdminServer.log===
> <2015-12-07 11:55:09 CET>
> <[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)'> <> <>
> <1449485709084>
> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)',5,Pooled
> Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: Exception occurred
> during SSLEngine.unwrap(ByteBuffer,ByteBuffer[]).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doAction(JaSSLEngine.java:748)
> at weblogic.security.SSL.jsseadapter.JaSSLEngine.unwrap(JaSSLEngine.java:132)
> at weblogic.socket.JSSEFilterImpl.unwrap(JSSEFilterImpl.java:611)
> at
> weblogic.socket.JSSEFilterImpl.unwrapAndHandleResults(JSSEFilterImpl.java:515)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:98)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:77)
> at weblogic.socket.JSSESocket.startHandshake(JSSESocket.java:240)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:574)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:545)
> at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:230)
> at
> weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:685)
> at
> weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:41)
> at org.apache.cxf.resource.URIResolver.tryFileSystem(URIResolver.java:184)
> at org.apache.cxf.resource.URIResolver.resolve(URIResolver.java:120)
> at
> org.apache.cxf.resource.ExtendedURIResolver.resolve(ExtendedURIResolver.java:41)
> at
> org.apache.cxf.transport.TransportURIResolver.resolve(Transpor
[jira] [Created] (CXF-6778) Invalid replyDestination is cached after jms connection has been reset
Jerome Waibel created CXF-6778:
--
Summary: Invalid replyDestination is cached after jms connection
has been reset
Key: CXF-6778
URL: https://issues.apache.org/jira/browse/CXF-6778
Project: CXF
Issue Type: Bug
Components: JMS, Transports
Affects Versions: 3.0.8, 3.1.5
Reporter: Jerome Waibel
Priority: Critical
We have a spring boot application that is doing SOAP over JMS with a tibco
backend.
Whenever the JMS connection is reset our application fails to receive the
answer for the SOA request until the application server is restarted.
>From the logs we see that re-establishing the jms connection is working fine:
{quote}
2016-02-05 12:59:03.458 WARN 5662 --- [TIBCO EMS TCPLink Reader
(Server-608470)] o.s.j.c.CachingConnectionFactory : Encountered a
JMSException - resetting the underlying JMS Connection
javax.jms.JMSException: Connection has been terminated
at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:509)
at
com.tibco.tibjms.TibjmsConnection._invokeOnExceptionCallback(TibjmsConnection.java:2025)
at
com.tibco.tibjms.TibjmsConnection._onDisconnected(TibjmsConnection.java:2394)
at
com.tibco.tibjms.TibjmsConnection$ServerLinkEventHandler.onEventDisconnected(TibjmsConnection.java:349)
at
com.tibco.tibjms.TibjmsxLinkTcp$LinkReader.work(TibjmsxLinkTcp.java:330)
at
com.tibco.tibjms.TibjmsxLinkTcp$LinkReader.run(TibjmsxLinkTcp.java:259)
2016-02-05 12:59:04.701 INFO 5662 --- [ajp-bio-18009-exec-1]
o.s.j.c.CachingConnectionFactory: Established shared JMS Connection:
QueueConnection[ClientId=null Connected=tcp://ems2-k:12004,
URL=tcp://ems2-k:12004]
{quote}
After the connection has been reset when our application does the next SOAP
call sending the request works fine, but when CXF waits for the reply the
following exception occurs:
{quote}
javax.xml.ws.soap.SOAPFaultException: Timeout receiving message with
correlationId b02ad4683421442db439b54797fcc7350003
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161)
{quote}
Debugging shows that the problem seems to be located in _public Destination
getReplyDestination(Session session) in
org.apache.cxf.transport.jms.JMSConfiguration_. There a Destination object for
receiving the answer is created once and cached forever. There is no way this
cached destination will ever be dropped and recreated. This destination object
(implemented by a temporary queue in our case) contains a reference to the jms
connection. So after a reset of the connection it still contains the old,
invalid jms connection object. This is why after a connection reset it is
impossible to receive any more replies.
Using a debugger, setting a breakpoint in this method and manually setting
replyDestinationDest to null forces this method to recreate the temporary
queue. After that receiving replies is working again after a jms connection
reset. This is of course not possible for our live environment, there all
servers have to be restarted after a jms connection reset.
This behaviour was introduced in CXF3. Before upgrading we used CXF 2 where the
temporary response queue seems not to be cached but created and deleted for
every request. With CXF 2 our application worked fine when the jms connection
was reset.
Steps for reproducing this error (sorry, no example project yet):
* Have a SOAP server
* Have a SOAP client using Spring so that CachingConnectionFactory will do a
proper connection reset
* Have a SOAP over JMS broker
* Make one successful client request so that the replyDestinationDest gets
created and cached.
* Force a JMS connection reset (e.g. drop connection from the broker admin
console)
* Try another client request. The client will reconnect but re-use the old
replyDestinationDest and never be able to receive the reply again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CXF-5965) Improve Wadl to Java Tests
[ https://issues.apache.org/jira/browse/CXF-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-5965. --- Resolution: Duplicate > Improve Wadl to Java Tests > -- > > Key: CXF-5965 > URL: https://issues.apache.org/jira/browse/CXF-5965 > Project: CXF > Issue Type: Test > Components: JAX-RS, Tooling >Reporter: Sergey Beryozkin > > JAXRSContainerTest is very light, it only checks that the expected number of > the generated files have been compiled. As such it is easy to introduce > regressions. WSDL to Java tooling tests are good, they can be used as the > examples of how the tests should be done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6362) CXF and BigData platform integration
[ https://issues.apache.org/jira/browse/CXF-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin updated CXF-6362: -- Fix Version/s: (was: NeedMoreInfo) 3.2.0 Perhaps something around micro-containers, etc ? > CXF and BigData platform integration > > > Key: CXF-6362 > URL: https://issues.apache.org/jira/browse/CXF-6362 > Project: CXF > Issue Type: New Feature > Components: Integration >Reporter: Sergey Beryozkin > Fix For: 3.2.0 > > > CXF should be able to run in a native mode on top of the leading BigData > platforms. > Typical use case: > CXF serves as a frontend which accepts the data that are pushed into a > BigData runtime. CXF streams back the result data (via WebSockets, HTTP/2, > even plain HTTP, other transports). > Right now CXF and Big Data runtimes will run in its own processes/containers. > For example, CXF offers an HBase search extension. The CXF server will create > an HBase query and use a remote HBase client to fetch some data - this is > sub-optimal. > Not clear yet how to address such an integration or what platform to start > with, Spark or Hadoop. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-6618) Create JAXRS Spark Streaming demo
[ https://issues.apache.org/jira/browse/CXF-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned CXF-6618: - Assignee: Sergey Beryozkin This is a work in progress > Create JAXRS Spark Streaming demo > -- > > Key: CXF-6618 > URL: https://issues.apache.org/jira/browse/CXF-6618 > Project: CXF > Issue Type: Task > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-5855) Introduce support for Server Sent Events
[ https://issues.apache.org/jira/browse/CXF-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned CXF-5855: - Assignee: Andriy Redko Hi Andriy - only FYI that this issue already exists, addressing it sometime in 2016 will do :-) > Introduce support for Server Sent Events > > > Key: CXF-5855 > URL: https://issues.apache.org/jira/browse/CXF-5855 > Project: CXF > Issue Type: New Feature > Components: Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > > We now have a good WebSocket transport support. It would be good to get > Server Sent Events (SSE) supported on top of it, I believe Atmosphere does > support SSE. > SSE has been voted as one of the most interesting technologies in EE 8 plans > and support for it will very likely be required in JAX-RS. Jersey leads the > way with its SSE support already -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-5756) Investigate the possibility of supporting JOLT for JSON to JSON conversions
[ https://issues.apache.org/jira/browse/CXF-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-5756. --- Resolution: Later > Investigate the possibility of supporting JOLT for JSON to JSON conversions > --- > > Key: CXF-5756 > URL: https://issues.apache.org/jira/browse/CXF-5756 > Project: CXF > Issue Type: New Feature > Components: JAX-RS >Reporter: Sergey Beryozkin >Priority: Minor > > JOLT (https://github.com/bazaarvoice/jolt) seems to be a pretty interesting > project. > Perhaps we can have a JAX-RS request and response filter using JOLT as an > alternative to CXF JSONProvider specific transformation support for the > purpose of supporting the backward/forward compatibility at JSON level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6349) Introduce HTTP/2 Transport
[ https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin updated CXF-6349: -- Fix Version/s: (was: NeedMoreInfo) 3.2.0 > Introduce HTTP/2 Transport > --- > > Key: CXF-6349 > URL: https://issues.apache.org/jira/browse/CXF-6349 > Project: CXF > Issue Type: New Feature > Components: Transports >Reporter: Sergey Beryozkin > Fix For: 3.2.0 > > > https://http2.github.io/ > Can be complementary to what Aki has done with WebSockets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6349) Introduce HTTP/2 Transport
[ https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148530#comment-15148530 ] Sergey Beryozkin commented on CXF-6349: --- Only making a version more specific > Introduce HTTP/2 Transport > --- > > Key: CXF-6349 > URL: https://issues.apache.org/jira/browse/CXF-6349 > Project: CXF > Issue Type: New Feature > Components: Transports >Reporter: Sergey Beryozkin > Fix For: 3.2.0 > > > https://http2.github.io/ > Can be complementary to what Aki has done with WebSockets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6526) Support JSR 371 (MVC) spec
[ https://issues.apache.org/jira/browse/CXF-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin updated CXF-6526: -- Fix Version/s: (was: NeedMoreInfo) 3.2.0 > Support JSR 371 (MVC) spec > -- > > Key: CXF-6526 > URL: https://issues.apache.org/jira/browse/CXF-6526 > Project: CXF > Issue Type: New Feature >Reporter: Sergey Beryozkin > Fix For: 3.2.0 > > > https://www.jcp.org/en/jsr/detail?id=371 > Its API needs to be checked if it can be loaded with Java 7, if yes the work > can start in 3.1.x, otherwise in a Java 8 trunk. > It will have to be based around CXFCdiServlet as it is strictly CDI bound -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6775) java2wadl - annotation javax.ws.rs.ApplicationPath
[ https://issues.apache.org/jira/browse/CXF-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148549#comment-15148549 ] Lanceleur commented on CXF-6775: The solution with the "address" property works. Thanks! > java2wadl - annotation javax.ws.rs.ApplicationPath > -- > > Key: CXF-6775 > URL: https://issues.apache.org/jira/browse/CXF-6775 > Project: CXF > Issue Type: Task >Reporter: Lanceleur >Assignee: Sergey Beryozkin > > Is it possible to get application path information in the generated wadl ? > Cheers, > Jérémie. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6779) Swagger Feature should become discoverable
Sergey Beryozkin created CXF-6779: - Summary: Swagger Feature should become discoverable Key: CXF-6779 URL: https://issues.apache.org/jira/browse/CXF-6779 Project: CXF Issue Type: Improvement Components: JAX-RS Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Fix For: 3.2.0, 3.1.6 We have an interest in this feature becoming easier to set up in a Spring Boot context -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6780) Exception raied when invoking setter public final void org.apache.cxf.wsdl11.WSDLManagerImpl.setBus(org.apache.cxf.Bus)
fareeha naz created CXF-6780: Summary: Exception raied when invoking setter public final void org.apache.cxf.wsdl11.WSDLManagerImpl.setBus(org.apache.cxf.Bus) Key: CXF-6780 URL: https://issues.apache.org/jira/browse/CXF-6780 Project: CXF Issue Type: Bug Environment: Eclipse marse and weblogic 12.1.3 Reporter: fareeha naz Feb 16, 2016 6:40:12 PM org.apache.cxf.common.injection.ResourceInjector invokeSetter SEVERE: exception raied when invoking setter public final void org.apache.cxf.wsdl11.WSDLManagerImpl.setBus(org.apache.cxf.Bus) java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.cxf.common.injection.ResourceInjector.invokeSetter(ResourceInjector.java:287) at org.apache.cxf.common.injection.ResourceInjector.visitMethod(ResourceInjector.java:232) at org.apache.cxf.common.annotation.AnnotationProcessor.processMethods(AnnotationProcessor.java:89) at org.apache.cxf.common.annotation.AnnotationProcessor.accept(AnnotationProcessor.java:72) at org.apache.cxf.common.injection.ResourceInjector.inject(ResourceInjector.java:118) at org.apache.cxf.common.injection.ResourceInjector.inject(ResourceInjector.java:112) at org.apache.cxf.bus.extension.ExtensionManagerImpl.loadAndRegister(ExtensionManagerImpl.java:242) at org.apache.cxf.bus.extension.ExtensionManagerImpl.getBeanOfType(ExtensionManagerImpl.java:320) at org.apache.cxf.bus.spring.SpringBeanLocator.getBeanOfType(SpringBeanLocator.java:128) at org.apache.cxf.bus.extension.ExtensionManagerBus.getExtension(ExtensionManagerBus.java:215) at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:170) at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161) at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129) at org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82) at javax.xml.ws.Service.(Service.java:92) at com.ses.webservice.secureimap.client.cxfgen.SecureIntegrationServicesImap.(SecureIntegrationServicesImap.java:44) at com.secureexchangesolutions._2012.secureintegrationserviceimap.v1.SecureIntegrationServiceImap_WSHttpBindingSecureIntegrationServiceImap_Client.sendMessage(SecureIntegrationServiceImap_WSHttpBindingSecureIntegrationServiceImap_Client.java:64) at com.adamsoft.edoc.beans.em.pChart.PatientChartBean.(PatientChartBean.java:97) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.lang.Class.newInstance(Class.java:442) at com.sun.faces.mgbean.BeanBuilder.newBeanInstance(BeanBuilder.java:185) at com.sun.faces.mgbean.BeanBuilder.build(BeanBuilder.java:105) at com.sun.faces.mgbean.BeanManager.createAndPush(BeanManager.java:368) at com.sun.faces.mgbean.BeanManager.create(BeanManager.java:222) at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:86) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:188) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:188) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:188) at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:103) at com.sun.el.parser.AstValue.getValue(AstValue.java:179) at com.sun.el.parser.AstEqual.getValue(AstEqual.java:58) at com.sun.el.parser.AstOr.getValue(AstOr.java:58) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224) at weblogic.servlet.jsp.ELHelper.evaluate(ELHelper.java:32) at jsp_servlet._pages._em._pchart.__patientchart._jsp__tag21(__patientchart.java:2251) at jsp_servlet._pages._em._pchart.__patientchart._jsp__tag0(__patientchart.java:1398) at jsp_servlet._pages._em._pchart.__patientchart._jspService(__patientchart.java:1275) at weblogic.servlet.jsp.JspBase.service(JspBase.java:35) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280) at weblogic.servlet.internal.StubSecurityHelper$ServletSer
[jira] [Commented] (CXF-6777) javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
[
https://issues.apache.org/jira/browse/CXF-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148626#comment-15148626
]
Colm O hEigeartaigh commented on CXF-6777:
--
The Weblogic HostnameVerifier is failing, so I think this is nothing to do with
CXF:
<2015-12-07 11:55:09 CET>
...
HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
hostname=test.osb.ibis.vip.
What I suggest is writing a simple Java SSL test to connect to your web service
endpoint to try to reproduce the error. Maybe there is some problem with the
certificate in question.
Colm.
> javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
> --
>
> Key: CXF-6777
> URL: https://issues.apache.org/jira/browse/CXF-6777
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Reporter: Sebastian Krupa
> Attachments: SR Oracle.zip
>
>
> Could you help me - i have problem with Weblogic 12.2.1 when CXF 3.1.4
> dynamic client tries to invoke SSL based web services.
> I have already reported it to Oracle support - but they said that it is CXF
> problem not Weblogic, so here I am :) to ask you about it.
> I'm putting here reported issue(number in my oracle support SR
> 3-11832157061), note *2029567.1* is error that has same exception like mine
> by it has been fixed(Oracle says so) in WLS 12.1.3
> {panel:title=Fragments from Oracle support
> page|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
> {color:red}We encountered a problem that is described in this note
> *2029567.1* in one of our application that will be launched on WLS 12.2.1.
> This error ocurs when dynamic Apache CXF client is invoked. Exception is like
> follows:{color}
> <2015-12-07 11:55:09 CET> specified trustmanager validation status 0>
> <2015-12-07 11:55:09 CET>
>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: No trust failure, validateErr=0.>
> <2015-12-07 11:55:09 CET> hostname validation checks: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> chain received from test.osb.ibis.vip - 172.16.200.115 failed hostname
> verification check. Certificate contained test.osb.ibis.vip but check
> expected test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> Verification failed for certificate with CommonName 'test.osb.ibis.vip'
> against hostname: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: Exception occurred during SSLEngine.wrap(ByteBuffer,ByteBuffer).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
>
> {color:red}Excpetion from admin server log:{color}
> ==AdminServer.log===
> <2015-12-07 11:55:09 CET>
> <[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)'> <> <>
> <1449485709084>
> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)',5,Pooled
> Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: Exception occurred
> during SSLEngine.unwrap(ByteBuffer,ByteBuffer[]).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doAction(JaSSLEngine.java:748)
> at weblogic.security.SSL.jsseadapter.JaSSLEngine.unwrap(JaSSLEngine.java:132)
> at weblogic.socket.JSSEFilterImpl.unwrap(JSSEFilterImpl.java:611)
> at
> weblogic.socket.JSSEFilterImpl.unwrapAndHandleResults(JSSEFilterImpl.java:515)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:98)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:77)
> at weblogic.socket.JSSESocket.startHandshake(JSSESocket.java:240)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:574)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:545)
> at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:230)
> at
> weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:685)
> at
> weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:41)
> at org.apache.cxf.resource.URIResolver.tryFileSystem(URIResolve
[jira] [Resolved] (CXF-6777) javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
[
https://issues.apache.org/jira/browse/CXF-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-6777.
--
Resolution: Not A Problem
> javax.net.ssl.SSLKeyException: Hostname verification failed on WLS 12.2.1
> --
>
> Key: CXF-6777
> URL: https://issues.apache.org/jira/browse/CXF-6777
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Reporter: Sebastian Krupa
> Attachments: SR Oracle.zip
>
>
> Could you help me - i have problem with Weblogic 12.2.1 when CXF 3.1.4
> dynamic client tries to invoke SSL based web services.
> I have already reported it to Oracle support - but they said that it is CXF
> problem not Weblogic, so here I am :) to ask you about it.
> I'm putting here reported issue(number in my oracle support SR
> 3-11832157061), note *2029567.1* is error that has same exception like mine
> by it has been fixed(Oracle says so) in WLS 12.1.3
> {panel:title=Fragments from Oracle support
> page|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
> {color:red}We encountered a problem that is described in this note
> *2029567.1* in one of our application that will be launched on WLS 12.2.1.
> This error ocurs when dynamic Apache CXF client is invoked. Exception is like
> follows:{color}
> <2015-12-07 11:55:09 CET> specified trustmanager validation status 0>
> <2015-12-07 11:55:09 CET>
>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: No trust failure, validateErr=0.>
> <2015-12-07 11:55:09 CET> hostname validation checks: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> chain received from test.osb.ibis.vip - 172.16.200.115 failed hostname
> verification check. Certificate contained test.osb.ibis.vip but check
> expected test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET> Verification failed for certificate with CommonName 'test.osb.ibis.vip'
> against hostname: test.osb.ibis.vip>
> <2015-12-07 11:55:09 CET>
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)',5,Pooled Threads]]weblogic.security.SSL.jsseadapter:
> SSLENGINE: Exception occurred during SSLEngine.wrap(ByteBuffer,ByteBuffer).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
>
> {color:red}Excpetion from admin server log:{color}
> ==AdminServer.log===
> <2015-12-07 11:55:09 CET>
> <[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)'> <> <>
> <1449485709084>
> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
> <[Thread[[ACTIVE] ExecuteThread: '0' for queue:
> 'weblogic.kernel.Default (self-tuning)',5,Pooled
> Threads]]weblogic.security.SSL.jsseadapter: SSLENGINE: Exception occurred
> during SSLEngine.unwrap(ByteBuffer,ByteBuffer[]).
> javax.net.ssl.SSLKeyException: Hostname verification failed:
> HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier,
> hostname=test.osb.ibis.vip.
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doPostHandshake(JaSSLEngine.java:677)
> at
> weblogic.security.SSL.jsseadapter.JaSSLEngine.doAction(JaSSLEngine.java:748)
> at weblogic.security.SSL.jsseadapter.JaSSLEngine.unwrap(JaSSLEngine.java:132)
> at weblogic.socket.JSSEFilterImpl.unwrap(JSSEFilterImpl.java:611)
> at
> weblogic.socket.JSSEFilterImpl.unwrapAndHandleResults(JSSEFilterImpl.java:515)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:98)
> at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:77)
> at weblogic.socket.JSSESocket.startHandshake(JSSESocket.java:240)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:574)
> at weblogic.net.http.HttpsClient.New(HttpsClient.java:545)
> at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:230)
> at
> weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:685)
> at
> weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:41)
> at org.apache.cxf.resource.URIResolver.tryFileSystem(URIResolver.java:184)
> at org.apache.cxf.resource.URIResolver.resolve(URIResolver.java:120)
> at
> org.apache.cxf.resource.ExtendedURIResolver.resolve(ExtendedURIResolver.java:41)
> at
> org.apache.cxf.transport.TransportURIResolver.resolve(TransportURIResolver.java:150)
> at
> org.apache.cxf.wsdl11.CatalogWSDLLocator.getBaseInputSource(CatalogWSDLLocator.java:74)
> at
> org.apache.cxf.wsdl11.AbstractWrapperWSDLLocator.getBaseInputSourc
[jira] [Resolved] (CXF-6779) Swagger Feature should become discoverable
[ https://issues.apache.org/jira/browse/CXF-6779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-6779. --- Resolution: Fixed > Swagger Feature should become discoverable > -- > > Key: CXF-6779 > URL: https://issues.apache.org/jira/browse/CXF-6779 > Project: CXF > Issue Type: Improvement > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin > Fix For: 3.2.0, 3.1.6 > > > We have an interest in this feature becoming easier to set up in a Spring > Boot context -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-5439) Introduce annotations for marking CXF interceptors and features to enable the auto-discovery
[ https://issues.apache.org/jira/browse/CXF-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-5439. --- Resolution: Fixed Assignee: Sergey Beryozkin Fix Version/s: 3.1.6 3.2.0 > Introduce annotations for marking CXF interceptors and features to enable the > auto-discovery > > > Key: CXF-5439 > URL: https://issues.apache.org/jira/browse/CXF-5439 > Project: CXF > Issue Type: Improvement > Components: Core >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin >Priority: Minor > Fix For: 3.2.0, 3.1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6781) InternalContextUtils should bak all the data from the input stream before send back partialResponse
Freeman Fang created CXF-6781: - Summary: InternalContextUtils should bak all the data from the input stream before send back partialResponse Key: CXF-6781 URL: https://issues.apache.org/jira/browse/CXF-6781 Project: CXF Issue Type: Bug Reporter: Freeman Fang as the transport might discard any data on the stream when this thread unwinds or when the empty response is sent back -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-6781) InternalContextUtils should bak all the data from the input stream before send back partialResponse
[ https://issues.apache.org/jira/browse/CXF-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-6781: - Assignee: Freeman Fang > InternalContextUtils should bak all the data from the input stream before > send back partialResponse > --- > > Key: CXF-6781 > URL: https://issues.apache.org/jira/browse/CXF-6781 > Project: CXF > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang > > as the transport might discard any data on the stream when this thread > unwinds or when the empty response is sent back -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6781) InternalContextUtils should bak all the data from the input stream before send back partialResponse
[ https://issues.apache.org/jira/browse/CXF-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-6781. --- Resolution: Fixed Fix Version/s: 3.1.6 3.2.0 commit fix http://git-wip-us.apache.org/repos/asf/cxf/commit/2726b68f for master http://git-wip-us.apache.org/repos/asf/cxf/commit/afaf1deb for 3.1.x-fixes branch > InternalContextUtils should bak all the data from the input stream before > send back partialResponse > --- > > Key: CXF-6781 > URL: https://issues.apache.org/jira/browse/CXF-6781 > Project: CXF > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang > Fix For: 3.2.0, 3.1.6 > > > as the transport might discard any data on the stream when this thread > unwinds or when the empty response is sent back -- This message was sent by Atlassian JIRA (v6.3.4#6332)
