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

Andriy Redko commented on CXF-8410:
-----------------------------------

[~fjmateo] no, with `factoryBean.create()` a large chunk of initialization 
happens but not all. Also, *HTTPTransportFactory* is just one of many along the 
way, you are going to hit many roadblocks later on (cuz loggers are used mostly 
by every single class). So safest path is to go with different scheduler.

> HTTPTransportFactory's logger performs blocking call
> ----------------------------------------------------
>
>                 Key: CXF-8410
>                 URL: https://issues.apache.org/jira/browse/CXF-8410
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.4.1
>            Reporter: Francisco Mateo
>            Priority: Major
>         Attachments: stacktrace.log
>
>
> I'm doing a POC using clients generated from wsdl2java and Spring Webflux.
> When I enable [BlockHound|https://github.com/reactor/BlockHound] to check for 
> any blocking calls, the logger from HTTPTransportFactory blocks: 
> [https://github.com/apache/cxf/blob/cxf-3.4.2/rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPTransportFactory.java#L71]
> From debugging, when the logger is initialized, it attempts to load 
> [https://github.com/apache/cxf/blob/cxf-3.4.2/rt/transports/http/src/main/java/org/apache/cxf/transport/http/Messages.properties]
> Loading that file from the containing JAR via ResourceBundle is a blocking 
> operation as far as I can tell.
> My expectation is that when I use an async method from the generated client, 
> there should not be any blocking calls made.
> I've created a sample project and a failing test that showcases the issue: 
> [https://github.com/ciscoo/cxf-blockhound-webflux]
> I've also attached the stacktrace as well which shows the blocking call.



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

Reply via email to