[midPoint] DOCKERED MIDPONT (2 NODES) RUNNING ON AN ORACLE CLUSTER
Oleksandr Nekriach
o.nekriach at dynatech.lv
Tue Apr 24 16:18:35 CEST 2018
Hi Fabian,
Try to find misconfiguration in jmx settings.
PS.If you expect from community help you should send more information. To
help you find misconfiguration share whole startup logs, configuration and
start up scripts (user name and password can be replaced with username1
password1 and etc).
On 24 April 2018 at 15:40, Fabian Bosch <fabian.bosch at daasi.de> wrote:
> Same here with mariaDB and midPoint v3.7.1.
> Any solution to this?
>
> regards
>
> Fabian
>
> -- Midpoint 3.7.1 --
>
> [embedded Tomcat opts (midpoint.sh)]
>
> JAVA_OPTS="$JAVA_OPTS
> -Xms2048M
> -Xmx2048M
> -Dpython.cachedir=$MIDPOINT_HOME/tmp
> -Djavax.net.ssl.trustStore=$MIDPOINT_HOME/keystore.jceks
> -Djavax.net.ssl.trustStoreType=jceks
> -Dmidpoint.home=$MIDPOINT_HOME
> -Dmidpoint.nodeId=NodeA
> -Dcom.sun.management.jmxremote.port=20001
> -Dcom.sun.management.jmxremote.rmi.port=20001
> -Dcom.sun.management.jmxremote.ssl=false
> -Dcom.sun.management.jmxremote.password.file=/opt/
> midpoint/midpoint-3.7-home/jmxremote.password
> -Dcom.sun.management.jmxremote.access.file=/opt/
> midpoint/midpoint-3.7-home/jmxremote.access"
>
> [MidPoint-Config]
>
> <repository>
> <repositoryServiceFactoryClass>com.evolveum.midpoint.repo.
> sql.SqlRepositoryFactory</repositoryServiceFactoryClass>
> <baseDir>${midpoint.home}</baseDir>
> <embedded>false</embedded>
> <asServer>true</asServer>
> <driverClassName>org.mariadb.jdbc.Driver</driverClassName>
> <jdbcUsername>midpoint</jdbcUsername>
> <jdbcPassword>secret</jdbcPassword>
> <jdbcUrl>jdbc:mariadb://midpoint.remote.tld:3306/
> midpoint?characterEncoding=utf-8;LOCK_MODE=1;DB_CLOSE_ON_
> EXIT=FALSE;LOCK_TIMEOUT=10000</jdbcUrl>
> <hibernateDialect>com.evolveum.midpoint.repo.sql.
> util.MidPointMySQLDialect</hibernateDialect>
> <hibernateHbm2ddl>validate</hibernateHbm2ddl>
> </repository>
> <taskManager>
> <clustered>true</clustered>
> <jmxUsername>midpoint</jmxUsername>
> <jmxPassword>secret</jmxPassword>
> </taskManager>
>
> Am 24.10.2017 um 21:51 schrieb Carlos Ferreira:
>
> Hi,
>
> 1. I have downloaded the evolveum/midpoint image from docker hub;
>
> 2. I have create 2 containers, each one running MIDPOINT in 2 separate
> servers;
>
> 3. I configured the Config.xml file (in both nodes):
>
> *********************** /var/opt/midpoint/config.xml
> ****************************************************
>
> (...)
>
> <configuration>
> <midpoint>
> <webApplication>
> <importFolder>${midpoint.home}/import</importFolder>
> </webApplication>
> <repository>
> <repositoryServiceFactoryClass>com.evolveum.midpoint.repo.
> sql.SqlRepositoryFactory</repositoryServiceFactoryClass>
> <baseDir>${midpoint.home}</baseDir>
> <embedded>false</embedded>
> <asServer>true</asServer>
> <database>oracle</database>
> <jdbcUsername>midpoint_wi</jdbcUsername>
> <jdbcPassword>secret</jdbcPassword>
> <jdbcUrl>jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL =
> TCP)(HOST = orarac.trt)(PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA =
> (SERVER = DEDICATED) (SERVICE_NAME = prod.trt3.jus.br)))</jdbcUrl>
> </repository>
> <taskManager>
> <clustered>true</clustered>
> <jmxUsername>midpoint</jmxUsername>
> <jmxPassword>secret</jmxPassword>
> </taskManager>
>
> (...)
> *********************** /var/opt/midpoint/config.xml
> ****************************************************
>
>
> ----->>> midpoint was configured to access an ORACLE DATABASE running in a
> CLUSTER;
>
>
> 4. The setenv.sh (/usr/local/tomcat/bin/setenv.sh) file has been
> configured as follows:
>
> a) on node A
> CATALINA_OPTS="-Dmidpoint.nodeId=NodeA -Dmidpoint.home=/var/opt/midpoint/
> -Dcom.sun.management.jmxremote=true -Dmidpoint.jmxHostName=10.3.190.47
> -Dcom.sun.management.jmx
> remote.port=20001 -Dcom.sun.management.jmxremote.ssl=false
> -Dcom.sun.management.jmxremote.password.file=/var/opt/midpoint/jmxremote.password
> -Dcom.sun.management.jmxremo
> te.access.file=/var/opt/midpoint/jmxremote.access"
>
> b) on node B
> CATALINA_OPTS="-Dmidpoint.nodeId=NodeB -Dmidpoint.home=/var/opt/midpoint/
> -Dcom.sun.management.jmxremote=true -Dmidpoint.jmxHostName=10.3.190.79
> -Dcom.sun.management.jmx
> remote.port=20002 -Dcom.sun.management.jmxremote.ssl=false
> -Dcom.sun.management.jmxremote.password.file=/var/opt/midpoint/jmxremote.password
> -Dcom.sun.management.jmxremo
> te.access.file=/var/opt/midpoint/jmxremote.access"
>
>
> 3. I have run the script that creates on necessary objects (tables, etc)
> in the oracle database;
>
> 4. When I start the first node (A, for example), I am able to log in;
>
> 5. When I try to login in in the second node (B), I receive the following
> message:
>
> " Currently we are unable to process your request. Kindly try again later."
>
> 6. In the "idm.log" file, I have the message:
>
> 2017-10-24 19:35:05,771 [] [QuartzScheduler_midPointScheduler-NodeB_ClusterManager]
> WARN (org.quartz.impl.jdbcjobstore.JobStoreTX): This scheduler instance
> (NodeB) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
>
> 7. If I drop all the objects and re-execute the install script and try to
> login firstly from node B, I am successful. Nevertheless, I receive the
> same error message when trying to log in from node A.
>
>
> Did I miss anything?
>
>
> Thks,
>
> Carlos A Ferreira
>
>
> _______________________________________________
> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
--
Best regards,
Oleksandr Nekriach | Identity and access management engineer
Dynatech, Mednieku str. 4a, Riga, LV-1010, Latvia
<https://maps.google.com/?q=Mednieku+str.+4a,+Riga,+LV-1010,+Latvia&entry=gmail&source=g>
+37125314685 <+371%2025%20314%20685>
,
o.nekriach at dynatech.lv
|
www.dynatech.lv
Stay connected:
<https://www.facebook.com/DynatechLatvia/?ref=br_rs>
<https://www.linkedin.com/company-beta/17893047/>
Confidentiality Notice: This message contains confidential information and
is intended only for the named recipient(s). If you are not the addressee
you may not copy, distribute or perform any other activities with this
information. If you have received this transmission in error, please notify
us by e-mail immediately. E-mail transmission cannot be guaranteed to be
secure or error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180424/5faf1eb6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: o.nekriach at dynatech.lv1520941785292-7771
Type: image/png
Size: 790 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180424/5faf1eb6/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: o.nekriach at dynatech.lv1520941785292-7770
Type: image/png
Size: 4265 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180424/5faf1eb6/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: o.nekriach at dynatech.lv1520941785292-7772
Type: image/png
Size: 786 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180424/5faf1eb6/attachment-0002.png>
More information about the midPoint
mailing list