Darkside138/DiscordSoundboard

Console stuck on Connected to Websocket

Closed this issue · 1 comments

Just a few days ago, when I started up the application, it begins to boot up but then stops after a "Connected to Websocket" message. It usually goes through all the details and then stops after the estimated boot up time. Anyone know what the problem might be? I've copied and pasted what all shows up in the console when I start it up below:


| _ _ / / __ \ _ | ___ \ _ \ / || _ | | | | \ | | _ \ ___ | _ |/ _ \ | ___ \ _
| | | | | | \ --.| / \/ | | | |_/ / | | | \ --. | | | | | | | | | | | | |
/ /| | | / /
\ | |
/ / | | |
| | | | | | --. \ | | | | | /| | | | --. | | | | | | | . ` | | | | ___ | | | | _ || /| | | |
| |/ / | |/_
/ / _
/\ _/ / |\ | |/ / /_
/ /\ _/ / |
| | |\ | |/ /| |/ /\ _/ / | | || |\ | |/ /
|
/ _/_/ _/_/_| _|/ _/ _/ _/_| _// _/ _/_| |/_| _|__/

Discord Soundboard (v3.0.4)

2020-10-28 15:08:02.304 INFO 9456 --- [ main] n.d.discordsoundboard.MainController : Starting MainController v3.0.4 on DESKTOP-DB5F2V2 with PID 9456 (C:\Users\Josh\Desktop\DSB\DiscordSoundboard\DiscordSoundboard\lib\DiscordSoundboard-3.0.4.jar started by Josh in C:\Users\Josh\Desktop\DSB\DiscordSoundboard\DiscordSoundboard\bin)
2020-10-28 15:08:02.310 INFO 9456 --- [ main] n.d.discordsoundboard.MainController : No active profile set, falling back to default profiles: default
2020-10-28 15:08:03.930 INFO 9456 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode.
2020-10-28 15:08:04.023 INFO 9456 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 74ms. Found 2 repository interfaces.
2020-10-28 15:08:04.682 INFO 9456 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-10-28 15:08:05.627 INFO 9456 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2020-10-28 15:08:05.651 INFO 9456 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2020-10-28 15:08:05.652 INFO 9456 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.27]
2020-10-28 15:08:05.781 INFO 9456 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2020-10-28 15:08:05.781 INFO 9456 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 3366 ms
2020-10-28 15:08:06.216 INFO 9456 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2020-10-28 15:08:06.519 INFO 9456 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.4.6.Final}
2020-10-28 15:08:06.782 INFO 9456 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
2020-10-28 15:08:06.957 INFO 9456 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2020-10-28 15:08:07.379 INFO 9456 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2020-10-28 15:08:07.437 INFO 9456 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
2020-10-28 15:08:08.955 INFO 9456 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2020-10-28 15:08:08.969 INFO 9456 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2020-10-28 15:08:11.413 INFO 9456 --- [ main] net.dv8tion.jda.api.JDA : Login Successful!
2020-10-28 15:08:11.754 INFO 9456 --- [inWS-ReadThread] n.d.j.internal.requests.WebSocketClient : Connected to WebSocket

Duplicate on #145