I have probably a very stupid error here, but I cannot get a simple Grails 4.0.4 project to connect to a Neo4j Desktop instance (1.3.8).
The neo4j service is running and I have been able to verify that I have connectivity to it from other tools, like DBeaver and Python.
The neo4j database settings in application.yml looks like this:
grails:
neo4j:
url: bolt://localhost:7687
username: "neo4j"
password: "neo4j"
The project I generated from start.grails.org running this:
curl -O start.grails.org/myapp.zip -d version=4.0.4 -d features=events,geb2,neo4j
The problem is when I try to launch a Grails project, the app fails to start with the message:
Application run failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'neo4jDatastore': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.grails.datastore.gorm.neo4j.Neo4jDatastore]: Constructor threw exception; nested exception is org.neo4j.driver.v1.exceptions.ServiceUnavailableException: Connection to the database terminated. This can happen due to network instabilities, or due to restarts of the database
Would be grateful for some hints that could help me get started.
Thanks!
As per http://gorm.grails.org/snapshot/neo4j/manual/#releaseNotes, there doesn't seem to be a version that yet supports Neo4j 4.x.
The latest supported version is Neo4j 3.x with GORM 7.0.x
Related
I tried running my Grails 3.3.2 application on Java 9 and for the most part the application worked. Mail (using this plugin: org.grails.plugins:mail:2.0.0), however, doesn't work, so cannot reset password, for example.
Attempting to send mail results in this error:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mailService': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException
I believe the issue is with Spring Boot and not the plugin itself. It seems there is a problem with bean creation and Java 9 that Spring Boot addresses is their 2.x version (Grails 3.3.2 runs on Spring Boot 1.5.x).
Just wondering what the time frame is for Grails and Java 9. Thanks!
The roadmap is for forth quarter this year (2018). Grails 4 will support Spring Boot 2 (which has just been released) and is the first version of Spring Boot which will support Java 9.
https://www.grails3book.com/blog/2018/2018-03-29-grails-jdk-9.html
I am new to apache-kylin,and currently I am deploying kylin on Vmware Worksation.I met some problems when it started.Then I check the log file,here is part of what it shows:
Error creating bean with name 'aclService': Invocation of init method failed; nested exception is org.apache.hadoop.hbase.TableExistsException: kylin_metadata_acl
detail info
problems with deploying apache kylin
Who can help?Thanks
I'm trying to get most basic example for Spring Cloud Dataflow running on CloudFoundry.
I've followed the steps here: http://docs.spring.io/spring-cloud-dataflow-admin-cloudfoundry/docs/current-SNAPSHOT/reference/htmlsingle/#getting-started to make the admin app available in my org/space.
Then I tried to create the most basic example from http://cloud.spring.io/spring-cloud-dataflow/, namely to create the "ticktock" stream:
dataflow:>stream create ticktock --definition "time | log" --deploy
I can see that both apps ticktock-time and ticktock-log are created in the space, the needed service "redis" is bound to these apps and they try to start. Unfortunately they don't start completely, because they have problem to access "redis" service. In the log we find:
Exception encountered during context initialization - cancelling
refresh attempt:
org.springframework.context.ApplicationContextException: Failed to
start bean 'outputBindingLifecycle'; nested exception is
org.springframework.context.ApplicationContextException: Failed to
start bean 'inputBindingLifecycle'; nested exception is
org.springframework.data.redis.RedisConnectionFailureException: Cannot
get Jedis connection; nested exception is
redis.clients.jedis.exceptions.JedisConnectionException: Could not get
a resource from the pool
which eventually is caused by
Caused by: redis.clients.jedis.exceptions.JedisConnectionException:
java.net.ConnectException: Connection refused
Am I missing some configuration step in between?
Alexander
There seems to be an issue with our deployer using the master branch of the Java buildpack. Try these settings for the Dataflow Server:
cf set-env s-c-dataflow-server CLOUDFOUNDRY_BUILDPACK https://github.com/cloudfoundry/java-buildpack.git#v3.6
cf restage s-c-dataflow-server
Also, be aware that we currently launch apps using "streamname-module" as part of the URL so unless you use unique stream names you might collide with other users and get a "400 Bad Request" error.
i just tried to access Neo4j through Gephi. After that when i tried to access Neo4j, it throw the following error. I'm using Neo4j 2.0.1.
Error:
Starting Neo4j Server failed: Error starting org.neo4j.kernel.EmbeddedGraphDatabase, C:\Users\Sakthi\Documents\Neo4j\default.graphdb
Make sure you don't have another Neo4j server running against the same folder
Make sure the user running gephi has read/write access to that folder
Look for the messages.log in that folder, and see if you can find any exceptions
I am attempting to deploy a war (a grails 1.3.7 app) to an jboss 6 which had been in a jboss 5 environment. The war is not dependent on jboss services or j2ee (it could have been deployed straight to tomcat). When deploying to jb6, I get the following error message:
14:54:17,281 ERROR [AbstractKernelController] Error installing to Real:
name=vfs:///opt/jboss-6.0.0.Final/server/jbossweb-standalone/deploy/pip.war
state=PreReal mode=Manual requiredState=Real:
org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///opt/jboss-6.0.0.Final/server/jbossweb-standalone/deploy/app.war
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) [:2.2.0.GA]
...
...
...
Caused by: java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name
specified nor any ResourceProvider could process resource-env-ref named env/cxf
of type org.apache.cxf.Bus
It seems as though JBoss support services are not able to get created, but don't see any underlying problems preventing the service creation. Also some other web apps are deployed to this instance of jboss, so the overall installation is "sound". I've done some investigation, but not sure where to go next. Any ideas as or pointers as to the likely problem?
This looks like a problem with JNDI, you have a reference to a JNDI in your project, more than likely your web.xml, this resource is not defined as a service in your Jboss server deploy directory, for instance a jdbc.xml definition you are relying on.