Structr - which version of Neo4j to use - java

Windows 7, java 8, Neo4j 3.0.0-M03, initial install of structr.
When I first try to run the program I'm getting this error:
SEVERE: Vital service HttpService failed to start: No resource provider available for servlet JsonRestServlet. Aborting
Reading the Google Groups the report is that structr is only good up to 2.2.6 - looking at the Neo4j Release Page 2.2.6 has been skipped - it goes from 2.1.8 to 2.2.8.
My question is what version should I use?
Also - is java 7 still a requirement? Looking at the Oracle website I'm seeing that 7 has been deprecated and won't be patched.

The most recent pre-built versions of Structr are built against and embed Neo4j 2.2.8.
To use with custom Neo4j versions, you can to build your own driver, see https://github.com/structr/structr-neo4j-driver. Should work with any 2.x version of Neo4j.
On the Java side, Java JDK 8 is a requirement.

Related

Pentaho - Unable to create a database connection

When I go to create a Database Connection in Kettle I am getting the exact same errors as in this question: Kettle / Pentaho Data Integration - unable to create a Database Connection (XulException: java.lang.reflect.InvocationTargetException)
org.pentaho.ui.xul.XulException: java.lang.reflect.InvocationTargetException
And after clicking OK there is this message:
General error in dialog
The difference for me being that I seem to be using the correct Java. I have upgraded to PDI 9.1 and according to the documentation Java 8 is still the only supported Java.
My Config:
MacOS 10.15.7 (Catalina)
Pentaho Data Integration (or Kettle) 9.1.0.0-324
Java jdk1.8.0_161.jdk
What else have I tried?
I cleared my cache as described in the comments below.
I updated my SWT as described in this tread: PDI will not start under MacOS Catalina 10.15
I changed my Java 8 build to jkd1.8.0_202.jdk per this thread: Issue while accessing DB Connections- PDI 8

Error linking JNA library on AdoptOpenJDK on MacOS

