Reputation: 1487
I've received the message "Process finished with exit code 1" when I run my project. I have tried several solutions but no topic is the same error as mine. My project doesn't execute any line of code, just abort the process.
Upvotes: 54
Views: 84654
Reputation: 1487
EDIT: If your code was previously working and you didn't change anything it just stopped working then it might be an IntelliJ issue.
Be aware that this will remove the configuration from your workspace.
Upvotes: 8
Reputation: 1012
for me I added : exclude = DataSourceAutoConfiguration.class
by default spring boot searches for datasource so we need to exclude the same
Example :
@SpringBootApplication(exclude = DataSourceAutoConfiguration.class)
public class ProcessorApplication {
public static void main(String[] args) {
try {
SpringApplication.run(ProcessorApplication.class, args);
} catch (Exception e) {
e.printStackTrace();
}
}
now the spring boot will exit normally :
Upvotes: 0
Reputation: 2296
Check you run configuration and run the application with proper profile like local, dev, QA or prod
based on your environment.
I also faced the same problem. I changed the profile and then it started without any issues.
any way just have a try.
Upvotes: 0
Reputation: 21
It's possible you are compiling from the cloud. If so, check if the cloud software is connected to the internet. Or try to sync the cloud software and see it's updated. Then, try to re-compile the work. It should work.
Alternatively, there might be lost link to the source file. E.g., you have moved the file into a new folder and some items didn't follow it to the new location, check this and re-compile.
Upvotes: 0
Reputation: 545
For me, after merging feature branch to my local branch, there was a duplicate entry in in my application.yml
file, caused the system not to start with message:
Thanks to @Yasitha Bandara
Upvotes: 1
Reputation: 1163
You must set logging.level.root
to DEBUG
and read related logging to find problem.
if your app uses application.yml file, add (or edit) this at beginning or end:
logging:
level:
root: DEBUG
if your app uses application.properties
, add (or edit) below line:
logging.level.root: DEBUG
for example, my app uses an undefined property and does not show the problem in common logs, after enabling debug level logging, I got below line in logs:
Could not find key 'app.services.account.service' in any property source
Upvotes: 9
Reputation: 154
My problem was as simple as some bad VM options because of copy/pasting from a strange application that omitted all the equal signs
I had
-Dconfig.file/somepathtothefile/resources/application.conf
instead of
-Dconfig.file=/somepathtothefile/resources/application.conf
Upvotes: 0
Reputation: 4267
For springboot projects, the most common reason is org.springframework.beans.factory.BeanCreationException
. Search BeanCreationException
, debug at each construct function, and debug the projects. Then you will find out the 'beanName' with problem, then you can focus on the bean.
Upvotes: 1
Reputation: 1270
Maybe not in this case exactly but missing logs could also caused by missing profile configuration in the logback.xml file.
Upvotes: 4
Reputation: 2375
Try to get stack trace by putting "try-catch" block, arround "run" method calling, in your main method, and print stack trace within "catch" as follows.
public static void main(String[] args) {
try {
SpringApplication.run(MyApplication.class, args);
} catch (Exception e) {
e.printStackTrace();
}
}
Upvotes: 161
Reputation: 311
Had the same problem.
Fixed by specifying parent Spring Boot Starter project.
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.1.2.RELEASE</version>
<relativePath />
</parent>
Upvotes: 0
Reputation: 169
Its very complicated because mostly it might happen due to missing of properties. In my case the below property not defined in application.properties which cause this issue and its clue less. Hope this will help you
Due to missing properties like server port or any other placeholder which is defined in any Bean or Component can cause this issue. verify all the properties and placeholders.
@Value(value = "${resource.path.accountNumbers}")
private Resource accountNumbers;
application.properties--verify all properties/placeholders
resource.path.accountNumbers=classpath:accountNumbers.properties
Upvotes: 0
Reputation: 502
I encounter the same problem. Springboot exits with code 1 without error. But that was when I created a project without using Spring Initializer.
I suggest you backup your code and recreate the project with Spring Initializer (service URL: https://start.spring.io), that should work. and you will be able to compare the setup difference.
Upvotes: 1