evanthika.blogspot.com
Evanthika Amarasiri's Blog: Reason for 'javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?' while working with WSO2 products
http://evanthika.blogspot.com/2015/05/reason-for-javaxnetsslsslexception.html
Monday, May 11, 2015. Reason for 'javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? While working with WSO2 products. While configuring WSO2 API manage to work with WSO2 IS as the Auth Manager, while trying to login to API Store/API Publisher, noticed the following exception. Javaxnet.ssl.SSLException: Unrecognized SSL message, plaintext connection? The reason for this was that we have configured a HTTP port for an HTTPS URL. Server URL of the Authentication service.
evanthika.blogspot.com
Evanthika Amarasiri's Blog: April 2014
http://evanthika.blogspot.com/2014_04_01_archive.html
Tuesday, April 29, 2014. Expiration times of L1 and L2 caches with Hazelcast for WSO2 products. Recently I had a doubt about how L1 and L2 caches work with WSO2 products. Then I went through the blog on WSO2 Multi-tenant Cache: JSR-107 (JCache) implementation based on Hazelcast. By Azeez and got an idea about the caches and how they work. In Cabon 4.2.0 based products, which is using Hazelcast. Friday, April 25, 2014. Retrieving availble HTTP methods from a back-end server through WSO2 ESB APIs. Extract ...
evanthika.blogspot.com
Evanthika Amarasiri's Blog: Dealing with "HTTP 502 Bad Gateway"
http://evanthika.blogspot.com/2015/07/dealing-with-http-502-bad-gateway-nginx.html
Friday, July 10, 2015. Dealing with "HTTP 502 Bad Gateway". Recently, while configuring WSO2 products with NginX, we were struggling to connect to the management console of the product since it was returning "HTTP 502 Bad Gateway" error. After doing some research, found out that it was a problem with SELinux. There are two SELinux boolean settings available by default. One of them is httpd can network connect which allows httpd to connect to anything on the network. Subscribe to: Post Comments (Atom).
evanthika.blogspot.com
Evanthika Amarasiri's Blog: September 2013
http://evanthika.blogspot.com/2013_09_01_archive.html
Monday, September 16, 2013. How to solve "WARNING: UNPROTECTED PRIVATE KEY FILE! While trying to connect to a remote server using my private key, I got the below exception. Warning: Permanently added '122.248.220.36' (ECDSA) to the list of known hosts. @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @. WARNING: UNPROTECTED PRIVATE KEY FILE! Permissions 0664 for 'evanthika.pem' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. Colombo, Sri Lanka.
evanthika.blogspot.com
Evanthika Amarasiri's Blog: September 2014
http://evanthika.blogspot.com/2014_09_01_archive.html
Friday, September 19, 2014. How to solve the famous token regeneration issue in an API-M cluster. In a API Manager clustered environment (in my case, I have a publisher, a store, two gateway nodes and two key manager nodes fronted by a WSO2 ELB 2.1.1), while regenerating tokens, if you come across an error saying Error in getting new accessToken. With an exception as below at Key Manager node, then this is due to a configuration issue. At org.apache.axis2.rpc.receivers.RPCUtil.inv...At org.apache....
evanthika.blogspot.com
Evanthika Amarasiri's Blog: Common SVN related issues faced with WSO2 products and how they can be solved
http://evanthika.blogspot.com/2015/07/common-svn-related-issues-faced-with.html
Tuesday, July 21, 2015. Common SVN related issues faced with WSO2 products and how they can be solved. TID: [0] [ESB] [2015-07-21 14:49:55,145] ERROR {org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository} - Error while attempting to create the directory: http:/ xx.xx.xx.xx/svn/wso2/-1234 {org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository}. SvnUrl http:/ svnrepo.example.com/repos/ /SvnUrl. Javalang.RuntimeException: org.wso2.carbon.deplo...At org.ws...
evanthika.blogspot.com
Evanthika Amarasiri's Blog: February 2014
http://evanthika.blogspot.com/2014_02_01_archive.html
Monday, February 3, 2014. Solving "org.apache.ws.security.WSSecurityException: An unsupported signature or encryption algorithm was used". While trying out the scenario which I have explained in my previous post Accessing a non secured backend from a secured client with the help of WSO2 ESB. With security scenario 3 onward, you might have come across an issue as below on client side. Orgapache.axis2.AxisFault: Error in encryption. At SecurityClient.runSecurityClient(SecurityClient.java:99). At org.ap...
evanthika.blogspot.com
Evanthika Amarasiri's Blog: November 2014
http://evanthika.blogspot.com/2014_11_01_archive.html
Tuesday, November 25, 2014. Salesforce Outbound Provisioning with WSO2 IS - Configuration that needs to be done in Salesforce. 1 Go to https:/ developer.salesforce.com/signup and sign up as a new user giving your email address (use the email address as the Username). 2 You will get an email asking you to activate your account. Click on the given link and specify a password and other required information (Secret Question, etc). Once you do that, you will be logged into Salesforce. 4 You need to create a n...
evanthika.blogspot.com
Evanthika Amarasiri's Blog: How to print the results summary when JMeter is running on headless mode
http://evanthika.blogspot.com/2015/07/how-to-print-results-summary-when.html
Thursday, July 9, 2015. How to print the results summary when JMeter is running on headless mode. When you are running JMeter in GUI mode, you can easily view the results through the Summary report. Or through the Aggregate report. But how do you view the summary if you are running JMeter in headless mode? This can be configured through the jmeter.properties file which resides in $JMETER HOME/bin folder. Note that this is enabled by default in latest versions of JMeter. E.g.:- Version 2.13. Why or why no...
evanthika.blogspot.com
Evanthika Amarasiri's Blog: December 2012
http://evanthika.blogspot.com/2012_12_01_archive.html
Wednesday, December 5, 2012. POX security with WSO2 ESB Proxy services. WSO2 ESB supports POX (Pure Old XML) security now. Let us see how we can test this with the latest version of WSO2 ESB . Pre-requisites - Download the latest stable release of WSO2 ESB from here. Start WSO2 ESB server. Create a Proxy Service. (We will use the Echo service shipped with WSO2 ESB here). Address uri="http:/ localhost:828 0. PublishWSDL uri="http:/ localhost:828 0. A) Through a preferred browser. Subscribe to: Posts (Atom).