Member since
07-25-2022
8
Posts
3
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
85 | 04-04-2024 08:45 AM |
04-17-2024
02:41 PM
1 Kudo
Thank you @MattWho Your recommendation worked for me. I have updated bootstrap.conf file in nifi. Was able to successfully enable DB controller service and persist data into Ignite database from Nifi. Details: Copied jvm parameters available in the file \apache-ignite-2.16.0-bin\bin\include\jvmdefaults.sh to \nifi-2.0.0-M2\conf\bootstrap.conf file Here is the format and exact list of java arguments added in nifi bootstrap java.arg.21=--add-opens=java.base/jdk.internal.access=ALL-UNNAMED
java.arg.22=--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED
java.arg.23=--add-opens=java.base/sun.nio.ch=ALL-UNNAMED
java.arg.24=--add-opens=java.base/sun.util.calendar=ALL-UNNAMED
java.arg.25=--add-opens=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
java.arg.26=--add-opens=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
java.arg.27=--add-opens=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED
java.arg.28=--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED
java.arg.29=--add-opens=java.base/java.io=ALL-UNNAMED
java.arg.30=--add-opens=java.base/java.nio=ALL-UNNAMED
java.arg.31=--add-opens=java.base/java.net=ALL-UNNAMED
java.arg.32=--add-opens=java.base/java.util=ALL-UNNAMED
java.arg.33=--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
java.arg.34=--add-opens=java.base/java.util.concurrent.locks=ALL-UNNAMED
java.arg.35=--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED
java.arg.36=--add-opens=java.base/java.lang=ALL-UNNAMED
java.arg.37=--add-opens=java.base/java.lang.invoke=ALL-UNNAMED
java.arg.38=--add-opens=java.base/java.math=ALL-UNNAMED
java.arg.39=--add-opens=java.sql/java.sql=ALL-UNNAMED
java.arg.40=--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
java.arg.41=--add-opens=java.base/java.time=ALL-UNNAMED
java.arg.42=--add-opens=java.base/java.text=ALL-UNNAMED
java.arg.43=--add-opens=java.management/sun.management=ALL-UNNAMED
java.arg.44=--add-opens=java.desktop/java.awt.font=ALL-UNNAMED We just need to make sure java.arg.<> numbers are unused in the bootstrap file that we are working on. Thanks again!
... View more
04-17-2024
10:55 AM
@MattWho Here is the log from nifi-app.log 2024-04-17 12:50:13,061 ERROR [Timer-Driven Process Thread-2] o.a.n.c.s.StandardControllerServiceNode StandardControllerServiceNode[service=DBCPConnectionPool[id=025a6b87-e362-3761-5695-a2871b444c4b], name=Ignite-db-localhost, active=true] Failed to invoke @OnEnabled method
java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.dbcp2.BasicDataSource
at org.apache.nifi.dbcp.AbstractDBCPConnectionPool.onConfigured(AbstractDBCPConnectionPool.java:139)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:145)
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:133)
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:78)
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:55)
at org.apache.nifi.controller.service.StandardControllerServiceNode$2.run(StandardControllerServiceNode.java:655)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.NoClassDefFoundError: Could not initialize class org.apache.ignite.IgniteJdbcThinDriver [in thread "Timer-Driven Process Thread-2"]
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:534)
at java.base/java.lang.Class.forName(Class.java:513)
at java.sql/java.sql.DriverManager.isDriverAllowed(DriverManager.java:559)
at java.sql/java.sql.DriverManager.isDriverAllowed(DriverManager.java:551)
at java.sql/java.sql.DriverManager.getDrivers(DriverManager.java:452)
at java.sql/java.sql.DriverManager.getDrivers(DriverManager.java:429)
at org.apache.commons.dbcp2.BasicDataSource.<clinit>(BasicDataSource.java:75)
... 15 common frames omitted
... View more
04-16-2024
01:34 PM
@Jim_Steinebrey @MattWho Thanks for your response. As mentioned, I have created another folder "thirdparty_lib" and updated the new location of jar file in "Database Driver Location(s)" field. I am still getting the same error. Please advise.
... View more
04-15-2024
04:11 PM
1 Kudo
@ckumar Yes I've placed ignite-core-2.16.0.jar file in nifi lib directory.
... View more
04-04-2024
03:02 PM
1 Kudo
Hi, I have Nifi 2.0-M2 and Apache Ignite 2.16 database running on my localhost. http://localhost:8443/nifi jdbc:ignite:thin://localhost:10800 (I am able to connect to Ignite localhost db from Dbeaver) I have copied ignite-core-2.16.0.jar file to nifi lib directory (before starting nifi) and tried to create DBCPConnectionPool controller service in Nifi to connect to Ignite database. DB Controller service returns the below error. Failed to invoke @OnEnabled method: java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.dbcp2.BasicDataSource - Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.NoClassDefFoundError: Could not initialize class org.apache.ignite.IgniteJdbcThinDriver [in thread "Timer-Driven Process Thread-10"] Can you let me know what am I missing here? Please let me know if more details are required. Screenshot of DB controller service
... View more
Labels:
- Labels:
-
Apache NiFi
04-04-2024
08:45 AM
This issue was resolved after upgrading Nifi to 2.0-M2
... View more
01-09-2024
03:15 PM
We have upgraded nifi to 2.0M1 recently. It was clean install and process groups were imported from Nifi-registry. All InvokeHttp processors remained invalid and the reason seems to be that the SSL context service attribute was not recognized. Please refer the attached screenshot. When I manually selected right SSL context controller service from drop down list, InvokeHttp processor becomes valid and and another observation here is: the action of setting right SSL context service is not treated as code change and process group still shows green. Please advise if there is any work around to fix this problem. Currently we are manually setting controller service after automated deployment pipeline is complete. To isolate the issue, we have tried to replicate by creating simple process group with InvokeHttp processor. Downloaded definition and re-imported onto Nifi canvas. Issue was reproduced. This might be a bug in Nifi 2.0M1. Please advise.
... View more
Labels:
- Labels:
-
Apache NiFi
07-25-2022
03:01 PM
I have gone through data enrichment article using Simple KV lookup service. SimpleKeyValueLookupService reference url https://community.cloudera.com/t5/Community-Articles/Data-flow-enrichment-with-NiFi-part-1-LookupRecord-processor/ta-p/246940 Can the same be achieved by using RestLookupService ? If yes, what format of data should the api return (equivalent to key value pairs)?
... View more
Labels:
- Labels:
-
Apache NiFi