sivaramtm Super Contributor.
Super Contributor.
274 views

Loopback driver job takes long time to process the events

Hi,

Loopback driver job is taking more than 8 hrs to process 5000 events. We could see that below error is causing the delay. Appreciate your help.

<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.6.3.0">DirXML</product>
<contact>NetIQ Corporation</contact>
</source>
<input>
<trigger class-name="User" event-id="trigger-job:Enable users#20190605155222#0#0" qualified-src-dn="O=BBC\OU=users\OU=contractors\CN=Z8YRQ" source="Enable users" src-dn="\BBCIDV\BBC\users\contractors\Z8YRQ" src-entry-id="343980">
<operation-data source="Enable users"/>
</trigger>
</input>
</nds>
[06/05/19 17:52:22.713]:loopback ST:Stripping operation data from input document
[06/05/19 17:52:22.714]:loopback PT:Receiving DOM document from application.
[06/05/19 17:52:22.714]:loopback PT:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.6.3.0">DirXML</product>
<contact>NetIQ Corporation</contact>
</source>
<input>
<trigger class-name="User" event-id="trigger-job:Enable users#20190605155222#0#0" qualified-src-dn="O=BBC\OU=users\OU=contractors\CN=Z8YRQ" source="Enable users" src-dn="\BBCIDV\BBC\users\contractors\Z8YRQ" src-entry-id="343980"/>
</input>
</nds>
[06/05/19 17:52:22.715]:loopback PT:No input transformation policies.
[06/05/19 17:52:22.716]:loopback PT:Applying schema mapping policies to input.
[06/05/19 17:52:22.716]:loopback PT:Applying policy: %+C%14CMappingRule-1%-C.
[06/05/19 17:52:22.716]:loopback PT: Mapping class-name 'User' to 'User'.
[06/05/19 17:52:22.716]:loopback PT:Resolving association references.
[06/05/19 17:52:22.717]:loopback PT:No event transformation policies.
[06/05/19 17:52:22.717]:loopback PT:Applying publisher filter.
[06/05/19 17:52:22.717]:loopback PT:Publisher processing trigger for \BBCIDV\BBC\users\contractors\Z8YRQ.
[06/05/19 17:52:22.717]:loopback PT:No command transformation policies.
[06/05/19 17:52:22.718]:loopback PT:Filtering out notification-only attributes.
[06/05/19 17:52:22.718]:loopback PT:Pumping XDS to eDirectory.
[06/05/19 17:52:22.725]:loopback PT:
DirXML Log Event -------------------
Driver: \BBCIDV\system\driverset1\Loopback Driver
Channel: Publisher
Object: \BBCIDV\BBC\users\contractors\Z8YRQ
Status: Error
Message: Code(-9038) Element <trigger> found under <input> is not allowed.
[06/05/19 17:52:22.730]:loopback PT:Fixing up association references.
[06/05/19 17:52:22.730]:loopback PT:Applying schema mapping policies to output.
[06/05/19 17:52:22.730]:loopback PT:Applying policy: %+C%14CMappingRule-1%-C.
[06/05/19 17:52:22.731]:loopback PT:No output transformation policies.
[06/05/19 17:52:22.731]:loopback PT:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.6.3.0">DirXML</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="trigger-job:Enable users#20190605155222#0#0" level="error">Code(-9038) Element <trigger> found under <input> is not allowed.<application>DirXML</application>
<module>Loopback Driver</module>
<object-dn>\BBCIDV\BBC\users\contractors\Z8YRQ</object-dn>
<component>Publisher</component>
</status>
</output>
</nds>
[06/05/19 17:52:22.733]:loopback ST:Restoring operation data to output document
[06/05/19 17:52:22.733]:loopback ST:SubscriptionShim.execute() returned:
[06/05/19 17:52:22.733]:loopback ST:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.6.3.0">DirXML</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="trigger-job:Enable users#20190605155222#0#0" level="error">Code(-9038) Element <trigger> found under <input> is not allowed.<application>DirXML</application>
<module>Loopback Driver</module>
<object-dn>\BBCIDV\BBC\users\contractors\Z8YRQ</object-dn>
<component>Publisher</component>
<operation-data source="Enable users"/>
</status>
</output>
</nds>
[06/05/19 17:52:22.735]:loopback ST:No input transformation policies.
[06/05/19 17:52:22.735]:loopback ST:Applying schema mapping policies to input.
[06/05/19 17:52:22.735]:loopback ST:Applying policy: %+C%14CMappingRule-1%-C.
[06/05/19 17:52:22.736]:loopback ST:Resolving association references.
[06/05/19 17:52:22.736]:loopback ST:Processing returned document.
[06/05/19 17:52:22.736]:loopback ST:Processing operation <status> for .
[06/05/19 17:52:22.736]:loopback ST:
DirXML Log Event -------------------
Driver: \BBCIDV\system\driverset1\Loopback Driver
Channel: Subscriber
Object: \BBCIDV\BBC\users\contractors\Z8YRQ
Status: Error
Message: Code(-9038) Element <trigger> found under <input> is not allowed.<application>DirXML</application>
<module>Loopback Driver</module>
<object-dn>\BBCIDV\BBC\users\contractors\Z8YRQ</object-dn>
<component>Publisher</component>
[06/05/19 17:52:22.745]:loopback ST:End transaction.

