Hi guys im having an issue with my intellij react project, ive already connected to the MySQL DB from intelliJ..
After running springboot:run, it installs all dependencies for the app after all is done i get a target folder thats red and a package-lock.json thats also red what does this mean?
Im new to react so im trying to run this app locally but when i run the project i get this error:
"Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.
2018-06-22 13:23:20.295 ERROR 6796 --- [ restartedMain] o.s.boot.SpringApplication : Application startup failed"
Project has already been built by previous Dev im just trying to get it ti run locally now.
what could i be doing wrong?
Spring-boot is one of the wonderful thing to get started to fast, it
does many things automatically. At the same time, missing
configuration will lead to this kind of errors.
Please double check application.yaml/.properties and pom.xml for more details.
This error is thrown when dependencies are not resolved correctly and mis-configuration of dependencies.
If it is a Maven project, right click on project folder and do 'Maven -> Re-Import'. It will fetch the missing maven dependencies.
Also, whatever is mentioned as part of the dependencies should have proper configurations. Let's say for example, you're mentioning mysql as dependency and doesn't provide connection/username/password details then this error occurs.
Please provide more details/error-trace log to provide more accurate answer.
Hope it helps!!
Related
We recently upgraded an old rails app from rails 3 to 4.2, along with many other gem updates. Now I can't get my rails app to load any pages. We were on JRuby 9.1.0.0 but upgraded to 9.1.8.0. However, I'm hitting the same problem on both versions.
Once we start tomcat with our latest .war, it runs all the way until I see the INFO: Server startup in 1234ms message. I've added some debug statements in my rails environment / initializers files to follow it through and it is hitting each of them. So once I see the startup message from tomcat, I figured it would be okay. However, it immediately spits out the following message quite a few times:
DEBUG: resetting rack response due exception
Every time I load a URL, it also shows that message in my logs.
I see that it's from this jruby-rack class but I have no idea how to debug or troubleshoot this further.
I assume that something in my configuration is causing a problem or that a class/module is somehow short-circuiting it but I'm not sure how to identify which one it is or isolate the issue.
Does anybody know of a way to get some more verbose logs or ways to figure out where the problem is happening?
Happy to post any config/gemfiles etc if it will help.
After receiving some great help from the #jruby IRC channel, they mentioned the error message was missing the specific exception message. I was using the latest version, v1.1.21 so I just made a hack-build that added some logging to identify my problem further. Turns out it was a runtime error because of some missing config.
I made an issue with jruby-rack and a PR which will hopefully make its way into the next release!
On Ubuntu v15 my Jekyll Blog with jekyll lunr-js-search builds well as well as it gets build in gitlab-ci.
Now, I moved my project to Windows system with same versions of node, bower etc. I get following error on windows as well as gitlab-ci (This error repeated on gitlab-ci when I've made only a single line change in post). HOW TO FIX ?
ERROR
Dependency Error: Yikes! It looks like you don't have /builds/sachingpta/home/_plugins/lunrjs/jekyll_lunr_js_search.rb or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: 'cannot load such file -- v8' If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/!
It got built on gitlab, it could be due to gitlab update with dashboard message: We're currently deploying 8.17.0 RC2, so you may encounter intermittent errors. Somebody mentioned that required dependency therubyracer does not compiles on windows so this question is closed. I've to compile project on ubuntu only :(
I am trying to run a MapReduce 2 job on hadoop but get an error about connecting to port 8021. As far as I know this port is for the JobTracker, which is not used in MR2. This makes me wonder if I am somehow accidentally using MR1. However, extensive web search did not get me anywhere.
I used the new API (org.apache.hadoop.mapreduce.*) and compiled with javac -cp 'yarn classpath' sourcefolder. Does anyone have a clue what I might be doing wrong?
Please check your configuration files and also make sure that your job tracker and task tracker are active. If its having problem connecting to port 8021, it might be used by other applications.
I want to deploy my application to glassvish v3 with asadmin deploy command however I get an error:
com.sun.enterprise.admin.cli.CommandException: remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive#1c2a1c7
What can be the problem?
To me, the problem was coming from the fact that in /domains/domain/applications there was still the application I was trying to deploy again.
Another file access possibility I just ran into:
Service was started as root and the app undeployed/deployed. Then, as the correct limited rights user, undeploy/deploy. On deploy you'll receive this error, as the application files will still exist in he 'domains/yourdomain/applications' directory, and will be owned by root.
+1 to Keeg's comment on the awesome error messages we've all come to expect from Glassfish.
Hey I got the same error.In my case,I'd made a directory named "Web-INF",apparently the name of the folder has to be (mandatory) in upper-case i.e. "WEB-INF".
In short,check for spelling errors.
It solved my issue.So just wanted to share.I'm new to glassfish, so can't really tell you the exact solution.But what worked for me could be a solution for you as well.
Just in case someone else finds this question and the above answer doesn't match your case... Our problem was that the temporary area on the Glassfish server was full. Clearing some space let me redeploy the same application. Thank goodness for excellent error messages.
I had an ear project, where the ear package had different version number configured to maven pom.xml than the rest of the projects it contained. It searched sub-modules from version 1.x and the rest of the project was at 1.y version. I updated every pom to same version and that made the trick.
I'm using NetBeans and GlassFish 3.0.1 to create an EJB3 application. I have written a few Unit Tests, which get run via JUnit and make use of the embedded GlassFish. Whenever I run these tests on my development machine (so from within NetBeans), it's all good.
Now I would like to let Hudson do those tests. At the moment it is failing with lookup failure on a resource (in this case the datasource to a JPA persistance unit):
[junit] SEVERE: Exception while invoking class org.glassfish.persistence.jpa.JPADeployer prepare method
[junit] java.lang.RuntimeException: javax.naming.NamingException: Lookup failed for 'mvs_devel' in SerialContext
After searching around and trying to learn about this, I believe it is related to the embedded GlassFish not having been configured with resources. In other words it's missing a domain.xml file. Right?
Two questions:
Why does it work with NetBeans on my dev box? What magic does NetBeans do in the background?
How should I provide the file? Where does the embedded GlassFish on the Hudson-box expect it?
Hudson is using the same Ant build-scripts (created by NetBeans).
I've read this post about instanceRoot and the EmbeddedFileSystemBuilder, but I don't understand enough of that. Is this needed for every TestCase (Emb. GF gets started/stopped for each bean-under-test)? Is this part of EJBContainer.createEJBContainer()? Again, why is it not necessary to do this when running tests on NetBeans?
Update
Following Peter's advice I can confirm: when running ant on a freshly checked out copy of the code, with the same properties as hudson is configured, the tests get executed!
10-1 it is a classpath issue as IDE's tend to swap paths in and out depending if you run normally or unittests.
Try running the tests on a commandline from a freshly checked out version from your SCM. Chances are you'll have the same error. Debugging on your local machine is a lot easier than on a remote machine.
When it builds reliably on the command line (in a separate directory) then it is time to move to hudson.