XOG Error: Status-Code: 502: Bad Gateway

[Anon Anon]

Hello,
we have got an issue with custom GEL script in process, the script was running for months without problems, but now it's giving following error (Other processes with custom GEL scripts are running without errors):

BPM-0704: An error occurred while executing custom script: org.apache.commons.jelly.JellyTagException: null:329:71: <soap:invoke> 
Failed to send a SOAP message generated to 'https://url.com/niku/xog'.HTTP Error: Status-Code: 502: Bad Gateway 
at com.niku.union.gel.tags.soap.InvokeTag.doTag(InvokeTag.java:77) 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:43) 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:662) Caused by: java.lang.RuntimeException: HTTP Error: Status-Code: 502: Bad Gateway 
at com.niku.union.xml.SimpleSOAPMessage.processRequest(SimpleSOAPMessage.java:264) 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:73) ... 
14 more Root cause java.lang.RuntimeException: HTTP Error: Status-Code: 502: Bad Gateway at com.niku.union.xml.SimpleSOAPMessage.processRequest(SimpleSOAPMessage.java:264) 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:73) 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:43) 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:662)

Does anyone touched this error or does anyone some solution for this?

Thanks,
Martin

[Deactivated User]

Just wondering again...
Are the Gel scripts run on the app server or are they run on workstation.
In the later case there could be a change in the network settings.

Martti K.

[Anon Anon]

Hello,
thank you for your answer, the GEL script runs on app server so I don't think there could be a problem with network setting.

Have you or someone else got any other idea?

Thanks,
Martin

[navzjoshi00]

http://getnetgoing.com/HTTP-502.html
http://www.checkupdown.com/status/E502.html
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Can you check the app log as well ?

NJ

[Anon Anon]

Hello,
I checked app logs, but there are no errors connected to this issue.
Regards,
Martin

[FIller Mark]

Bad gateway refers to http error 502 which is mean that a server which is try to fulfill the client request received an invalid response from upstream server. It is often a network error between servers on the internet, meaning the problem wouldn't be with your computer or internet connection. Empty or incomplete headers or response body typically caused by broken connections or server side crash can cause 502 errors if accessed via a gateway or proxy. Since it's just a generic error, it doesn't actually tell you the website's exact issue.

How to Solve 502 Errors

• Perform a hard-refresh in your browser. On Macs, this is done by pressing Cmd + Shift + R.
• Clear your browser cache and delete cookies. Your browser may be holding on to certain files that were saved once you visited the website with a 502 error.
• Change your DNS servers. If you've never changed them in the past you likely still have the default servers assigned to you by your ISP, try using open DNS servers such as Google's Public DNS.
• Finally, restart your computer/networking equipment. Some temporary issues with your computer and how it's connecting to your network could be causing 502 errors, especially if you're seeing the error on more than one website. In these cases, a restart would help.