Thanks
Siva ram T
Labels (1)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Loopback driver job takes long time to process the events

On 6/5/2019 12:14 PM, sivaramtm wrote:
>
> Hi,
>
> Loopback driver job is taking more than 8 hrs to process 5000 events. We
> could see that below error is causing the delay. Appreciate your help.
>
> <nds dtdversion="4.0" ndsversion="8.x">
> <source>
> <product edition="Advanced" version="4.6.3.0">DirXML</product>
> <contact>NetIQ Corporation</contact>
> </source>
> <input>
> <trigger class-name="User" event-id="trigger-job:Enable
> users#20190605155222#0#0"
> qualified-src-dn="O=BBC\OU=users\OU=contractors\CN=Z8YRQ" source="Enable
> users" src-dn="\BBCIDV\BBC\users\contractors\Z8YRQ"
> src-entry-id="343980">
> <operation-data source="Enable users"/>
> </trigger>
> </input>
> </nds>
> [06/05/19 17:52:22.713]:loopback ST:Stripping operation data from input
> document
> [06/05/19 17:52:22.714]:loopback PT:Receiving DOM document from
> application.
> [06/05/19 17:52:22.714]:loopback PT:
> <nds dtdversion="4.0" ndsversion="8.x">
> <source>
> <product edition="Advanced" version="4.6.3.0">DirXML</product>
> <contact>NetIQ Corporation</contact>
> </source>
> <input>
> <trigger class-name="User" event-id="trigger-job:Enable
> users#20190605155222#0#0"
> qualified-src-dn="O=BBC\OU=users\OU=contractors\CN=Z8YRQ" source="Enable
> users" src-dn="\BBCIDV\BBC\users\contractors\Z8YRQ"
> src-entry-id="343980"/>
> </input>
> </nds>
> [06/05/19 17:52:22.715]:loopback PT:No input transformation policies.
> [06/05/19 17:52:22.716]:loopback PT:Applying schema mapping policies to
> input.
> [06/05/19 17:52:22.716]:loopback PT:Applying policy:
> %+C%14CMappingRule-1%-C.
> [06/05/19 17:52:22.716]:loopback PT: Mapping class-name 'User' to
> 'User'.
> [06/05/19 17:52:22.716]:loopback PT:Resolving association references.
> [06/05/19 17:52:22.717]:loopback PT:No event transformation policies.
> [06/05/19 17:52:22.717]:loopback PT:Applying publisher filter.
> [06/05/19 17:52:22.717]:loopback PT:Publisher processing trigger for
> \BBCIDV\BBC\users\contractors\Z8YRQ.
> [06/05/19 17:52:22.717]:loopback PT:No command transformation policies.
> [06/05/19 17:52:22.718]:loopback PT:Filtering out notification-only
> attributes.
> [06/05/19 17:52:22.718]:loopback PT:Pumping XDS to eDirectory.
> [06/05/19 17:52:22.725]:loopback PT:
> DirXML Log Event -------------------
> Driver: \BBCIDV\system\driverset1\Loopback Driver
> Channel: Publisher
> Object: \BBCIDV\BBC\users\contractors\Z8YRQ
> Status: Error
> Message: Code(-9038) Element <trigger> found under <input> is not
> allowed.
> [06/05/19 17:52:22.730]:loopback PT:Fixing up association references.
> [06/05/19 17:52:22.730]:loopback PT:Applying schema mapping policies to
> output.
> [06/05/19 17:52:22.730]:loopback PT:Applying policy:
> %+C%14CMappingRule-1%-C.
> [06/05/19 17:52:22.731]:loopback PT:No output transformation policies.
> [06/05/19 17:52:22.731]:loopback PT:
> <nds dtdversion="4.0" ndsversion="8.x">
> <source>
> <product edition="Advanced" version="4.6.3.0">DirXML</product>
> <contact>NetIQ Corporation</contact>
> </source>
> <output>
> <status event-id="trigger-job:Enable users#20190605155222#0#0"
> level="error">Code(-9038) Element <trigger> found under <input> is
> not allowed.<application>DirXML</application>
> <module>Loopback Driver</module>
> <object-dn>\BBCIDV\BBC\users\contractors\Z8YRQ</object-dn>
> <component>Publisher</component>
> </status>
> </output>
> </nds>
> [06/05/19 17:52:22.733]:loopback ST:Restoring operation data to output
> document
> [06/05/19 17:52:22.733]:loopback ST:SubscriptionShim.execute()
> returned:
> [06/05/19 17:52:22.733]:loopback ST:
> <nds dtdversion="4.0" ndsversion="8.x">
> <source>
> <product edition="Advanced" version="4.6.3.0">DirXML</product>
> <contact>NetIQ Corporation</contact>
> </source>
> <output>
> <status event-id="trigger-job:Enable users#20190605155222#0#0"
> level="error">Code(-9038) Element <trigger> found under <input> is
> not allowed.<application>DirXML</application>
> <module>Loopback Driver</module>
> <object-dn>\BBCIDV\BBC\users\contractors\Z8YRQ</object-dn>
> <component>Publisher</component>
> <operation-data source="Enable users"/>
> </status>
> </output>
> </nds>
> [06/05/19 17:52:22.735]:loopback ST:No input transformation policies.
> [06/05/19 17:52:22.735]:loopback ST:Applying schema mapping policies to
> input.
> [06/05/19 17:52:22.735]:loopback ST:Applying policy:
> %+C%14CMappingRule-1%-C.
> [06/05/19 17:52:22.736]:loopback ST:Resolving association references.
> [06/05/19 17:52:22.736]:loopback ST:Processing returned document.
> [06/05/19 17:52:22.736]:loopback ST:Processing operation <status> for .
> [06/05/19 17:52:22.736]:loopback ST:
> DirXML Log Event -------------------
> Driver: \BBCIDV\system\driverset1\Loopback Driver
> Channel: Subscriber
> Object: \BBCIDV\BBC\users\contractors\Z8YRQ
> Status: Error
> Message: Code(-9038) Element <trigger> found under <input>
> is not allowed.<application>DirXML</application>
> <module>Loopback Driver</module>
> <object-dn>\BBCIDV\BBC\users\contractors\Z8YRQ</object-dn>
> <component>Publisher</component>
> [06/05/19 17:52:22.745]:loopback ST:End transaction.



