Henrry_han Contributor.
Contributor.
954 views

OO Execution Error: Failed to open HTTP connection; failed to GET resource at https://ec2.us-east-1.

Hi,

I am working on CSA 4.70 (with embedded OO) and AWS EC2 Integration, After perform an order, seems OO flow cannot connect to EC2 Apis, see below errors. Does anyone have any idea? thanks a lot.
Is it a proxy issue or others?..... EC2 apis are on Internet, OO is installed in company intranet.

 

2017-08-25 17:26:34,091 [1_WorkerExecutionThread-0_150000001] (PluginAdapterImpl.java:331) ERROR - org.hp.symphony.rest.client.exceptions.RestClientException: failed to GET resource at https://ec2.us-east-1.amazonaws.com/?Action=DescribeAvailabilityZones&Version=2014-06-15
at org.hp.symphony.rest.client.Resource.executeHttpMethod(Resource.java:283)
at org.hp.symphony.rest.client.Resource.doGet(Resource.java:90)
at com.iconclude.content.actions.EC2.EC2Base.sendRequest(EC2Base.java:558)
at com.iconclude.content.actions.EC2.EC2Base.sendRequest(EC2Base.java:488)
at com.iconclude.content.actions.EC2.ops.EnumerateAvailabilityZones.executeAction(EnumerateAvailabilityZones.java:55)
at com.iconclude.content.actions.EC2.EC2Base.execute(EC2Base.java:634)
at com.iconclude.content.actions.EC2.EC2Base.execute(EC2Base.java:626)
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.hp.oo.sdk.plugins.abstracts.BaseActionPlugin.execute(BaseActionPlugin.java:53)
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.hp.oo.maven.PluginAdapterImpl.executePlugin(PluginAdapterImpl.java:328)
at com.hp.oo.maven.PluginAdapterImpl.execute(PluginAdapterImpl.java:248)
at com.hp.oo.execution.control.actions.contentexecution.ContentExecutionActions.executeContentAction(ContentExecutionActions.java:97)
at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at io.cloudslang.worker.execution.reflection.ReflectionAdapterImpl.executeControlAction(ReflectionAdapterImpl.java:62)
at io.cloudslang.worker.execution.services.ExecutionServiceImpl.executeStep(ExecutionServiceImpl.java:326)
at io.cloudslang.worker.execution.services.ExecutionServiceImpl.execute(ExecutionServiceImpl.java:80)
at io.cloudslang.worker.management.services.SimpleExecutionRunnable.executeRegularStep(SimpleExecutionRunnable.java:167)
at io.cloudslang.worker.management.services.SimpleExecutionRunnable.run(SimpleExecutionRunnable.java:120)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at io.cloudslang.worker.management.services.WorkerThreadFactory$1.run(WorkerThreadFactory.java:33)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.hp.symphony.rest.client.exceptions.RestClientException: Failed to open HTTP connection
at com.hp.symphony.rest.client.handlers.HttpConnectionHandler.openConnection(HttpConnectionHandler.java:79)
at com.hp.symphony.rest.client.handlers.HttpConnectionHandler.handleRequest(HttpConnectionHandler.java:301)
at com.hp.symphony.rest.client.handlers.HttpConnectionHandler.handle(HttpConnectionHandler.java:394)
at com.hp.symphony.rest.client.HandlerChainImpl.proceed(HandlerChainImpl.java:21)
at com.hp.symphony.rest.client.handlers.RedirectionHandler.handle(RedirectionHandler.java:31)
at com.hp.symphony.rest.client.HandlerChainImpl.proceed(HandlerChainImpl.java:21)
at com.hp.symphony.rest.client.HandlerChainOutputStream.writeInternalBuffer(HandlerChainOutputStream.java:95)
at com.hp.symphony.rest.client.HandlerChainOutputStream.close(HandlerChainOutputStream.java:37)
at com.hp.symphony.rest.client.HandlerChainExecuter.writeEntity(HandlerChainExecuter.java:66)
at com.hp.symphony.rest.client.HandlerChainExecuter.executeChain(HandlerChainExecuter.java:42)
at org.hp.symphony.rest.client.Resource.executeHttpMethod(Resource.java:270)
... 32 more
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at com.hp.symphony.rest.client.httpconnection.HttpConnectionImpl.connect(HttpConnectionImpl.java:81)
at com.hp.symphony.rest.client.handlers.HttpConnectionHandler.openConnection(HttpConnectionHandler.java:76)
... 42 more
Failed to open HTTP connection; failed to GET resource at https://ec2.us-east-1.amazonaws.com/?Action=DescribeAvailabilityZones&Version=2014-06-15

 

0 Likes
5 Replies
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: OO Execution Error: Failed to open HTTP connection; failed to GET resource at https://ec2.us-eas

It seems to be that this is a proxy related error.

Try to use the proxy inputs as well. Will it trigger similar error?

Andrei Vasile Truta
0 Likes
Henrry_han Contributor.
Contributor.

Re: OO Execution Error: Failed to open HTTP connection; failed to GET resource at https://ec2.us-eas

Thanks a lot for your quick response. I am not familar with OO configuration, could you please tell me how to configure the Proxy.  I mean is there a global setting for this instead of modifying OO flow?

Many thanks.

0 Likes
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: OO Execution Error: Failed to open HTTP connection; failed to GET resource at https://ec2.us-eas

the proxy part is something you can configure for your particular usecase on the flow level - as inputs

Screenshot_99.png

For instance on the above attached you can see some default inputs that the http client get operation has

with those kind of inputs - if you define them in CSA you can make sure you pass some proxy settings to the flow level itslef.

Hope it helps,

Andrei Vasile Truta
0 Likes
Henrry_han Contributor.
Contributor.

Re: OO Execution Error: Failed to open HTTP connection; failed to GET resource at https://ec2.us-eas

Thanks a lot for your solution, I think it would be working.

But for easy, is there any Global Setting for all relavant flows/system level instead of specifying the proxy for each particular flow? Like any Environment variables for proxy setting?

0 Likes
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: OO Execution Error: Failed to open HTTP connection; failed to GET resource at https://ec2.us-eas

You could set some proxy settings in the central-wrapper.conf but those will not be passed to the flow inputs as I know.

to have some global proxy related values in your run-time environment (central) better to create some system properties with the exact names as the proxy inputs seen in the screenshot that I provided and you could set those values once in Central under Content Management > Configuration Items > System Properties.

As long as the flows are set by default so  that the inputs get their value with Assign From - these system properties values that you will define in Central will be used at runtime so you can achieve the desire behavior

Andrei Vasile Truta
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.