You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by COURTAULT Francois <Fr...@gemalto.com> on 2018/10/11 16:25:51 UTC
Performance issue in cxf-rt-rs-client-3.1.15.jar
Hello,
Just to keep you informed.
During some performance/stress tests using TomEE 7.1.0 we have found an issue with REST client.
After re-analyzing thread dumps, we found several threads with this pattern:
java.lang.Thread.State: RUNNABLE
at java.util.WeakHashMap.put(WeakHashMap.java:453)
at java.util.Collections$SetFromMap.add(Collections.java:5461)
at org.apache.cxf.jaxrs.client.spec.ClientImpl$WebTargetImpl.initTargetClientIfNeeded(ClientImpl.java:358)
Some people already have this kind of issue:
http://www.adam-bien.com/roller/abien/entry/endless_loops_in_unsychronized_weakhashmap
I got some feedback from cxf guys and it seems that they will fix it on 3.2.7 and 3.1.18 I guess.
I have created an issue in JIRA you can monitor: CXF-7869 Infinite loop in rest client<https://issues.apache.org/jira/projects/CXF/issues/CXF-7869>
Could you please include the cxf fix in future TomEE version please ?
BTW, I have another question: why TomEE embeds cxf 3.1.x instead of cxf 3.2.x ?
Could you please
________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Re: Performance issue in cxf-rt-rs-client-3.1.15.jar
Posted by Matthew Broadhead <ma...@nbmlaw.co.uk.INVALID>.
there is an RC2 available although a classloader bug has been found in
BVal integration. i think they are trying to get it released before
CodeOne
On 12/10/18 16:53, COURTAULT Francois wrote:
> Hello,
>
> Glad to hear that.
> Any release date for TomEE 8 ? Oracle Code announcement ? ;-)
>
> Best Regards.
>
> -----Original Message-----
> From: Matthew Broadhead [mailto:matthew.broadhead@nbmlaw.co.uk.INVALID]
> Sent: jeudi 11 octobre 2018 19:00
> To: users@tomee.apache.org
> Subject: Re: Performance issue in cxf-rt-rs-client-3.1.15.jar
>
> tomee 8 is going to have 3.2.6
>
> On 11/10/18 18:25, COURTAULT Francois wrote:
>> Hello,
>>
>> Just to keep you informed.
>> During some performance/stress tests using TomEE 7.1.0 we have found an issue with REST client.
>>
>> After re-analyzing thread dumps, we found several threads with this pattern:
>> java.lang.Thread.State: RUNNABLE
>> at java.util.WeakHashMap.put(WeakHashMap.java:453)
>> at java.util.Collections$SetFromMap.add(Collections.java:5461)
>> at
>> org.apache.cxf.jaxrs.client.spec.ClientImpl$WebTargetImpl.initTargetCl
>> ientIfNeeded(ClientImpl.java:358) Some people already have this kind
>> of issue:
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.
>> adam-bien.com%2Froller%2Fabien%2Fentry%2Fendless_loops_in_unsychronize
>> d_weakhashmap&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C67
>> c96e552a0748b0a2bd08d62f9b0f40%7C37d0a9db7c464096bfe31add5b495d6d%7C1%
>> 7C0%7C636748740352217094&sdata=3n%2Fq7SI9r1YFAKlf0xEwxNmtasQ5jZmrs
>> 0X9eys6oyY%3D&reserved=0
>>
>> I got some feedback from cxf guys and it seems that they will fix it on 3.2.7 and 3.1.18 I guess.
>> I have created an issue in JIRA you can monitor: CXF-7869 Infinite
>> loop in rest
>> client<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2
>> F%2Fissues.apache.org%2Fjira%2Fprojects%2FCXF%2Fissues%2FCXF-7869&
>> data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C67c96e552a0748b0a2bd
>> 08d62f9b0f40%7C37d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636748740352
>> 217094&sdata=oOLiFlKmb3b1%2B%2Bve5MDM6wbHXBDV%2BPDcAdYco6%2BD4pE%3
>> D&reserved=0>
>>
>> Could you please include the cxf fix in future TomEE version please ?
>>
>> BTW, I have another question: why TomEE embeds cxf 3.1.x instead of cxf 3.2.x ?
>>
>> Could you please
>>
>> ________________________________
>> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
>> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
>> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
>>
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
RE: Performance issue in cxf-rt-rs-client-3.1.15.jar
Posted by COURTAULT Francois <Fr...@gemalto.com>.
Hello,
Glad to hear that.
Any release date for TomEE 8 ? Oracle Code announcement ? ;-)
Best Regards.
-----Original Message-----
From: Matthew Broadhead [mailto:matthew.broadhead@nbmlaw.co.uk.INVALID]
Sent: jeudi 11 octobre 2018 19:00
To: users@tomee.apache.org
Subject: Re: Performance issue in cxf-rt-rs-client-3.1.15.jar
tomee 8 is going to have 3.2.6
On 11/10/18 18:25, COURTAULT Francois wrote:
> Hello,
>
> Just to keep you informed.
> During some performance/stress tests using TomEE 7.1.0 we have found an issue with REST client.
>
> After re-analyzing thread dumps, we found several threads with this pattern:
> java.lang.Thread.State: RUNNABLE
> at java.util.WeakHashMap.put(WeakHashMap.java:453)
> at java.util.Collections$SetFromMap.add(Collections.java:5461)
> at
> org.apache.cxf.jaxrs.client.spec.ClientImpl$WebTargetImpl.initTargetCl
> ientIfNeeded(ClientImpl.java:358) Some people already have this kind
> of issue:
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.
> adam-bien.com%2Froller%2Fabien%2Fentry%2Fendless_loops_in_unsychronize
> d_weakhashmap&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C67
> c96e552a0748b0a2bd08d62f9b0f40%7C37d0a9db7c464096bfe31add5b495d6d%7C1%
> 7C0%7C636748740352217094&sdata=3n%2Fq7SI9r1YFAKlf0xEwxNmtasQ5jZmrs
> 0X9eys6oyY%3D&reserved=0
>
> I got some feedback from cxf guys and it seems that they will fix it on 3.2.7 and 3.1.18 I guess.
> I have created an issue in JIRA you can monitor: CXF-7869 Infinite
> loop in rest
> client<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2
> F%2Fissues.apache.org%2Fjira%2Fprojects%2FCXF%2Fissues%2FCXF-7869&
> data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C67c96e552a0748b0a2bd
> 08d62f9b0f40%7C37d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636748740352
> 217094&sdata=oOLiFlKmb3b1%2B%2Bve5MDM6wbHXBDV%2BPDcAdYco6%2BD4pE%3
> D&reserved=0>
>
> Could you please include the cxf fix in future TomEE version please ?
>
> BTW, I have another question: why TomEE embeds cxf 3.1.x instead of cxf 3.2.x ?
>
> Could you please
>
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
>
________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Re: Performance issue in cxf-rt-rs-client-3.1.15.jar
Posted by Matthew Broadhead <ma...@nbmlaw.co.uk.INVALID>.
tomee 8 is going to have 3.2.6
On 11/10/18 18:25, COURTAULT Francois wrote:
> Hello,
>
> Just to keep you informed.
> During some performance/stress tests using TomEE 7.1.0 we have found an issue with REST client.
>
> After re-analyzing thread dumps, we found several threads with this pattern:
> java.lang.Thread.State: RUNNABLE
> at java.util.WeakHashMap.put(WeakHashMap.java:453)
> at java.util.Collections$SetFromMap.add(Collections.java:5461)
> at org.apache.cxf.jaxrs.client.spec.ClientImpl$WebTargetImpl.initTargetClientIfNeeded(ClientImpl.java:358)
> Some people already have this kind of issue:
> http://www.adam-bien.com/roller/abien/entry/endless_loops_in_unsychronized_weakhashmap
>
> I got some feedback from cxf guys and it seems that they will fix it on 3.2.7 and 3.1.18 I guess.
> I have created an issue in JIRA you can monitor: CXF-7869 Infinite loop in rest client<https://issues.apache.org/jira/projects/CXF/issues/CXF-7869>
>
> Could you please include the cxf fix in future TomEE version please ?
>
> BTW, I have another question: why TomEE embeds cxf 3.1.x instead of cxf 3.2.x ?
>
> Could you please
>
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
>