Re: invalidmapping [only propagation allowed for derived]
Neat! It was just a matter of clicking on the "->" arrow in the mapping window. Thanks Andrea Best Regards, Arnold Miller Sent: Wednesday, March 25, 2020 at 2:35 AM From: "Andrea Patricelli" To: user@syncope.apache.org Subject: Re: invalidmapping [only propagation allowed for derived] Hi Arnold, Since derived attributes' values are generated, you can only propagate them (towards the resource, i.e. identity-store). You cannot pull from the identity-store the value of a derived attribute simply because its values are derived from other (plain) attributes ones. If you are pushing data towards a resource, i.e. execute a propagation task, you have to define the mapping for the derived attribute(s) as propagation only (->). Please refer to 1, 2 and 3. HTH, Andrea [1] https://syncope.apache.org/docs/2.1/reference-guide.html#propagation [2] https://syncope.apache.org/docs/2.1/reference-guide.html#mapping [3] https://syncope.apache.org/docs/2.1/reference-guide.html#derived Il 25/03/20 00:58, Arnold Miller ha scritto: Hi there! I'm trying to sync first and last names to a single full name to an identity store by using a push task, so I created a derived schema with the combination of both; however, when I try to map this the system says: invalidmapping [only propagation allowed for derived] Does anybody know what to do in this case? Thank you! Best Regards, Arnold Miller -- Dott. Andrea Patricelli Tel. +39 3204524292 Engineer @ Tirasa S.r.l. Viale Vittoria Colonna 97 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member
invalidmapping [only propagation allowed for derived]
Hi there! I'm trying to sync first and last names to a single full name to an identity store by using a push task, so I created a derived schema with the combination of both; however, when I try to map this the system says: invalidmapping [only propagation allowed for derived] Does anybody know what to do in this case? Thank you! Best Regards, Arnold Miller
Re: How to delete old users
Looks like I might need something else. I see this in my logs: "Sync script: found 1411 events to sync." However, when I go to realms it shows a different number: "Showing 1 to 10 of 1526 rows" That's the number I expect to be decreased. It should be 1411, isn't it? That's the whole number of users that the query brings Best Regards, Arnold Miller Sent: Tuesday, October 22, 2019 at 4:45 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: How to delete old users On 21/10/19 22:40, Arnold Miller wrote: Hi Francesco, I set my Pull Task in INCREMENTAL mode and the SYNC operation was already available for the related connector but Syncope did not delete any old users. Any clues? Task configuration: Pull mode: Incremental Matching rule: Update Unmatching rule: Provision Allow create: checked Allow update: checked Allow delete: unchecked Sync status: unchecked Ah! Of course "Allow delete" should be checked... Regards. Sent: Saturday, October 12, 2019 at 6:59 AM From: "Francesco Chicchiriccò" To: user Subject: Re: How to delete old users On Il 11-ott-19, alle 22:33, Arnold Miller wrote: Hi! How can I configure Syncope to delete users that are not anymore in the identity store where I pulled them from? I'm currently using version 2.1.4 Hi, you need to set your Pull Task in INCREMENTAL mode [1], as "This is the only mode which allows pulling delete events". Beware that ConnId's SYNC operation must be available for the related connector, otherwise incremental pull is not possible. HTH Regards. [1] http://syncope.apache.org/docs/2.1/reference-guide.html#pull-mode -- 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/
Re: How to delete old users
Hi Francesco, I set my Pull Task in INCREMENTAL mode and the SYNC operation was already available for the related connector but Syncope did not delete any old users. Any clues? Task configuration: Pull mode: Incremental Matching rule: Update Unmatching rule: Provision Allow create: checked Allow update: checked Allow delete: unchecked Sync status: unchecked Best Regards, Arnold Miller Sent: Saturday, October 12, 2019 at 6:59 AM From: "Francesco Chicchiriccò" To: user Subject: Re: How to delete old users On Il 11-ott-19, alle 22:33, Arnold Miller wrote: Hi! How can I configure Syncope to delete users that are not anymore in the identity store where I pulled them from? I'm currently using version 2.1.4 Hi, you need to set your Pull Task in INCREMENTAL mode [1], as "This is the only mode which allows pulling delete events". Beware that ConnId's SYNC operation must be available for the related connector, otherwise incremental pull is not possible. HTH Regards. [1] http://syncope.apache.org/docs/2.1/reference-guide.html#pull-mode -- 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/
How to delete old users
Hi! How can I configure Syncope to delete users that are not anymore in the identity store where I pulled them from? I'm currently using version 2.1.4 Thanks Best Regards, Arnold Miller
Re: Error in Syncope 2.1.3
It happens the same issue with 2.1.4 Best Regards, Arnold Miller Sent: Friday, May 10, 2019 at 1:25 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Error in Syncope 2.1.3 Hi, any particular reason to stick with 2.1.3? 2.1.4 has been available for few weeks, try with that first. Regards. On 08/05/19 22:53, Arnold Miller wrote: Hi, I was configuring my recently installed 2.1.3 Syncope then suddenly I started getting a popup window with the message described below everytime I needed to add a connector, a resource, a mapping or a task: Warning! Operation is taking to long: it will be executed in background. Please check later for the result (errors won't be triggered). My console.log has a bunch of these exceptions: 14:43:14.589 ERROR org.apache.syncope.client.console.SyncopeConsoleSession - Could not execute org.apache.syncope.client.console.topology.TopologyWebSocketBehavior$ResourceChecker@1a9c9401 org.springframework.core.task.TaskRejectedException: Executor [java.util.concurrent.ThreadPoolExecutor@6c49d740[Running, pool size = 20, active threads = 20, queued tasks = 50, completed tasks = 0]] did not accept task: org.apache.syncope.client.console.topology.TopologyWebSocketBehavior$ResourceChecker@1a9c9401 at org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor.submit(ThreadPoolTaskExecutor.java:344) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE] at org.apache.syncope.client.console.SyncopeConsoleSession.execute(SyncopeConsoleSession.java:132) ~[syncope-client-console-2.1.3.jar:2.1.3] at org.apache.syncope.client.console.topology.TopologyWebSocketBehavior.timeoutHandlingConnectionChecker(TopologyWebSocketBehavior.java:183) ~[syncope-client-console-2.1.3.jar:2.1.3] at org.apache.syncope.client.console.topology.TopologyWebSocketBehavior.access$300(TopologyWebSocketBehavior.java:51) ~[syncope-client-console-2.1.3.jar:2.1.3] at org.apache.syncope.client.console.topology.TopologyWebSocketBehavior$ResCheck.run(TopologyWebSocketBehavior.java:256) ~[syncope-client-console-2.1.3.jar:2.1.3] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_152] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_152] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152] Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@145b68fa rejected from java.util.concurrent.ThreadPoolExecutor@6c49d740[Running, pool size = 20, active threads = 20, queued tasks = 50, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) ~[?:1.8.0_152] at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) ~[?:1.8.0_152] at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) ~[?:1.8.0_152] at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) ~[?:1.8.0_152] at org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor.submit(ThreadPoolTaskExecutor.java:341) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE] ... 7 more 14:43:24.548 ERROR org.apache.syncope.client.console.SyncopeConsoleSession - Could not execute org.apache.syncope.client.console.topology.TopologyWebSocketBehavior$ConnCheck@6680129f org.springframework.core.task.TaskRejectedException: Executor [java.util.concurrent.ThreadPoolExecutor@6c49d740[Running, pool size = 20, active threads = 20, queued tasks = 50, completed tasks = 0]] did not accept task: org.apache.syncope.client.console.topology.TopologyWebSocketBehavior$ConnCheck@6680129f at org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor.execute(ThreadPoolTaskExecutor.java:317) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE] at org.apache.syncope.client.console.SyncopeConsoleSession.execute(SyncopeConsoleSession.java:124) ~[syncope-client-console-2.1.3.jar:2.1.3] at org.apache.syncope.client.console.topology.TopologyWebSocketBehavior.onMessage(TopologyWebSocketBehavior.java:124) ~[syncope-client-console-2.1.3.jar:2.1.3] at org.apache.wicket.protocol.ws.api.WebSocketBehavior.onEvent(WebSocketBehavior.java:64) ~[wicket-native-websocket-core-8.2.0.jar:8.2.0] at org.apache.wicket.settings.FrameworkSettings.dispatchEvent(FrameworkSettings.java:147) ~[wicket-core-8.2.0.jar:8.2.0] at org.apache.wicket.ComponentEventSender.dispatchToComponent(ComponentEventSender.java:292) ~[wicket-core-8.2.0.jar:8.2.0] at org.apache.wicket.ComponentEventSender.access$100(ComponentEventSender.java:36) ~[wicket-core-8.2.0.jar:8.2.0] at org.apache.wicket.ComponentEventSender$ComponentEventVisitor.component(ComponentEventSender.java:329) ~[wicket-core-8.2.0.jar:8.2.0] at org.apache.wicket.ComponentEventSender$ComponentEventVisitor.component(ComponentEventSender.java:306) ~[wicket-core-
Error in Syncope 2.1.3
ecute(ThreadPoolTaskExecutor.java:314) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE] ... 45 more I'm stuck. Help is appreciated. PD: I restarted Tomcat but it happened again. Best Regards, Arnold Miller
Re: Slow task
> I'm on 2.1.1 Does it mean I should upgrade to one of the fix versions specified there? 2.0.12, 2.1.3, 3.0.0 My guess is that going from 2.1.1 to 2.1.3 is the less painful option. Are there any guidelines somewhere? One more thing I'd like to know: Sounds to me like the read afterwards is unnecessary. Could it be disabled by configuration? Additionally, guessing the performance after the upgrade it would be: 3 seconds per 5 scripts changes to 1.8 seconds per 3 scripts (using an easy rule of 3). Then 18000*1.8 = 32400 seconds = 540 minutes = 9 hours That's a lot still! Best Regards, Arnold Miller Sent: Thursday, April 04, 2019 at 12:47 PM From: "Arnold Miller" To: user@syncope.apache.org Subject: Re: Slow task I'm on 2.1.1 Does it mean I should upgrade to one of the fix versions specified there? 2.0.12, 2.1.3, 3.0.0 My guess is that going from 2.1.1 to 2.1.3 is the less painful option. Are there any guidelines somewhere? One more thing I'd like to know: Sounds to me like the read afterwards is unnecessary. Could it be disabled by configuration? Best Regards, Arnold Miller Sent: Wednesday, April 03, 2019 at 5:16 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Slow task Hi, which version are you running? This sounds like as https://issues.apache.org/jira/browse/SYNCOPE-1409 Regards. On 03/04/19 11:58, Arnold Miller wrote: > Being concerned with the slowness of the process I decided to track the execution time it takes for every script for a single user and I found: > > 16:24:17.582 INFO Search script finished. Time elapsed: 0.194 seconds Method: run > 16:24:18.251 INFO Search script finished. Time elapsed: 0.166 seconds Method: run > 16:24:18.843 INFO Update script finished. Time elapsed: 0.244 seconds Method: run > 16:24:19.417 INFO Search script finished. Time elapsed: 0.161 seconds Method: run > 16:24:19.996 INFO Search script finished. Time elapsed: 0.172 seconds Method: run > > The first most obvious question is: Why does Syncope call the search script 4 times? Additionally, I see that between the 2nd and 3rd times it calls the update script. The sum of the time elapsed for that sample is 0.937, however the time at the beginning of the line shows that the whole process can take about 3 seconds per user. > > Doing math, if I have 18k users then it will take: > 18000*3 = 54000 seconds = 900 minutes = 15 hours > (This is what is actually taking!!) > > What is it that Syncope does behind scenes? > How can I optimize this process? > > > Best Regards, > > Arnold Miller > > >> Sent: Wednesday, March 27, 2019 at 6:33 PM >> From: "Francesco Chicchiriccò" >> To: user@syncope.apache.org >> Subject: Re: Slow task >> >> On 27/03/19 17:21, Arnold Miller wrote: >>> It is a standard Push task: Resource -> Push task -> run. >> A PushTask execution will simply generate as may PropagationTasks as >> needed and then execute them; for a REST resource, it means calling the >> create or update Groovy script. >> >> Hence: your guess is correct, if you have 18000 captured by the PushTask. >> >> Regards. >> >>> *Sent:* Wednesday, March 27, 2019 at 11:06 AM >>> *From:* "Francesco Chicchiriccò" >>> *To:* user@syncope.apache.org >>> *Subject:* Re: Slow task >>> Hi, >>> what kind of task (the one running for 6+ hours) do you have? It's a >>> standard PushTask, or a SchedTask you made on purpose? >>> Regards. >>> On 27/03/19 17:03, Arnold Miller wrote: >>> >>> No. >>> My guess is that Syncope makes 18000 calls using either the create >>> or the update Groovy script. >>> Best Regards, >>> >>> Arnold Miller >>> *Sent:* Wednesday, March 27, 2019 at 7:58 AM >>> *From:* "Filipe Silva" >>> *To:* user@syncope.apache.org >>> *Subject:* Re: Slow task >>> >>> Hi >>> >>> Are you making only one call to get all the info? >>> >>> I use groovy and made pagination in the rest call. >>> >>> Regards >>> >>> Filipe Silva >>> >>> On 26/03/19 21:40, Arnold Miller wrote: >>> >>> Hi everyone, >>> I have a task running for 6 hours trying to update the >>> information of a total of 18000 users. It has processed only >>> half of them. The task consists of calling a rest web service >>> with about 10 parameters. If I run the web service call only >>> it could take about 300 milliseconds. >>> What am I doing wrong? >>> Best Regards, >>> Arnold Miller -- 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/
Re: Slow task
I'm on 2.1.1 Does it mean I should upgrade to one of the fix versions specified there? 2.0.12, 2.1.3, 3.0.0 My guess is that going from 2.1.1 to 2.1.3 is the less painful option. Are there any guidelines somewhere? One more thing I'd like to know: Sounds to me like the read afterwards is unnecessary. Could it be disabled by configuration? Best Regards, Arnold Miller Sent: Wednesday, April 03, 2019 at 5:16 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Slow task Hi, which version are you running? This sounds like as https://issues.apache.org/jira/browse/SYNCOPE-1409 Regards. On 03/04/19 11:58, Arnold Miller wrote: > Being concerned with the slowness of the process I decided to track the execution time it takes for every script for a single user and I found: > > 16:24:17.582 INFO Search script finished. Time elapsed: 0.194 seconds Method: run > 16:24:18.251 INFO Search script finished. Time elapsed: 0.166 seconds Method: run > 16:24:18.843 INFO Update script finished. Time elapsed: 0.244 seconds Method: run > 16:24:19.417 INFO Search script finished. Time elapsed: 0.161 seconds Method: run > 16:24:19.996 INFO Search script finished. Time elapsed: 0.172 seconds Method: run > > The first most obvious question is: Why does Syncope call the search script 4 times? Additionally, I see that between the 2nd and 3rd times it calls the update script. The sum of the time elapsed for that sample is 0.937, however the time at the beginning of the line shows that the whole process can take about 3 seconds per user. > > Doing math, if I have 18k users then it will take: > 18000*3 = 54000 seconds = 900 minutes = 15 hours > (This is what is actually taking!!) > > What is it that Syncope does behind scenes? > How can I optimize this process? > > > Best Regards, > > Arnold Miller > > >> Sent: Wednesday, March 27, 2019 at 6:33 PM >> From: "Francesco Chicchiriccò" >> To: user@syncope.apache.org >> Subject: Re: Slow task >> >> On 27/03/19 17:21, Arnold Miller wrote: >>> It is a standard Push task: Resource -> Push task -> run. >> A PushTask execution will simply generate as may PropagationTasks as >> needed and then execute them; for a REST resource, it means calling the >> create or update Groovy script. >> >> Hence: your guess is correct, if you have 18000 captured by the PushTask. >> >> Regards. >> >>> *Sent:* Wednesday, March 27, 2019 at 11:06 AM >>> *From:* "Francesco Chicchiriccò" >>> *To:* user@syncope.apache.org >>> *Subject:* Re: Slow task >>> Hi, >>> what kind of task (the one running for 6+ hours) do you have? It's a >>> standard PushTask, or a SchedTask you made on purpose? >>> Regards. >>> On 27/03/19 17:03, Arnold Miller wrote: >>> >>> No. >>> My guess is that Syncope makes 18000 calls using either the create >>> or the update Groovy script. >>> Best Regards, >>> >>> Arnold Miller >>> *Sent:* Wednesday, March 27, 2019 at 7:58 AM >>> *From:* "Filipe Silva" >>> *To:* user@syncope.apache.org >>> *Subject:* Re: Slow task >>> >>> Hi >>> >>> Are you making only one call to get all the info? >>> >>> I use groovy and made pagination in the rest call. >>> >>> Regards >>> >>> Filipe Silva >>> >>> On 26/03/19 21:40, Arnold Miller wrote: >>> >>> Hi everyone, >>> I have a task running for 6 hours trying to update the >>> information of a total of 18000 users. It has processed only >>> half of them. The task consists of calling a rest web service >>> with about 10 parameters. If I run the web service call only >>> it could take about 300 milliseconds. >>> What am I doing wrong? >>> Best Regards, >>> Arnold Miller -- 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/
Re: Slow task
Being concerned with the slowness of the process I decided to track the execution time it takes for every script for a single user and I found: 16:24:17.582 INFO Search script finished. Time elapsed: 0.194 seconds Method: run 16:24:18.251 INFO Search script finished. Time elapsed: 0.166 seconds Method: run 16:24:18.843 INFO Update script finished. Time elapsed: 0.244 seconds Method: run 16:24:19.417 INFO Search script finished. Time elapsed: 0.161 seconds Method: run 16:24:19.996 INFO Search script finished. Time elapsed: 0.172 seconds Method: run The first most obvious question is: Why does Syncope call the search script 4 times? Additionally, I see that between the 2nd and 3rd times it calls the update script. The sum of the time elapsed for that sample is 0.937, however the time at the beginning of the line shows that the whole process can take about 3 seconds per user. Doing math, if I have 18k users then it will take: 18000*3 = 54000 seconds = 900 minutes = 15 hours (This is what is actually taking!!) What is it that Syncope does behind scenes? How can I optimize this process? Best Regards, Arnold Miller > Sent: Wednesday, March 27, 2019 at 6:33 PM > From: "Francesco Chicchiriccò" > To: user@syncope.apache.org > Subject: Re: Slow task > > On 27/03/19 17:21, Arnold Miller wrote: > > It is a standard Push task: Resource -> Push task -> run. > > A PushTask execution will simply generate as may PropagationTasks as > needed and then execute them; for a REST resource, it means calling the > create or update Groovy script. > > Hence: your guess is correct, if you have 18000 captured by the PushTask. > > Regards. > > > *Sent:* Wednesday, March 27, 2019 at 11:06 AM > > *From:* "Francesco Chicchiriccò" > > *To:* user@syncope.apache.org > > *Subject:* Re: Slow task > > Hi, > > what kind of task (the one running for 6+ hours) do you have? It's a > > standard PushTask, or a SchedTask you made on purpose? > > Regards. > > On 27/03/19 17:03, Arnold Miller wrote: > > > > No. > > My guess is that Syncope makes 18000 calls using either the create > > or the update Groovy script. > > Best Regards, > > > > Arnold Miller > > *Sent:* Wednesday, March 27, 2019 at 7:58 AM > > *From:* "Filipe Silva" > > *To:* user@syncope.apache.org > > *Subject:* Re: Slow task > > > > Hi > > > > Are you making only one call to get all the info? > > > > I use groovy and made pagination in the rest call. > > > > Regards > > > > Filipe Silva > > > > On 26/03/19 21:40, Arnold Miller wrote: > > > > Hi everyone, > > I have a task running for 6 hours trying to update the > > information of a total of 18000 users. It has processed only > > half of them. The task consists of calling a rest web service > > with about 10 parameters. If I run the web service call only > > it could take about 300 milliseconds. > > What am I doing wrong? > > Best Regards, > > Arnold Miller > > > -- > 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/ > >
Re: Slow task
It is a standard Push task: Resource -> Push task -> run. Best Regards, Arnold Miller Sent: Wednesday, March 27, 2019 at 11:06 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Slow task Hi, what kind of task (the one running for 6+ hours) do you have? It's a standard PushTask, or a SchedTask you made on purpose? Regards. On 27/03/19 17:03, Arnold Miller wrote: No. My guess is that Syncope makes 18000 calls using either the create or the update Groovy script. Best Regards, Arnold Miller Sent: Wednesday, March 27, 2019 at 7:58 AM From: "Filipe Silva" To: user@syncope.apache.org Subject: Re: Slow task Hi Are you making only one call to get all the info? I use groovy and made pagination in the rest call. Regards Filipe Silva On 26/03/19 21:40, Arnold Miller wrote: Hi everyone, I have a task running for 6 hours trying to update the information of a total of 18000 users. It has processed only half of them. The task consists of calling a rest web service with about 10 parameters. If I run the web service call only it could take about 300 milliseconds. What am I doing wrong? Best Regards, Arnold Miller -- 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/
Re: Slow task
No. My guess is that Syncope makes 18000 calls using either the create or the update Groovy script. Best Regards, Arnold Miller Sent: Wednesday, March 27, 2019 at 7:58 AM From: "Filipe Silva" To: user@syncope.apache.org Subject: Re: Slow task Hi Are you making only one call to get all the info? I use groovy and made pagination in the rest call. Regards Filipe Silva On 26/03/19 21:40, Arnold Miller wrote: Hi everyone, I have a task running for 6 hours trying to update the information of a total of 18000 users. It has processed only half of them. The task consists of calling a rest web service with about 10 parameters. If I run the web service call only it could take about 300 milliseconds. What am I doing wrong? Best Regards, Arnold Miller
Slow task
Hi everyone, I have a task running for 6 hours trying to update the information of a total of 18000 users. It has processed only half of them. The task consists of calling a rest web service with about 10 parameters. If I run the web service call only it could take about 300 milliseconds. What am I doing wrong? Best Regards, Arnold Miller
Re: Dashboard does not show running task
I wonder if anyone has ever done the same upgrade and experienced the same issues.
Help is appreciated
Best Regards,
Arnold Miller
Sent: Friday, November 09, 2018 at 4:01 PM
From: "Arnold Miller"
To: user@syncope.apache.org
Cc: ilgro...@apache.org
Subject: Re: Dashboard does not show running task
I ran all updates and applied all changes as suggested but when I start Tomcat I get this exception:
07-Nov-2018 15:46:50.471 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'logicInitializer' defined in URL [jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%208.5/webapps/syncope/WEB-INF/lib/syncope-core-logic-2.1.1.jar!/org/apache/syncope/core/logic/init/LogicInitializer.class]: Invocation of init method failed; nested exception is org.apache.openjpa.persistence.PersistenceException: (conn=2443) Cannot add or update a child row: a foreign key constraint fails (`syncopedev`.`#sql-54c_98b`, CONSTRAINT `#sql-54c_98b_ibfk_5` FOREIGN KEY (`JOBDELEGATE_ID`) REFERENCES `implementation` (`id`)) {stmnt 1138410662 ALTER TABLE Task ADD FOREIGN KEY (JOBDELEGATE_ID) REFERENCES Implementation (id)} [code=1452, state=23000]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1699)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:573)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:495)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:317)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:315)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:759)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:869)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550)
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:409)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:291)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:103)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4745)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:988)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1860)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.openjpa.persistence.PersistenceException: (conn=2443) Cannot add or update a child row: a foreign key constraint fails (`syncopedev`.`#sql-54c_98b`, CONSTRAINT `#sql-54c_98b_ibfk_5` FOREIGN KEY (`JOBDELEGATE_ID`) REFERENCES `implementation` (`id`)) {stmnt 1138410662 ALTER TABLE Task ADD FOREIGN KEY (JOBDELEGATE_ID) REFERENCES Implementation (id)} [code=1452, state=23000]
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:608)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:473)
at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:175)
at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:179)
at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:136)
at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFact
Re: Dashboard does not show running task
hCreateAndSetSession(Application.java:1546) at org.apache.wicket.Session.get(Session.java:175) at org.apache.syncope.client.console.SyncopeConsoleSession.get(SyncopeConsoleSession.java:87) at org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener.onException(SyncopeConsoleRequestCycleListener.java:80) at org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) at org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) at org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) at org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) at org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) at org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) at org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) at org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) at org.apache.wicket.request.cycle.RequestCycle.handleException(RequestCycle.java:366) at org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:317) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:259) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) at org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.apache.wicket.authroles.authentication.AuthenticatedWebApplication.newSession(AuthenticatedWebApplication.java:117) ... 38 more Caused by: javax.xml.ws.WebServiceException: Remote exception with status code: NOT_FOUND at org.apache.syncope.client.lib.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:76) at org.apache.syncope.client.lib.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:42) at org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:315) at org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:880) at org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:786) at org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:238) at com.sun.proxy.$Proxy225.platform(Unknown Source) at org.apache.syncope.client.console.SyncopeConsoleSession.(SyncopeConsoleSession.java:99) ... 43 more Thank you for the help! Best Regards, Arnold Miller Sent: Tuesday, October 30, 2018 at 1:09
Re: Dashboard does not show running task
I followed the links but when I run the upgrade tool and got plenty of: 6504 WARN [main] openjpa.jdbc.Schema - Existing index "[index_name]" on table "[table_name]" is incompatible with the same index in the given schema definition. . I wonder if it should have happened or not. Best Regards, Arnold Miller Sent: Thursday, October 18, 2018 at 1:34 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Dashboard does not show running task On 16/10/18 18:42, Arnold Miller wrote: I'm planning to upgrade my Syncope from version 2.0.6 to version 2.1.1 (latest). Are there any guidelines to do this upgrade? What is the safest way to do it? https://cwiki.apache.org/confluence/display/SYNCOPE/Upgrade+from+2.0+Jazz http://syncope.apache.org/docs/2.1/reference-guide.html#upgrade-from-apache-syncope-2-0 then https://cwiki.apache.org/confluence/display/SYNCOPE/Upgrade+from+2.1.0+to+2.1.1 HTH Regards. Sent: Tuesday, September 18, 2018 at 1:00 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Dashboard does not show running task On 17/09/2018 23:55, Arnold Miller wrote: I'm using Syncope 2.0.6 The task I'm running is not small. I can see things related to the task happening (log files). I also use the reload button, but nothing happens. Syncope 2.0.9 introduced several improvements in Job management, I strongly suggest to upgrade - since you'd be at it, go to latest 2.0.10. Regards. Sent: Monday, September 17, 2018 at 1:31 AM From: "Francesco Chicchiriccò" To: "user@syncope.apache.org" Subject: Re: Dashboard does not show running task On 14/09/2018 22:37, Arnold Miller wrote: Hi everyone, It sometimes has happend to me that while executing a task and seeing things happening (in the log files) the dashboard does not show any task running. Has anyone else experienced that? Hi, first of all, which Syncope version? As a general consideration, consider that Admin Console's dashboard is refreshed every while, and small tasks might not even fit in the refresh window, in order to be displayed. Regards. -- 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/
Re: Dashboard does not show running task
I'm planning to upgrade my Syncope from version 2.0.6 to version 2.1.1 (latest). Are there any guidelines to do this upgrade? What is the safest way to do it? Thank you Best Regards, Arnold Miller Sent: Tuesday, September 18, 2018 at 1:00 AM From: "Francesco Chicchiriccò" To: user@syncope.apache.org Subject: Re: Dashboard does not show running task On 17/09/2018 23:55, Arnold Miller wrote: I'm using Syncope 2.0.6 The task I'm running is not small. I can see things related to the task happening (log files). I also use the reload button, but nothing happens. Syncope 2.0.9 introduced several improvements in Job management, I strongly suggest to upgrade - since you'd be at it, go to latest 2.0.10. Regards. Sent: Monday, September 17, 2018 at 1:31 AM From: "Francesco Chicchiriccò" To: "user@syncope.apache.org" Subject: Re: Dashboard does not show running task On 14/09/2018 22:37, Arnold Miller wrote: Hi everyone, It sometimes has happend to me that while executing a task and seeing things happening (in the log files) the dashboard does not show any task running. Has anyone else experienced that? Hi, first of all, which Syncope version? As a general consideration, consider that Admin Console's dashboard is refreshed every while, and small tasks might not even fit in the refresh window, in order to be displayed. Regards. -- 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/
Re: Dashboard does not show running task
I'm using Syncope 2.0.6 The task I'm running is not small. I can see things related to the task happening (log files). I also use the reload button, but nothing happens. Best Regards, Arnold Miller Sent: Monday, September 17, 2018 at 1:31 AM From: "Francesco Chicchiriccò" To: "user@syncope.apache.org" Subject: Re: Dashboard does not show running task On 14/09/2018 22:37, Arnold Miller wrote: Hi everyone, It sometimes has happend to me that while executing a task and seeing things happening (in the log files) the dashboard does not show any task running. Has anyone else experienced that? Hi, first of all, which Syncope version? As a general consideration, consider that Admin Console's dashboard is refreshed every while, and small tasks might not even fit in the refresh window, in order to be displayed. Regards. -- 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/
Dashboard does not show running task
Hi everyone, It sometimes has happend to me that while executing a task and seeing things happening (in the log files) the dashboard does not show any task running. Has anyone else experienced that? Best Regards, Arnold Miller
Re: Invalid any object name
Looks like I was able to solve it by adding 'name' attribute to the mapping (and the scripts) but the question is why is it?
I never had this attribute there nor defined in AnyTypeClasses.
Now I have another problem: it does not accept characters like '+' or '*'. What should I do in this case?
Best Regards,
Arnold Miller
Sent: Friday, August 17, 2018 at 4:19 PM
From: "Arnold Miller"
To: user@syncope.apache.org
Subject: Invalid any object name
Hello everyone!
Does anybody know what is this about?
Thanks for the help!!
core-persistence.log
15:51:00.601 WARN org.apache.syncope.core.persistence.jpa.validation.entity.EntityValidationListener - Bean validation errors found: [ConstraintViolationImpl{rootBean=JPAAnyObject[null], propertyPath='name', message='InvalidName;Invalid any object name', leafBean=JPAAnyObject[null], value=JPAAnyObject[null]}, ConstraintViolationImpl{rootBean=JPAAnyObject[null], propertyPath='name', message='may not be null', leafBean=JPAAnyObject[null], value=null}]
core.log
15:51:44.730 ERROR org.apache.syncope.core.provisioning.java.data.AbstractAnyDataBinder - No name specified for this anyObject
15:51:44.734 ERROR org.apache.syncope.core.provisioning.api.pushpull.SyncopeResultHandler - Could not create PRINT RC-535
org.apache.syncope.core.persistence.api.attrvalue.validation.InvalidEntityException: JPAAnyObject [Standard, InvalidName]
at org.apache.syncope.core.persistence.jpa.validation.entity.EntityValidationListener.validate(EntityValidationListener.java:73) ~[syncope-core-persistence-jpa-2.0.6.jar:2.0.6]
at sun.reflect.GeneratedMethodAccessor868.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_152]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_152]
at org.apache.openjpa.event.BeanLifecycleCallbacks.makeCallback(BeanLifecycleCallbacks.java:85) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.persistence.PersistenceListenerAdapter.makeCallback(PersistenceListenerAdapter.java:71) ~[openjpa-persistence-2.4.2.jar:2.4.2]
at org.apache.openjpa.persistence.PersistenceListenerAdapter.beforePersist(PersistenceListenerAdapter.java:85) ~[openjpa-persistence-2.4.2.jar:2.4.2]
at org.apache.openjpa.event.LifecycleEventManager.fireEvent(LifecycleEventManager.java:404) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.event.LifecycleEventManager.fireEvent(LifecycleEventManager.java:308) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.kernel.BrokerImpl.fireLifecycleEvent(BrokerImpl.java:814) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:140) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3508) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1213) ~[openjpa-kernel-2.4.2.jar:2.4.2]
at org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:879) ~[openjpa-persistence-2.4.2.jar:2.4.2]
at org.apache.syncope.core.persistence.jpa.dao.AbstractAnyDAO.save(AbstractAnyDAO.java:535) ~[syncope-core-persistence-jpa-2.0.6.jar:2.0.6]
at org.apache.syncope.core.persistence.jpa.dao.JPAAnyObjectDAO.doSave(JPAAnyObjectDAO.java:207) ~[syncope-core-persistence-jpa-2.0.6.jar:2.0.6]
at org.apache.syncope.core.persistence.jpa.dao.JPAAnyObjectDAO.save(JPAAnyObjectDAO.java:218) ~[syncope-core-persistence-jpa-2.0.6.jar:2.0.6]
at org.apache.syncope.core.persistence.jpa.dao.JPAAnyObjectDAO.save(JPAAnyObjectDAO.java:68) ~[syncope-core-persistence-jpa-2.0.6.jar:2.0.6]
at sun.reflect.GeneratedMethodAccessor1206.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_152]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_152]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) ~[spring-aop-4.3.11.RELEASE.jar:4.3.11.RELEASE]
at com.sun.proxy.$Proxy90.save(Unknown Source) ~[?:?]
at org.apache.syncope.core.workflow.java.DefaultAnyObjectWorkflowAdapter.doCreate(DefaultAnyObjectWorkflowAdapter.java:52) ~[syncope-core-workflow-java-2.0.6.jar:2.0.6]
at org.apache.syncope.core.workflow.java.AbstractAnyObjectWorkflowAdapter.create(AbstractAnyObjectWorkflowAdapter.java:56) ~[syncope-core-workflow-java-2.0.6.jar:2.0.6]
Invalid any object name
.3.11.RELEASE.jar:4.3.11.RELEASE] at org.apache.syncope.core.persistence.jpa.spring.DomainTransactionInterceptor.invoke(DomainTransactionInterceptor.java:64) ~[syncope-core-persistence-jpa-2.0.6.jar:2.0.6] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.11.RELEASE.jar:4.3.11.RELEASE] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.11.RELEASE.jar:4.3.11.RELEASE] at com.sun.proxy.$Proxy300.execute(Unknown Source) ~[?:?] at org.apache.syncope.core.provisioning.java.job.TaskJob$1.exec(TaskJob.java:80) ~[syncope-core-provisioning-java-2.0.6.jar:2.0.6] at org.apache.syncope.core.provisioning.java.job.TaskJob$1.exec(TaskJob.java:70) ~[syncope-core-provisioning-java-2.0.6.jar:2.0.6] at org.apache.syncope.core.spring.security.AuthContextUtils.execWithAuthContext(AuthContextUtils.java:136) ~[syncope-core-spring-2.0.6.jar:2.0.6] at org.apache.syncope.core.provisioning.java.job.TaskJob.execute(TaskJob.java:69) ~[syncope-core-provisioning-java-2.0.6.jar:2.0.6] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.3.0.jar:?] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ~[quartz-2.3.0.jar:?] Best Regards, Arnold Miller
Re: Getting IllegalStateException when running task
Dear Alireza,
What I mean is that I'm not returning all the fields and that's why it fails.
To make it clearer I give you an example:
Let's say that in my source (or master) identity store I have both "idnumber" and "username", and both are unique. The problem is that when I select both of them to be the remote key Syncope says "there must be exactly one remote key". This is a problem because some of the destination identity stores work with the "idnumber" only whereas others work with the "username" only; so if I mark "idnumber" to be the remote key then the systems that work only with "username" will not be able to return it because they just don't have it; in spite they have the rest of the mandatory fields.
Best Regards,
Arnold Miller
Sent: Tuesday, May 15, 2018 at 12:08 AM
From: "alireza ranjbaran"
To: user@syncope.apache.org
Subject: Re: Getting IllegalStateException when running task
Dear Arnold,
Would you please explain more details?
For the error you posted at first, you should be sure that you return all "mandatory" fields include __UID__, __NAME__, the key you have defined in your mapping, ect. for example if you mapped the Syncope 'username' to DB 'uname', you can fill the result as below (here email, organization and department are optional):
sql.eachRow("SELECT * FROM Users" + where, {result.add([__UID__:it.uname, __NAME__:it.uname, email:it.email, uname:it.uname, organization:it.organization, department:it.department])} )
You are not forced to use primary key. Alternate key or even fixed values can be pass as result.
On Mon, May 14, 2018 at 9:06 PM, Arnold Miller <arnold.mille...@gmx.com> wrote:
Looks like I will need to create another resource and duplicate information (except the previously used remote key).
Will be glad to hear if anyone has another solution.
Best Regards,
Arnold Miller
Sent: Thursday, May 10, 2018 at 3:04 PM
From: "Arnold Miller" <arnold.mille...@gmx.com>
To: user@syncope.apache.org
Subject: Re: Getting IllegalStateException when running task
I certainly have an identity store which uses an alternate key instead of the one I marked as a remote key.
Specifically, the master identity store has both the remote and the alternate keys, but the identity store where I am trying to push the updates has only the alternate key.
If in Syncope "there must be exactly one remote key" how else can I handle this problem?
Best Regards,
Arnold Miller
Sent: Thursday, May 10, 2018 at 1:29 AM
From: "Francesco Chicchiriccò" <ilgro...@apache.org>
To: user@syncope.apache.org
Subject: Re: Getting IllegalStateException when running task
On 09/05/2018 22:49, Arnold Miller wrote:
Hi,
I'm getting this
"java.lang.IllegalStateException: Object {Uid=Attribute: {Name=__UID__, .
was returned by the connector but failed to pass the framework filter. This seems like wrong implementation of the filter in the connector."
when the Search script is executed after running a Push task.
From a previous message I found that the search script must return all the attributes it is asked for:
https://www.mail-archive.com/user@syncope.apache.org/msg02339.html
Which basically means that you fill in all the values in ATTRS_TO_GET [.]
I am doing that and also I am returning the result as suggested in
https://github.com/apache/syncope/blob/2_0_X/fit/core-reference/src/test/resources/rest/SearchScript.groovy#L76-L93
like this:
result.add(buildConnectorObject(node));
My questions:
1. Why am I getting that "IllegalStateException" described above?
The error above means that your search script is returning something that does not match with the original request: suppose that Syncope asks for a filter like as "name == 'Francesco'" and the result returned from the search script does not have the "name" attribute, or value is "Arnold".
2. If the script is finding the item it is requested to, why does it trigger the creation script instead of the update script?
The point is exactly this: because of the exception above, Syncope does not find any item, hence create is invoked.
HTH
Regards.
--
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/
--
Best Regards,
Alireza Ranjbaran
ITS Security Operations Engineer at MTN Irancell
Re: Getting IllegalStateException when running task
Looks like I will need to create another resource and duplicate information (except the previously used remote key).
Will be glad to hear if anyone has another solution.
Best Regards,
Arnold Miller
Sent: Thursday, May 10, 2018 at 3:04 PM
From: "Arnold Miller"
To: user@syncope.apache.org
Subject: Re: Getting IllegalStateException when running task
I certainly have an identity store which uses an alternate key instead of the one I marked as a remote key.
Specifically, the master identity store has both the remote and the alternate keys, but the identity store where I am trying to push the updates has only the alternate key.
If in Syncope "there must be exactly one remote key" how else can I handle this problem?
Best Regards,
Arnold Miller
Sent: Thursday, May 10, 2018 at 1:29 AM
From: "Francesco Chicchiriccò"
To: user@syncope.apache.org
Subject: Re: Getting IllegalStateException when running task
On 09/05/2018 22:49, Arnold Miller wrote:
Hi,
I'm getting this
"java.lang.IllegalStateException: Object {Uid=Attribute: {Name=__UID__, .
was returned by the connector but failed to pass the framework filter. This seems like wrong implementation of the filter in the connector."
when the Search script is executed after running a Push task.
From a previous message I found that the search script must return all the attributes it is asked for:
https://www.mail-archive.com/user@syncope.apache.org/msg02339.html
Which basically means that you fill in all the values in ATTRS_TO_GET [.]
I am doing that and also I am returning the result as suggested in
https://github.com/apache/syncope/blob/2_0_X/fit/core-reference/src/test/resources/rest/SearchScript.groovy#L76-L93
like this:
result.add(buildConnectorObject(node));
My questions:
1. Why am I getting that "IllegalStateException" described above?
The error above means that your search script is returning something that does not match with the original request: suppose that Syncope asks for a filter like as "name == 'Francesco'" and the result returned from the search script does not have the "name" attribute, or value is "Arnold".
2. If the script is finding the item it is requested to, why does it trigger the creation script instead of the update script?
The point is exactly this: because of the exception above, Syncope does not find any item, hence create is invoked.
HTH
Regards.
--
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/
Re: Getting IllegalStateException when running task
I certainly have an identity store which uses an alternate key instead of the one I marked as a remote key.
Specifically, the master identity store has both the remote and the alternate keys, but the identity store where I am trying to push the updates has only the alternate key.
If in Syncope "there must be exactly one remote key" how else can I handle this problem?
Best Regards,
Arnold Miller
Sent: Thursday, May 10, 2018 at 1:29 AM
From: "Francesco Chicchiriccò"
To: user@syncope.apache.org
Subject: Re: Getting IllegalStateException when running task
On 09/05/2018 22:49, Arnold Miller wrote:
Hi,
I'm getting this
"java.lang.IllegalStateException: Object {Uid=Attribute: {Name=__UID__, .
was returned by the connector but failed to pass the framework filter. This seems like wrong implementation of the filter in the connector."
when the Search script is executed after running a Push task.
From a previous message I found that the search script must return all the attributes it is asked for:
https://www.mail-archive.com/user@syncope.apache.org/msg02339.html
Which basically means that you fill in all the values in ATTRS_TO_GET [.]
I am doing that and also I am returning the result as suggested in
https://github.com/apache/syncope/blob/2_0_X/fit/core-reference/src/test/resources/rest/SearchScript.groovy#L76-L93
like this:
result.add(buildConnectorObject(node));
My questions:
1. Why am I getting that "IllegalStateException" described above?
The error above means that your search script is returning something that does not match with the original request: suppose that Syncope asks for a filter like as "name == 'Francesco'" and the result returned from the search script does not have the "name" attribute, or value is "Arnold".
2. If the script is finding the item it is requested to, why does it trigger the creation script instead of the update script?
The point is exactly this: because of the exception above, Syncope does not find any item, hence create is invoked.
HTH
Regards.
--
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/
Getting IllegalStateException when running task
Hi,
I'm getting this
"java.lang.IllegalStateException: Object {Uid=Attribute: {Name=__UID__, .
was returned by the connector but failed to pass the framework filter. This seems like wrong implementation of the filter in the connector."
when the Search script is executed after running a Push task.
From a previous message I found that the search script must return all the attributes it is asked for:
https://www.mail-archive.com/user@syncope.apache.org/msg02339.html
Which basically means that you fill in all the values in ATTRS_TO_GET [.]
I am doing that and also I am returning the result as suggested in
https://github.com/apache/syncope/blob/2_0_X/fit/core-reference/src/test/resources/rest/SearchScript.groovy#L76-L93
like this:
result.add(buildConnectorObject(node));
My questions:
1. Why am I getting that "IllegalStateException" described above?
2. If the script is finding the item it is requested to, why does it trigger the creation script instead of the update script?
Best Regards,
Arnold Miller
Re: Null password
Dear Dima,
> Which operation are you doing?
for both CREATE and UPDATE operations (scripts) I get null password.
> are you creating a push task?
Yes. I created a Push task for the correspondent resource.
> did you add the password to the mapping?
Yes. The mapping is 'password' to '__PASSWORD__'
Sent: Wednesday, May 02, 2018 at 10:49 AM
From: "Dima Ayash"
To: user@syncope.apache.org
Subject: Re: Null password
On 05/02/2018 05:39 PM, Arnold Miller wrote:
Dear Dima,
that is exactly what I'm doing but all I get is a null value. I checked the Syncope db and I see a value there, which is encrypted.
Dear Arnold,
Which operation are you doing? are you creating a push task? did you add the password to the mapping?
Best regards,
Dima Ayash
Sent: Wednesday, May 02, 2018 at 9:14 AM
From: "Dima Ayash"
To: user@syncope.apache.org
Subject: Re: Null password
Dear Arnold,
In the case of the password you need just to use the parameter (password) like the parameter (id) for example, which is mentioned in the comment.
Best regards,
Dima Ayash.
On 05/01/2018 11:44 PM, Arnold Miller wrote:
Hi,
still having no idea why this happens.
The comment in the original script says "password: password string, clear text", so 'password' should have this value but it comes null to my script.
>>
Hi, I'm trying to push a user to an identity store via scripted sql but I
always get a null password for every user, even if it is not null in Syncope.
Anyone knows?
I have these variables in Create Script, all of them null:
password
attributes.get("__PASSWORD__")
attributes.get("password")
Arnold
Re: Null password
Dear Dima,
that is exactly what I'm doing but all I get is a null value. I checked the Syncope db and I see a value there, which is encrypted.
Sent: Wednesday, May 02, 2018 at 9:14 AM
From: "Dima Ayash"
To: user@syncope.apache.org
Subject: Re: Null password
Dear Arnold,
In the case of the password you need just to use the parameter (password) like the parameter (id) for example, which is mentioned in the comment.
Best regards,
Dima Ayash.
On 05/01/2018 11:44 PM, Arnold Miller wrote:
Hi,
still having no idea why this happens.
The comment in the original script says "password: password string, clear text", so 'password' should have this value but it comes null to my script.
>>
Hi, I'm trying to push a user to an identity store via scripted sql but I
always get a null password for every user, even if it is not null in Syncope.
Anyone knows?
I have these variables in Create Script, all of them null:
password
attributes.get("__PASSWORD__")
attributes.get("password")
Arnold
Re: Null password
Hi,
still having no idea why this happens.
The comment in the original script says "password: password string, clear text", so 'password' should have this value but it comes null to my script.
>>
Hi, I'm trying to push a user to an identity store via scripted sql but I
always get a null password for every user, even if it is not null in Syncope.
Anyone knows?
I have these variables in Create Script, all of them null:
password
attributes.get("__PASSWORD__")
attributes.get("password")
Arnold
