При запуске телеграм бота на heroku выдает ошибку H10, как исправить?

Question

[Ilya5527]

При запуске телеграм бота на Heroku, выдает следующие ошибки:

2021-12-19T08:29:28.811009+00:00 heroku[web.1]: Process exited with status 1
2021-12-19T08:29:28.928872+00:00 heroku[web.1]: State changed from starting to crashed
2021-12-19T08:34:30.884295+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=testtgbot1.herokuapp.com request_id=a77a8de3-504d-4709-a778-c77984133f59 fwd="93.81.221.81" dyno= connect= service= status=503 bytes= protocol=https
2021-12-19T08:34:31.374086+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=testtgbot1.herokuapp.com request_id=a27748f9-f0b7-4d29-964a-1910d19d9a4f fwd="93.81.221.81" dyno= connect= service= status=503 bytes= protocol=https

Main класс:

@SpringBootApplication
public class Main {
    public static void main(String[] args) {
        SpringApplication.run(Main.class, args);
    }
}

App класс:

@Component
public class Application extends TelegramLongPollingBot {
    @Override
    public String getBotUsername() {
        return "MY_USERNAME";
    }

    @Override
    public String getBotToken() {
        return "MY_TOKEN";
    }

    @SneakyThrows
    @Override
    public void onUpdateReceived(Update update) {
        if (update.hasMessage() && update.getMessage().hasText()){
            if (update.getMessage().getText().equals("/start")){
                execute(new SendMessage().builder().chatId(update.getMessage().getChatId().toString()).text("Я бот, а ты тоже!").build());
            }
        }
    }
}

В документации написано, что H10 - ошибка в HTTP запросе, как ее убрать?

Comments

[Dmitry Roo]

Есть ссылка на документацию?

[Ilya5527]

https://devcenter.heroku.com/articles/error-codes#...

[Сергей Горностаев]

Ilya5527, как вы смогли вычитать что-то про http-ошибку из текст "a crashed web dyno or a boot timeout"?

[Ilya5527]

В документацие выше.

Whenever your app experiences an error, Heroku will return a standard error page with the HTTP status code 503. To help you debug the underlying error, however, the platform will also add custom error information to your logs. Each type of error gets its own error code, with all HTTP errors starting with the letter H and all runtime errors starting with R. Logging errors start with L.

H10 - App crashed
A crashed web dyno or a boot timeout on the web dyno will present this error.

[Ilya5527]

Сергей Горностаев,

2021-12-19T10:12:23.239377+00:00 heroku[web.1]: Starting process with command `java -Dserver.port=43729 $JAVA_OPTS -jar target/untitled-1.0-SNAPSHOT.jar`
2021-12-19T10:12:24.376631+00:00 app[web.1]: Create a Procfile to customize the command used to run this process: https://devcenter.heroku.com/articles/procfile
2021-12-19T10:12:24.393671+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-12-19T10:12:24.396921+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -XX:+UseContainerSupport -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2021-12-19T10:12:24.451945+00:00 app[web.1]: no main manifest attribute, in target/untitled-1.0-SNAPSHOT.jar
2021-12-19T10:12:24.587304+00:00 heroku[web.1]: Process exited with status 1
2021-12-19T10:12:24.883530+00:00 heroku[web.1]: State changed from starting to crashed
2021-12-19T10:12:24.886577+00:00 heroku[web.1]: State changed from crashed to starting
2021-12-19T10:12:27.721341+00:00 heroku[web.1]: Starting process with command `java -Dserver.port=19033 $JAVA_OPTS -jar target/untitled-1.0-SNAPSHOT.jar`
2021-12-19T10:12:28.661991+00:00 app[web.1]: Create a Procfile to customize the command used to run this process: https://devcenter.heroku.com/articles/procfile
2021-12-19T10:12:28.676866+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-12-19T10:12:28.680446+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -XX:+UseContainerSupport -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2021-12-19T10:12:28.733847+00:00 app[web.1]: no main manifest attribute, in target/untitled-1.0-SNAPSHOT.jar
2021-12-19T10:12:28.867324+00:00 heroku[web.1]: Process exited with status 1
2021-12-19T10:12:30.785906+00:00 heroku[web.1]: State changed from starting to crashed
2021-12-19T10:13:10.087796+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=testtgbot1.herokuapp.com request_id=43896c1f-a983-4722-ab86-f95f0389e2de fwd="93.81.221.81" dyno= connect= service= status=503 bytes= protocol=https
2021-12-19T10:13:10.568913+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=testtgbot1.herokuapp.com request_id=f1663e28-f1df-4919-b854-fd89e3ae3d3f fwd="93.81.221.81" dyno= connect= service= status=503 bytes= protocol=https

[Сергей Горностаев]

Ilya5527,
Корень проблемы: no main manifest attribute, in target/untitled-1.0-SNAPSHOT.jar
Решение: https://ru.stackoverflow.com/a/968833/204271

[Ilya5527]

2021-12-19T10:46:29.532182+00:00 app[web.1]: no main manifest attribute, in target/untitled-1.0-SNAPSHOT.jar

Все еще ошибка осталась, хотя указал путь!

<build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
                <version>3.1.1</version>
                <configuration>
                    <archive>
                        <manifest>
                            <mainClass>org.example.bot.Main</mainClass>
                        </manifest>
                    </archive>
                </configuration>
            </plugin>
        </plugins>
    </build>