Task #1318
openFE error when retrying provisioning operation after unbreaking provisioning brake
0%
Description
Steps to reproduce this issue:
- Set provisioning brake on UPDATE operation to limit 1 in 1 minute
- Perform two UPDATE operations in one minute
- Go and unbrake the brake, which should be activated by previous operations
- Increase limit in provisioning brake so that another operation can be performed
- Go on provisioning page for affected user
- Select blocked operation and retry provisioning
- You should receive internal server error
In our case, provisioning faild. The problem is, that FE is not updated and user still sees blocked operation instead of failed one.
Files
Updated by Peter Štrunc about 6 years ago
- File retry_error.gif retry_error.gif added
Updated by Peter Štrunc about 6 years ago
I replicated the same error after switching system from read-only to read write.
Affected version 9.2.0
Updated by Radek Tomiška about 6 years ago
- Assignee changed from Vít Švanda to Peter Štrunc
Add please log with exception.
Updated by Radek Tomiška about 6 years ago
I'm not able to reproduce issue on version 9.2.0.
Thx for the gif, but in this gif is wrong operation state - if brake is activated, the 'Blocked' state is used. Check your application log and provide more information to reproduce issue (maybe provisioning operation detail in attached gif will contain more information)
Updated by Peter Štrunc about 6 years ago
org.identityconnectors.framework.common.exceptions.ConnectorException: javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 21 - 00000057: LdapErr: DSID-0C090E21, comment: Error in attribute conversion operation, data 0, v2580^@]; remaining name 'cn=_příjmení Testovací,OU=_Uzivatele,OU=_CMHB,DC=ad,DC=cmhb,DC=cz' at net.tirasa.connid.bundles.ldap.schema.LdapSchemaMapping.create(LdapSchemaMapping.java:344) at net.tirasa.connid.bundles.ad.crud.ADCreate.executeImpl(ADCreate.java:214) at net.tirasa.connid.bundles.ad.crud.ADCreate.create(ADCreate.java:81) at net.tirasa.connid.bundles.ad.ADConnector.create(ADConnector.java:194) at org.identityconnectors.framework.impl.api.local.operations.CreateImpl.create(CreateImpl.java:107) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.identityconnectors.framework.impl.api.local.operations.ConnectorAPIOperationRunnerProxy.invoke(ConnectorAPIOperationRunnerProxy.java:98) at com.sun.proxy.$Proxy351.create(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.identityconnectors.framework.impl.api.local.operations.ThreadClassLoaderManagerProxy.invoke(ThreadClassLoaderManagerProxy.java:96) at com.sun.proxy.$Proxy351.create(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.identityconnectors.framework.impl.api.DelegatingTimeoutProxy.invoke(DelegatingTimeoutProxy.java:99) at com.sun.proxy.$Proxy351.create(Unknown Source) at org.identityconnectors.framework.impl.api.AbstractConnectorFacade.create(AbstractConnectorFacade.java:157) at eu.bcvsolutions.idm.ic.connid.service.impl.ConnIdIcConnectorService.createObject(ConnIdIcConnectorService.java:97) at eu.bcvsolutions.idm.ic.service.impl.DefaultIcConnectorFacade.createObject(DefaultIcConnectorFacade.java:54) at eu.bcvsolutions.idm.acc.event.processor.provisioning.ProvisioningCreateProcessor.processInternal(ProvisioningCreateProcessor.java:95) at eu.bcvsolutions.idm.acc.event.processor.provisioning.AbstractProvisioningProcessor.process(AbstractProvisioningProcessor.java:104) at eu.bcvsolutions.idm.core.api.event.AbstractEntityEventProcessor.onApplicationEvent(AbstractEntityEventProcessor.java:237) at eu.bcvsolutions.idm.core.api.event.AbstractEntityEventProcessor$$FastClassBySpringCGLIB$$df69624d.invoke(<generated>) at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655) at eu.bcvsolutions.idm.acc.event.processor.provisioning.ProvisioningCreateProcessor$$EnhancerBySpringCGLIB$$736cdaf.onApplicationEvent(<generated>) at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:381) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:348)
But this is just generic LDAP error, problem is not the error, but the way IdM is handling it. Provisioning record stays as not executed/blocked, instead of turning into failed one.
Updated by Peter Štrunc about 6 years ago
- Assignee changed from Peter Štrunc to Radek Tomiška
Updated by Radek Tomiška about 6 years ago
- Assignee changed from Radek Tomiška to Peter Štrunc
- Target version deleted (
Morganite (9.2.1))
I'm still not able to reproduce issue on version 9.2.0, maybe it was connected with your environment (server and db state). The issue still occurs on your environment?