UnsatisfiedLinkError for Cordys native method

I am getting an UnsatisfiedLinkError error when I try to call a web service from the Operation Test Tool in Process Platform. Why would Cordys be unable to find its own internal DLL when calling a web service from within Cordys?

<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
        <faultcode xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/">ns0:Server</faultcode>
        <faultstring xml:lang="en-US">com.eibus.xml.nom.Node.writeBytes(III)[B</faultstring>
        <faultactor>http://schemas.cordys.com/apps/util</faultactor>
        <detail>
          <cordys:FaultDetails xmlns:cordys="http://schemas.cordys.com/General/1.0/">
            <cordys:LocalizableMessage xmlns:cordys="http://schemas.cordys.com/General/1.0/">
              <cordys:MessageCode xmlns:cordys="http://schemas.cordys.com/General/1.0/">Cordys.WSAppServer.Messages.wsAppsDefaultError</cordys:MessageCode>
              <cordys:Insertion xmlns:cordys="http://schemas.cordys.com/General/1.0/">com.eibus.xml.nom.Node.writeBytes(III)[B</cordys:Insertion>
            </cordys:LocalizableMessage>
          </cordys:FaultDetails>
          <cordys:FaultRelatedException xmlns:cordys="http://schemas.cordys.com/General/1.0/">
            <![CDATA[java.lang.UnsatisfiedLinkError: com.eibus.xml.nom.Node.writeBytes(III)[B
            at com.eibus.xml.nom.Node.writeBytes(Native Method)
            at com.eibus.xml.nom.Node.write(Node.java:2165)
            at com.eibus.xml.nom.Node.write(Node.java:2228)
            at com.eibus.xml.nom.Node.writeToString(Node.java:2290)
            at com.ptap.gms.util.HandlebarsTemplateUtil.applyHandlebarsTemplate(HandlebarsTemplateUtil.java:26)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:497)
            at com.cordys.cpc.bsf.connector.BsfMethodCall.invoke(BsfMethodCall.java:325)
            at com.cordys.cpc.bsf.connector.TransactionHandler.handleJavaCall(TransactionHandler.java:2175)
            at com.cordys.cpc.bsf.connector.TransactionHandler.execute(TransactionHandler.java:2497)
            at com.cordys.cpc.bsf.connector.WSAppServerTransaction.process(WSAppServerTransaction.java:97)
            at com.eibus.soap.SOAPTransaction.processApplicationTransaction(SOAPTransaction.java:1357)
            at com.eibus.soap.SOAPTransaction.handleBodyBlock(SOAPTransaction.java:1281)
            at com.eibus.soap.SOAPTransaction.<init>(SOAPTransaction.java:558)
            at com.eibus.soap.SOAPTransaction.<init>(SOAPTransaction.java:210)
            at com.eibus.soap.Processor.onReceive(Processor.java:1335)
            at com.eibus.soap.Processor.onReceive(Processor.java:1316)
            at com.eibus.connector.nom.Connector.onReceive(Connector.java:483)
            at com.eibus.transport.NonTransactionalWorkerThreadBody.doWork(NonTransactionalWorkerThreadBody.java:61)
            at com.eibus.transport.NonTransactionalWorkerThreadBody.run(NonTransactionalWorkerThreadBody.java:26)
            at com.eibus.util.threadpool.WorkerThread.run(WorkerThread.java:67)
    ]]>
          </cordys:FaultRelatedException>
        </detail>
      </SOAP:Fault>
Tagged:
Sign In or Register to comment.