Clarity

  • 1.  Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 05:24 AM

    Hi Experts,

     

    I am facing the below error while running a process..

     

    BPM-0704: An error occurred while executing custom script : org.apache.commons.jelly.JellyTagException: null:246:63: <soap:invoke> Failed to send a SOAP message generated to http://ppm/niku/xog Connection reset at com.niku.union.gel.tags.soap.InvokeTag

     

    The process completes in all other environments except production.

    Please help!

     

    regards,

    D



  • 2.  Re: Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 05:50 AM

    Can you check if this isn't the case ?

    SOAP CALL IS FAILING

    https://communities.ca.com/message/16507927

     

    NJ



  • 3.  Re: Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 05:51 AM


  • 4.  Re: Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 05:52 AM


  • 5.  Re: Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 07:03 AM

    Thanks navjoshi !

     

    I checked those links.

     

    I have verified that the xog url is correct.

    When i launch the url in a separate browser window, i can see the xog wsdl page.

     

    My  process custom script parameter that stores the xog url. This parameter is passed to the soap invoke tag.

    <soap:invoke endpoint="${xogURL}"  var="xogresult">

     

    Besides, the same process completes without errors in dev and test clarity environments.

     

    I have also run the process multiple times to rule out network connectivity issue. It fails with same error.

    The trace/error in the process message is as follows...

     

    org.apache.commons.jelly.JellyTagException: null:246:63: <soap:invoke> Failed to send a SOAP message generated to 'http://ppm/niku/xog'.Connection resetferedInputStream.java:218)


    org.apache.commons.jelly.JellyTagException: null:246:63: <soap:invoke> Failed to send a SOAP message generated to 'http://ppm/niku/xog'.Connection reset

     

            at com.niku.union.gel.tags.soap.InvokeTag.doTag(InvokeTag.java:64)

     

            at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

     

            at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

     

            at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)

     

            at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)

     

            at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

     

            at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

     

            at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)

     

            at com.niku.union.gel.tags.ScriptTag.doTag(ScriptTag.java:20)

     

            at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

     

            at com.niku.union.gel.GELScript.run(GELScript.java:80)

     

            at com.niku.union.gel.GELController.invoke(GELController.java:20)

     

            at com.niku.bpm.services.ExecuteCustomAction.run(ExecuteCustomAction.java:180)

     

            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)

     

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

     

    Caused by: java.net.SocketException: Connection reset

     

            at java.net.SocketInputStream.read(SocketInputStream.java:168)

     

            at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

     

            at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)

     

            at java.io.BufferedInputStream.read(BufferedInputStream.java:317)

     

            at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)

     

            at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)

     

            at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:652)

     

            at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1072)

     

            at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)

     

            at com.niku.union.xml.SimpleSOAPMessage.processRequest(SimpleSOAPMessage.java:261)

     

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:86)

     

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:61)

     

            at com.niku.union.gel.tags.soap.InvokeTag.doTag(InvokeTag.java:60)

     

            ... 14 more

     

    Root cause

     

    java.net.SocketException: Connection reset

     

            at java.net.SocketInputStream.read(SocketInputStream.java:168)

     

            at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

     

            at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)

     

            at java.io.BufferedInputStream.read(BufferedInputStream.java:317)

     

            at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)

     

            at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)

     

            at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:652)

     

            at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1072)

     

            at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)

     

            at com.niku.union.xml.SimpleSOAPMessage.processRequest(SimpleSOAPMessage.java:261)

     

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:86)

     

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:61)

     

            at com.niku.union.gel.tags.soap.InvokeTag.doTag(InvokeTag.java:60)

     

            at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

     

            at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

     

            at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)

     

            at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)

     

            at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

     

            at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

     

            at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)

     

            at com.niku.union.gel.tags.ScriptTag.doTag(ScriptTag.java:20)

     

            at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

     

            at com.niku.union.gel.GELScript.run(GELScript.java:80)

     

            at com.niku.union.gel.GELController.invoke(GELController.java:20)

     

            at com.niku.bpm.services.ExecuteCustomAction.run(ExecuteCustomAction.java:180)

     

            at EDU...


    regards,

    D



  • 6.  Re: Process fails with error BPM-0704: An error occurred while executing custom script



  • 7.  Re: Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 10:39 AM

    Are you sure that the server where the bg service is running it is resolving the hostname 'ppm' to the correct IP address for the server?

     

    And just to confirm, your normal url for accessing the wsdl list is http://ppm/niku/wsdl ? (not a different port than 80, not a different protocol than http?)

     

    Are you also certain that /niku/xog isn't being blocked or protected by anything in the production environment to that address (load balancers, gateways/proxies, SSO url protection)?  Since accessing /niku/wsdl is a different url/endpoint, it is possible that one is configured whilst the other is not.

     

    Have you checked the app-access and app-ca logs for the app services running at the http://ppm server to see if the connections are getting there at all, or if errors are being reported when the connection is being made?



  • 8.  Re: Process fails with error BPM-0704: An error occurred while executing custom script

    Posted Mar 25, 2015 08:37 AM

    Hi,

     

    I had a similar problem once: a process running a XOG did not work (couldn't reach the endpoint), but I had no problem running the XOG  directly from my laptop.

     

    The problem was that the Clarity URL that I was using as endpoint was valid only on the client network (outside world). Inside server network, I had to use another endpoint to access Clarity.

     

    I replaced the Clarity URL by the internal server name and then the process started to work.

     

    Regards,

    Roberto Barra