The illegal key size error is almost certainly due to the length of the
keystore/truststore password, but the ideal solution is not to decrease the
password length, but rather to either install the Unlimited Strength
Jurisdiction Policy files if possible, and/or switch to using a JKS keystore
Thanks for the pointer, Aldrin. I learned something new today :)
Sounds like you all have a great handle on this.
/me goes back to lurking
Aldrin Piri wrote:
I think with some of the general ideas we discussed, we are tracking
appropriately with currently accepted guidance. Of particular note
Aldrin Piri wrote
> Currently, NIFI_HOME is determined via the physical location of the script
> and thus the reason why it is picking up the other path. Typically, the
> bin directory is not one that is suggested to be configured external to
> the
> distribution in the interest of facilitating
I think with some of the general ideas we discussed, we are tracking
appropriately with currently accepted guidance. Of particular note is our
discussed terms of tagging/versions of the images that would be created
exclusively and solely with community releases.
I base this interpretation off
Hello,
Currently, NIFI_HOME is determined via the physical location of the script
and thus the reason why it is picking up the other path. Typically, the
bin directory is not one that is suggested to be configured external to the
distribution in the interest of facilitating upgrade processes.
I
NiFi 1.1.0, Linux Fedora
$ java -version
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)
The tar is installed in one place, owned by a privileged user. Another
location is owned by another user and the
I notice that the server takes a minute or so to come up after running
nifi.sh start. I think the first few times I tried running nifi, I tried
connecting to the server immediately after running nifi.sh. Obviously I
couldn't connect as the server wasn't up yet. Maybe I tried to rerun the
script
Thanks for pointing that out Oleg. I'll see what's occupying that port.
Pushkar
On Mon, Jan 9, 2017 at 8:10 PM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Pushkar
>
> It appears that something is running on port 8080 so Jetty can not start.
> You can see at the bottom of the log
Pushkar
It appears that something is running on port 8080 so Jetty can not start. You
can see at the bottom of the log the following (see below)
1.
2017-01-09 17:24:23,606 WARN [main] org.apache.nifi.web.server.JettyServer
Failed to start web server... shutting down.
2.
Oleg
I've pasted the app log here http://pastebin.com/YXkEvNZJ
and the bootstrap log here http://pastebin.com/iPJeJvwX.
I built the project using 'maven clean install' (after setting
MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=128m" because of OutOfMemory
exceptions).
Then I extracted the
Toivo,
I'm guessing the original DBCPService API only has getConnection()
because that was all that was really needed by the processors at the
time, and/or to keep more control over the DataSource object (for
example, the controller service's shutdown() method closes the
DataSource). Having said
Pushkar
Any chance you can look and provide relevant logs? You can find them in the
/log directory.
Also, could you please be more specific as to what directions did you follow.
Just want to make sure that if there are any issues with documentation it is
corrected.
Cheers
Oleg
> On Jan 9,
Hi,
I'm installing NiFi on my arch linux machine following the instructions in
https://github.com/apache/nifi.
After I built the project, I executed the NiFi startup script and tried
connecting to the local server but I got a 404 error with the following
message.
HTTP ERROR: 404
Problem
Spring JdbcTemplate, SimpleJdbcCall and DataSource
Does anybody use Spring JdbcTemplate, SimpleJdbcCall?
Both take DataSource constructor parameeter and not Connection.
And later when SimpleJdbcCall (or JdbcTemplate) need Connection, it will ask
it from DataSource and release afterwards.
14 matches
Mail list logo