Re: [CANCEL][VOTE] Release ManifoldCF 2.26, RC0
It is possible that Solr needs the older version of Zookeeper.
If you swap out the current one and replace it with the one the version of
SolrJ we use references, does the test pass then? If it does, we're going
to have to figure out how to address the fact that we have two connectors
that each depend on a different version of zookeeper. But first please let
me know if it works. I'll suggest a way of reconciling these once I know.
Karl
On Thu, Oct 26, 2023 at 7:37 PM Mingchun Zhao
wrote:
> I ran the ant test using Guylaine's patch and the Kafka IT test passed!
> However, the Solr IT test failure still occurs.
> ```
> run-IT-HSQLDB:
> [junit] Testsuite:
> org.apache.manifoldcf.agents.output.solr.tests.SolrCrawlHSQLDBIT
> [junit] Configuration file successfully read
> [junit] [main] INFO org.eclipse.jetty.util.log - Logging initialized
> @6974ms to org.eclipse.jetty.util.log.Slf4jLog
> [junit] [main] INFO org.eclipse.jetty.server.Server -
> jetty-9.4.48.v20220622; built: 2022-06-21T20:42:25.880Z; git:
> 6b67c5719d1f4371b33655ff2d047d24e171e49a; jvm 11.0.11+9
> [junit] [main] INFO org.eclipse.jetty.server.session -
> DefaultSessionIdManager workerName=node0
> [junit] [main] INFO org.eclipse.jetty.server.session - No
> SessionScavenger set, using defaults
> [junit] [main] INFO org.eclipse.jetty.server.session - node0 Scavenging
> every 66ms
> [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Started o.e.j.w.WebAppContext@4565a70a{ManifoldCF Crawler
>
> Interface,/mcf-crawler-ui,file:///private/var/folders/zh/mx4q_qh93cv6jtp13ht8b1frgn/T/jetty-0_0_0_0-8346-mcf-crawler-ui_war-_mcf-crawler-ui-any-3250496980318085250/webapp/,AVAILABLE}{/Users/zhaomingchun/ManifoldCF/guylaine/manifoldcf/dist/web/war/mcf-crawler-ui.war}
> [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Started o.e.j.w.WebAppContext@a0a9fa5{ManifoldCF Authorities API
>
> Webapp,/mcf-authority-service,file:///private/var/folders/zh/mx4q_qh93cv6jtp13ht8b1frgn/T/jetty-0_0_0_0-8346-mcf-authority-service_war-_mcf-authority-service-any-6182863812882423778/webapp/,AVAILABLE}{/Users/zhaomingchun/ManifoldCF/guylaine/manifoldcf/dist/web/war/mcf-authority-service.war}
> [junit] Creating mock service
> [junit] Mock service created
> [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Started o.e.j.w.WebAppContext@15723761{ManifoldCF General API
>
> Webapp,/mcf-api-service,file:///private/var/folders/zh/mx4q_qh93cv6jtp13ht8b1frgn/T/jetty-0_0_0_0-8346-mcf-api-service_war-_mcf-api-service-any-14231646742487500933/webapp/,AVAILABLE}{/Users/zhaomingchun/ManifoldCF/guylaine/manifoldcf/dist/web/war/mcf-api-service.war}
> [junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
> Started ServerConnector@6f63c44f{HTTP/1.1, (http/1.1)}{0.0.0.0:8346}
> [junit] [main] INFO org.eclipse.jetty.server.Server - Started @9062ms
> [junit] [main] INFO org.eclipse.jetty.server.Server -
> jetty-9.4.48.v20220622; built: 2022-06-21T20:42:25.880Z; git:
> 6b67c5719d1f4371b33655ff2d047d24e171e49a; jvm 11.0.11+9
> [junit] [main] INFO org.eclipse.jetty.server.session -
> DefaultSessionIdManager workerName=node0
> [junit] [main] INFO org.eclipse.jetty.server.session - No
> SessionScavenger set, using defaults
> [junit] [main] INFO org.eclipse.jetty.server.session - node0 Scavenging
> every 66ms
> [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Started o.e.j.s.ServletContextHandler@6b2e0f78{/solr,null,AVAILABLE}
> [junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
> Started ServerConnector@3ec2ecea{HTTP/1.1, (http/1.1)}{0.0.0.0:8188}
> [junit] [main] INFO org.eclipse.jetty.server.Server - Started @9071ms
> [junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
> Stopped ServerConnector@3ec2ecea{HTTP/1.1, (http/1.1)}{0.0.0.0:8188}
> [junit] [main] INFO org.eclipse.jetty.server.session - node0 Stopped
> scavenging
> [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Stopped o.e.j.s.ServletContextHandler@6b2e0f78{/solr,null,STOPPED}
> ```
>
> 2023年10月27日(金) 0:35 Guylaine BASSETTE :
>
> > Hi Mingchun,
> >
> > If you want, you can access my repository directly:
> > https://github.com/guylaine-bassette/manifoldcf
> >
> > I have made a Fork of Github ManifoldCF. Use the branch:
> > Fix-kafka-IT-tests. It is up to date with the last trunk commit.
> >
> > Le 26/10/2023 à 17:13, Mingchun Zhao a écrit :
> > > Sorry, there was a typo: track -> trunk
> > >
> > > 2023年10月27日(金) 0:12 Mingchun Zhao:
> > >
> > >> Hi Guylaine, Thanks!
> > >> Was your patch based on the latest track? Unfortunately, I was unable
> to
> > >> apply your patch in my environment.
> > >>
> > >> 2023年10月26日(木) 20:44 Guylaine BASSETTE<
> guylaine.basse...@francelabs.com
> > >:
> > >>
> > >>> Hello Mingchun,
> > >>>
> > >>> As mentioned in my previous e-mail to Karl, my
Re: [CANCEL][VOTE] Release ManifoldCF 2.26, RC0
I ran the ant test using Guylaine's patch and the Kafka IT test passed!
However, the Solr IT test failure still occurs.
```
run-IT-HSQLDB:
[junit] Testsuite:
org.apache.manifoldcf.agents.output.solr.tests.SolrCrawlHSQLDBIT
[junit] Configuration file successfully read
[junit] [main] INFO org.eclipse.jetty.util.log - Logging initialized
@6974ms to org.eclipse.jetty.util.log.Slf4jLog
[junit] [main] INFO org.eclipse.jetty.server.Server -
jetty-9.4.48.v20220622; built: 2022-06-21T20:42:25.880Z; git:
6b67c5719d1f4371b33655ff2d047d24e171e49a; jvm 11.0.11+9
[junit] [main] INFO org.eclipse.jetty.server.session -
DefaultSessionIdManager workerName=node0
[junit] [main] INFO org.eclipse.jetty.server.session - No
SessionScavenger set, using defaults
[junit] [main] INFO org.eclipse.jetty.server.session - node0 Scavenging
every 66ms
[junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
Started o.e.j.w.WebAppContext@4565a70a{ManifoldCF Crawler
Interface,/mcf-crawler-ui,file:///private/var/folders/zh/mx4q_qh93cv6jtp13ht8b1frgn/T/jetty-0_0_0_0-8346-mcf-crawler-ui_war-_mcf-crawler-ui-any-3250496980318085250/webapp/,AVAILABLE}{/Users/zhaomingchun/ManifoldCF/guylaine/manifoldcf/dist/web/war/mcf-crawler-ui.war}
[junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
Started o.e.j.w.WebAppContext@a0a9fa5{ManifoldCF Authorities API
Webapp,/mcf-authority-service,file:///private/var/folders/zh/mx4q_qh93cv6jtp13ht8b1frgn/T/jetty-0_0_0_0-8346-mcf-authority-service_war-_mcf-authority-service-any-6182863812882423778/webapp/,AVAILABLE}{/Users/zhaomingchun/ManifoldCF/guylaine/manifoldcf/dist/web/war/mcf-authority-service.war}
[junit] Creating mock service
[junit] Mock service created
[junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
Started o.e.j.w.WebAppContext@15723761{ManifoldCF General API
Webapp,/mcf-api-service,file:///private/var/folders/zh/mx4q_qh93cv6jtp13ht8b1frgn/T/jetty-0_0_0_0-8346-mcf-api-service_war-_mcf-api-service-any-14231646742487500933/webapp/,AVAILABLE}{/Users/zhaomingchun/ManifoldCF/guylaine/manifoldcf/dist/web/war/mcf-api-service.war}
[junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
Started ServerConnector@6f63c44f{HTTP/1.1, (http/1.1)}{0.0.0.0:8346}
[junit] [main] INFO org.eclipse.jetty.server.Server - Started @9062ms
[junit] [main] INFO org.eclipse.jetty.server.Server -
jetty-9.4.48.v20220622; built: 2022-06-21T20:42:25.880Z; git:
6b67c5719d1f4371b33655ff2d047d24e171e49a; jvm 11.0.11+9
[junit] [main] INFO org.eclipse.jetty.server.session -
DefaultSessionIdManager workerName=node0
[junit] [main] INFO org.eclipse.jetty.server.session - No
SessionScavenger set, using defaults
[junit] [main] INFO org.eclipse.jetty.server.session - node0 Scavenging
every 66ms
[junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
Started o.e.j.s.ServletContextHandler@6b2e0f78{/solr,null,AVAILABLE}
[junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
Started ServerConnector@3ec2ecea{HTTP/1.1, (http/1.1)}{0.0.0.0:8188}
[junit] [main] INFO org.eclipse.jetty.server.Server - Started @9071ms
[junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
Stopped ServerConnector@3ec2ecea{HTTP/1.1, (http/1.1)}{0.0.0.0:8188}
[junit] [main] INFO org.eclipse.jetty.server.session - node0 Stopped
scavenging
[junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
Stopped o.e.j.s.ServletContextHandler@6b2e0f78{/solr,null,STOPPED}
```
2023年10月27日(金) 0:35 Guylaine BASSETTE :
> Hi Mingchun,
>
> If you want, you can access my repository directly:
> https://github.com/guylaine-bassette/manifoldcf
>
> I have made a Fork of Github ManifoldCF. Use the branch:
> Fix-kafka-IT-tests. It is up to date with the last trunk commit.
>
> Le 26/10/2023 à 17:13, Mingchun Zhao a écrit :
> > Sorry, there was a typo: track -> trunk
> >
> > 2023年10月27日(金) 0:12 Mingchun Zhao:
> >
> >> Hi Guylaine, Thanks!
> >> Was your patch based on the latest track? Unfortunately, I was unable to
> >> apply your patch in my environment.
> >>
> >> 2023年10月26日(木) 20:44 Guylaine BASSETTE >:
> >>
> >>> Hello Mingchun,
> >>>
> >>> As mentioned in my previous e-mail to Karl, my patch contained other
> >>> files to be updated. I don't know why they don't have been taken into
> >>> account, but would you be interested in trying my patch? I have fixed
> the
> >>> spots I had missed... (joint with this mail)
> >>>
> >>> With these modifications I went through all tests of kafka.
> >>> Le 26/10/2023 à 03:47, Mingchun Zhao a écrit :
> >>>
> >>> Hi there, Allow me to share my `ant test` result using the latest
> Github
> >>> trunk.
> >>> I got a lot of `Broker may not be available` warnings in the Kafka IT
> test
> >>> and it eventually failed.
> >>>
> >>> ```
> >>> ...
> >>> [junit] [kafka-producer-network-thread | producer-3] INFO
> >>>
Re: [CANCEL][VOTE] Release ManifoldCF 2.26, RC0
Hi Mingchun, If you want, you can access my repository directly: https://github.com/guylaine-bassette/manifoldcf I have made a Fork of Github ManifoldCF. Use the branch: Fix-kafka-IT-tests. It is up to date with the last trunk commit. Le 26/10/2023 à 17:13, Mingchun Zhao a écrit : Sorry, there was a typo: track -> trunk 2023年10月27日(金) 0:12 Mingchun Zhao: Hi Guylaine, Thanks! Was your patch based on the latest track? Unfortunately, I was unable to apply your patch in my environment. 2023年10月26日(木) 20:44 Guylaine BASSETTE: Hello Mingchun, As mentioned in my previous e-mail to Karl, my patch contained other files to be updated. I don't know why they don't have been taken into account, but would you be interested in trying my patch? I have fixed the spots I had missed... (joint with this mail) With these modifications I went through all tests of kafka. Le 26/10/2023 à 03:47, Mingchun Zhao a écrit : Hi there, Allow me to share my `ant test` result using the latest Github trunk. I got a lot of `Broker may not be available` warnings in the Kafka IT test and it eventually failed. ``` ... [junit] [kafka-producer-network-thread | producer-3] INFO org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] Node 0 disconnected. [junit] [kafka-producer-network-thread | producer-3] WARN org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] Connection to node 0 (/192.168.10.103:9092) could not be established. Broker may not be available. [junit] [kafka-producer-network-thread | producer-1] INFO org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Node 0 disconnected. [junit] [kafka-producer-network-thread | producer-1] WARN org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Connection to node 0 (/192.168.10.103:9092) could not be established. Broker may not be available. [junit] [kafka-producer-network-thread | producer-2] INFO org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] Node 0 disconnected. [junit] [kafka-producer-network-thread | producer-2] WARN org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] Connection to node 0 (/192.168.10.103:9092) could not be established. Broker may not be available. [junit] [kafka-producer-network-thread | producer-3] INFO org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] Node 0 disconnected. [junit] [kafka-producer-network-thread | producer-3] WARN org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] Connection to node 0 (/192.168.10.103:9092) could not be established. Broker may not be available. [junit] - --- [junit] Testcase: sanityCheck(org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT): Caused an ERROR [junit] ManifoldCF did not terminate in the allotted time of 12 milliseconds [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: ManifoldCF did not terminate in the allotted time of 12 milliseconds [junit] at org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT.waitJobInactive(APISanityHSQLDBIT.java:289) [junit] at org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT.sanityCheck(APISanityHSQLDBIT.java:177) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [junit] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] [junit] BUILD FAILED /Users/zhaomingchun/ManifoldCF/manifoldcf/build.xml:517: The following error occurred while executing this line: /Users/zhaomingchun/ManifoldCF/manifoldcf/build.xml:471: The following error occurred while executing this line: /Users/zhaomingchun/ManifoldCF/manifoldcf/dist/connector-build.xml:1104: Test org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT failed Total time: 38 minutes 13 seconds ``` 2023年10月26日(木) 5:42 Karl Wright : I see you have committed this. You missed a few spots; the extra jar was mentioned in multiple places. I committed another fix to correct that. Karl On Wed, Oct 25, 2023 at 10:46 AM Guylaine BASSETTE wrote: Hello Karl, Thank you very much for this update! I have tested your suggestions and kafka ITs tests ended successfully. :-) Here you can find the patch. My only doubt is this warning I had in some parts of the kafka test: ``` [junit] [Controller-0-to-broker-0-send-thread] INFO org.apache.kafka.clients.NetworkClient - [Controller id=0, targetBrokerId=0] Node 0 disconnected. [junit] [Controller-0-to-broker-0-send-thread] WARN org.apache.kafka.clients.NetworkClient - [Controller id=0, targetBrokerId=0] Connection to node 0 (guylaine-virtual-machine/127.0.1.1:9092) could not be established. Broker may not be
Re: [CANCEL][VOTE] Release ManifoldCF 2.26, RC0
Sorry, there was a typo: track -> trunk 2023年10月27日(金) 0:12 Mingchun Zhao : > Hi Guylaine, Thanks! > Was your patch based on the latest track? Unfortunately, I was unable to > apply your patch in my environment. > > 2023年10月26日(木) 20:44 Guylaine BASSETTE : > >> Hello Mingchun, >> >> As mentioned in my previous e-mail to Karl, my patch contained other >> files to be updated. I don't know why they don't have been taken into >> account, but would you be interested in trying my patch? I have fixed the >> spots I had missed... (joint with this mail) >> >> With these modifications I went through all tests of kafka. >> Le 26/10/2023 à 03:47, Mingchun Zhao a écrit : >> >> Hi there, Allow me to share my `ant test` result using the latest Github >> trunk. >> I got a lot of `Broker may not be available` warnings in the Kafka IT test >> and it eventually failed. >> >> ``` >> ... >> [junit] [kafka-producer-network-thread | producer-3] INFO >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] >> Node 0 disconnected. >> [junit] [kafka-producer-network-thread | producer-3] WARN >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] >> Connection to node 0 (/192.168.10.103:9092) could not be established. >> Broker may not be available. >> [junit] [kafka-producer-network-thread | producer-1] INFO >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] >> Node 0 disconnected. >> [junit] [kafka-producer-network-thread | producer-1] WARN >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] >> Connection to node 0 (/192.168.10.103:9092) could not be established. >> Broker may not be available. >> [junit] [kafka-producer-network-thread | producer-2] INFO >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] >> Node 0 disconnected. >> [junit] [kafka-producer-network-thread | producer-2] WARN >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] >> Connection to node 0 (/192.168.10.103:9092) could not be established. >> Broker may not be available. >> [junit] [kafka-producer-network-thread | producer-3] INFO >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] >> Node 0 disconnected. >> [junit] [kafka-producer-network-thread | producer-3] WARN >> org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] >> Connection to node 0 (/192.168.10.103:9092) could not be established. >> Broker may not be available. >> [junit] - --- >> [junit] Testcase: >> sanityCheck(org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT): >> Caused an ERROR >> [junit] ManifoldCF did not terminate in the allotted time of 12 >> milliseconds >> [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: >> ManifoldCF did not terminate in the allotted time of 12 milliseconds >> [junit] at >> org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT.waitJobInactive(APISanityHSQLDBIT.java:289) >> [junit] at >> org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT.sanityCheck(APISanityHSQLDBIT.java:177) >> [junit] at >> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native >> Method) >> [junit] at >> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> [junit] at >> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> [junit] >> [junit] >> >> BUILD FAILED >> /Users/zhaomingchun/ManifoldCF/manifoldcf/build.xml:517: The following >> error occurred while executing this line: >> /Users/zhaomingchun/ManifoldCF/manifoldcf/build.xml:471: The following >> error occurred while executing this line: >> /Users/zhaomingchun/ManifoldCF/manifoldcf/dist/connector-build.xml:1104: >> Test org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT failed >> >> Total time: 38 minutes 13 seconds >> ``` >> >> >> 2023年10月26日(木) 5:42 Karl Wright : >> >> >> I see you have committed this. You missed a few spots; the extra jar was >> mentioned in multiple places. I committed another fix to correct that. >> >> Karl >> >> >> On Wed, Oct 25, 2023 at 10:46 AM Guylaine BASSETTE >> wrote: >> >> >> Hello Karl, >> >> Thank you very much for this update! I have tested your suggestions and >> kafka ITs tests ended successfully. :-) >> >> Here you can find the patch. >> >> My only doubt is this warning I had in some parts of the kafka test: >> >> ``` >> >> [junit] [Controller-0-to-broker-0-send-thread] INFO >> org.apache.kafka.clients.NetworkClient - [Controller id=0, >> targetBrokerId=0] Node 0 disconnected. >> [junit] [Controller-0-to-broker-0-send-thread] WARN >> org.apache.kafka.clients.NetworkClient - [Controller id=0, >> targetBrokerId=0] Connection to node 0 >> (guylaine-virtual-machine/127.0.1.1:9092) could not be established. Broker >>
Re: [CANCEL][VOTE] Release ManifoldCF 2.26, RC0
Hi Guylaine, Thanks! Was your patch based on the latest track? Unfortunately, I was unable to apply your patch in my environment. 2023年10月26日(木) 20:44 Guylaine BASSETTE : > Hello Mingchun, > > As mentioned in my previous e-mail to Karl, my patch contained other files > to be updated. I don't know why they don't have been taken into account, > but would you be interested in trying my patch? I have fixed the spots I > had missed... (joint with this mail) > > With these modifications I went through all tests of kafka. > Le 26/10/2023 à 03:47, Mingchun Zhao a écrit : > > Hi there, Allow me to share my `ant test` result using the latest Github > trunk. > I got a lot of `Broker may not be available` warnings in the Kafka IT test > and it eventually failed. > > ``` > ... > [junit] [kafka-producer-network-thread | producer-3] INFO > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] > Node 0 disconnected. > [junit] [kafka-producer-network-thread | producer-3] WARN > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] > Connection to node 0 (/192.168.10.103:9092) could not be established. > Broker may not be available. > [junit] [kafka-producer-network-thread | producer-1] INFO > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] > Node 0 disconnected. > [junit] [kafka-producer-network-thread | producer-1] WARN > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] > Connection to node 0 (/192.168.10.103:9092) could not be established. > Broker may not be available. > [junit] [kafka-producer-network-thread | producer-2] INFO > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] > Node 0 disconnected. > [junit] [kafka-producer-network-thread | producer-2] WARN > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] > Connection to node 0 (/192.168.10.103:9092) could not be established. > Broker may not be available. > [junit] [kafka-producer-network-thread | producer-3] INFO > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] > Node 0 disconnected. > [junit] [kafka-producer-network-thread | producer-3] WARN > org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-3] > Connection to node 0 (/192.168.10.103:9092) could not be established. > Broker may not be available. > [junit] - --- > [junit] Testcase: > sanityCheck(org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT): > Caused an ERROR > [junit] ManifoldCF did not terminate in the allotted time of 12 > milliseconds > [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: > ManifoldCF did not terminate in the allotted time of 12 milliseconds > [junit] at > org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT.waitJobInactive(APISanityHSQLDBIT.java:289) > [junit] at > org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT.sanityCheck(APISanityHSQLDBIT.java:177) > [junit] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [junit] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [junit] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [junit] > [junit] > > BUILD FAILED > /Users/zhaomingchun/ManifoldCF/manifoldcf/build.xml:517: The following > error occurred while executing this line: > /Users/zhaomingchun/ManifoldCF/manifoldcf/build.xml:471: The following > error occurred while executing this line: > /Users/zhaomingchun/ManifoldCF/manifoldcf/dist/connector-build.xml:1104: > Test org.apache.manifoldcf.agents.output.kafka.APISanityHSQLDBIT failed > > Total time: 38 minutes 13 seconds > ``` > > > 2023年10月26日(木) 5:42 Karl Wright : > > > I see you have committed this. You missed a few spots; the extra jar was > mentioned in multiple places. I committed another fix to correct that. > > Karl > > > On Wed, Oct 25, 2023 at 10:46 AM Guylaine BASSETTE > wrote: > > > Hello Karl, > > Thank you very much for this update! I have tested your suggestions and > kafka ITs tests ended successfully. :-) > > Here you can find the patch. > > My only doubt is this warning I had in some parts of the kafka test: > > ``` > > [junit] [Controller-0-to-broker-0-send-thread] INFO > org.apache.kafka.clients.NetworkClient - [Controller id=0, > targetBrokerId=0] Node 0 disconnected. > [junit] [Controller-0-to-broker-0-send-thread] WARN > org.apache.kafka.clients.NetworkClient - [Controller id=0, > targetBrokerId=0] Connection to node 0 > (guylaine-virtual-machine/127.0.1.1:9092) could not be established. Broker > may not be available. > [junit] [Controller-0-to-broker-0-send-thread] WARN > kafka.controller.RequestSendThread - [RequestSendThread controllerId=0] > Controller 0's connection to broker
Re: [CANCEL][VOTE] Release ManifoldCF 2.26, RC0
Oh yes sorry, when I made the patch, I put a bad version of the build.xml. But I see you didn't take the other files I have modified... Is it because they was bad according to you? Le 25/10/2023 à 22:42, Karl Wright a écrit : I see you have committed this. You missed a few spots; the extra jar was mentioned in multiple places. I committed another fix to correct that. Karl On Wed, Oct 25, 2023 at 10:46 AM Guylaine BASSETTE < guylaine.basse...@francelabs.com> wrote: Hello Karl, Thank you very much for this update! I have tested your suggestions and kafka ITs tests ended successfully. :-) Here you can find the patch. My only doubt is this warning I had in some parts of the kafka test: ``` [junit] [Controller-0-to-broker-0-send-thread] INFO org.apache.kafka.clients.NetworkClient - [Controller id=0, targetBrokerId=0] Node 0 disconnected. [junit] [Controller-0-to-broker-0-send-thread] WARN org.apache.kafka.clients.NetworkClient - [Controller id=0, targetBrokerId=0] Connection to node 0 (guylaine-virtual-machine/ 127.0.1.1:9092) could not be established. Broker may not be available. [junit] [Controller-0-to-broker-0-send-thread] WARN kafka.controller.RequestSendThread - [RequestSendThread controllerId=0] Controller 0's connection to broker guylaine-virtual-machine:9092 (id: 0 rack: null) was unsuccessful [junit] java.io.IOException: Connection to guylaine-virtual-machine:9092 (id: 0 rack: null) failed. [junit] at org.apache.kafka.clients.NetworkClientUtils.awaitReady(NetworkClientUtils.java:70) [junit] at kafka.controller.RequestSendThread.brokerReady(ControllerChannelManager.scala:298) [junit] at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:251) [junit] at org.apache.kafka.server.util.ShutdownableThread.run(ShutdownableThread.java:130) [junit] [Controller-0-to-broker-0-send-thread] INFO org.apache.kafka.clients.NetworkClient - [Controller id=0, targetBrokerId=0] Client requested connection close from node 0 [junit] [controller-event-thread] INFO state.change.logger - [Controller id=0 epoch=2] Sending LeaderAndIsr request to broker 0 with 1 become-leader and 0 become-follower partitions ``` I have also ran an "ant test". It run core-framework and ITs tests until mongoDB connector with this fail: ``` [junit] Testcase: sanityCheck(org.apache.manifoldcf.agents.output.mongodboutput.tests.APISanityHSQLDBIT): Caused an ERROR [junit] Could not start process: [junit] java.lang.RuntimeException: Could not start process: [junit] at de.flapdoodle.embed.mongo.AbstractMongoProcess.onAfterProcessStart(AbstractMongoProcess.java:81) [junit] at de.flapdoodle.embed.process.runtime.AbstractProcess.(AbstractProcess.java:115) [junit] at de.flapdoodle.embed.mongo.AbstractMongoProcess.(AbstractMongoProcess.java:54) [junit] at de.flapdoodle.embed.mongo.MongodProcess.(MongodProcess.java:50) [junit] at de.flapdoodle.embed.mongo.MongodExecutable.start(MongodExecutable.java:44) [junit] at de.flapdoodle.embed.mongo.MongodExecutable.start(MongodExecutable.java:34) [junit] at de.flapdoodle.embed.process.runtime.Executable.start(Executable.java:109) [junit] at org.apache.manifoldcf.agents.output.mongodboutput.tests.BaseITHSQLDB.setUpMongoDB(BaseITHSQLDB.java:72) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [junit] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] [junit] [junit] Testcase: sanityCheck(org.apache.manifoldcf.agents.output.mongodboutput.tests.APISanityHSQLDBIT): Caused an ERROR [junit] null [junit] java.lang.NullPointerException [junit] at org.apache.manifoldcf.agents.output.mongodboutput.tests.APISanityHSQLDBIT.removeTestArea(APISanityHSQLDBIT.java:109) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [junit] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ``` And no more success for the ITs tests of Solr connector... Guylaine Le 25/10/2023 à 12:52, Karl Wright a écrit : I was able to reproduce the problem last night. I believe the cause may well be that we've moved too many dependencies to the framework level. Specifically, I think perhaps only zookeeper and netty should run there, but the Scala library probably needs to run at the same classloader level as the other Scala jars, so it should be moved back into connectors/kafka and removed from framework/build.xml and from build.xml and from connector-build.xml. Sadly
