Re: server-user Digest of: get.24132

2023-07-20 Thread Benoit TELLIER
Hi  Mihai,

Is it possible to provide more details than just IOS users?

Can we identify which request IOS is sending exactly (IMAP syntax) ?

If IOS is submitting an overly complex request then why? Is this a rare case? 
Or not? On whcih conditions does this happens?

Without this information, it is hard to move things forward...

--


Best regards,



Benoit TELLIER



General manager of Linagora VIETNAM.

Product owner for Team-Mail product.

Chairman of the Apache James project.



Mail: btell...@linagora.com

Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)

On Jul 20, 2023 6:41 PM, from Mihai Zamfira Hello,
I understand your opinion and I respect it, but this problem affects 
approximately 30% of the market share of mobile phone users.
 I will try to find a solution.

> On 20 Jul 2023, at 14:15, Benoit TELLIER  wrote:
>
> No this setting of the Lucene search index is not available yet.
>
> We could welcome a contribution on that topic, I believe.
>
> But having restrictive defaults seems like a good idea to me.
>
> --
>
>
> Best regards,
>
>
>
> Benoit TELLIER
>
>
>
> General manager of Linagora VIETNAM.
>
> Product owner for Team-Mail product.
>
> Chairman of the Apache James project.
>
>
>
> Mail: btell...@linagora.com
>
> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
>
>
> On Jul 20, 2023 2:23 PM, from Mihai Zamfira Hi,
> This behavior is specific to the Mail application on iPhone devices. If you 
> can guide me on where to intervene in the Apache James code to add a logger 
> to obtain the requested data.
> However, we cannot modify the client application.
> Regards
>
>>
>>
>> From: Benoit TELLIER 
>> Subject: Re: Lucene "maxClauseCount is set to 1024" error
>> Date: 18 July 2023 at 09:51:38 EEST
>> To: James Users List 
>>
>>
>> Hello,
>>
>> The IMAP clients likely transmit a too complex search query with to=
>> o much clauses and Lucene refuses to execute such a complex query=2E
>>
>> This =
>> is what you want! We want the search engine to be protected from denial of =
>> service attacks: this might have been what you noticed=2E
>>
>> I'm interested b=
>> y the IMAP contextual logs especially the MUA declared by the ID command, t=
>> he exact search query that triggered the error=2E
>>
>> --
>>
>>
>> Best regards,
>>
>>
>>
>> Be=
>> noit TELLIER
>>
>>
>>
>> General manager of Linagora VIETNAM=2E
>>
>> Product owner for T=
>> eam-Mail product=2E
>>
>> Chairman of the Apache James project=2E
>>
>>
>>
>> Mail: btell=
>> ier@linagora=2Ecom
>>
>> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
>>
>>
>> On Jul 1=
>> 8, 2023 12:04 PM, from Mihai Zamfira Hello=2E
>> I use the latest version avai=
>> lable on github of apache james jpa-guice which is integrated with LDAP and=
>> an external rdbms=2E
>> I get the following errors when mobile clients access=
>> the account via IMAP=2E The emails are downloaded to the phone, but in the=
>> log there are errors of the form below=2E
>> I don't know if this is specific=
>> only to the Iphone or not=2E 
>>
>>
>> 07:51:39=2E182 [ERROR] o=2Ea=2Ej=2Ei=2Ep=
>> =2EAbstractMailboxProcessor - Unexpected error during IMAP processing
>> org=
>> =2Eapache=2Elucene=2Esearch=2EBooleanQuery$TooManyClauses: maxClauseCount i=
>> s set to 1024
>>at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd(Boole=
>> anQuery=2Ejava:136)
>>at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd=
>> (BooleanQuery=2Ejava:127)
>>at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esea=
>> rch=2ELuceneMessageSearchIndex=2EcreateUidQuery(LuceneMessageSearchIndex=2E=
>> java:949)
>>at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMess=
>> ageSearchIndex=2EcreateFlagQuery(LuceneMessageSearchIndex=2Ejava:1023)
>>at =
>> org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=
>> =2EcreateQuery(LuceneMessageSearchIndex=2Ejava:1208)
>>at org=2Eapache=2Ejam=
>> es=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=2EsearchMultimap(=
>> LuceneMessageSearchIndex=2Ejava:523)
>>at org=2Eapache=2Ejames=2Emailbox=2El=
>> ucene=2Esearch=2ELuceneMessageSearchIndex=2EdoSearch(LuceneMessageSearchInd=
>> ex=2Ejava:491)
>>at org=2Eapache=2Ejames=2Emailbox=2Estore=2Esearch=2EListen=
>> ingMessageSearchIndex=2Elambda$search$2(ListeningMessageSearchIndex=2Ejava:=
>> 84)
>>at com=2Egithub=2Efge=2Elambdas=2Esupplier=2ESupplierChainer=2Elambda$=
>> sneakyThrow$195(SupplierChainer=2Ejava:74)
>>at java=2Ebase/java=2Eutil=2EOp=
>> tional=2EorElseGet(Optional=2Ejava:369)
>>at org=2Eapache=2Ejames=2Emailbox=
>> =2Estore=2Esearch=2EListeningMessageSearchIndex=2Esearch(ListeningMessageSe=
>> archIndex=2Ejava:84)
>>at org=2Eapache=2Ejames=2Emailbox=2Estore=2EStoreMess=
>> ageManager=2Esearch(StoreMessageManager=2Ejava:837)
>>at org=2Eapache=2Ejame=
>> s=2Emailbox=2Estore=2EStoreMessageManager=2Esearch(StoreMessageManager=2Eja=
>> va:132)
>>at org=2Eapache=2Ejames=2Eimap=2Eprocessor=2ESearchProcessor=2Eper=
>> 

Re: server-user Digest of: get.24132

2023-07-20 Thread Mihai Zamfira
Hello, 
I understand your opinion and I respect it, but this problem affects 
approximately 30% of the market share of mobile phone users.
 I will try to find a solution.

> On 20 Jul 2023, at 14:15, Benoit TELLIER  wrote:
> 
> No this setting of the Lucene search index is not available yet.
> 
> We could welcome a contribution on that topic, I believe.
> 
> But having restrictive defaults seems like a good idea to me.
> 
> --
> 
> 
> Best regards,
> 
> 
> 
> Benoit TELLIER
> 
> 
> 
> General manager of Linagora VIETNAM.
> 
> Product owner for Team-Mail product.
> 
> Chairman of the Apache James project.
> 
> 
> 
> Mail: btell...@linagora.com
> 
> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
> 
> 
> On Jul 20, 2023 2:23 PM, from Mihai Zamfira Hi,
> This behavior is specific to the Mail application on iPhone devices. If you 
> can guide me on where to intervene in the Apache James code to add a logger 
> to obtain the requested data. 
> However, we cannot modify the client application.
> Regards
> 
>> 
>> 
>> From: Benoit TELLIER 
>> Subject: Re: Lucene "maxClauseCount is set to 1024" error
>> Date: 18 July 2023 at 09:51:38 EEST
>> To: James Users List 
>> 
>> 
>> Hello,
>> 
>> The IMAP clients likely transmit a too complex search query with to=
>> o much clauses and Lucene refuses to execute such a complex query=2E
>> 
>> This =
>> is what you want! We want the search engine to be protected from denial of =
>> service attacks: this might have been what you noticed=2E
>> 
>> I'm interested b=
>> y the IMAP contextual logs especially the MUA declared by the ID command, t=
>> he exact search query that triggered the error=2E
>> 
>> --
>> 
>> 
>> Best regards,
>> 
>> 
>> 
>> Be=
>> noit TELLIER
>> 
>> 
>> 
>> General manager of Linagora VIETNAM=2E
>> 
>> Product owner for T=
>> eam-Mail product=2E
>> 
>> Chairman of the Apache James project=2E
>> 
>> 
>> 
>> Mail: btell=
>> ier@linagora=2Ecom
>> 
>> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
>> 
>> 
>> On Jul 1=
>> 8, 2023 12:04 PM, from Mihai Zamfira Hello=2E
>> I use the latest version avai=
>> lable on github of apache james jpa-guice which is integrated with LDAP and=
>> an external rdbms=2E
>> I get the following errors when mobile clients access=
>> the account via IMAP=2E The emails are downloaded to the phone, but in the=
>> log there are errors of the form below=2E
>> I don't know if this is specific=
>> only to the Iphone or not=2E 
>> 
>> 
>> 07:51:39=2E182 [ERROR] o=2Ea=2Ej=2Ei=2Ep=
>> =2EAbstractMailboxProcessor - Unexpected error during IMAP processing
>> org=
>> =2Eapache=2Elucene=2Esearch=2EBooleanQuery$TooManyClauses: maxClauseCount i=
>> s set to 1024
>>at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd(Boole=
>> anQuery=2Ejava:136)
>>at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd=
>> (BooleanQuery=2Ejava:127)
>>at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esea=
>> rch=2ELuceneMessageSearchIndex=2EcreateUidQuery(LuceneMessageSearchIndex=2E=
>> java:949)
>>at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMess=
>> ageSearchIndex=2EcreateFlagQuery(LuceneMessageSearchIndex=2Ejava:1023)
>>at =
>> org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=
>> =2EcreateQuery(LuceneMessageSearchIndex=2Ejava:1208)
>>at org=2Eapache=2Ejam=
>> es=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=2EsearchMultimap(=
>> LuceneMessageSearchIndex=2Ejava:523)
>>at org=2Eapache=2Ejames=2Emailbox=2El=
>> ucene=2Esearch=2ELuceneMessageSearchIndex=2EdoSearch(LuceneMessageSearchInd=
>> ex=2Ejava:491)
>>at org=2Eapache=2Ejames=2Emailbox=2Estore=2Esearch=2EListen=
>> ingMessageSearchIndex=2Elambda$search$2(ListeningMessageSearchIndex=2Ejava:=
>> 84)
>>at com=2Egithub=2Efge=2Elambdas=2Esupplier=2ESupplierChainer=2Elambda$=
>> sneakyThrow$195(SupplierChainer=2Ejava:74)
>>at java=2Ebase/java=2Eutil=2EOp=
>> tional=2EorElseGet(Optional=2Ejava:369)
>>at org=2Eapache=2Ejames=2Emailbox=
>> =2Estore=2Esearch=2EListeningMessageSearchIndex=2Esearch(ListeningMessageSe=
>> archIndex=2Ejava:84)
>>at org=2Eapache=2Ejames=2Emailbox=2Estore=2EStoreMess=
>> ageManager=2Esearch(StoreMessageManager=2Ejava:837)
>>at org=2Eapache=2Ejame=
>> s=2Emailbox=2Estore=2EStoreMessageManager=2Esearch(StoreMessageManager=2Eja=
>> va:132)
>>at org=2Eapache=2Ejames=2Eimap=2Eprocessor=2ESearchProcessor=2Eper=
>> formUidSearch(SearchProcessor=2Ejava:263)
>>at org=2Eapache=2Ejames=2Eimap=
>> =2Eprocessor=2ESearchProcessor=2Elambda$processRequestReactive$2(SearchProc=
>> essor=2Ejava:105)
>>at com=2Egithub=2Efge=2Elambdas=2Efunctions=2EFunctionCh=
>> ainer=2EdoApply(FunctionChainer=2Ejava:20)
>>at com=2Egithub=2Efge=2Elambdas=
>> =2Efunctions=2EThrowingFunction=2Eapply(ThrowingFunction=2Ejava:17)
>>at rea=
>> ctor=2Ecore=2Epublisher=2EMonoFlatMap$FlatMapMain=2EonNext(MonoFlatMap=2Eja=
>> va:132)
>>at reactor=2Ecore=2Epublisher=2EFluxMap$MapSubscriber=2EonNext(Flu=
>> 

Re: server-user Digest of: get.24132

2023-07-20 Thread Benoit TELLIER
No this setting of the Lucene search index is not available yet.

We could welcome a contribution on that topic, I believe.

But having restrictive defaults seems like a good idea to me.

--


Best regards,



Benoit TELLIER



General manager of Linagora VIETNAM.

Product owner for Team-Mail product.

Chairman of the Apache James project.



Mail: btell...@linagora.com

Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)


