You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Dino Mifsud <di...@gmail.com> on 2017/07/25 17:12:50 UTC
H2 Database
I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
Thanks
Re: H2 Database
Posted by Andrea Patricelli <an...@apache.org>.
Hi,
Il 26/07/2017 12:32, Dino Mifsud ha scritto:
> Hi Yes...I solved the issue it now starts well. Apparently it was
> caused by jdbc pool setting in Tomcat which I had set up following the
> steps here:
>
> https://syncope.apache.org/docs/reference-guide.html#apache-tomcat-8-and-8-5
>
> are these settings not needed for Tomcat?
>
Yes those settings are needed.
Best regards,
Andrea
>
>> On 26 Jul 2017, at 12:15 PM, Andrea Patricelli
>> <andreapatricelli@apache.org <ma...@apache.org>> wrote:
>>
>> Have you created database syncope with credentials syncope/syncope?
>>
>> And, moreover, have you carefully followed DBMS configuration guide
>> at [1]?
>> Be careful while editing provisioning.properties and
>> Master.properties, you have only to update some lines, not all the file.
>>
>> [1] https://syncope.apache.org/docs/reference-guide.html#postgresql
>>
>>
>> Il 26/07/2017 12:10, Dino Mifsud ha scritto:
>>> No I missed that thanks. It seems to have solved the issue. The
>>> database tables now seem to be created in postgres however the
>>> application still fails to start. The error in the log folder is this :
>>>
>>> 12:03:49.617 INFO
>>> org.apache.syncope.core.provisioning.java.ConnectorManager - Done
>>> loading 0 connectors
>>> 12:03:51.889 ERROR
>>> org.apache.syncope.core.provisioning.api.job.JobManager - Could not
>>> remove job taskJob89de5014-e3f5-4462-84d8-d97575740baf
>>> org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row
>>> lock: ERROR: current transaction is aborted, commands ignored until
>>> end of transaction block {prepstmnt 583897870 SELECT * FROM
>>> QRTZ_LOCKS WHERE SCHED_NAME = 'scheduler' AND LOCK_NAME = ? FOR
>>> UPDATE} [code=0, state=25P02]
>>> at
>>> org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:157)
>>> ~[quartz-2.3.0.jar:?]
>>> at
>>> org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:113)
>>> ~[quartz-2.3.0.jar:?]
>>> at
>>> org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStoreCMT.java:238)
>>> ~[quartz-2.3.0.jar:?]
>>> at
>>> org.quartz.impl.jdbcjobstore.JobStoreSupport.removeTrigger(JobStoreSupport.java:1428)
>>> ~[quartz-2.3.0.jar:?]
>>> at
>>> org.quartz.core.QuartzScheduler.unscheduleJob(QuartzScheduler.java:1059)
>>> ~[quartz-2.3.0.jar:?]
>>> at org.quartz.impl.StdScheduler.unscheduleJob(StdScheduler.java:311)
>>> ~[quartz-2.3.0.jar:?]
>>> at
>>> org.apache.syncope.core.provisioning.java.job.JobManagerImpl.unregisterJob(JobManagerImpl.java:262)
>>> ~[syncope-core-provisioning-java-2.0.4.jar:2.0.4]
>>> at
>>> org.apache.syncope.core.provisioning.java.job.JobManagerImpl.registerJob(JobManagerImpl.java:157)
>>> ~[syncope-core-provisioning-java-2.0.4.jar:2.0.4]
>>> at
>>> org.apache.syncope.core.provisioning.java.job.JobManagerImpl.register(JobManagerImpl.java:237)
>>> ~[syncope-core-provisioning-java-2.0.4.jar:2.0.4]
>>> at
>>> org.apache.syncope.core.provisioning.java.job.JobManagerImpl$3.exec(JobManagerImpl.java:334)
>>> ~[syncope-core-provisioning-java-2.0.4.jar:2.0.4]
>>> at
>>> org.apache.syncope.core.provisioning.java.job.JobManagerImpl$3.exec(JobManagerImpl.java:324)
>>> ~[syncope-core-provisioning-java-2.0.4.jar:2.0.4]
>>> at
>>> org.apache.syncope.core.spring.security.AuthContextUtils.execWithAuthContext(AuthContextUtils.java:136)
>>> ~[syncope-core-spring-2.0.4.jar:2.0.4]
>>> at
>>> org.apache.syncope.core.provisioning.java.job.JobManagerImpl.load(JobManagerImpl.java:324)
>>> ~[syncope-core-provisioning-java-2.0.4.jar:2.0.4]
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> ~[?:1.8.0_91]
>>> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
>>> at
>>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)
>>> ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
>>> ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>>> ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
>>> ~[spring-tx-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282)
>>> ~[spring-tx-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
>>> ~[spring-tx-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.apache.syncope.core.persistence.jpa.spring.DomainTransactionInterceptor.invoke(DomainTransactionInterceptor.java:64)
>>> ~[syncope-core-persistence-jpa-2.0.4.jar:2.0.4]
>>> at
>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>>> ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
>>> ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at com.sun.proxy.$Proxy133.load(Unknown Source) ~[?:?]
>>> at
>>> org.apache.syncope.core.logic.init.LogicInitializer.afterPropertiesSet(LogicInitializer.java:70)
>>> ~[syncope-core-logic-2.0.4.jar:2.0.4]
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
>>> ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
>>> ~[spring-context-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
>>> ~[spring-context-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443)
>>> ~[spring-web-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325)
>>> ~[spring-web-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107)
>>> ~[spring-web-4.3.9.RELEASE.jar:4.3.9.RELEASE]
>>> at
>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4738)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1678)
>>> ~[catalina.jar:8.0.28]
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> ~[?:1.8.0_91]
>>> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
>>> at
>>> org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
>>> ~[tomcat-coyote.jar:8.0.28]
>>> at
>>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
>>> ~[?:1.8.0_91]
>>> at
>>> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
>>> ~[?:1.8.0_91]
>>> at
>>> org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:463)
>>> ~[catalina.jar:8.0.28]
>>> at
>>> org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:413)
>>> ~[catalina.jar:8.0.28]
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> ~[?:1.8.0_91]
>>> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
>>> at
>>> org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
>>> ~[tomcat-coyote.jar:8.0.28]
>>> at
>>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
>>> ~[?:1.8.0_91]
>>> at
>>> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
>>> ~[?:1.8.0_91]
>>> at
>>> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
>>> ~[?:1.8.0_91]
>>> at
>>> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
>>> ~[?:1.8.0_91]
>>> at
>>> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
>>> ~[?:1.8.0_91]
>>> at
>>> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
>>> ~[?:1.8.0_91]
>>> at
>>> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
>>> ~[?:1.8.0_91]
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> ~[?:1.8.0_91]
>>> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
>>> at
>>> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
>>> ~[?:1.8.0_91]
>>> at sun.rmi.transport.Transport$1.run(Transport.java:200) ~[?:1.8.0_91]
>>> at sun.rmi.transport.Transport$1.run(Transport.java:197) ~[?:1.8.0_91]
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> ~[?:1.8.0_91]
>>> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>>> ~[?:1.8.0_91]
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> ~[?:1.8.0_91]
>>> at
>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>>> ~[?:1.8.0_91]
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> [?:1.8.0_91]
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> [?:1.8.0_91]
>>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]
>>>> On 26 Jul 2017, at 10:53 AM, Andrea Patricelli
>>>> <andreapatricelli@apache.org <ma...@apache.org>>
>>>> wrote:
>>>>
>>>> have you also run
>>>>
>>>> $ 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/customForm.json /opt/syncope/conf
>>>>
>>>> As explained here [1]?
>>>>
>>>> [1] https://syncope.apache.org/docs/reference-guide.html#customization
>>>>
>>>> Il 26/07/2017 10:43, Dino Mifsud ha scritto:
>>>>> Yes actually it seems the build is using the test profiles as also
>>>>> the syncope-console tries to connect to syncope/rest on port 9080
>>>>> instead of 8080. How can I solve this pls?
>>>>>
>>>>>> On 26 Jul 2017, at 9:45 AM, Andrea Patricelli
>>>>>> <andreapatricelli@apache.org
>>>>>> <ma...@apache.org>> wrote:
>>>>>>
>>>>>> It seems that your installation is using test Master.properties file.
>>>>>> What is the content of your
>>>>>> core/src/main/resources/domains/Master.properties?
>>>>>>
>>>>>> What kind of JEE container are you using? About this please refer
>>>>>> to [1]?
>>>>>>
>>>>>> Best regards,
>>>>>> Andrea
>>>>>>
>>>>>> [1]
>>>>>> https://syncope.apache.org/docs/reference-guide.html#javaee-container
>>>>>>
>>>>>> Il 26/07/2017 09:28, Dino Mifsud ha scritto:
>>>>>>> Hi Yes, I followed those steps and generated with maven archetype however it still seems to be going towards H2 database. Infant it complains that it cannot find the H2 jar file.
>>>>>>>
>>>>>>>
>>>>>>>> On 25 Jul 2017, at 7:12 PM, Dino Mifsud<di...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>> --
>>>>>> Dott. Andrea Patricelli
>>>>>> Tel. +39 3204524292
>>>>>>
>>>>>> Developer @ Tirasa S.r.l.
>>>>>> Viale D'Annunzio 267 - 65127 Pescara
>>>>>> Tel +39 0859116307 / FAX +39 0859111173
>>>>>> http://www.tirasa.net
>>>>>>
>>>>>> Apache Syncope PMC Member
>>>>>
>>>>
>>>> --
>>>> Dott. Andrea Patricelli
>>>> Tel. +39 3204524292
>>>>
>>>> Developer @ Tirasa S.r.l.
>>>> Viale D'Annunzio 267 - 65127 Pescara
>>>> Tel +39 0859116307 / FAX +39 0859111173
>>>> http://www.tirasa.net
>>>>
>>>> Apache Syncope PMC Member
>>>
>>
>> --
>> Dott. Andrea Patricelli
>> Tel. +39 3204524292
>>
>> Developer @ Tirasa S.r.l.
>> Viale D'Annunzio 267 - 65127 Pescara
>> Tel +39 0859116307 / FAX +39 0859111173
>> http://www.tirasa.net
>>
>> Apache Syncope PMC Member
>
--
Dott. Andrea Patricelli
Tel. +39 3204524292
Developer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net
Apache Syncope PMC Member
Re: H2 Database
Posted by Andrea Patricelli <an...@apache.org>.
have you also run
$ 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/customForm.json /opt/syncope/conf
As explained here [1]?
[1] https://syncope.apache.org/docs/reference-guide.html#customization
Il 26/07/2017 10:43, Dino Mifsud ha scritto:
> Yes actually it seems the build is using the test profiles as also the
> syncope-console tries to connect to syncope/rest on port 9080 instead
> of 8080. How can I solve this pls?
>
>> On 26 Jul 2017, at 9:45 AM, Andrea Patricelli
>> <andreapatricelli@apache.org <ma...@apache.org>> wrote:
>>
>> It seems that your installation is using test Master.properties file.
>> What is the content of your
>> core/src/main/resources/domains/Master.properties?
>>
>> What kind of JEE container are you using? About this please refer to [1]?
>>
>> Best regards,
>> Andrea
>>
>> [1] https://syncope.apache.org/docs/reference-guide.html#javaee-container
>>
>> Il 26/07/2017 09:28, Dino Mifsud ha scritto:
>>> Hi Yes, I followed those steps and generated with maven archetype however it still seems to be going towards H2 database. Infant it complains that it cannot find the H2 jar file.
>>>
>>>
>>>> On 25 Jul 2017, at 7:12 PM, Dino Mifsud<di...@gmail.com> wrote:
>>>>
>>>> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>>>>
>>>>
>>>> Thanks
>> --
>> Dott. Andrea Patricelli
>> Tel. +39 3204524292
>>
>> Developer @ Tirasa S.r.l.
>> Viale D'Annunzio 267 - 65127 Pescara
>> Tel +39 0859116307 / FAX +39 0859111173
>> http://www.tirasa.net
>>
>> Apache Syncope PMC Member
>
--
Dott. Andrea Patricelli
Tel. +39 3204524292
Developer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net
Apache Syncope PMC Member
Re: H2 Database
Posted by Dino Mifsud <di...@gmail.com>.
Yes actually it seems the build is using the test profiles as also the syncope-console tries to connect to syncope/rest on port 9080 instead of 8080. How can I solve this pls?
> On 26 Jul 2017, at 9:45 AM, Andrea Patricelli <an...@apache.org> wrote:
>
> It seems that your installation is using test Master.properties file.
> What is the content of your core/src/main/resources/domains/Master.properties?
>
> What kind of JEE container are you using? About this please refer to [1]?
>
> Best regards,
> Andrea
>
> [1] https://syncope.apache.org/docs/reference-guide.html#javaee-container <https://syncope.apache.org/docs/reference-guide.html#javaee-container>
>
> Il 26/07/2017 09:28, Dino Mifsud ha scritto:
>> Hi Yes, I followed those steps and generated with maven archetype however it still seems to be going towards H2 database. Infant it complains that it cannot find the H2 jar file.
>>
>>
>>> On 25 Jul 2017, at 7:12 PM, Dino Mifsud <di...@gmail.com> <ma...@gmail.com> wrote:
>>>
>>> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>>>
>>>
>>> Thanks
> --
> Dott. Andrea Patricelli
> Tel. +39 3204524292
>
> Developer @ Tirasa S.r.l.
> Viale D'Annunzio 267 - 65127 Pescara
> Tel +39 0859116307 / FAX +39 0859111173
> http://www.tirasa.net <http://www.tirasa.net/>
>
> Apache Syncope PMC Member
Re: H2 Database
Posted by Dino Mifsud <di...@gmail.com>.
Master properties file content is
Master.driverClassName=org.postgresql.Driver
Master.url=jdbc:postgresql://localhost:5432/syncope
Master.schema=
Master.username=syncope
Master.password=syncope
Master.databasePlatform=org.apache.openjpa.jdbc.sql.PostgresDictionary
Master.orm=META-INF/spring-orm.xml
Master.pool.maxActive=10
Master.pool.minIdle=2
Master.audit.sql=audit.sql
Its actually as it is generated...I don't need to change it as the properties are good.
I am using Tomcat as a container
mvn archetype:generate \
-DarchetypeGroupId=org.apache.syncope \
-DarchetypeArtifactId=syncope-archetype \
-DarchetypeRepository=http://repo1.maven.org/maven2 \
-DarchetypeVersion=2.0.4
> On 26 Jul 2017, at 9:45 AM, Andrea Patricelli <an...@apache.org> wrote:
>
> It seems that your installation is using test Master.properties file.
> What is the content of your core/src/main/resources/domains/Master.properties?
>
> What kind of JEE container are you using? About this please refer to [1]?
>
> Best regards,
> Andrea
>
> [1] https://syncope.apache.org/docs/reference-guide.html#javaee-container <https://syncope.apache.org/docs/reference-guide.html#javaee-container>
>
> Il 26/07/2017 09:28, Dino Mifsud ha scritto:
>> Hi Yes, I followed those steps and generated with maven archetype however it still seems to be going towards H2 database. Infant it complains that it cannot find the H2 jar file.
>>
>>
>>> On 25 Jul 2017, at 7:12 PM, Dino Mifsud <di...@gmail.com> <ma...@gmail.com> wrote:
>>>
>>> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>>>
>>>
>>> Thanks
> --
> Dott. Andrea Patricelli
> Tel. +39 3204524292
>
> Developer @ Tirasa S.r.l.
> Viale D'Annunzio 267 - 65127 Pescara
> Tel +39 0859116307 / FAX +39 0859111173
> http://www.tirasa.net <http://www.tirasa.net/>
>
> Apache Syncope PMC Member
Re: H2 Database
Posted by Andrea Patricelli <an...@apache.org>.
It seems that your installation is using test Master.properties file.
What is the content of your
core/src/main/resources/domains/Master.properties?
What kind of JEE container are you using? About this please refer to [1]?
Best regards,
Andrea
[1] https://syncope.apache.org/docs/reference-guide.html#javaee-container
Il 26/07/2017 09:28, Dino Mifsud ha scritto:
> Hi Yes, I followed those steps and generated with maven archetype however it still seems to be going towards H2 database. Infant it complains that it cannot find the H2 jar file.
>
>
>> On 25 Jul 2017, at 7:12 PM, Dino Mifsud <di...@gmail.com> wrote:
>>
>> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>>
>>
>> Thanks
--
Dott. Andrea Patricelli
Tel. +39 3204524292
Developer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net
Apache Syncope PMC Member
Re: H2 Database
Posted by Dino Mifsud <di...@gmail.com>.
Hi Yes, I followed those steps and generated with maven archetype however it still seems to be going towards H2 database. Infant it complains that it cannot find the H2 jar file.
> On 25 Jul 2017, at 7:12 PM, Dino Mifsud <di...@gmail.com> wrote:
>
> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>
>
> Thanks
Re: H2 Database
Posted by Andrea Patricelli <an...@apache.org>.
Hi Dino,
are you generating the project from archetype like described at [1] or
are you using another evaluation method?
Supposing that you are using the archetype you can refer to [2] and [3]
in order to setup PostreSQL DBMS.
[1] https://syncope.apache.org/docs/getting-started.html#create-project
[2]
https://syncope.apache.org/docs/reference-guide.html#system-administration
[3] https://syncope.apache.org/docs/reference-guide.html#postgresql
Il 25/07/2017 19:12, Dino Mifsud ha scritto:
> I would like to use a postgres DB instead of the H2 database. I did the changes in Master.properties file as shown but still it seems it is using the H2 database. What could be the problem please?
>
>
> Thanks
--
Dott. Andrea Patricelli
Tel. +39 3204524292
Developer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net
Apache Syncope PMC Member