[jira] [Updated] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode

2024-05-09 Thread Andriy Redko (Jira)


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

Andriy Redko updated CXF-9007:
--
Fix Version/s: 4.1.0
   4.0.5

> NullPointerException in XMLStreamDataWriter.writeNode
> -
>
> Key: CXF-9007
> URL: https://issues.apache.org/jira/browse/CXF-9007
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 4.0.3, 4.0.4
>Reporter: Magnus Holm
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 4.1.0, 4.0.5
>
> Attachments: dispatch-impl-npe.txt, interceptor-npe.txt, 
> invoke-async-npe.txt, invoke-sync-npe.txt
>
>
> We're encountering sporadic weird {{NullPointerException}} in various of our 
> tests using different client configurations with wsdls. It seems to only 
> occur right after initialising the client, e.g. only on the first call. I 
> suspect it's some kind of race-condition, but I've not been able to create a 
> reproducer. I was hoping maybe someone from the project would have insight 
> into why this could be happening by looking at the stacktraces. 
> The error we're hitting appears to be here: 
> {code}
> java.lang.NullPointerException: Cannot invoke 
> "org.w3c.dom.Node.getOwnerDocument()" because "nd" is null
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.writeNode(XMLStreamDataWriter.java:160)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:101)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:67)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:55)
>  ~[cxf-core-4.0.4.jar:4.0.4]
> {code}
> Update: we're using cxf-rt-transports-http-hc5.
> We've had this issue on 4.0.3 and 4.0.4. We might've had it on previous 
> versions as well, but I don't have build history going back that far.  
> JDK versions: Corretto 17 (17.0.8-amzn), Zulu 17 (17.0.10-zulu) ++



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode

2024-05-09 Thread Andriy Redko (Jira)


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

Andriy Redko commented on CXF-9007:
---

[~maghol] I have submitted a potential fix but I cannot reproduce the problem 
myself, any chances you could share the test case(s) that are failing for you 
sporadically? Thank you.

> NullPointerException in XMLStreamDataWriter.writeNode
> -
>
> Key: CXF-9007
> URL: https://issues.apache.org/jira/browse/CXF-9007
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 4.0.3, 4.0.4
>Reporter: Magnus Holm
>Assignee: Andriy Redko
>Priority: Major
> Attachments: dispatch-impl-npe.txt, interceptor-npe.txt, 
> invoke-async-npe.txt, invoke-sync-npe.txt
>
>
> We're encountering sporadic weird {{NullPointerException}} in various of our 
> tests using different client configurations with wsdls. It seems to only 
> occur right after initialising the client, e.g. only on the first call. I 
> suspect it's some kind of race-condition, but I've not been able to create a 
> reproducer. I was hoping maybe someone from the project would have insight 
> into why this could be happening by looking at the stacktraces. 
> The error we're hitting appears to be here: 
> {code}
> java.lang.NullPointerException: Cannot invoke 
> "org.w3c.dom.Node.getOwnerDocument()" because "nd" is null
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.writeNode(XMLStreamDataWriter.java:160)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:101)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:67)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:55)
>  ~[cxf-core-4.0.4.jar:4.0.4]
> {code}
> Update: we're using cxf-rt-transports-http-hc5.
> We've had this issue on 4.0.3 and 4.0.4. We might've had it on previous 
> versions as well, but I don't have build history going back that far.  
> JDK versions: Corretto 17 (17.0.8-amzn), Zulu 17 (17.0.10-zulu) ++



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode

2024-05-09 Thread Andriy Redko (Jira)


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

Andriy Redko updated CXF-9007:
--
Summary: NullPointerException in XMLStreamDataWriter.writeNode  (was: 
NullPointerException in client response-handling)

> NullPointerException in XMLStreamDataWriter.writeNode
> -
>
> Key: CXF-9007
> URL: https://issues.apache.org/jira/browse/CXF-9007
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 4.0.3, 4.0.4
>Reporter: Magnus Holm
>Assignee: Andriy Redko
>Priority: Major
> Attachments: dispatch-impl-npe.txt, interceptor-npe.txt, 
> invoke-async-npe.txt, invoke-sync-npe.txt
>
>
> We're encountering sporadic weird {{NullPointerException}} in various of our 
> tests using different client configurations with wsdls. It seems to only 
> occur right after initialising the client, e.g. only on the first call. I 
> suspect it's some kind of race-condition, but I've not been able to create a 
> reproducer. I was hoping maybe someone from the project would have insight 
> into why this could be happening by looking at the stacktraces. 
> The error we're hitting appears to be here: 
> {code}
> java.lang.NullPointerException: Cannot invoke 
> "org.w3c.dom.Node.getOwnerDocument()" because "nd" is null
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.writeNode(XMLStreamDataWriter.java:160)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:101)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:67)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:55)
>  ~[cxf-core-4.0.4.jar:4.0.4]
> {code}
> Update: we're using cxf-rt-transports-http-hc5.
> We've had this issue on 4.0.3 and 4.0.4. We might've had it on previous 
> versions as well, but I don't have build history going back that far.  
> JDK versions: Corretto 17 (17.0.8-amzn), Zulu 17 (17.0.10-zulu) ++



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CXF-9007) NullPointerException in client response-handling