On Jul 20, 2023 2:23 PM, from Mihai Zamfira Hi,
This behavior is specific to the Mail application on iPhone devices. If you can 
guide me on where to intervene in the Apache James code to add a logger to 
obtain the requested data.
However, we cannot modify the client application.
Regards

>
>
> From: Benoit TELLIER 
> Subject: Re: Lucene "maxClauseCount is set to 1024" error
> Date: 18 July 2023 at 09:51:38 EEST
> To: James Users List 
>
>
> Hello,
>
> The IMAP clients likely transmit a too complex search query with to=
> o much clauses and Lucene refuses to execute such a complex query=2E
>
> This =
> is what you want! We want the search engine to be protected from denial of =
> service attacks: this might have been what you noticed=2E
>
> I'm interested b=
> y the IMAP contextual logs especially the MUA declared by the ID command, t=
> he exact search query that triggered the error=2E
> 
> --
>
>
> Best regards,
>
>
>
> Be=
> noit TELLIER
>
>
>
> General manager of Linagora VIETNAM=2E
>
> Product owner for T=
> eam-Mail product=2E
>
> Chairman of the Apache James project=2E
>
>
>
> Mail: btell=
> ier@linagora=2Ecom
>
> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
>
>
> On Jul 1=
> 8, 2023 12:04 PM, from Mihai Zamfira Hello=2E
> I use the latest version avai=
> lable on github of apache james jpa-guice which is integrated with LDAP and=
> an external rdbms=2E
> I get the following errors when mobile clients access=
> the account via IMAP=2E The emails are downloaded to the phone, but in the=
> log there are errors of the form below=2E
> I don't know if this is specific=
> only to the Iphone or not=2E
>
>
> 07:51:39=2E182 [ERROR] o=2Ea=2Ej=2Ei=2Ep=
> =2EAbstractMailboxProcessor - Unexpected error during IMAP processing
> org=
> =2Eapache=2Elucene=2Esearch=2EBooleanQuery$TooManyClauses: maxClauseCount i=
> s set to 1024
>   at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd(Boole=
> anQuery=2Ejava:136)
>   at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd=
> (BooleanQuery=2Ejava:127)
>   at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esea=
> rch=2ELuceneMessageSearchIndex=2EcreateUidQuery(LuceneMessageSearchIndex=2E=
> java:949)
>   at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMess=
> ageSearchIndex=2EcreateFlagQuery(LuceneMessageSearchIndex=2Ejava:1023)
>   at =
> org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=
> =2EcreateQuery(LuceneMessageSearchIndex=2Ejava:1208)
>   at org=2Eapache=2Ejam=
> es=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=2EsearchMultimap(=
> LuceneMessageSearchIndex=2Ejava:523)
>   at org=2Eapache=2Ejames=2Emailbox=2El=
> ucene=2Esearch=2ELuceneMessageSearchIndex=2EdoSearch(LuceneMessageSearchInd=
> ex=2Ejava:491)
>   at org=2Eapache=2Ejames=2Emailbox=2Estore=2Esearch=2EListen=
> ingMessageSearchIndex=2Elambda$search$2(ListeningMessageSearchIndex=2Ejava:=
> 84)
>   at com=2Egithub=2Efge=2Elambdas=2Esupplier=2ESupplierChainer=2Elambda$=
> sneakyThrow$195(SupplierChainer=2Ejava:74)
>   at java=2Ebase/java=2Eutil=2EOp=
> tional=2EorElseGet(Optional=2Ejava:369)
>   at org=2Eapache=2Ejames=2Emailbox=
> =2Estore=2Esearch=2EListeningMessageSearchIndex=2Esearch(ListeningMessageSe=
> archIndex=2Ejava:84)
>   at org=2Eapache=2Ejames=2Emailbox=2Estore=2EStoreMess=
> ageManager=2Esearch(StoreMessageManager=2Ejava:837)
>   at org=2Eapache=2Ejame=
> s=2Emailbox=2Estore=2EStoreMessageManager=2Esearch(StoreMessageManager=2Eja=
> va:132)
>   at org=2Eapache=2Ejames=2Eimap=2Eprocessor=2ESearchProcessor=2Eper=
> formUidSearch(SearchProcessor=2Ejava:263)
>   at org=2Eapache=2Ejames=2Eimap=
> =2Eprocessor=2ESearchProcessor=2Elambda$processRequestReactive$2(SearchProc=
> essor=2Ejava:105)
>   at com=2Egithub=2Efge=2Elambdas=2Efunctions=2EFunctionCh=
> ainer=2EdoApply(FunctionChainer=2Ejava:20)
>   at com=2Egithub=2Efge=2Elambdas=
> =2Efunctions=2EThrowingFunction=2Eapply(ThrowingFunction=2Ejava:17)
>   at rea=
> ctor=2Ecore=2Epublisher=2EMonoFlatMap$FlatMapMain=2EonNext(MonoFlatMap=2Eja=
> va:132)
>   at reactor=2Ecore=2Epublisher=2EFluxMap$MapSubscriber=2EonNext(Flu=
> xMap=2Ejava:122)
>   at reactor=2Ecore=2Epublisher=2EFluxOnErrorResume$ResumeS=
> ubscriber=2EonNext(FluxOnErrorResume=2Ejava:79)
>   at reactor=2Ecore=2Epublis=
> her=2EFluxSubscribeOnCallable$CallableSubscribeOnSubscription=2Erun(FluxSub=
> scribeOnCallable=2Ejava:251)
>   at reactor=2Ecore=2Escheduler=2ESchedulerTask=
> =2Ecall(SchedulerTask=2Ejava:68)
>   at 

