[jira] [Assigned] (CXF-8221) Upgrade Http Components Core and Client to 5.0

2021-10-14 Thread Andriy Redko (Jira) 


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

Andriy Redko reassigned CXF-8221:
-

Assignee: Andriy Redko

> Upgrade Http Components Core and Client to 5.0
> --
>
> Key: CXF-8221
> URL: https://issues.apache.org/jira/browse/CXF-8221
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>
> Notable changes and features included in the 5.0 series are:
> * Support for the HTTP/2 protocol and conformance to requirements and
> recommendations of the latest HTTP/2 protocol specification documents
> (RFC 7540, RFC 7541.)
>   Supported features:
> ** HPACK header compression
> ** Stream multiplexing (client and server)
> ** Flow control
> ** Response push
> ** Message trailers
> ** Expect-continue handshake
> ** Connection validation (ping)
> ** Application-layer protocol negotiation (ALPN)
> ** TLS 1.2 security features
> * Improved conformance to requirements and recommendations of the
> latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)
> * New connection pool implementation with lax connection limit
> guarantees and better performance under higher concurrency due to
> absence of a global pool lock.
> * Support for Reactive Streams API [http://www.reactive-streams.org/]
> * Package name space changed to 'org.apache.hc.client5'.
> * Maven group id changed to 'org.apache.httpcomponents.client5'.
> HttpClient 5.0 releases can be co-located with earlier major versions
> on the same classpath due to the change in package names and Maven
> module coordinates.
> Download - 
> Release notes - <
> https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CXF-8221) Upgrade Http Components Core and Client to 5.0

2021-10-14 Thread Dennis Kieselhorst (Jira) 


[ 
https://issues.apache.org/jira/browse/CXF-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428985#comment-17428985
 ] 

Dennis Kieselhorst commented on CXF-8221:
-

Sure, please go ahead. 

> Upgrade Http Components Core and Client to 5.0
> --
>
> Key: CXF-8221
> URL: https://issues.apache.org/jira/browse/CXF-8221
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.5.0
>
>
> Notable changes and features included in the 5.0 series are:
> * Support for the HTTP/2 protocol and conformance to requirements and
> recommendations of the latest HTTP/2 protocol specification documents
> (RFC 7540, RFC 7541.)
>   Supported features:
> ** HPACK header compression
> ** Stream multiplexing (client and server)
> ** Flow control
> ** Response push
> ** Message trailers
> ** Expect-continue handshake
> ** Connection validation (ping)
> ** Application-layer protocol negotiation (ALPN)
> ** TLS 1.2 security features
> * Improved conformance to requirements and recommendations of the
> latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)
> * New connection pool implementation with lax connection limit
> guarantees and better performance under higher concurrency due to
> absence of a global pool lock.
> * Support for Reactive Streams API [http://www.reactive-streams.org/]
> * Package name space changed to 'org.apache.hc.client5'.
> * Maven group id changed to 'org.apache.httpcomponents.client5'.
> HttpClient 5.0 releases can be co-located with earlier major versions
> on the same classpath due to the change in package names and Maven
> module coordinates.
> Download - 
> Release notes - <
> https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CXF-8605) Introduce HTTP/2 Transport: server-side support

2021-10-14 Thread Andriy Redko (Jira) 


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

Andriy Redko updated CXF-8605:
--
Affects Version/s: 3.4.5

> Introduce HTTP/2 Transport: server-side support
> ---
>
> Key: CXF-8605
> URL: https://issues.apache.org/jira/browse/CXF-8605
> Project: CXF
>  Issue Type: Sub-task
>Affects Versions: 3.4.5
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CXF-8606) Introduce HTTP/2 Transport: client-side support

2021-10-14 Thread Andriy Redko (Jira) 


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

Andriy Redko updated CXF-8606:
--
Affects Version/s: 3.4.5

