Issue in connect with IBM Netcool for pulling events

Yogesh_Yadav
Tera Contributor

‎08-03-2024 04:20 AM

Trying to connect to IBM Netcool using "IBM Netcool _V2" OOB event pull connector getting below error:

 

Error:

failed to run 3PC java.lang.ClassCastException: class org.mozilla.javascript.Undefined cannot be cast to class org.mozilla.javascript.NativeObject (org.mozilla.javascript.Undefined and org.mozilla.javascript.NativeObject are in unnamed module of loader 'app')

 

Preview file
18 KB
0 Helpfuls
  • 640 Views
3 REPLIES 3

Satishkumar B
Giga Sage
Giga Sage

‎08-04-2024 01:11 AM

Hi @Yogesh_Yadav 
The error indicates a type casting issue, where an undefined value is being treated as a NativeObject in the script.

Resolution Steps:

  1. Check Script Logic: Review the event pull connector script to identify where the value might be undefined and add appropriate type checks.
  2. Script Includes: Ensure that any Script Includes or functions used by the connector are compatible with your ServiceNow instance and the version of IBM Netcool you're connecting to.
  3. Debugging: Use ServiceNow's logs and debugging tools to pinpoint the exact line or function causing the error.
  4. Documentation and Support: Refer to the ServiceNow and IBM Netcool documentation for known issues or updates related to the "IBM Netcool _V2" connector. Contact ServiceNow or IBM support if needed.

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/event-manageme...


…………………………………………........................................................................................
Mark it helpful 👍and Accept Solution ✅!! If this helps you to understand.

…………………………………………........................................................................................



0 Helpfuls

Yogesh_Yadav
Tera Contributor

‎08-05-2024 10:29 AM

Thanks Satish for your reply.

Earlier trying with port 4100 so not working, while troubleshoot Netcool team ask to troubleshoot on port 8080 and it working now.

 

Thank you 🙂

0 Helpfuls

Satishkumar B
Giga Sage
Giga Sage
In response to Yogesh_Yadav

‎08-05-2024 12:43 PM

@Yogesh_Yadav Thank you for the assisting with the resolution. It appears that the issue was related to the port configuration. The resolution was to use port 8080 instead of port 4100, and everything is working fine now.

 

please consider marking the response as helpful👍 and accept the solution ✅

0 Helpfuls