Re: server-user Digest of: get.24132

2023-07-20 Thread Mihai Zamfira
Hi,
This behavior is specific to the Mail application on iPhone devices. If you can 
guide me on where to intervene in the Apache James code to add a logger to 
obtain the requested data. 
However, we cannot modify the client application.
Regards

> 
> 
> From: Benoit TELLIER 
> Subject: Re: Lucene "maxClauseCount is set to 1024" error
> Date: 18 July 2023 at 09:51:38 EEST
> To: James Users List 
> 
> 
> Hello,
> 
> The IMAP clients likely transmit a too complex search query with to=
> o much clauses and Lucene refuses to execute such a complex query=2E
> 
> This =
> is what you want! We want the search engine to be protected from denial of =
> service attacks: this might have been what you noticed=2E
> 
> I'm interested b=
> y the IMAP contextual logs especially the MUA declared by the ID command, t=
> he exact search query that triggered the error=2E
> 
> --
> 
> 
> Best regards,
> 
> 
> 
> Be=
> noit TELLIER
> 
> 
> 
> General manager of Linagora VIETNAM=2E
> 
> Product owner for T=
> eam-Mail product=2E
> 
> Chairman of the Apache James project=2E
> 
> 
> 
> Mail: btell=
> ier@linagora=2Ecom
> 
> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
> 
> 
> On Jul 1=
> 8, 2023 12:04 PM, from Mihai Zamfira Hello=2E
> I use the latest version avai=
> lable on github of apache james jpa-guice which is integrated with LDAP and=
> an external rdbms=2E
> I get the following errors when mobile clients access=
> the account via IMAP=2E The emails are downloaded to the phone, but in the=
> log there are errors of the form below=2E
> I don't know if this is specific=
> only to the Iphone or not=2E 
> 
> 
> 07:51:39=2E182 [ERROR] o=2Ea=2Ej=2Ei=2Ep=
> =2EAbstractMailboxProcessor - Unexpected error during IMAP processing
> org=
> =2Eapache=2Elucene=2Esearch=2EBooleanQuery$TooManyClauses: maxClauseCount i=
> s set to 1024
>   at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd(Boole=
> anQuery=2Ejava:136)
>   at org=2Eapache=2Elucene=2Esearch=2EBooleanQuery=2Eadd=
> (BooleanQuery=2Ejava:127)
>   at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esea=
> rch=2ELuceneMessageSearchIndex=2EcreateUidQuery(LuceneMessageSearchIndex=2E=
> java:949)
>   at org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMess=
> ageSearchIndex=2EcreateFlagQuery(LuceneMessageSearchIndex=2Ejava:1023)
>   at =
> org=2Eapache=2Ejames=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=
> =2EcreateQuery(LuceneMessageSearchIndex=2Ejava:1208)
>   at org=2Eapache=2Ejam=
> es=2Emailbox=2Elucene=2Esearch=2ELuceneMessageSearchIndex=2EsearchMultimap(=
> LuceneMessageSearchIndex=2Ejava:523)
>   at org=2Eapache=2Ejames=2Emailbox=2El=
> ucene=2Esearch=2ELuceneMessageSearchIndex=2EdoSearch(LuceneMessageSearchInd=
> ex=2Ejava:491)
>   at org=2Eapache=2Ejames=2Emailbox=2Estore=2Esearch=2EListen=
> ingMessageSearchIndex=2Elambda$search$2(ListeningMessageSearchIndex=2Ejava:=
> 84)
>   at com=2Egithub=2Efge=2Elambdas=2Esupplier=2ESupplierChainer=2Elambda$=
> sneakyThrow$195(SupplierChainer=2Ejava:74)
>   at java=2Ebase/java=2Eutil=2EOp=
> tional=2EorElseGet(Optional=2Ejava:369)
>   at org=2Eapache=2Ejames=2Emailbox=
> =2Estore=2Esearch=2EListeningMessageSearchIndex=2Esearch(ListeningMessageSe=
> archIndex=2Ejava:84)
>   at org=2Eapache=2Ejames=2Emailbox=2Estore=2EStoreMess=
> ageManager=2Esearch(StoreMessageManager=2Ejava:837)
>   at org=2Eapache=2Ejame=
> s=2Emailbox=2Estore=2EStoreMessageManager=2Esearch(StoreMessageManager=2Eja=
> va:132)
>   at org=2Eapache=2Ejames=2Eimap=2Eprocessor=2ESearchProcessor=2Eper=
> formUidSearch(SearchProcessor=2Ejava:263)
>   at org=2Eapache=2Ejames=2Eimap=
> =2Eprocessor=2ESearchProcessor=2Elambda$processRequestReactive$2(SearchProc=
> essor=2Ejava:105)
>   at com=2Egithub=2Efge=2Elambdas=2Efunctions=2EFunctionCh=
> ainer=2EdoApply(FunctionChainer=2Ejava:20)
>   at com=2Egithub=2Efge=2Elambdas=
> =2Efunctions=2EThrowingFunction=2Eapply(ThrowingFunction=2Ejava:17)
>   at rea=
> ctor=2Ecore=2Epublisher=2EMonoFlatMap$FlatMapMain=2EonNext(MonoFlatMap=2Eja=
> va:132)
>   at reactor=2Ecore=2Epublisher=2EFluxMap$MapSubscriber=2EonNext(Flu=
> xMap=2Ejava:122)
>   at reactor=2Ecore=2Epublisher=2EFluxOnErrorResume$ResumeS=
> ubscriber=2EonNext(FluxOnErrorResume=2Ejava:79)
>   at reactor=2Ecore=2Epublis=
> her=2EFluxSubscribeOnCallable$CallableSubscribeOnSubscription=2Erun(FluxSub=
> scribeOnCallable=2Ejava:251)
>   at reactor=2Ecore=2Escheduler=2ESchedulerTask=
> =2Ecall(SchedulerTask=2Ejava:68)
>   at reactor=2Ecore=2Escheduler=2EScheduler=
> Task=2Ecall(SchedulerTask=2Ejava:28)
>   at java=2Ebase/java=2Eutil=2Econcurre=
> nt=2EFutureTask=2Erun(FutureTask=2Ejava:264)
>   at java=2Ebase/java=2Eutil=2E=
> concurrent=2EScheduledThreadPoolExecutor$ScheduledFutureTask=2Erun(Schedule=
> dThreadPoolExecutor=2Ejava:304)
>   at java=2Ebase/java=2Eutil=2Econcurrent=2E=
> ThreadPoolExecutor=2ErunWorker(ThreadPoolExecutor=2Ejava:1128)
>   at