Vice Admiral
Vice Admiral
1822 views

IDM Error (-9083) Error submitting event to subscriber

Jump to solution

Hi,

The NULL Driver was working all the while and sending email notification and suddenly I see the Java error in the trace. 

12:46:31 8FD10700 Drvrs: User Updates ST:Applying policy: Notify User via Email upon Creation Policy.

12:46:31 8FD10700 Drvrs: User Updates ST: Applying to modify #1.

12:46:31 8FD10700 Drvrs: User Updates ST: Evaluating selection criteria for rule 'Notify User on Alternate Email Update Policy'.

12:46:31 8FD10700 Drvrs: User Updates ST: (if-src-dn in-subtree "uitm\staff") = TRUE.

12:46:31 8FD10700 Drvrs: User Updates ST: (if-op-attr 'homeEmailAddress' changing) = TRUE.

12:46:31 8FD10700 Drvrs: User Updates ST: Rule selected.

12:46:31 8FD10700 Drvrs: User Updates ST: Applying rule 'Notify User on Alternate Email Update Policy'.

12:46:31 8FD10700 Drvrs: User Updates ST: Action: do-send-email-from-template(notification-dn="security\Default Notification Collection",template-dn="security\Default Notification Collection\Update Alternate Email Template",token-attr("Internet EMail Address"),token-attr("Full Name"),token-attr("CN"),token-attr("homeEmailAddress")).

12:46:31 8FD10700 Drvrs: User Updates ST:

DirXML Log Event -------------------

Driver: \1UITM-TREE\system\IAMDriverSet\User Updates

Channel: Subscriber

Status: Error

Message: Code(-9010) An exception occurred: java.lang.NumberFormatException: null

   at java.lang.Integer.parseInt(Integer.java:542)

   at java.lang.Integer.parseInt(Integer.java:615)

   at com.novell.nds.dirxml.engine.rules.DoSendEmailFromTemplate$NotificationAttrs.<init>(DoSendEmailFromTemplate.java:480)

   at com.novell.nds.dirxml.engine.rules.DoSendEmailFromTemplate.apply(DoSendEmailFromTemplate.java:123)

   at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:189)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:310)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.Subscriber.processEvents(Subscriber.java:975)

   at com.novell.nds.dirxml.engine.Driver.submitTransaction(Driver.java:901)

   at com.novell.nds.dirxml.engine.DriverEntry.submitTransaction(DriverEntry.java:1174)

   at com.novell.nds.dirxml.engine.DriverEntry.processCachedTransaction(DriverEntry.java:1058)

12:46:31 8FD10700 Drvrs:    at com.novell.nds.dirxml.engine.DriverEntry.eventLoop(DriverEntry.java:866)

   at com.novell.nds.dirxml.engine.DriverEntry.run(DriverEntry.java:640)

   at java.lang.Thread.run(Thread.java:748)

 

12:46:31 8FD10700 Drvrs: User Updates ST:

DirXML Log Event -------------------

Driver: \1UITM-TREE\system\IAMDriverSet\User Updates

Channel: Subscriber

Status: Error

Message: Code(-9083) Error submitting event to subscriber: Code(-9010) An exception occurred: java.lang.NumberFormatException: null

   at java.lang.Integer.parseInt(Integer.java:542)

   at java.lang.Integer.parseInt(Integer.java:615)

   at com.novell.nds.dirxml.engine.rules.DoSendEmailFromTemplate$NotificationAttrs.<init>(DoSendEmailFromTemplate.java:480)

   at com.novell.nds.dirxml.engine.rules.DoSendEmailFromTemplate.apply(DoSendEmailFromTemplate.java:123)

   at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:189)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:310)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:436)

   at com.novell.nds.dirxml.engine.Subscriber.processEvents(Subscriber.java:975)

   at com.novell.nds.dirxml.engine.Driver.submitTransaction(Driver.java:901)

   at com.novell.nds.dirxml.engine.DriverEntry.submitTransaction(DriverEntry.java:1174)

12:46:31 8FD10700 Drvrs:    at com.novell.nds.dirxml.engine.DriverEntry.processCachedTransaction(DriverEntry.java:1058)

   at com.novell.nds.dirxml.engine.DriverEntry.eventLoop(DriverEntry.java:866)

   at com.novell.nds.dirxml.engine.DriverEntry.run(DriverEntry.java:640)

   at java.lang.Thread.run(Thread.java:748)

 

Anyone had any clue ?

Regards,
Keng