> Introduce HTTP/2 Transport: client-side support
> ---
>
> Key: CXF-8606
> URL: https://issues.apache.org/jira/browse/CXF-8606
> Project: CXF
>  Issue Type: Sub-task
>Affects Versions: 3.4.5
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CXF-6349) Introduce HTTP/2 Transport

2021-10-14 Thread Andriy Redko (Jira) 


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

Andriy Redko updated CXF-6349:
--
Fix Version/s: 3.5.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
>Affects Versions: 3.4.5
>Reporter: Sergey Beryozkin
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>
> [https://http2.github.io/]
> Can be complementary to what Aki has done with WebSockets.
> h2. Proposal
> All four web containers (Jetty / Tomcat / Undertow / Netty), which CXF 
> integrates with, support HTTP/2 over TCP (h2c) and HTTP/2 over TLS (h2). 
> Technically it is possible to only support HTTP/2 protocol [1], but 
> practically both HTTP/1.1 and HTTP/2 always come together. As such, the it 
> would make sense to enhance current CXF's `ServerEngine`s implementations to 
> turn H2 (or H2C if TLS/SSL is not configured) on, in addition to HTTP/1.1, 
> controllable by property:
> {noformat}
> org.apache.cxf.transports.http2.enabled = true | false{noformat}
> At the moment, only CXF's Undertow transport 
> (`cxf-rt-transports-http-undertow`) allows to configure HTTP/2 support using 
> `Bus` property `org.apache.cxf.transports.http_undertow.EnableHttp2`. The 
> proposal is to deprecate this property for removal in favor of 
> `org.apache.cxf.transports.http2.enabled` (semantic of this property would be 
> kept the same). Meantime, both properties will be supported.
> Since CXF also provides clients, it is expected to have H2 and H2C support 
> for clients as well.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CXF-6349) Introduce HTTP/2 Transport

2021-10-14 Thread Andriy Redko (Jira) 


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

Andriy Redko updated CXF-6349:
--
Affects Version/s: 3.4.5

> Introduce HTTP/2 Transport 
> ---
>
> Key: CXF-6349
> URL: https://issues.apache.org/jira/browse/CXF-6349
> Project: CXF
>  Issue Type: New Feature
>  Components: Transports
>Affects Versions: 3.4.5
>Reporter: Sergey Beryozkin
>Assignee: Andriy Redko
>Priority: Major
>
> [https://http2.github.io/]
> Can be complementary to what Aki has done with WebSockets.
> h2. Proposal
> All four web containers (Jetty / Tomcat / Undertow / Netty), which CXF 
> integrates with, support HTTP/2 over TCP (h2c) and HTTP/2 over TLS (h2). 
> Technically it is possible to only support HTTP/2 protocol [1], but 
> practically both HTTP/1.1 and HTTP/2 always come together. As such, the it 
> would make sense to enhance current CXF's `ServerEngine`s implementations to 
> turn H2 (or H2C if TLS/SSL is not configured) on, in addition to HTTP/1.1, 
> controllable by property:
> {noformat}
> org.apache.cxf.transports.http2.enabled = true | false{noformat}
> At the moment, only CXF's Undertow transport 
> (`cxf-rt-transports-http-undertow`) allows to configure HTTP/2 support using 
> `Bus` property `org.apache.cxf.transports.http_undertow.EnableHttp2`. The 
> proposal is to deprecate this property for removal in favor of 
> `org.apache.cxf.transports.http2.enabled` (semantic of this property would be 
> kept the same). Meantime, both properties will be supported.
> Since CXF also provides clients, it is expected to have H2 and H2C support 
> for clients as well.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CXF-8221) Upgrade Http Components Core and Client to 5.0

2021-10-14 Thread Andriy Redko (Jira) 


[ 
https://issues.apache.org/jira/browse/CXF-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428981#comment-17428981
 ] 

Andriy Redko commented on CXF-8221:
---

[~deki] [~coheigea] guys, do you mind if I assign this issue to myself, working 
on HTTP/2 support and it would be required for the client support, thank you!

