Anybody in stackoverflow land have the live log viewer working through a proxy? This is what mine looks like...
If I go directly to port 9443, everything works. Any help would be appreciated.
Related
I try to use WSO2 ESB at workplace where Proxy Server is available.
Set Proxy Server settings in axis2.xml,
Install certificate.
Initialize Salesforce connector(Salesforce certificate has been installed).
Test the API, run into an exception - SOAPProcessingException,
Really appreciate if someone can give ideas of solution.
First of all I have tried this type of a scenario using WSO2 ESB 4.9.0 and which was perfectly working fine. By looking at your error messages I can see that there was an Authentication failure, hence Sales Force end point returns some HTML error message. The ESB tries to build this HTML error message using the SOAP builder leading to this situation.
This could be due to some missing configuration in your setting. You may follow [1] to enable HTTP Proxy to Sales Force. Then to setup Sales Force [2] will be helpful.
Couple of thing I need to highlight here. Did you import the Salesforce certificate into the ESBs client trust store using the keytool import command. If not please go ahead and do so. Also is there a particular reason for you to use NHTTP transport here. Ideally we would use Passthrough transport to add the proxy host as given in [1].
If you still get the error after following the above steps please enable the wirelogs and post it here to investigate further. Follow these steps to enable wirelogs.
Open log4j.properties file from a text editor.
log4j.properties file is located in $ESB_HOME/repository/conf directory.
Un-comment the following entry.
log4j.logger.org.apache.synapse.transport.http.wire=DEBUG
Hope this helps you.
[1] https://docs.wso2.com/display/ESB470/Enabling+SSL+Tunneling+through+a+Proxy+Server
[2]https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Salesforce+Connector+Operations
I am very new to WSO2 and I am working through the WSO2 example Cloud to RDBMS using WSO2 Enterprise Service Bus. I have followed the example as closely as I can. When I click "TryIt" for the service I am running into an "Error connecting to the Tryit ajax proxy" I do have the axis2 server started with the command /opt/wso2esb-4.8.1/samples/axis2Server$ ./axis2server.sh and the axis2 server looks to be operating correctly. Please let me know if the example is dated or if there is something else I need to do. It is certainly missing steps that I have had to infer and I may have not known to take a step that it didn't explicitly tell me to take.
Thank you for your help.
Regards,
-Joe
Fixed by deleting artifacts from server and re-deploying (no other changes).
Has anybody managed to get XMPP protocol working successfully with WSO2ESB (WSO2 Enterprise Service Bus)?
I have managed to get the server setup correctly and it registered on Openfire as a session. From there nothing seems to work. I have deployed a service which has xmpp as a transport. The service deploys successfully but it doesn't seem to create a session on Openfire and the xmpp endpoint url appears not well formed:
xmpp://wso2esb#null/services/XMPPPOC
As you can see the domain is coming out as null.
I can find no issues in the wso2esb log or the openfire logs to indicate any problem.
Has anybody has any success using XMPP as a protocol with WSO2 products (at all, let alone ESB). It seems to be that it doesn't work and it certainly appears scantly documented.
Any suggestions would be appreciated.
I came across an issue using WSO2 Stratos 1.6.0 when trying to browse the registry. The browser just hangs when clicking on Resources > Browse. Having a look at the network traffic I see an HTTP POST request to /carbon/admin/jsp/session-validate.jsp that doesn't complete.
I then started debugging the org.apache.synapse.transport.passthru.ServerWorker (2.1.1-wsov1) in the WSO2ELB (2.0.2). I found that the code that writes the ACK to the response output stream is being skipped. This only appears to happen when POSTing to /carbon/admin/jsp/session-validate.jsp, when I hacked the /carbon/admin/js/main.js to perform a GET, everything worked fine.
So my question(s) being... is this a bug in main.js? is it a bug in ServerWorker in WSO2ELB? is there a special reason that the sessionAwareFunction in main.js uses POST as opposed to GET?
This is a bug in the transport ELB uses. Please use the latest release ELB http://wso2.com/products/elastic-load-balancer/
I have an ASPX page. When the page is loaded there is code in the code behind that uses an API. The API makes an HTTPS call out to a third party, commercial web service. I am trying to troubleshoot why the API calls are not working properly. Apparently the API actually constructs an XML request that is sent out over HTTPS to the web service. I've been told by the support rep that I need to provide them with the XML that is being sent. The only way I can figure out how to get the XML is to use a tool like Fiddler to see what is being sent out. So how can I use Fiddler to see the contents of the XML request that is being sent from the server out to the web service? I am running everything directly on the server but all I am seeing is the GET request for the ASPX file itself. I am not seeing anything in relation to the HTTPS request that the server code is sending out to the web service. I have not used Fiddler much so I am hoping that maybe I just don't have it set up right to monitor that traffic.
Corey
After mucking around with it a bit I found this post: Why isn't fiddler capturing request when invoking XMLRPC from iis?. That seemed to do the trick! Basically it sounds like the default proxy settings in Win7 are on a per user basis. So I went in and changed the identity of the AppPool for my site to a local user (Administrator) and then it worked great. I started up Fiddler. Then I started up my ASP.NET app and then when I loaded the page I saw the request that went out to the web service from my code behind! Yay!