Closed Sociopaat closed 6 years ago
Adam-
commented
6 years ago Not a bug, you just have to create the table as part of the setup process. The schema file is in the project under resources. I would not mind having a better way to create the schemas on startup (maybe spring has something for this?)
Sociopaat
commented
6 years ago I've manually added the sql files no errors in tomcat logs anymore
Snapshot is running but i can't access any of the api
keep getting 404 errors http://*ip*:8080/runelite-1.3.5-SNAPSHOT/ http://*ip*:8080/runelite-1.3.5-SNAPSHOT/hiscore?username=zezima
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Sat Apr 14 16:33:03 CEST 2018
There was an unexpected error (type=Not Found, status=404).
No message availableFull log
Apr 14, 2018 4:48:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/runelite-1.3.5-SNAPSHOT.war
Apr 14, 2018 4:48:32 PM org.apache.catalina.deploy.WebXml setVersion
WARNING: Unknown version string [3.1]. Default version will be used.
Apr 14, 2018 4:48:33 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Sat Apr 14 16:48:33 CEST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v1.5.6.RELEASE)
2018-04-14 16:48:34.276 INFO 26108 --- [bio-8080-exec-1] n.r.h.service.SpringBootWebApplication : Starting SpringBootWebApplication on ubunturunelite with PID 26108 (/var/lib/tomcat7/webapps/runelite-1.3.5-SNAPSHOT/WEB-INF/classes started by tomcat7 in /var/lib/tomcat7)
2018-04-14 16:48:34.290 INFO 26108 --- [bio-8080-exec-1] n.r.h.service.SpringBootWebApplication : No active profile set, falling back to default profiles: default
2018-04-14 16:48:34.356 INFO 26108 --- [bio-8080-exec-1] ationConfigEmbeddedWebApplicationContext : Refreshing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@e87528f: startup date [Sat Apr 14 16:48:34 CEST 2018]; root of context hierarchy
2018-04-14 16:48:35.293 INFO 26108 --- [bio-8080-exec-1] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 937 ms
2018-04-14 16:48:35.617 INFO 26108 --- [bio-8080-exec-1] o.s.b.w.servlet.ServletRegistrationBean : Mapping servlet: 'dispatcherServlet' to [/]
2018-04-14 16:48:35.617 INFO 26108 --- [bio-8080-exec-1] o.s.b.w.servlet.FilterRegistrationBean : Mapping filter: 'errorPageFilter' to: [/*]
2018-04-14 16:48:35.618 INFO 26108 --- [bio-8080-exec-1] o.s.b.w.servlet.FilterRegistrationBean : Mapping filter: 'characterEncodingFilter' to: [/*]
2018-04-14 16:48:35.618 INFO 26108 --- [bio-8080-exec-1] o.s.b.w.servlet.FilterRegistrationBean : Mapping filter: 'hiddenHttpMethodFilter' to: [/*]
2018-04-14 16:48:35.618 INFO 26108 --- [bio-8080-exec-1] o.s.b.w.servlet.FilterRegistrationBean : Mapping filter: 'httpPutFormContentFilter' to: [/*]
2018-04-14 16:48:35.618 INFO 26108 --- [bio-8080-exec-1] o.s.b.w.servlet.FilterRegistrationBean : Mapping filter: 'requestContextFilter' to: [/*]
2018-04-14 16:48:36.169 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerAdapter : Looking for @ControllerAdvice: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@e87528f: startup date [Sat Apr 14 16:48:34 CEST 2018]; root of context hierarchy
2018-04-14 16:48:36.229 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/account/session-check]}" onto public void net.runelite.http.service.account.AccountService.sessionCheck(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse) throws java.io.IOException
2018-04-14 16:48:36.230 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/account/callback]}" onto public java.lang.Object net.runelite.http.service.account.AccountService.callback(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,java.lang.String,java.lang.String,java.lang.String) throws java.lang.InterruptedException,java.util.concurrent.ExecutionException,java.io.IOException
2018-04-14 16:48:36.230 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/account/login]}" onto public net.runelite.http.api.account.OAuthResponse net.runelite.http.service.account.AccountService.login()
2018-04-14 16:48:36.230 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/account/logout]}" onto public void net.runelite.http.service.account.AccountService.logout(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse) throws java.io.IOException
2018-04-14 16:48:36.233 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/{cacheId}/{indexId}/{archiveId}]}" onto public net.runelite.http.api.cache.CacheArchive net.runelite.http.service.cache.CacheController.getCacheArchive(int,int,int)
2018-04-14 16:48:36.233 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/{cacheId}/{indexId}/{archiveId}/data]}" onto public byte[] net.runelite.http.service.cache.CacheController.getArchiveData(int,int,int)
2018-04-14 16:48:36.234 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/item/{itemId}/image],produces=[image/png]}" onto public org.springframework.http.ResponseEntity<byte[]> net.runelite.http.service.cache.CacheController.getItemImage(int,int,int,int) throws java.io.IOException
2018-04-14 16:48:36.234 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/npc/{npcId}]}" onto public net.runelite.cache.definitions.NpcDefinition net.runelite.http.service.cache.CacheController.getNpc(int) throws java.io.IOException
2018-04-14 16:48:36.234 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/]}" onto public java.util.List<net.runelite.http.api.cache.Cache> net.runelite.http.service.cache.CacheController.listCaches()
2018-04-14 16:48:36.234 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/{cacheId}]}" onto public java.util.List<net.runelite.http.api.cache.CacheIndex> net.runelite.http.service.cache.CacheController.listIndexes(int)
2018-04-14 16:48:36.234 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/{cacheId}/{indexId}]}" onto public java.util.List<net.runelite.http.api.cache.CacheArchive> net.runelite.http.service.cache.CacheController.listArchives(int,int)
2018-04-14 16:48:36.235 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/item/{itemId}]}" onto public net.runelite.cache.definitions.ItemDefinition net.runelite.http.service.cache.CacheController.getItem(int) throws java.io.IOException
2018-04-14 16:48:36.235 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/cache/object/{objectId}]}" onto public net.runelite.cache.definitions.ObjectDefinition net.runelite.http.service.cache.CacheController.getObject(int) throws java.io.IOException
2018-04-14 16:48:36.237 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/config/{key:.+}],methods=[PUT]}" onto public void net.runelite.http.service.config.ConfigService.setKey(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,java.lang.String,java.lang.String) throws java.io.IOException
2018-04-14 16:48:36.237 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/config/{key:.+}],methods=[DELETE]}" onto public void net.runelite.http.service.config.ConfigService.unsetKey(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,java.lang.String) throws java.io.IOException
2018-04-14 16:48:36.237 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/config]}" onto public net.runelite.http.api.config.Configuration net.runelite.http.service.config.ConfigService.get(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse) throws java.io.IOException
2018-04-14 16:48:36.239 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/examine/npc/{id}]}" onto public java.lang.String net.runelite.http.service.examine.ExamineService.getNpc(int)
2018-04-14 16:48:36.239 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/examine/npc/{id}],methods=[POST]}" onto public void net.runelite.http.service.examine.ExamineService.submitNpc(int,java.lang.String)
2018-04-14 16:48:36.239 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/examine/object/{id}],methods=[POST]}" onto public void net.runelite.http.service.examine.ExamineService.submitObject(int,java.lang.String)
2018-04-14 16:48:36.239 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/examine/item/{id}],methods=[POST]}" onto public void net.runelite.http.service.examine.ExamineService.submitItem(int,java.lang.String)
2018-04-14 16:48:36.239 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/examine/item/{id}]}" onto public java.lang.String net.runelite.http.service.examine.ExamineService.getItem(int)
2018-04-14 16:48:36.240 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/examine/object/{id}]}" onto public java.lang.String net.runelite.http.service.examine.ExamineService.getObject(int)
2018-04-14 16:48:36.240 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/feed]}" onto public net.runelite.http.api.feed.FeedResult net.runelite.http.service.feed.FeedController.getFeed() throws java.io.IOException
2018-04-14 16:48:36.240 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/hiscore/{endpoint}/{skillName}]}" onto public net.runelite.http.api.hiscore.SingleHiscoreSkillResult net.runelite.http.service.hiscore.HiscoreController.singleSkillLookup(net.runelite.http.api.hiscore.HiscoreEndpoint,java.lang.String,java.lang.String) throws java.io.IOException
2018-04-14 16:48:36.241 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/hiscore/{endpoint}]}" onto public net.runelite.http.api.hiscore.HiscoreResult net.runelite.http.service.hiscore.HiscoreController.lookup(net.runelite.http.api.hiscore.HiscoreEndpoint,java.lang.String) throws java.io.IOException
2018-04-14 16:48:36.242 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/item/{itemId}/icon/large],produces=[image/gif]}" onto public org.springframework.http.ResponseEntity<byte[]> net.runelite.http.service.item.ItemController.getIconLarge(javax.servlet.http.HttpServletResponse,int)
2018-04-14 16:48:36.242 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/item/{itemId}/price]}" onto public org.springframework.http.ResponseEntity<net.runelite.http.api.item.ItemPrice> net.runelite.http.service.item.ItemController.itemPrice(int,java.time.Instant)
2018-04-14 16:48:36.242 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/item/price]}" onto public net.runelite.http.api.item.ItemPrice[] net.runelite.http.service.item.ItemController.prices(int[])
2018-04-14 16:48:36.242 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/item/{itemId}]}" onto public net.runelite.http.api.item.Item net.runelite.http.service.item.ItemController.getItem(javax.servlet.http.HttpServletResponse,int)
2018-04-14 16:48:36.242 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/item/{itemId}/icon],produces=[image/gif]}" onto public org.springframework.http.ResponseEntity<byte[]> net.runelite.http.service.item.ItemController.getIcon(int)
2018-04-14 16:48:36.243 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/item/search]}" onto public net.runelite.http.api.item.SearchResult net.runelite.http.service.item.ItemController.search(java.lang.String)
2018-04-14 16:48:36.245 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/session/ping]}" onto public org.springframework.http.ResponseEntity net.runelite.http.service.session.SessionController.ping(java.util.UUID)
2018-04-14 16:48:36.245 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/session]}" onto public java.util.UUID net.runelite.http.service.session.SessionController.get(javax.servlet.http.HttpServletRequest)
2018-04-14 16:48:36.245 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/session/count]}" onto public int net.runelite.http.service.session.SessionController.count()
2018-04-14 16:48:36.246 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/session],methods=[DELETE]}" onto public org.springframework.http.ResponseEntity net.runelite.http.service.session.SessionController.delete(java.util.UUID,javax.servlet.http.HttpServletRequest)
2018-04-14 16:48:36.246 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/sprite],produces=[image/png]}" onto public org.springframework.http.ResponseEntity<byte[]> net.runelite.http.service.sprite.SpriteController.getSprite(int,int) throws java.io.IOException
2018-04-14 16:48:36.246 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/update-check]}" onto public java.lang.Boolean net.runelite.http.service.updatecheck.UpdateCheckService.check()
2018-04-14 16:48:36.247 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/worlds]}" onto public net.runelite.http.api.worlds.WorldResult net.runelite.http.service.worlds.WorldsService.listWorlds() throws java.io.IOException
2018-04-14 16:48:36.247 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/xp/get]}" onto public net.runelite.http.api.xp.XpData net.runelite.http.service.xp.XpTrackerController.get(java.lang.String,java.time.Instant) throws java.io.IOException
2018-04-14 16:48:36.248 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/xp/update]}" onto public void net.runelite.http.service.xp.XpTrackerController.update(java.lang.String) throws java.io.IOException
2018-04-14 16:48:36.248 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/xtea],methods=[POST]}" onto public void net.runelite.http.service.xtea.XteaService.submit(net.runelite.http.api.xtea.XteaRequest)
2018-04-14 16:48:36.248 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/xtea]}" onto public java.util.List<net.runelite.http.api.xtea.XteaKey> net.runelite.http.service.xtea.XteaService.get()
2018-04-14 16:48:36.249 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/xtea/{region}]}" onto public net.runelite.http.api.xtea.XteaKey net.runelite.http.service.xtea.XteaService.getRegion(int)
2018-04-14 16:48:36.250 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/error],produces=[text/html]}" onto public org.springframework.web.servlet.ModelAndView org.springframework.boot.autoconfigure.web.BasicErrorController.errorHtml(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse)
2018-04-14 16:48:36.250 INFO 26108 --- [bio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/error]}" onto public org.springframework.http.ResponseEntity<java.util.Map<java.lang.String, java.lang.Object>> org.springframework.boot.autoconfigure.web.BasicErrorController.error(javax.servlet.http.HttpServletRequest)
2018-04-14 16:48:36.283 INFO 26108 --- [bio-8080-exec-1] o.s.w.s.handler.SimpleUrlHandlerMapping : Mapped URL path [/webjars/**] onto handler of type [class org.springframework.web.servlet.resource.ResourceHttpRequestHandler]
2018-04-14 16:48:36.284 INFO 26108 --- [bio-8080-exec-1] o.s.w.s.handler.SimpleUrlHandlerMapping : Mapped URL path [/**] onto handler of type [class org.springframework.web.servlet.resource.ResourceHttpRequestHandler]
2018-04-14 16:48:36.318 INFO 26108 --- [bio-8080-exec-1] o.s.w.s.handler.SimpleUrlHandlerMapping : Mapped URL path [/**/favicon.ico] onto handler of type [class org.springframework.web.servlet.resource.ResourceHttpRequestHandler]
2018-04-14 16:48:36.506 INFO 26108 --- [bio-8080-exec-1] o.s.j.e.a.AnnotationMBeanExporter : Registering beans for JMX exposure on startup
2018-04-14 16:48:36.514 INFO 26108 --- [bio-8080-exec-1] s.a.ScheduledAnnotationBeanPostProcessor : No TaskScheduler/ScheduledExecutorService bean found for scheduled processing
2018-04-14 16:48:36.522 INFO 26108 --- [bio-8080-exec-1] n.r.h.service.SpringBootWebApplication : Started SpringBootWebApplication in 2.608 seconds (JVM running for 1049.335)
2018-04-14 16:48:36.523 INFO 26108 --- [bio-8080-exec-1] n.r.h.service.SpringBootWebApplication : RuneLite API started
Apr 14, 2018 4:48:36 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive /var/lib/tomcat7/webapps/runelite-1.3.5-SNAPSHOT.war has finished in 4,302 ms
2018-04-14 16:48:44.027 INFO 26108 --- [bio-8080-exec-3] o.s.web.servlet.DispatcherServlet : FrameworkServlet 'dispatcherServlet': initialization started
2018-04-14 16:48:44.047 INFO 26108 --- [bio-8080-exec-3] o.s.web.servlet.DispatcherServlet : FrameworkServlet 'dispatcherServlet': initialization completed in 19 ms
Trying to get the api running, had to fix some errors before; too many connections; set idletime to 10 to fix it and increased mysql max connections
then i got
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Invalid default value for 'last_used'and had to remove the NO_ZERO_IN_DATE, NO_ZERO_DATE in the mysql conf to get it running
Now the snapshot shows as running in tomcat
When i try to reach the api it gives a 404 error
When i look at my logs /var/log/tomcat7/catalina.out it shows this error
Can't find any solution to this