> Upgrade Http Components Core and Client to 5.0
> --
>
> Key: CXF-8221
> URL: https://issues.apache.org/jira/browse/CXF-8221
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.5.0
>
>
> Notable changes and features included in the 5.0 series are:
> * Support for the HTTP/2 protocol and conformance to requirements and
> recommendations of the latest HTTP/2 protocol specification documents
> (RFC 7540, RFC 7541.)
>   Supported features:
> ** HPACK header compression
> ** Stream multiplexing (client and server)
> ** Flow control
> ** Response push
> ** Message trailers
> ** Expect-continue handshake
> ** Connection validation (ping)
> ** Application-layer protocol negotiation (ALPN)
> ** TLS 1.2 security features
> * Improved conformance to requirements and recommendations of the
> latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)
> * New connection pool implementation with lax connection limit
> guarantees and better performance under higher concurrency due to
> absence of a global pool lock.
> * Support for Reactive Streams API [http://www.reactive-streams.org/]
> * Package name space changed to 'org.apache.hc.client5'.
> * Maven group id changed to 'org.apache.httpcomponents.client5'.
> HttpClient 5.0 releases can be co-located with earlier major versions
> on the same classpath due to the change in package names and Maven
> module coordinates.
> Download - 
> Release notes - <
> https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (CXF-8419) Graal VM native image run fails

2021-10-14 Thread Andriy Redko (Jira) 


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

Andriy Redko resolved CXF-8419.
---
Resolution: Won't Fix

No feedback from the user

> Graal VM native image run fails
> ---
>
> Key: CXF-8419
> URL: https://issues.apache.org/jira/browse/CXF-8419
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 3.4.2, 3.3.9
>Reporter: sendev
>Priority: Major
>  Labels: graalvm, spring-boot
>
> Hi,
> I am trying to follow the guide to create native image for CXF client that 
> was referenced in the defect that I created earlier #8340 . My example is 
> using
>  JaxWsProxyFactoryBean to create client.
>  
> I tried 3.3.9 version of CXF and I got following error while running native 
> image 
>  
> {code:java}
> 2021-02-09 17:30:11.322  INFO 5013 --- [   main] 
> com.cxf.client.ClientApplication : Starting ClientApplication using 
> Java 1.8.0_282 on BGTMNWL-9123HKG with PID 5013 
> (/home/urajas4/cxf-client/build/client started by urajas4 in 
> /home/urajas4/cxf-client/build)
> 2021-02-09 17:30:11.322  INFO 5013 --- [   main] 
> com.cxf.client.ClientApplication : No active profile set, falling 
> back to default profiles: default
> 2021-02-09 17:30:11.385  INFO 5013 --- [   main] 
> o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 
> 8081 (http)
> Feb 09, 2021 5:30:11 PM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-nio-8081"]
> Feb 09, 2021 5:30:11 PM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service [Tomcat]
> Feb 09, 2021 5:30:11 PM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet engine: [Apache Tomcat/9.0.41]
> Feb 09, 2021 5:30:11 PM org.apache.catalina.core.ApplicationContext log
> INFO: Initializing Spring embedded WebApplicationContext
> 2021-02-09 17:30:11.394  INFO 5013 --- [   main] 
> w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: 
> initialization completed in 71 ms
> JVM_MaxObjectInspectionAge called:  Unimplemented
> Aborted (core dumped)
> {code}
>  
>  
> Then I upgrade to CXF 3.4.2 and getting following error when running native 
> image. The application runs fine as java application using CXF 3.4.2 or 3.3.9.
>  
> {code:java}
> 2021-02-09 18:15:54.564 ERROR 8528 --- [   main] 
> o.s.b.web.embedded.tomcat.TomcatStarter  : Error starting Tomcat context. 
> Exception: org.springframework.beans.factory.UnsatisfiedDependencyException. 
> Message: Error creating bean with name 
> 'org.apache.cxf.spring.boot.autoconfigure.CxfAutoConfiguration': Unsatisfied 
> dependency expressed through field 'properties'; nested exception is 
> org.springframework.boot.context.properties.ConfigurationPropertiesBindException:
>  Error creating bean with name 
> 'cxf-org.apache.cxf.spring.boot.autoconfigure.CxfProperties': Could not bind 
> properties to 'CxfProperties' : prefix=cxf, ignoreInvalidFields=false, 
> ignoreUnknownFields=true; nested exception is 
> org.springframework.boot.context.properties.bind.BindException: Failed to 
> bind properties under 'cxf' to 
> org.apache.cxf.spring.boot.autoconfigure.CxfProperties
> Feb 09, 2021 6:15:54 PM org.apache.catalina.core.StandardService stopInternal
> INFO: Stopping service [Tomcat]
> 2021-02-09 18:15:54.566  WARN 8528 --- [   main] 
> ConfigServletWebServerApplicationContext : Exception encountered during 
> context initialization - cancelling refresh attempt: 
> org.springframework.context.ApplicationContextException: Unable to start web 
> server; nested exception is 
> org.springframework.boot.web.server.WebServerException: Unable to start 
> embedded Tomcat
> 2021-02-09 18:15:54.567  INFO 8528 --- [   main] 
> ConditionEvaluationReportLoggingListener : Error starting ApplicationContext. 
> To display the conditions report re-run your application with 'debug' enabled.
> 2021-02-09 18:15:54.567 ERROR 8528 --- [   main] 
> o.s.b.d.LoggingFailureAnalysisReporter   : ***
> APPLICATION FAILED TO START
> ***Description:Failed to bind properties under 'cxf' 
> to org.apache.cxf.spring.boot.autoconfigure.CxfProperties:Reason: 
> org.hibernate.validator.internal.constraintvalidators.bv.NotNullValidator.()Action:Update
>  your application's configuration
> {code}
>  
> The steps I followed.
>  Placed all the native image configuration from 
> [https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jaxws_graalvm_dynamic/client/src/main/resources/META-INF/native-image/org.apache.cxf.samples/jaxws_graalvm_dynamic_client]
>  into my sample project and customized the configurations.
>  # Using CXF 3.3.9/3.4.2 and as per the above confluence document those

[jira] [Commented] (CXF-8608) WSSCTest always failed with JDK8

2021-10-14 Thread Freeman Yue Fang (Jira) 


[ 
https://issues.apache.org/jira/browse/CXF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428948#comment-17428948
 ] 

Freeman Yue Fang commented on CXF-8608:
---

Seems not related to file descriptor limit, different testcases(different 
TestParam) can interfere with each other. 
If I put the failed TestParam in the beginning of the test like
{code}
--- 
a/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/wssc/WSSCTest.java
+++ 
b/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/wssc/WSSCTest.java
@@ -120,6 +120,7 @@ public class WSSCTest extends 
AbstractBusClientServerTestBase {
 @Parameters(name = "{0}")
 public static Collection data() {
 return Arrays.asList(new TestParam[] {
+new 
TestParam("SecureConversation_UserNameOverTransport_IPingService", STAX_PORT2, 
true),
 new 
TestParam("SecureConversation_UserNameOverTransport_IPingService", PORT2, 
false),
 new 
TestParam("SecureConversation_MutualCertificate10SignEncrypt_IPingService", 
PORT, false),
 new TestParam("AC_IPingService", PORT, false),
@@ -200,7 +201,6 @@ public class WSSCTest extends 
AbstractBusClientServerTestBase {
 new TestParam("_XD-SEES_IPingService", STAX_PORT, false),
 new TestParam("_XD-ES_IPingService", STAX_PORT, false),
 
-new 
TestParam("SecureConversation_UserNameOverTransport_IPingService", STAX_PORT2, 
true),
 // TODO Endorsing derived keys not supported.
 // new 
TestParam("SecureConversation_MutualCertificate10SignEncrypt_IPingService",
 //   STAX_PORT, true),

{code}
All TestParam passed with JDK8/JDK11/JDK17



> WSSCTest always failed with JDK8
> 
>
> Key: CXF-8608
> URL: https://issues.apache.org/jira/browse/CXF-8608
> Project: CXF
>  Issue Type: Task
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>
> Though I don't see this error with JDK11+
> ENV
> {code}
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /Users/ffang/kit/apache-maven-3.6.3
> Java version: 1.8.0_261, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_261.jdk/Contents/Home/jre
> Default locale: en_CA, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (CXF-8608) WSSCTest always failed with JDK8

2021-10-14 Thread Freeman Yue Fang (Jira) 


[ 
https://issues.apache.org/jira/browse/CXF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428935#comment-17428935
 ] 

Freeman Yue Fang edited comment on CXF-8608 at 10/14/21, 5:33 PM:
--

Error is like
{code}
[INFO] Running org.apache.cxf.systest.ws.wssc.WSSCTest
javax.xml.ws.WebServiceException: Could not send Message.
at 
org.apache.cxf.jaxws.JaxWsClientProxy.mapException(JaxWsClientProxy.java:183)
at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145)
at com.sun.proxy.$Proxy59.ping(Unknown Source)
at 
org.apache.cxf.systest.ws.wssc.WSSCTest.testSecureConversation(WSSCTest.java:271)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: javax.net.ssl.SSLException: SSLException invoking 
https://localhost:48104/SecureConversation_UserNameOverTransport_IPingService: 
Couldn't kickstart handshaking
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:423)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1400)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1384)
at 
org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:56)
at 
org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:228)
at 
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPC

[jira] [Commented] (CXF-8608) WSSCTest always failed with JDK8

2021-10-14 Thread Freeman Yue Fang (Jira) 


[ 
https://issues.apache.org/jira/browse/CXF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428935#comment-17428935
 ] 

Freeman Yue Fang commented on CXF-8608:
---

Error is like
{code}
[INFO] Running org.apache.cxf.systest.ws.wssc.WSSCTest
javax.xml.ws.WebServiceException: Could not send Message.
at 
org.apache.cxf.jaxws.JaxWsClientProxy.mapException(JaxWsClientProxy.java:183)
at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145)
at com.sun.proxy.$Proxy59.ping(Unknown Source)
at 
org.apache.cxf.systest.ws.wssc.WSSCTest.testSecureConversation(WSSCTest.java:271)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: javax.net.ssl.SSLException: SSLException invoking 
https://localhost:48104/SecureConversation_UserNameOverTransport_IPingService: 
Couldn't kickstart handshaking
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:423)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1400)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1384)
at 
org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:56)
at 
org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:228)
at 
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:671)
at 
org.apache.cxf.intercept