Labels (1)
1 Solution

Accepted Solutions
Vice Admiral
Vice Admiral

Hi,

The problem solved. So it was due to the an undocumented attributes (notfSMTPTimeout) introduced  in IDM 4.8 (as per Support said) at Default Notification Collection under Security container.

Setting this to  a value fixed the issues.

Regards,

Keng

 

View solution in original post

10 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

So first off, it is important to be able to parse the error messages.  🙂

 

You got:

Message: Code(-9010) An exception occurred: java.lang.NumberFormatException

and

Message: Code(-9083) Error submitting event to subscriber: Code(-9010) An exception occurred: java.lang.NumberFormatException: null

 

thus the important part is NOT the 9010 nor 9083 but the Number Format Exception errors. 

So there is a integer expected that you are not sending. (I forget, does the do-send-email have a timeout value now?  do-start-workflow does. I wonder if you perhaps failed to set a value. Designer forces you to, but you could edit the XML by hand or use iManager to do it incorrectly.

I would look for numbers referenced as obvious integers in your policy as a first step.

 

Vice Admiral
Vice Admiral

Hi,

That's the strange part. It was working till last week this error appeared. User reported no receiving any email notifications.

My policy is fairly simple, if the attribute homeEmailAddress is changing, trigger a send-email-from-template whereby passsing the Attributes Internet EmailAddress, Full Name, CN and homeEmailAddress as part of the information used inside the email template.

I had another 2 policy which also uses send-email-from-template. They also return the same error.

So I can see it may not related to the policy but something else... Hmmm

Regards,
keng

Tags (1)
Knowledge Partner Knowledge Partner
Knowledge Partner

Could you possibly include some trace?  Maybe this is something new, maybe not.  But sometimes it is easy to miss an important detail that a second set of eyes can help identify.

0 Likes
Vice Admiral
Vice Admiral

Hi,

Attached is the ndstrace.log. I had simulated 2 scenarios that use send-email-from template which caused the errors. One is homeEmailAddress modification and another one is new Vendor creation.

Regards,

Keng

Vice Admiral
Vice Admiral

Hi,

The problem solved. So it was due to the an undocumented attributes (notfSMTPTimeout) introduced  in IDM 4.8 (as per Support said) at Default Notification Collection under Security container.

Setting this to  a value fixed the issues.

Regards,

Keng

 

View solution in original post

Knowledge Partner Knowledge Partner
Knowledge Partner

Excellent find!  A number was expected and you were missing it.  And I guess right at some timeout value.  Just did not know about the new 4.8 'feature'  Thanks for the work on tracking this down.

0 Likes
Captain
Captain

This saved our day! I was really lost why do-send-email-from-template stopped working after idm48 upgrade.

To Product management: It is very odd that attribute is not updated  by IDM48 install/upgrade program. Documentation for it. and GUI would also be nice :). Setting default value by install program would save a lot of headache.

Kind regards

Veli-Matti

 

Captain
Captain

Fix is available - Bug 1159122: Error while using the <do-send-email> and the <do-send-email-from-template> policy actions is resolved.
https://www.netiq.com/documentation/identity-manager-48/releasenotes_idm4801_engine/data/releasenotes_idm4801_engine.html

 

Lieutenant Commander
Lieutenant Commander
Hi, i have this error appearing when applying a send email policy when user created, and the driver go into a freeze state,  the email tokens are mapped well, but whenever an email policy applied the whole driver stops.
any idea?
 
Warning: NLS unused message: Templates_DefaultNotificationCollection in: com.novell.idm.notificationtemplates.internal.notftemplates
 
EMAIL POLICY TEMPLATE:
=====================
<description>Manager Email New User</description>
<conditions>
<and disabled="true">
<if-class-name mode="nocase" op="equal">User</if-class-name>
</and>
</conditions>
<actions>
<do-send-email-from-template notification-dn="Security\Default Notification Collection" template-dn="security\Default Notification Collection\TEST">
<arg-string name="to">
<token-text xml:space="preserve">email address.com</token-text>
</arg-string>
<arg-string name="GivenName">
<token-src-attr name="Given Name"/>
</arg-string>
<arg-string name="Surname">
<token-src-attr name="Surname"/>
</arg-string>
</do-send-email-from-template>
</rule>
Knowledge Partner Knowledge Partner
Knowledge Partner

If you are tagging along with this thread, could you list the items above, that are reported to solve it, that you have tried and that have failed. If you have not tried them, please do and let us know.

 

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.