2024-05-09 Thread Andriy Redko (Jira)


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

Andriy Redko reassigned CXF-9007:
-

Assignee: Andriy Redko

> NullPointerException in client response-handling
> 
>
> Key: CXF-9007
> URL: https://issues.apache.org/jira/browse/CXF-9007
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 4.0.3, 4.0.4
>Reporter: Magnus Holm
>Assignee: Andriy Redko
>Priority: Major
> Attachments: dispatch-impl-npe.txt, interceptor-npe.txt, 
> invoke-async-npe.txt, invoke-sync-npe.txt
>
>
> We're encountering sporadic weird {{NullPointerException}} in various of our 
> tests using different client configurations with wsdls. It seems to only 
> occur right after initialising the client, e.g. only on the first call. I 
> suspect it's some kind of race-condition, but I've not been able to create a 
> reproducer. I was hoping maybe someone from the project would have insight 
> into why this could be happening by looking at the stacktraces. 
> The error we're hitting appears to be here: 
> {code}
> java.lang.NullPointerException: Cannot invoke 
> "org.w3c.dom.Node.getOwnerDocument()" because "nd" is null
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.writeNode(XMLStreamDataWriter.java:160)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:101)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:67)
>  ~[cxf-core-4.0.4.jar:4.0.4]
>   at 
> org.apache.cxf.databinding.source.XMLStreamDataWriter.write(XMLStreamDataWriter.java:55)
>  ~[cxf-core-4.0.4.jar:4.0.4]
> {code}
> Update: we're using cxf-rt-transports-http-hc5.
> We've had this issue on 4.0.3 and 4.0.4. We might've had it on previous 
> versions as well, but I don't have build history going back that far.  
> JDK versions: Corretto 17 (17.0.8-amzn), Zulu 17 (17.0.10-zulu) ++



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CXF-9011) WSDLTo JAXWS Frontend service.vm Velocity template uses deprecated URL constructor

2024-05-09 Thread Andriy Redko (Jira)


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

Andriy Redko resolved CXF-9011.
---
Resolution: Fixed

> WSDLTo JAXWS Frontend service.vm Velocity template uses deprecated URL 
> constructor
> --
>
> Key: CXF-9011
> URL: https://issues.apache.org/jira/browse/CXF-9011
> Project: CXF
>  Issue Type: Bug
>  Components: Soap Binding
>Affects Versions: 4.0.4
>Reporter: Francisco Mateo
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
>
> The URL constructors were deprecated in Java 20 
> [https://bugs.openjdk.org/browse/JDK-8294241].
> The template uses the deprecated constructor: 
> [https://github.com/apache/cxf/blob/cxf-4.0.4/tools/wsdlto/frontend/jaxws/src/main/java/org/apache/cxf/tools/wsdlto/frontend/jaxws/template/service.vm#L123]
> This becomes an issue when applications compile with warnings enabled, for 
> example {{-Xlint:all -Werror}}
> Seems we could just switch to using {{URI.create(...).toURL()}} in the 
> template since that has been available since Java 1.4



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (CXF-9006) TrustedAuthorityValidatorCRLTest#testIsCertChainValid fails when using Red Hat OpenJDK on PPC64LE

2024-05-09 Thread Andriy Redko (Jira)


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

Andriy Redko updated CXF-9006:
--
Fix Version/s: 4.0.5

> TrustedAuthorityValidatorCRLTest#testIsCertChainValid fails when using Red 
> Hat OpenJDK on PPC64LE
> -
>
> Key: CXF-9006
> URL: https://issues.apache.org/jira/browse/CXF-9006
> Project: CXF
>  Issue Type: Test
>Affects Versions: 4.0.4, 4.1.0
> Environment: Java version: 17.0.6, vendor: Red Hat, Inc., runtime: 
> /usr/lib/jvm/java-17-openjdk-17.0.6.0.10-3.el9.ppc64le
> OS name: "linux", version: "5.14.0-378.el9.ppc64le", arch: "ppc64le", family: 
> "unix"
>Reporter: Jamie Mark Goodyear
>Priority: Minor
> Fix For: 4.1.0, 4.0.5
>
> Attachments: wss40.cer, wss40CA.cer, wss40CACRL.cer, wss40rev.cer
>
>
> {{TrustedAuthorityValidatorCRLTest#testIsCertChainValid}} failing when using 
> Red Hat OpenJDK 17. The error revealed when using 
> {{-Djava.security.debug=certpath}} is that the JVM can not find a valid 
> certification path to the requested target -- note: this unit test works on 
> Bellsoft, Temurin, IBM, Corretto, Zulu, on other platforms, and is confirmed 
> to work with Semeru/Temurin Java on PPC64LE.
> Given this is restricted to one particular JVM distribution/platform, would 
> this be a candidate for a skip test?
> {{sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
> valid certification path to requested target at 
> java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141)
>  at 
> java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126)
>  at 
> java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297) 
> at 
> org.apache.cxf.xkms.x509.validator.TrustedAuthorityValidator.isCertificateChainValid(TrustedAuthorityValidator.java:84)}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)