[jira] [Assigned] (CXF-8608) WSSCTest always failed with JDK8

2021-10-14 Thread Freeman Yue Fang (Jira) 


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

Freeman Yue Fang reassigned CXF-8608:
-

Assignee: Freeman Yue Fang

> WSSCTest always failed with JDK8
> 
>
> Key: CXF-8608
> URL: https://issues.apache.org/jira/browse/CXF-8608
> Project: CXF
>  Issue Type: Task
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>
> Though I don't see this error with JDK11+
> ENV
> {code}
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /Users/ffang/kit/apache-maven-3.6.3
> Java version: 1.8.0_261, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_261.jdk/Contents/Home/jre
> Default locale: en_CA, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CXF-8608) WSSCTest always failed with JDK8

2021-10-14 Thread Freeman Yue Fang (Jira) 
Freeman Yue Fang created CXF-8608:
-

 Summary: WSSCTest always failed with JDK8
 Key: CXF-8608
 URL: https://issues.apache.org/jira/browse/CXF-8608
 Project: CXF
  Issue Type: Task
Reporter: Freeman Yue Fang


Though I don't see this error with JDK11+
ENV
{code}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /Users/ffang/kit/apache-maven-3.6.3
Java version: 1.8.0_261, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_261.jdk/Contents/Home/jre
Default locale: en_CA, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)