Your trigger events are making it through the shim and looping back,
perhaps? After you are done with your trigger event, veto the event in
policy?
0 Likes
sivaramtm Super Contributor.
Super Contributor.

Re: Loopback driver job takes long time to process the event

I have added the Veto condition at end the rule in first policy. This makes rest of policies to stop executing.

Thanks
Siva ram T
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Loopback driver job takes long time to process the events

On 6/6/2019 6:54 AM, sivaramtm wrote:
>
> I have added the Veto condition at end the rule in first policy. This
> makes rest of policies to stop executing.


Are you processing the trigger in the Publisher channel? Did you set
the veto for If operation = trigger only?


0 Likes
sivaramtm Super Contributor.
Super Contributor.

Re: Loopback driver job takes long time to process the event

No. Processing the trigger in subscriber channel. Yes Condition added if Operation = trigger only.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Loopback driver job takes long time to process the events

On 6/6/2019 7:54 AM, sivaramtm wrote:
>
> No. Processing the trigger in subscriber channel. Yes Condition added if
> Operation = trigger only.


I think we are wasting time talking abouot this in theory. There is more
than you think is relevant to mention, which would be revealed in a
level 3 trace.

So please post the trace on pastebin.org or the like (susepaste.org
whatever).


0 Likes
sivaramtm Super Contributor.
Super Contributor.

Re: Loopback driver job takes long time to process the event

Please find the trace at https://pastebin.com/Lz9zVHr3
0 Likes
sivaramtm Super Contributor.
Super Contributor.

Re: Loopback driver job takes long time to process the event

Hi,

Issue resolved after adding the Veto condition in separate rule in the end of last policy. Now the driver process the events quickly. Thanks for the help.

Thanks
Siva ram T
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Loopback driver job takes long time to process the events

On 6/7/2019 11:14 AM, sivaramtm wrote:
>
> Hi,
>
> Issue resolved after adding the Veto condition in separate rule in the
> end of last policy. Now the driver process the events quickly. Thanks
> for the help.


Sorry, I was VPN'ed to a client all day yesterday that was blocking
susepaste.com so I could not look at your logs. Glad you figured it out.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.