I have proxy service on WSO2 Enterprise Service Bus 4.8.1. It makes pass through proxy to Echo service on the same server. After restart ESB server this service disappears because of
ERROR - ProxyService Error reading from wsdl URI java.net.ConnectException: Connection refused: connect
WARN - Axis2SynapseController The proxy service echoProxy cannot be deployed - Continue in Proxy Service fail-safe mode.
I think that internal service Echo is not started when this service starting and it causes this error. When ESB server is completely started Echo servise is running and it is possible to deploy echoProxy service. But I don't know how.
For your proxy, i believe you used option. That is why you get that error. If you go to repository/deployment/server/synapse/default/proxy folder, you will see the proxy configuration which you created. You can make a copy from that, and after server starts fine, you can deploy that file in the same location. It will be deployed successfully
Related
Every time the esb service is restarted, the logs previously running are refreshed. How do you keep the history?thank you
When we deploy the ESB in a VM it will not clear the wso2carbon logs with a server restart. Could you please elaborate on the server deployment. If you are using a container-based deployment you will need to mount the logs to an external directory to avoid this.
I have configured WSO2 Identity Server following this doc.
But when i log in to my webapp I get the following error :
Connection Refused.
I'm behind a corporate proxy. How should I configure IS server to make it work?
If you are having issues with connecting outside from your network without a proxy, you can use the following jvm parameters during the server startup to provide the proxy configurations.
ex:
sh wso2server.sh -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8000
-Dhttp.nonProxyHosts="localhost|127.0.0.1|10.*.*.*"
I'm trying to configure an aws beanstalk single instance. I've successfully created the instance, but when I navigate to the Environment URL, I get the following error.
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote server
What could be causing this and what do I need to do to fix it.
I'm deploying a java web app using tomcat.
I deployed an Application to AWS elastic beanstalk. When I try to open the application, I am getting 502 proxy error Saying following message.
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote server
Apache/2.2.31 (Amazon) Server at mehe.us-west-2.elasticbeanstalk.com
Port 80
Strange part is when I run the application from localhost(Still connected to amazon database) the application is working fine, but after deloying it is not working. Here's the link to application
Any ideas how to get rid off it.
The timeout value for HTTPD is lower than the timeout value set for ELB. Change the timeout value in /etc/httpd/conf/httpd.conf
The keep the value between reboots you'll need to either create a custom AMI or use .ebextensions feature.
I want configuration files for WSO2 ELB 2.1.1 and WSO2 ESB 4.8.1, axis2.xml loadbalancer.config carbon.xml catalina-server.xml and any other if there.
I have configured with one ELB(offset 0, 8280), one manager(offset 1, 8281) and one worker(offset 2, 8282) ESB and when i try to send a request via ELB I'm getting
DynamicLoadbalanceEndpoint application member not available
but both are available and get the log that mgt and worker have joined when they turn on in ELB.
Initially when i send a request i have got
httpclient.HttpMethodDirector: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
then I have set allowall in axis2.xml and got the error which I have mentioned.
What would be the problem? If someone who have already configured could share the configuration files it will be very helpful for me.
Thanks.
Please refer WSO2 Clustering and Deployment Guide. There are instructions to configure an ESB cluster.
If the ESB cluster is not connected to the ELB, you will see "application member not available" message in ELB logs when you try to send requests.
Maybe this will be useful to someone else in future:
The WSO2 Elastic Load Balancer has been discontinued as of July 1st 2015. You can download NGinx Plus [1] - the load balancer by NGinx - for which we provide support.