[jira] [Created] (CXF-8822) AsyncHTTPConduit removes query-parameters when path is empty
Magnus Holm created CXF-8822:
Summary: AsyncHTTPConduit removes query-parameters when path is
empty
Key: CXF-8822
URL: https://issues.apache.org/jira/browse/CXF-8822
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 3.5.5
Reporter: Magnus Holm
{{AsyncHTTPConduit.setupConnection(Message message, Address address,
HTTPClientPolicy csPolicy)}} performs some URI-cleanup which results in
query-parameters being removed when the path-part of the URI is empty.
{code:java}
@Test
public void testEmptyPathWithQueryParams() throws IOException {
String address = "http://localhost?param1=value1¶m2=value2";;
Greeter greeter = new SOAPService().getSoapPort();
setAddress(greeter, address);
HTTPConduit c = (HTTPConduit)((ClientProxy)
Proxy.getInvocationHandler(greeter)).getClient().getConduit();
MessageImpl message = new MessageImpl();
message.put(USE_ASYNC, true);
ExchangeImpl exchange = new ExchangeImpl();
message.setExchange(exchange);
c.prepare(message);
CXFHttpRequest e = message.get(CXFHttpRequest.class);
assertEquals(address, e.getUri().toString()); // query-parameters gone
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8822) AsyncHTTPConduit removes query-parameters when path is empty
[
https://issues.apache.org/jira/browse/CXF-8822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-8822:
-
Description:
{{AsyncHTTPConduit.setupConnection(Message message, Address address,
HTTPClientPolicy csPolicy)}} performs some URI-cleanup which results in
query-parameters being removed when the path-part of the URI is empty.
{code:java}
@Test
public void testEmptyPathWithQueryParams() throws IOException {
String address = "http://localhost?param1=value1¶m2=value2";;
Greeter greeter = new SOAPService().getSoapPort();
setAddress(greeter, address);
HTTPConduit c = (HTTPConduit)((ClientProxy)
Proxy.getInvocationHandler(greeter)).getClient().getConduit();
MessageImpl message = new MessageImpl();
message.put(USE_ASYNC, true);
ExchangeImpl exchange = new ExchangeImpl();
message.setExchange(exchange);
c.prepare(message);
CXFHttpRequest e = message.get(CXFHttpRequest.class);
assertEquals(address, e.getUri().toString()); // query-parameters gone
}
{code}
was:
{{AsyncHTTPConduit.setupConnection(Message message, Address address,
HTTPClientPolicy csPolicy)}} performs some URI-cleanup which results in
query-parameters being removed when the path-part of the URI is empty.
{code:java}
@Test
public void testEmptyPathWithQueryParams() throws IOException {
String address = "http://localhost?param1=value1¶m2=value2";;
Greeter greeter = new SOAPService().getSoapPort();
setAddress(greeter, address);
HTTPConduit c = (HTTPConduit)((ClientProxy)
Proxy.getInvocationHandler(greeter)).getClient().getConduit();
MessageImpl message = new MessageImpl();
message.put(USE_ASYNC, true);
ExchangeImpl exchange = new ExchangeImpl();
message.setExchange(exchange);
c.prepare(message);
CXFHttpRequest e = message.get(CXFHttpRequest.class);
assertEquals(address, e.getUri().toString()); // query-parameters gone
}
{code}
> AsyncHTTPConduit removes query-parameters when path is empty
>
>
> Key: CXF-8822
> URL: https://issues.apache.org/jira/browse/CXF-8822
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 3.5.5
>Reporter: Magnus Holm
>Priority: Major
>
> {{AsyncHTTPConduit.setupConnection(Message message, Address address,
> HTTPClientPolicy csPolicy)}} performs some URI-cleanup which results in
> query-parameters being removed when the path-part of the URI is empty.
> {code:java}
> @Test
> public void testEmptyPathWithQueryParams() throws IOException {
> String address = "http://localhost?param1=value1¶m2=value2";;
> Greeter greeter = new SOAPService().getSoapPort();
> setAddress(greeter, address);
> HTTPConduit c = (HTTPConduit)((ClientProxy)
> Proxy.getInvocationHandler(greeter)).getClient().getConduit();
> MessageImpl message = new MessageImpl();
> message.put(USE_ASYNC, true);
> ExchangeImpl exchange = new ExchangeImpl();
> message.setExchange(exchange);
> c.prepare(message);
> CXFHttpRequest e = message.get(CXFHttpRequest.class);
> assertEquals(address, e.getUri().toString()); // query-parameters gone
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CXF-8826) AsyncHTTPConduit (hc5) - Unexpected EOF during response processing
Magnus Holm created CXF-8826:
Summary: AsyncHTTPConduit (hc5) - Unexpected EOF during response
processing
Key: CXF-8826
URL: https://issues.apache.org/jira/browse/CXF-8826
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 3.5.5
Reporter: Magnus Holm
Attachments: http-hc-wireshark.png, http-hc5-wireshark.png
Unexpected EOF while processing large response streams with hc5 async-client
I'm encountering issues with large SOAP response payloads using the http-hc5
AsyncHTTPConduit. It seems the stream-reader encounters an unexpected EOF while
processing the stream. The issue is not reproducible with the http-hc
AsyncHTTPConduit. Test-cases are linked below.
I've also monitored the existing AsyncHTTPConduitTest with wireshark in both
modules http-hc and http-hc5. While http-hc behaves as you'd expect, http-hc5
produces RST,ACK (reset) instead of the expected FIN,ACK, even when processing
is seemingly successful. Attached a couple of screenshots to illustrate.
Unfortunately I've not been able to pinpoint what the cause of the issue is.
This has happened using three different backends, jetty, undertow and some
ancient SOAP production system that I'm sure are running neither of those, so
it seems the issue is at least on the client-side.
Testcases: https://github.com/magnho/cxf/pull/1
Fails with http-hc5, succeeds with http-hc.
See:
{{org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitLargeResponseTest}}
{{org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitLargeResponseTest}}
Please let me know if you need me to provide any further details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8826) AsyncHTTPConduit (hc5) - Unexpected EOF during response processing
[
https://issues.apache.org/jira/browse/CXF-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-8826:
-
Description:
I'm encountering issues with large SOAP response payloads using the http-hc5
{{AsyncHTTPConduit}}. It seems the stream-reader encounters an unexpected EOF
while processing the stream. The issue is not reproducible with the http-hc
{{AsyncHTTPConduit}}. Test-cases are linked below.
I've also monitored the existing {{AsyncHTTPConduitTest}} with wireshark in
both modules http-hc and http-hc5. While http-hc behaves as you'd expect,
http-hc5 produces RST,ACK (reset) instead of the expected FIN,ACK, even when
processing is seemingly successful. Attached a couple of screenshots to
illustrate.
Unfortunately I've not been able to pinpoint what the cause of the issue is.
This has happened using three different backends, jetty, undertow and some
ancient SOAP production system that I'm sure are running neither of those, so
it seems the issue is at least on the client-side.
Testcases: https://github.com/magnho/cxf/pull/1
Fails with http-hc5, succeeds with http-hc.
See:
{{org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitLargeResponseTest}}
{{org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitLargeResponseTest}}
Please let me know if you need me to provide any further details.
was:
Unexpected EOF while processing large response streams with hc5 async-client
I'm encountering issues with large SOAP response payloads using the http-hc5
AsyncHTTPConduit. It seems the stream-reader encounters an unexpected EOF while
processing the stream. The issue is not reproducible with the http-hc
AsyncHTTPConduit. Test-cases are linked below.
I've also monitored the existing AsyncHTTPConduitTest with wireshark in both
modules http-hc and http-hc5. While http-hc behaves as you'd expect, http-hc5
produces RST,ACK (reset) instead of the expected FIN,ACK, even when processing
is seemingly successful. Attached a couple of screenshots to illustrate.
Unfortunately I've not been able to pinpoint what the cause of the issue is.
This has happened using three different backends, jetty, undertow and some
ancient SOAP production system that I'm sure are running neither of those, so
it seems the issue is at least on the client-side.
Testcases: https://github.com/magnho/cxf/pull/1
Fails with http-hc5, succeeds with http-hc.
See:
{{org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitLargeResponseTest}}
{{org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitLargeResponseTest}}
Please let me know if you need me to provide any further details.
> AsyncHTTPConduit (hc5) - Unexpected EOF during response processing
> --
>
> Key: CXF-8826
> URL: https://issues.apache.org/jira/browse/CXF-8826
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 3.5.5
>Reporter: Magnus Holm
>Priority: Major
> Attachments: http-hc-wireshark.png, http-hc5-wireshark.png
>
>
> I'm encountering issues with large SOAP response payloads using the http-hc5
> {{AsyncHTTPConduit}}. It seems the stream-reader encounters an unexpected EOF
> while processing the stream. The issue is not reproducible with the http-hc
> {{AsyncHTTPConduit}}. Test-cases are linked below.
> I've also monitored the existing {{AsyncHTTPConduitTest}} with wireshark in
> both modules http-hc and http-hc5. While http-hc behaves as you'd expect,
> http-hc5 produces RST,ACK (reset) instead of the expected FIN,ACK, even when
> processing is seemingly successful. Attached a couple of screenshots to
> illustrate.
> Unfortunately I've not been able to pinpoint what the cause of the issue is.
> This has happened using three different backends, jetty, undertow and some
> ancient SOAP production system that I'm sure are running neither of those, so
> it seems the issue is at least on the client-side.
> Testcases: https://github.com/magnho/cxf/pull/1
> Fails with http-hc5, succeeds with http-hc.
> See:
> {{org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitLargeResponseTest}}
> {{org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitLargeResponseTest}}
> Please let me know if you need me to provide any further details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CXF-9007) NullPointerException in Dispatch response-handling
Magnus Holm created CXF-9007:
Summary: NullPointerException in Dispatch response-handling
Key: CXF-9007
URL: https://issues.apache.org/jira/browse/CXF-9007
Project: CXF
Issue Type: Bug
Affects Versions: 4.0.4
Reporter: Magnus Holm
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}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9007) NullPointerException in client response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-9007:
-
Summary: NullPointerException in client response-handling (was:
NullPointerException in Dispatch response-handling)
> 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.4
>Reporter: Magnus Holm
>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}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9007) NullPointerException in Dispatch response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-9007:
-
Attachment: dispatch-impl-npe.txt
> NullPointerException in Dispatch response-handling
> --
>
> Key: CXF-9007
> URL: https://issues.apache.org/jira/browse/CXF-9007
> Project: CXF
> Issue Type: Bug
>Affects Versions: 4.0.4
>Reporter: Magnus Holm
>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}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9007) NullPointerException in Dispatch response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-9007:
-
Attachment: interceptor-npe.txt
invoke-sync-npe.txt
invoke-async-npe.txt
> NullPointerException in Dispatch response-handling
> --
>
> Key: CXF-9007
> URL: https://issues.apache.org/jira/browse/CXF-9007
> Project: CXF
> Issue Type: Bug
>Affects Versions: 4.0.4
>Reporter: Magnus Holm
>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}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9007) NullPointerException in client response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-9007:
-
Description:
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
was:
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}
> 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.4
>Reporter: Magnus Holm
>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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9007) NullPointerException in client response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-9007:
-
Description:
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 version: Corretto 17 (17.0.8-amzn)
was:
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
> 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.4
>Reporter: Magnus Holm
>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 version: Corretto 17 (17.0.8-amzn)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-9007) NullPointerException in client response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843695#comment-17843695
]
Magnus Holm commented on CXF-9007:
--
[~reta] We've had it on 4.0.3 and 4.0.4 at least, and maybe older versions as
well. I've updated the description. We've had it happening with different
versions corretto & zulu JDK 17.
> 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.4
>Reporter: Magnus Holm
>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 version: Corretto 17 (17.0.8-amzn)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9007) NullPointerException in client response-handling
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magnus Holm updated CXF-9007:
-
Description:
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) ++
was:
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 version: Corretto 17 (17.0.8-amzn)
> 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.4
>Reporter: Magnus Holm
>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] [Commented] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848129#comment-17848129
]
Magnus Holm commented on CXF-9007:
--
[~reta] Sorry for the delay, struggling to find time. I built your branch and
re-ran tests and found out the potential fix causes a consistent failure for
another test which relates to large response processing/chunking. I will set
aside some time and provide you with both test-cases some time this week. Have
to unwrap the setup from some internal frameworking.
The new failure:
{code}
org.apache.cxf.binding.soap.SoapFault: Problems creating SAAJ object model
at
org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:261)
~[cxf-rt-bindings-soap-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:81)
~[cxf-rt-bindings-soap-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
[cxf-core-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:808)
[cxf-core-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1726)
[cxf-rt-transports-http-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream$1.run(HTTPConduit.java:1210)
[cxf-rt-transports-http-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
org.apache.cxf.workqueue.AutomaticWorkQueueImpl$3.run(AutomaticWorkQueueImpl.java:413)
[cxf-core-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[?:?]
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[?:?]
at
org.apache.cxf.workqueue.AutomaticWorkQueueImpl$AWQThreadFactory$1.run(AutomaticWorkQueueImpl.java:346)
[cxf-core-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at java.base/java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF; was expecting a
close tag for element
at [row,col {unknown-source}]: [1,16320]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701)
~[woodstox-core-6.6.2.jar:6.6.2]
at
com.ctc.wstx.sr.BasicStreamReader.throwUnexpectedEOF(BasicStreamReader.java:5607)
~[woodstox-core-6.6.2.jar:6.6.2]
at
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2811)
~[woodstox-core-6.6.2.jar:6.6.2]
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1122)
~[woodstox-core-6.6.2.jar:6.6.2]
at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:776)
~[cxf-core-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
at
org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:244)
~[cxf-rt-bindings-soap-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT]
... 10 more
{code}
> 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
[jira] [Commented] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850912#comment-17850912
]
Magnus Holm commented on CXF-9007:
--
[~reta] Sorry about the delay. Added a test-case for the issue in the original
report here:
https://github.com/magnho/cxf/pull/2/commits/aefcffcb0af236308cda8c2eb4186e15b8192e8d
Copied in a bunch of stuff to make this as similar to our local test-case as
possible. I managed to trigger the error here as well, added the test-output to
the commit as well. It runs successfully 9/10 times (at least), so it's a bit
of a hassle to trigger the failure.
The failure in my previous post seems to be a mistake on my side. Maybe I
managed to mix versions on the classpath or something, it does not fail any
more.
> 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] [Comment Edited] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850912#comment-17850912
]
Magnus Holm edited comment on CXF-9007 at 5/31/24 6:21 AM:
---
[~reta] Sorry about the delay. Added a test-case for the issue in the original
report here:
https://github.com/magnho/cxf/pull/2/commits/aefcffcb0af236308cda8c2eb4186e15b8192e8d
Copied in a bunch of stuff to make this as similar to our local test-case as
possible. I managed to trigger the error here as well, added the test-output to
the commit as well. It runs successfully 9/10 times (at least), so it's a bit
of a hassle to trigger the failure.
The failure in my previous post seems to be a mistake on my side. Maybe I
managed to mix versions on the classpath or something, it does not fail any
more.
edit: Sorry for not using existing wsdls etc. couldn't get that working.
was (Author: maghol):
[~reta] Sorry about the delay. Added a test-case for the issue in the original
report here:
https://github.com/magnho/cxf/pull/2/commits/aefcffcb0af236308cda8c2eb4186e15b8192e8d
Copied in a bunch of stuff to make this as similar to our local test-case as
possible. I managed to trigger the error here as well, added the test-output to
the commit as well. It runs successfully 9/10 times (at least), so it's a bit
of a hassle to trigger the failure.
The failure in my previous post seems to be a mistake on my side. Maybe I
managed to mix versions on the classpath or something, it does not fail any
more.
> 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] [Comment Edited] (CXF-9007) NullPointerException in XMLStreamDataWriter.writeNode
[
https://issues.apache.org/jira/browse/CXF-9007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850912#comment-17850912
]
Magnus Holm edited comment on CXF-9007 at 5/31/24 9:27 AM:
---
[~reta] Sorry about the delay. Added a test-case for the issue in the original
report here:
https://github.com/magnho/cxf/pull/2/commits/aefcffcb0af236308cda8c2eb4186e15b8192e8d
Copied in a bunch of stuff to make this as similar to our local test-case as
possible. I managed to trigger the error here as well, added the test-output to
the commit as well. It runs successfully 9/10 times (at least), so it's a bit
of a hassle to trigger the failure.
The failure in my previous post seems to be a mistake on my side. Maybe I
managed to mix versions on the classpath or something, it does not fail any
more.
edit: Sorry for not using existing wsdls etc. couldn't get that working.
edit2: Have not been able to trigger failures when running with your branch
change.
was (Author: maghol):
[~reta] Sorry about the delay. Added a test-case for the issue in the original
report here:
https://github.com/magnho/cxf/pull/2/commits/aefcffcb0af236308cda8c2eb4186e15b8192e8d
Copied in a bunch of stuff to make this as similar to our local test-case as
possible. I managed to trigger the error here as well, added the test-output to
the commit as well. It runs successfully 9/10 times (at least), so it's a bit
of a hassle to trigger the failure.
The failure in my previous post seems to be a mistake on my side. Maybe I
managed to mix versions on the classpath or something, it does not fail any
more.
edit: Sorry for not using existing wsdls etc. couldn't get that working.
> 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)