I am trying to run some JUnit tests over cassandra. But I get the following error:
[08/12/19 10:48:40:411](main)([]) INFO - c.h.c.c.e.EmbeddedCassandra - Starting embedded Cassandra server.
8/12/19 10:48:41:497](main)([]) ERROR - o.a.c.u.NativeLibraryDarwin - Failed to link the C library against JNA. Native methods will be unavailable.
java.lang.UnsatisfiedLinkError: /private/var/folders/ty/wl4gxf352m328101m101hwh40000gn/T/jna--321969061/jna10641195286884112036.tmp: dlopen(/private/var/folders/ty/wl4gxf352m328101m101hwh40000gn/T/jna--321969061/jna10641195286884112036.tmp, 1): no suitable image found. Did find:
/private/var/folders/ty/wl4gxf352m328101m101hwh40000gn/T/jna--321969061/jna10641195286884112036.tmp: code signature in (/private/var/folders/ty/wl4gxf352m328101m101hwh40000gn/T/jna--321969061/jna10641195286884112036.tmp) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
It was running well until I changed to mac mojave and re-setup everything. I think it is an issue related to permissions may be or JNA?
IDE: IntelliJ
Java: AdoptOpenJDK 11.0.4
JNA: 4.2.2
Any kind of help will be highly appreciated!
This is the result of a bug in AdoptOpenJDK jdk-11.0.4+11 on macOS, persisting through 11.2.
It will be fixed in the jdk-11.0.4+11.3 release.
If you can't wait for the new release you can temporarily resolve by downgrading to 11.0.3+7
What version of cassandra unit? Support for java 11 (https://issues.apache.org/jira/browse/CASSANDRA-9608) isn't in until cassandra 4 and I dont think embedded cassandra is setup for that yet

HTTP2 request sample crashes with Jmeter4, Java 10 No Client ALPNProcessors

I am unable to create a HTTP2 request using Jmeter 4.0.
I have installed latest JDK, and HTTP/2 protocol sampler plugin.
I have also observed that: "penJDK8ClientALPNProcessor#e23ec5a not applicable for java 10.0.2"
Tried using Java 9, but I get the same thing.
PS: I already tried adding the JVM_ARGS=...
Complete stack-trace is:
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: No Client ALPNProcessors!
at org.eclipse.jetty.util.FuturePromise.get(FuturePromise.java:138)
at com.blazemeter.jmeter.http2.sampler.HTTP2Connection.connect(HTTP2Connection.java:65)
at com.blazemeter.jmeter.http2.sampler.HTTP2Request.setConnection(HTTP2Request.java:247)
at com.blazemeter.jmeter.http2.sampler.HTTP2Request.sample(HTTP2Request.java:121)
at com.blazemeter.jmeter.http2.sampler.HTTP2Request.sample(HTTP2Request.java:107)
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:490)
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:416)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:250)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalStateException: No Client ALPNProcessors!
at org.eclipse.jetty.alpn.client.ALPNClientConnectionFactory.<init>(ALPNClientConnectionFactory.java:57)
at org.eclipse.jetty.http2.client.HTTP2Client.lambda$doStart$1(HTTP2Client.java:155)
at org.eclipse.jetty.http2.client.HTTP2Client$ClientSelectorManager.newConnection(HTTP2Client.java:438)
at org.eclipse.jetty.io.ManagedSelector.createEndPoint(ManagedSelector.java:222)
at org.eclipse.jetty.io.ManagedSelector.access$1500(ManagedSelector.java:60)
at org.eclipse.jetty.io.ManagedSelector$CreateEndPoint.run(ManagedSelector.java:825)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:754)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:672)
... 1 more
Suppressed: java.lang.IllegalStateException: org.eclipse.jetty.alpn.java.client.OpenJDK8ClientALPNProcessor#e23ec5a not applicable for java 10.0.2
at org.eclipse.jetty.alpn.java.client.OpenJDK8ClientALPNProcessor.init(OpenJDK8ClientALPNProcessor.java:41)
at org.eclipse.jetty.alpn.client.ALPNClientConnectionFactory.<init>(ALPNClientConnectionFactory.java:77)
... 8 more
The default installation of the HTTP/2 Sampler uses the dependencies ...
Install library: http2-client
Install library: jetty-alpn-openjdk8-client
Install library: jetty-alpn-client
Install library: http2-common
Install library: http2-hpack
Install library: jetty-io
Install library: jetty-http
Install library: jetty-util
Install plugin: bzm-http2 1.2
This list of dependencies are invalid for Java 9+.
In particular, the jetty-alpn-openjdk8-client dependency is invalid and not appropriate for Java 9+.
For Java 9+, the jetty-alpn-java-client should be used instead.
History:
Back in the days of Java 8, there was a need to support HTTP/2, which requires the ALPN layers for TLS.
Java 8 had no official support for ALPN, so the Jetty project maintained a JVM -Xbootclasspath/p:<path-to-alpn-boot.jar> replacement of the core SSL layers in the JVM to allow ALPN to be used.
This was a custom API not provided by the JVM itself.
https://www.eclipse.org/jetty/documentation/current/alpn-chapter.html
Other projects outside of Jetty started using this API as well.
When the Java 9 networking discussions started, there was a demand to have ALPN support be baked into the JVM itself.
This effort at openjdk became the official API for ALPN.
This new official API is different then the Java 8 API.
In short, you have to use the appropriate API layer for the JVM you are using.
If you want support for this, please open a new topic on the jmeter-plugins forum (feel free to reference this stackoverflow answer)
Looking into
penJDK8ClientALPNProcessor
my expectation is that you have to use Java 8 SE in order to get the plugin to work.
References:
HTTP/2 - How to get ready for the future
The New HTTP/2 Plugin for JMeter - The Complete Guide
Using jetty 9.4.19.v20190610:
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-alpn-java-client</artifactId>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-alpn-conscrypt-client</artifactId>
</dependency>

Jna Linkage Error : How to solve this error while starting cassandra

I am getting the following error while trying to start cassandra.
My configuration is as follows:
OS:Windows 10
Cassandra:3.11
jdk:1.9
As per JIRA, current latest cassandra 3.11 is still not fully supported for java 1.9. Hence, I would recommend you to try again with java 1.8.

Failed to deploy to Google App Engine because --use_java7 flag has not been set

------------ Deploying frontend ------------
Preparing to deploy: Created staging directory at:
'C:\Users\ADMINI~1\AppData\Local\Temp\appcfg2555411734473986257.tmp'
java.lang.RuntimeException: The application contains Java 7 classes,
but the --use_java7 flag has not been set.
Debugging information may be found in
C:\Users\Administrator\AppData\Local\Temp\appengine-deploy7182870224187999057.log
Debug Log:
Unable to update:
java.lang.RuntimeException: The application contains Java 7 classes, but the --use_java7 flag has not been set.
at com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:576)
at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:370)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:53)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:433)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
I'm attempting to deploy a google app to my google app engine account and eclipse is giving me this error. It seems rather straight forward, but I can't find where to set a flag for java7.
I'm using the latest version of Eclipse (Juno Service Release 1) and my google plugin is 4.2.
The relevant system level property is shown here: com.google.apphosting.runtime.use_java7
It can be passed into appCfg.sh like so:
appcfg.sh --use_java7 update
As per the 1.7.3 blog post:
In an upcoming release, we will be including some of the new Java 7
functionality as well as formal Java 7 support within the App Engine
Java runtime.
and...
And while Java 7 support is not yet available within the App Engine
Java runtime, developers interested in an early preview can sign up
for our trusted tester program.
You'll need to either be accepted into the TT program, or to wait for a future release where Java 7 works in production.

Categories

Resources