[midPoint] Running midPoint at the tomcat root

[Aivo Kuhlberg]

Hi Ivan,
Yes, I have only one midPoint clean install. When I do NOT add the Context line into the server.xml then the startup succeeds. But when I add this line then it seems that midPoint starts up 2 times - at last I see the midPoint bootscreen 2 times in idm.log and some error messages complaining:
cannot initialize TaskManager due to the following exception: Cannot initialize the Quartz scheduler.

Aivo


________________________________
Saatja: midPoint <midpoint-bounces at lists.evolveum.com> nimelIvan Noris <Ivan.Noris at evolveum.com>
Saadetud: 12. aprill 2017 14:22
Adressaat: midPoint General Discussion
Teema: Re: [midPoint] Running midPoint at the tomcat root

Hi Aivo,
I have never seen this although I have also never used midpoint as tomcat root app. (I used apache httpd rewrite module for this.)
But - don't you have TWO midpoints deployed? Two nodes or two WAR files in the same Tomcat...?

Ivan


________________________________
From: "Aivo Kuhlberg" <aivo.kuhlberg at rmit.ee>
To: "midpoint" <midpoint at lists.evolveum.com>
Sent: Wednesday, April 12, 2017 1:03:18 PM
Subject: [midPoint] Running midPoint at the tomcat root


Hi,
I am trying to run single midPoint instance at the tomcat root level so that my midPoint address should look like http://my.server.name:port instead of http://my.server.name:port/midpoint.
I found that by adding following line to conf/server.xml should solve the problem:

        <Context path="" docBase="midpoint" debug="0" reloadable="false" useHttpOnly="true"></Context>


This line should be added just before </Host> line. And in pronciple it works. Unfortunately after that I see every 10 seconds following errors:

2017-04-12 13:45:55,730 [] [ClusterManagerThread] ERROR (com.evolveum.midpoint.task.quartzimpl.cluster.NodeRegistrar): The record of this node cannot be read (OID d06c11c8-ba05-4abe-a721-0fa992c7b554 not found), but another node record with the name 'DefaultNode' exists. It seems that in this cluster there are two or more nodes with the same name 'DefaultNode'. Stopping the scheduler to minimize the damage., reason: Object of type 'NodeType' with oid 'd06c11c8-ba05-4abe-a721-0fa992c7b554' was not found. (class com.evolveum.midpoint.util.exception.ObjectNotFoundException)
2017-04-12 13:45:55,731 [] [ClusterManagerThread] INFO (com.evolveum.midpoint.task.quartzimpl.execution.LocalNodeManager): Shutting down Quartz scheduler
2017-04-12 13:45:55,731 [] [ClusterManagerThread] INFO (com.evolveum.midpoint.task.quartzimpl.execution.LocalNodeManager): Quartz scheduler was shut down
2017-04-12 13:45:55,731 [] [ClusterManagerThread] WARN (com.evolveum.midpoint.task.quartzimpl.cluster.NodeRegistrar): Scheduler stopped, please check your cluster configuration as soon as possible; kind of error = DUPLICATE_NODE_ID_OR_NAME
2017-04-12 13:45:55,735 [] [ClusterManagerThread] ERROR (com.evolveum.midpoint.task.quartzimpl.cluster.NodeRegistrar): Cannot update registration of this node (name DefaultNode, oid d06c11c8-ba05-4abe-a721-0fa992c7b554), because it does not exist in repository. It is probably caused by cluster misconfiguration (other node rewriting the Node object?) Stopping the scheduler., reason: Object of type 'NodeType' with oid 'd06c11c8-ba05-4abe-a721-0fa992c7b554' was not found. (class com.evolveum.midpoint.util.exception.ObjectNotFoundException)

Does anybody have any ideas what should I do to fix these errors or change my setup.
My environment: midpoint 3.5.1, tomcat 8.0.43, JAVA 1.8.0_121

Thanks,
Aivo Kuhlberg

________________________________
Käesolev e-kiri võib sisaldada asutusesiseseks kasutamiseks tunnistatud teavet.
This e-mail may contain information which is classified for official use.
_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint



--
Ivan Noris
Senior Identity Engineer
evolveum.com

________________________________
Käesolev e-kiri võib sisaldada asutusesiseseks kasutamiseks tunnistatud teavet.
This e-mail may contain information which is classified for official use.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170412/d9afc232/attachment.htm>