Hi, please post the content of your own core/src/main/resources/domains/Master.properties
and provide information about the MySQL database you are attempting to connect to: * MySQL version? * host / port / database name / username / password Regards. On 2019/04/02 20:16:46, o haya <[email protected]> wrote: > It's still not working. I get the same error. > Here's my latest catalina.out log, from startup: > [root@ip-192-168-0-164 logs]# tail -f catalina.out > 02-Apr-2019 20:11:44.233 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line argument: > -Dcatalina.home=/apps/apache-tomcat-9.0.17 > 02-Apr-2019 20:11:44.233 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line argument: > -Djava.io.tmpdir=/apps/apache-tomcat-9.0.17/temp > 02-Apr-2019 20:11:44.233 INFO [main] > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based > Apache Tomcat Native library which allows optimal performance in production > environments was not found on the java.library.path: > [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib] > 02-Apr-2019 20:11:44.428 INFO [main] org.apache.coyote.AbstractProtocol.init > Initializing ProtocolHandler ["http-nio-9080"] > 02-Apr-2019 20:11:44.502 INFO [main] org.apache.coyote.AbstractProtocol.init > Initializing ProtocolHandler ["ajp-nio-8009"] > 02-Apr-2019 20:11:44.508 INFO [main] > org.apache.catalina.startup.Catalina.load Server initialization in [1,059] > milliseconds > 02-Apr-2019 20:11:44.561 INFO [main] > org.apache.catalina.core.StandardService.startInternal Starting service > [Catalina] > 02-Apr-2019 20:11:44.561 INFO [main] > org.apache.catalina.core.StandardEngine.startInternal Starting Servlet > engine: [Apache Tomcat/9.0.17] > 02-Apr-2019 20:11:44.602 INFO [main] > org.apache.catalina.startup.HostConfig.deployWAR Deploying web application > archive [/apps/apache-tomcat-9.0.17/webapps/syncope-enduser.war] > 02-Apr-2019 20:11:47.979 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > > > > > > > > > > > > > > > > > > > > > > > > > 02-Apr-2019 20:11:50.584 INFO [main] > org.apache.catalina.startup.HostConfig.deployWAR Deployment of web > application archive [/apps/apache-tomcat-9.0.17/webapps/syncope-enduser.war] > has finished in [5,982] ms > 02-Apr-2019 20:11:50.585 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/ROOT] > > > > > > 02-Apr-2019 20:11:50.850 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > 02-Apr-2019 20:11:50.851 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/ROOT] has finished > in [266] ms > 02-Apr-2019 20:11:50.852 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/docs] > 02-Apr-2019 20:11:51.109 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > 02-Apr-2019 20:11:51.111 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/docs] has finished > in [260] ms > 02-Apr-2019 20:11:51.111 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/examples] > 02-Apr-2019 20:11:51.578 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > 02-Apr-2019 20:11:51.633 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/examples] has > finished in [522] ms > 02-Apr-2019 20:11:51.633 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/host-manager] > 02-Apr-2019 20:11:51.906 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > 02-Apr-2019 20:11:51.932 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/host-manager] has > finished in [299] ms > 02-Apr-2019 20:11:51.932 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/manager] > 02-Apr-2019 20:11:52.195 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > 02-Apr-2019 20:11:52.197 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/manager] has > finished in [265] ms > 02-Apr-2019 20:11:52.197 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/syncope] > 02-Apr-2019 20:11:58.474 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver > class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered > via the SPI and manual loading of the driver class is generally unnecessary. > 02-Apr-2019 20:12:13.412 SEVERE [main] > org.apache.catalina.core.StandardContext.startInternal One or more listeners > failed to start. Full details will be found in the appropriate container log > file > 02-Apr-2019 20:12:13.413 SEVERE [main] > org.apache.catalina.core.StandardContext.startInternal Context [/syncope] > startup failed due to previous errors > 02-Apr-2019 20:12:13.448 WARNING [main] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [syncope] appears to have started a thread named > [Log4j2-TF-5-AsyncLoggerConfig-1] but has failed to stop it. This is very > likely to create a memory leak. Stack trace of thread: > java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1027) > > java.util.concurrent.ConcurrentHashMap.putIfAbsent(ConcurrentHashMap.java:1535) > java.lang.ClassLoader.checkCerts(ClassLoader.java:895) > java.lang.ClassLoader.preDefineClass(ClassLoader.java:668) > java.lang.ClassLoader.defineClass(ClassLoader.java:761) > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > > org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2415) > > org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:863) > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1332) > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1186) > > org.apache.logging.log4j.core.impl.Log4jLogEvent.getThrownProxy(Log4jLogEvent.java:605) > > org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:64) > > org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:38) > > org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer.toSerializable(PatternLayout.java:334) > > org.apache.logging.log4j.core.layout.PatternLayout.toText(PatternLayout.java:233) > > org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:218) > > org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:58) > > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:177) > > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:170) > > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:161) > > org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender.append(RollingRandomAccessFileAppender.java:250) > > org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156) > > org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129) > > org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120) > > org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) > > org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:464) > > org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:120) > > org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:448) > org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:431) > > org.apache.logging.log4j.core.async.AsyncLoggerConfig.log(AsyncLoggerConfig.java:114) > > org.apache.logging.log4j.core.async.AsyncLoggerConfig.logToAsyncLoggerConfigsOnCurrentThread(AsyncLoggerConfig.java:162) > > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:111) > > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:97) > > com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) > com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) > java.lang.Thread.run(Thread.java:748) > 02-Apr-2019 20:12:13.449 SEVERE [main] > org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks > The web application [syncope] created a ThreadLocal with key of type > [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@5c43c90a]) and a value > of type [org.apache.logging.log4j.core.config.AppenderControl] (value > [org.apache.logging.log4j.core.config.AppenderControl@ebdcbb70[appender=restFile, > appenderName=restFile, level=null, intLevel=2147483647, > recursive=java.lang.ThreadLocal@5c43c90a, filter=null]]) but failed to remove > it when the web application was stopped. Threads are going to be renewed over > time to try and avoid a probable memory leak. > 02-Apr-2019 20:12:13.460 INFO [Log4j2-TF-5-AsyncLoggerConfig-1] > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading > Illegal access: this web application instance has been stopped already. Could > not load [org.apache.logging.log4j.core.impl.ExtendedStackTraceElement]. The > following stack trace is thrown for debugging purposes as well as to attempt > to terminate the thread which caused the illegal access. > java.lang.IllegalStateException: Illegal access: this web application > instance has been stopped already. Could not load > [org.apache.logging.log4j.core.impl.ExtendedStackTraceElement]. The following > stack trace is thrown for debugging purposes as well as to attempt to > terminate the thread which caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1383) > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1371) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1224) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1186) > at > org.apache.logging.log4j.core.impl.ThrowableProxy.toExtendedStackTrace(ThrowableProxy.java:713) > at > org.apache.logging.log4j.core.impl.ThrowableProxy.<init>(ThrowableProxy.java:138) > at > org.apache.logging.log4j.core.impl.ThrowableProxy.<init>(ThrowableProxy.java:122) > at > org.apache.logging.log4j.core.impl.Log4jLogEvent.getThrownProxy(Log4jLogEvent.java:605) > at > org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:64) > at > org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:38) > at > org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer.toSerializable(PatternLayout.java:334) > at > org.apache.logging.log4j.core.layout.PatternLayout.toText(PatternLayout.java:233) > at > org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:218) > at > org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:58) > at > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:177) > at > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:170) > at > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:161) > at > org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender.append(RollingRandomAccessFileAppender.java:250) > at > org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156) > at > org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129) > at > org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120) > at > org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) > at > org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:464) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:120) > at > org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:448) > at > org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:431) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.log(AsyncLoggerConfig.java:114) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.logToAsyncLoggerConfigsOnCurrentThread(AsyncLoggerConfig.java:162) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:111) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:97) > at > com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) > at > com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) > at java.lang.Thread.run(Thread.java:748) > > AsyncLogger error handling event seq=29, > value='Logger=org.springframework.web.context.ContextLoader Level=ERROR > Message=Context initialization failed': java.lang.NoClassDefFoundError: > org/apache/logging/log4j/core/impl/ExtendedStackTraceElement > java.lang.NoClassDefFoundError: > org/apache/logging/log4j/core/impl/ExtendedStackTraceElement > at > org.apache.logging.log4j.core.impl.ThrowableProxy.toExtendedStackTrace(ThrowableProxy.java:713) > at > org.apache.logging.log4j.core.impl.ThrowableProxy.<init>(ThrowableProxy.java:138) > at > org.apache.logging.log4j.core.impl.ThrowableProxy.<init>(ThrowableProxy.java:122) > at > org.apache.logging.log4j.core.impl.Log4jLogEvent.getThrownProxy(Log4jLogEvent.java:605) > at > org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:64) > at > org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:38) > at > org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer.toSerializable(PatternLayout.java:334) > at > org.apache.logging.log4j.core.layout.PatternLayout.toText(PatternLayout.java:233) > at > org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:218) > at > org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:58) > at > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:177) > at > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:170) > at > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:161) > at > org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender.append(RollingRandomAccessFileAppender.java:250) > at > org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156) > at > org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129) > at > org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120) > at > org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) > at > org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:464) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:120) > at > org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:448) > at > org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:431) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.log(AsyncLoggerConfig.java:114) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.logToAsyncLoggerConfigsOnCurrentThread(AsyncLoggerConfig.java:162) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:111) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:97) > at > com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) > at > com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.ClassNotFoundException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.logging.log4j.core.impl.ExtendedStackTraceElement]. The following > stack trace is thrown for debugging purposes as well as to attempt to > terminate the thread which caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1373) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1224) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1186) > ... 29 more > Caused by: java.lang.IllegalStateException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.logging.log4j.core.impl.ExtendedStackTraceElement]. The following > stack trace is thrown for debugging purposes as well as to attempt to > terminate the thread which caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1383) > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1371) > ... 31 more > 02-Apr-2019 20:12:13.467 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/syncope] has > finished in [21,270] ms > 02-Apr-2019 20:12:13.467 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/apps/apache-tomcat-9.0.17/webapps/syncope-console] > 02-Apr-2019 20:12:16.459 INFO [main] > org.apache.jasper.servlet.TldScanner.scanJars 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. > 02-Apr-2019 20:12:20.527 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/apps/apache-tomcat-9.0.17/webapps/syncope-console] > has finished in [7,059] ms > 02-Apr-2019 20:12:20.543 INFO [main] org.apache.coyote.AbstractProtocol.start > Starting ProtocolHandler ["http-nio-9080"] > 02-Apr-2019 20:12:20.556 INFO [main] org.apache.coyote.AbstractProtocol.start > Starting ProtocolHandler ["ajp-nio-8009"] > 02-Apr-2019 20:12:20.558 INFO [main] > org.apache.catalina.startup.Catalina.start Server startup in [36,049] > milliseconds > ^C > > > > > > > On Tuesday, April 2, 2019, 9:56:27 AM EDT, Francesco Chicchiriccò > <[email protected]> wrote: > > On 02/04/19 15:33, o haya wrote: > > > Hi, > Now, when I startup Tomcat, I am seeing this in the catalina.out: > 02-Apr-2019 13:17:06.383 WARNING [main] > org.apache.tomcat.jdbc.pool.ConnectionPool.checkPoolConfiguration maxIdle is > larger than maxActive, setting maxIdle to: 50 > Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver > class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered > via the SPI and manual loading of the driver class is generally unnecessary. > 02-Apr-2019 13:17:06.604 SEVERE [main] > org.apache.tomcat.jdbc.pool.ConnectionPool.init Unable to create initial > connections of pool. > com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link > failure > > This is error says it all: Syncope is not able to connect to MySQL. > > Could that be why I am getting that connection error now? Should I remove > that <Resource> from the Tomcat context.xml now? > > Yes, remove it. > > Start with a clean Tomcat, if possible. > > Regards. > > > On Tuesday, April 2, 2019, 8:40:52 AM EDT, Francesco Chicchiriccò > <[email protected]> wrote: > > FYI, the only Master.properties that matters is > /apps/syncope/myproject/core/src/main/resources/domains/Master.properties > because: > * anything under target/ is going to disappear at next build * the one > under test/ is used for the embedded mode, and should not be touched * the > one under /apps/apache-tomcat-9.0.17/webapps/syncope/ is your deployed > webapp, there is no point in changing that one > > Syncope 2.1 runs its whole integration test suite on Tomcat 9, and so does > embedded mode hence no, there is no issue with Tomcat 9. > As long as Syncope Core is not properly configured with its database > connection (Master.properties and provisioning.properties) there is no chance > you'll get anything but 404. I'd suggest to watch your Tomcat logs during > startup to identify the main issue - also looking at > /opt/syncope/log/core.log would help. > > And don't forget to build as we said below, after making your changes to > the files. > Regards. > > On 02/04/19 14:27, o haya wrote: > > > Re. " > It would have been > > http://:8080/syncope/rest > " > You are correct, but I get a 404 error in that case also :)... > > > Re. the Master.properties, here is where I found the copies (FYI, all my > work is under /apps): > [root@ip-192-168-x logs]# find /apps/ -name "Master.properties" > /apps/apache-tomcat-9.0.17/webapps/syncope/WEB-INF/classes/domains/Master.properties > /apps/syncope/myproject/core/src/main/resources/domains/Master.properties > /apps/syncope/myproject/core/src/test/resources/domains/Master.properties > /apps/syncope/myproject/core/target/classes/domains/Master.properties > /apps/syncope/myproject/core/target/test-classes/domains/Master.properties > /apps/syncope/myproject/core/target/syncope/WEB-INF/classes/domains/Master.properties > > > I just change my Tomcat to listen to 8080 instead of 9080, and still get > the same error so I still really think that whatever is serviceing the > /syncope/rest endpoint is not working (thus the NOT_FOUND) and also I get > this in the Tomcat localhost_access.log every time I test: > 127.0.0.1 - - [02/Apr/2019:12:17:46 +0000] "GET /syncope/rest/platform > HTTP/1.1" 404 1103 > 127.0.0.1 - - [02/Apr/2019:12:17:46 +0000] "GET /syncope/rest/platform > HTTP/1.1" 404 1103 > 172.31.xx.yy- - [02/Apr/2019:12:17:46 +0000] "GET /syncope-console/ > HTTP/1.1" 500 8876 > > > Also, FYI, I am using Tomcat 9.x. Is it possible that that is why this is > all not working? > > NOTE that I am running the Tomcat and Syncope that I can only access via > SSH and HTTP/HTTPS from a browser on a workstation that is remote from the > Tomcat/Syncope server. > > What I mean by that is that using a browser, I cannot access > http://localhost:8080 at all, only http://:8080. > Jim > > > > On Tuesday, April 2, 2019, 8:13:57 AM EDT, Francesco Chicchiriccò > <[email protected]> wrote: > > On 02/04/19 13:14, o haya wrote: > > > Hi, > In my latest attempt, I *DID* all this: > $ mvn clean verify \ > -Dconf.directory=/opt/syncope/conf \ > -Dbundles.directory=/opt/syncope/bundles \ > -Dlog.directory=/opt/syncope/log > $ cp core/target/classes/*properties /opt/syncope/conf > $ cp console/target/classes/*properties /opt/syncope/conf > $ cp enduser/target/classes/*properties /opt/syncope/conf > $ cp enduser/target/classes/customFormAttributes.json /opt/syncope/conf > $ cp enduser/target/classes/customTemplate.json /opt/syncope/conf > > and I still get the same error. Also FYI, when I point a browser to > http://:8080/rest, I get a 404 error from Tomcat. > > It would have been > > http://:8080/syncope/rest > > in case, but this is obviously not working, as your database connection is > not set up propertly. > > > Also, as I said, so far, what I think I have realized is that I didn't do > the changes for using mysql (modifying the provisioning.properties and the > Master.properties). I am looking at doing those modifications now. > > I did the provisioning.properties change already, but I found there are 5 > instances of Master.properties. Which one do I have to change? > > > Where are such 5 instances of Master.properties located? > > ...are you sure you're not familiar enough with docker-compose? It would be > just straightforward. > > Regards. > > > On Tuesday, April 2, 2019, 6:57:52 AM EDT, Francesco Chicchiriccò > <[email protected]> wrote: > > On 02/04/19 12:49, o haya wrote: > > > Hi, > Thanks. To be clear, here is what I want to do/build: > - Use Syncope 2.1.3 - Use mysql for the internal storage - Use an LDAP > connector (eventually) to an external LDAP (an Oracle Unified > Directory/OUD). > BUT I think I've been doing what you suggested (and just re-did everything > and got the same result... the NOT_FOUND error :(). > Reading through your email below, I think that one thing I am missing/not > doing is your reference [8], setting up the provisioning.properties file for > mysql. The [8] reference is for postgre. > Do you know what the provisioning.properties should be for mysql? > Also, would me NOT configuring the provisioning.properties file cause the > problem that I am seeing? > > Basically, I think that the problem I am having is that the /syncope/rest > endpoint is not working. > The problem is that Admin Console is incorrectly looking for Syncope Core > (e.g /syncope/rest) under > > http://localhost:9080/syncope/rest > > while instead it is deployed under > > http://localhost:8080/syncope/rest > > This is due by the fact that you are not building Syncope as expected for > deploying to an external Java EE container, e.g. > > $ mvn clean verify \ > -Dconf.directory=/opt/syncope/conf \ > -Dbundles.directory=/opt/syncope/bundles \ > -Dlog.directory=/opt/syncope/log > $ cp core/target/classes/*properties /opt/syncope/conf > $ cp console/target/classes/*properties /opt/syncope/conf > $ cp enduser/target/classes/*properties /opt/syncope/conf > $ cp enduser/target/classes/customFormAttributes.json /opt/syncope/conf > $ cp enduser/target/classes/customTemplate.json /opt/syncope/conf > > > Correct? > > > On Tuesday, April 2, 2019, 3:06:10 AM EDT, Francesco Chicchiriccò > <[email protected]> wrote: > > Sooooo, let's do a little order. > > 1. you want to try Apache Syncope with LDAP - cool > > 2. you come to [1] and click the big green button labeled as "I want to > build my IdM with Apache Syncope" > > 3. you are brought to [2], where you can see that latest version is > 2.1.3 Fusion and that there are many options available; also, some text > says "Don't know what to download? Click the buttons below to get more > information." > > 4. each buttons brings you to a different section of the Getting Started > guide [3], which explains pros and cons of the various distributions > > In a nutshell: > > * if you just want to look around, and like the idea of having some test > data with sample resources configured, go with Standalone Distribution > > * if you are familiar with Docker, and don't need test data, just use > our images, possibly through docker-compose or Kubernetes (sample available) > > * if you want to get full access to customization, stick with Maven but > please, follow the guide, e.g. > > - create new project [4] > - (optionally) run it as embedded [5] > - as suggested by [6], "consider reading the Apache Syncope Reference > Guide. to understand how to configure, extend, customize and deploy your > new Apache Syncope project" > - about deployment, you will find [7], in the Reference Guide, and > understand that you need (1) to create your deployment directories and > (2) that you need to build the project in a different way than [4], in > order to deploy the three WAR files onto an external Java EE container > - you might also be interested in configuring which DBMS [8] to use > for internal storage (default is PostgreSQL) > > Finally, you might find several posts about practical configurations in > my company's blog [9] - but, please, only consider the most reasonably > recent ones: did you notice that the post by Colm you started from is *6 > years old*??!? > > Hope this helps. > Regards. > > [1] http://syncope.apache.org/ > [2] http://syncope.apache.org/downloads > [3] http://syncope.apache.org/docs/getting-started.html > [4] http://syncope.apache.org/docs/getting-started.html#create-project > [5] http://syncope.apache.org/docs/getting-started.html#embedded-mode > [6] http://syncope.apache.org/docs/getting-started.html#moving-forward > [7] > http://syncope.apache.org/docs/reference-guide.html#deployment-directories > [8] http://syncope.apache.org/docs/reference-guide.html#dbms > [9]https://www.tirasa.net/en/blog > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > > > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > > > > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ >
