indranil2121
New Member.
275 views

SOAP driver unable to process few transactions

We have a SOAP driver integrated where we got an error while processing few transactions.

=========================================================================
DirXML Log Event -------------------
Driver: \IDVP-TREE\Energycorp\Services\IDM\DriverSet\NESCustomerWeb
Channel: Subscriber
Status: Fatal
Message: Code(-9005) The driver returned a "fatal" status indicating that the driver should be shut down. Detail from driver: Exception caused by SubscriptionShim.execute()
java.lang.NoClassDefFoundError: org/json/JSONException
at com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.XMLtoJSON(JSONHandlerExtension.java:321)
at com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.modifySubscriberRequest(JSONHandlerExtension.java:529)
at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown Source)
at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown Source)
at com.novell.nds.dirxml.remote.loader.Driver.driverStart(Driver.java:155)
at com.novell.nds.dirxml.remote.loader.RemoteLoader.run(RemoteLoader.java:951)
at java.lang.Thread.run(Thread.java:745)



<status level="fatal">Code(-9005) The driver returned a "fatal" status indicating that the driver should be shut down. Detail from driver: Exception caused by SubscriptionShim.execute()
java.lang.NoClassDefFoundError: org/json/JSONException
at com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.XMLtoJSON(JSONHandlerExtension.java:321)
at com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.modifySubscriberRequest(JSONHandlerExtension.java:529)
at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown Source)
at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown Source)
at com.novell.nds.dirxml.remote.loader.Driver.driverStart(Driver.java:155)
at com.novell.nds.dirxml.remote.loader.RemoteLoader.run(RemoteLoader.java:951)
at java.lang.Thread.run(Thread.java:745)
<application>DirXML</application>
<module>NESCustomerWeb</module>
<object-dn></object-dn>
<component>Subscriber</component>
</status>
</output>
====================================================================
Driver stopped working and blinking on such transaction. When we delete those transaction, driver get start perfectly.
Any suggestion or resolution plan for this?
Labels (1)
0 Likes
2 Replies
Knowledge Partner
Knowledge Partner

Re: SOAP driver unable to process few transactions

On 4/29/2019 10:24 AM, indranil2121 wrote:
>
> We have a SOAP driver integrated where we got an error while processing
> few transactions.
>
> =========================================================================
> DirXML Log Event -------------------
> Driver:
> \IDVP-TREE\Energycorp\Services\IDM\DriverSet\NESCustomerWeb
> Channel: Subscriber
> Status: Fatal
> Message: Code(-9005) The driver returned a "fatal" status
> indicating that the driver should be shut down. Detail from driver:
> Exception caused by SubscriptionShim.execute()
> java.lang.NoClassDefFoundError: org/json/JSONException
> at
> com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.XMLtoJSON(JSONHandlerExtension.java:321)
> at
> com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.modifySubscriberRequest(JSONHandlerExtension.java:529)
> at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown
> Source)
> at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown
> Source)
> at
> com.novell.nds.dirxml.remote.loader.Driver.driverStart(Driver.java:155)
> at
> com.novell.nds.dirxml.remote.loader.RemoteLoader.run(RemoteLoader.java:951)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
> <status level="fatal">Code(-9005) The driver returned a "fatal" status
> indicating that the driver should be shut down. Detail from driver:
> Exception caused by SubscriptionShim.execute()
> java.lang.NoClassDefFoundError: org/json/JSONException
> at
> com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.XMLtoJSON(JSONHandlerExtension.java:321)
> at
> com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.modifySubscriberRequest(JSONHandlerExtension.java:529)
> at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown
> Source)
> at com.novell.nds.dirxml.driver.soap.SOAPSubscriber.execute(Unknown
> Source)
> at
> com.novell.nds.dirxml.remote.loader.Driver.driverStart(Driver.java:155)
> at
> com.novell.nds.dirxml.remote.loader.RemoteLoader.run(RemoteLoader.java:951)
> at java.lang.Thread.run(Thread.java:745)
> <application>DirXML</application>
> <module>NESCustomerWeb</module>
> <object-dn></object-dn>
> <component>Subscriber</component>
> </status>
> </output>
> ====================================================================
> Driver stopped working and blinking on such transaction. When we delete
> those transaction, driver get start perfectly.
> Any suggestion or resolution plan for this?


So the error is in an XML to JSON class, which is odd, and looks like a
custom class.

com.ev.idm.drivers.soap.jsonxml.JSONHandlerExtension.XMLtoJSON

Who is EV? Did they give you a custom Java extension?

Look at the driver configuration, Driver properties, there are Java
extensions options (Might be hidden, there is a GCV like Hide/Show
choice and chose to show).

We would need to see the event coming into the policy that calls this.
Might need to show it on the Remote Loader side. Likely it is expectin
JSON or XML and is not getting valid JSON or XML.


0 Likes
Knowledge Partner
Knowledge Partner

Re: SOAP driver unable to process few transactions

Could you show example of your input SOAP document? (Maybe your doc has some inconsistencies, etc)
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.