0
Fixed

Identity Broker - Placeholder connector error message formatting

Richard Courtenay 6 years ago • updated by anonymous 3 years ago 2

I received the following error message. Please note that

{0}, {1)..{n} in the error message. It looks like a String.Format issue. (note: JIRA seems to have an issue with this code block)




20130304,21:17:11,Modify anchor for entity {0}

to

{1}

from connector

{2}

failed with reason

{3}

. Duration:

{4}

,Connector,Warning,"Modify anchor for entity af369b4d-adb3-4c76-9b93-bf467f56f920 to ef7d936d-e793-462d-a215-616aeb8e4fa1 from connector User Placeholder failed with reason Connector User Placeholder does not support anchor modification.. Duration: 00:00:00
Error details:
System.NotSupportedException: Connector User Placeholder does not support anchor modification.
at Unify.Framework.ConnectorToModifyAnchorConnectorBridge.get_MultiKeyedModifyAnchorConnector()
at Unify.Framework.ConnectorToModifyAnchorConnectorBridge.ModifyAnchor(MultiKeyValue oldKey, MultiKeyValue newKey)
at Unify.Framework.EventNotifierModifyAnchorConnectorDecorator.ModifyAnchor(MultiKeyValue oldKey, MultiKeyValue newKey)
at Unify.Framework.Adapter.<>c_DisplayClass37.<CheckAnchorChangeOnSave>b_32(KeyValuePair`2 keyValue)
at Unify.Framework.Visitor.<>c_DisplayClass1`1.<Visit>b_0(T item, Int32 index)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`1 visitor)
at Unify.Framework.Adapter.CheckAnchorChangeOnSave(IEntitySchema connectorSchema, IEnumerable`1 entitiesToSave, IEntityPartitionUpdatableContext connectorContext, IEnumerable`1 entityIds)
at Unify.Framework.Adapter.SaveEntities(IEnumerable`1 entities, Boolean reflect)
at Unify.Framework.Adapter.SaveEntity(IAdapterEntity entity, Boolean reflect)
at Unify.Framework.AdapterNotifierDecorator.SaveEntity(IAdapterEntity entityToSave)
at Unify.Framework.LDIFAdapter.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
at Unify.Framework.LDIFAdapterServiceHostDecorator.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
at SyncInvokeExportAdapterEntity(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)",Normal


I'll investigate the actual error separatly, but as far as this issue is concerned, I don't want the anchor modification to be reviewed. Just wanted to bring the formating of the error itself to light.

Affected Versions:
Fixed by Version:

Tony, could you please check this one out?

From the message it looks like it's using the message in place of the title in the notification message.

If it's not an issue in v4.0, please resolve as won't fix.

Thanks.

The incorrect resource value was passed to the log source, and so the values weren't formatted.