Seems like 9160 is hard coded somewhere and if you offset MB and tries to connect to a Cassandra lives in 9160, you can't do that.
Easy to reproduce; 1. start MB cassandra profile with 0 offset -> cassandra on 9160 2. start MB default profile with 2 offset -> errors at MB, since it tries to connect to 9162 (even you change the 9160 to something else in all configs, you still get the same error) And documentation has few issues too: https://docs.wso2.org/display/MB220/Standalone+Deployment+using+the+MB+Cassandra+Profile 1. following seems not true: If your Cassandra server is hosted in the same host in which MB runs, you do not need to make any changes to the connection string in the <MB_HOME>/repository/conf/advanced/andes-virtualhosts.xml file. By default it is <connectionString>localhost:9160</connectionString>. If your Cassandra server is running in a different host, for example the 10.100.3.234 server, you need to change the connection string to <connectionString>10.100.3.234:9160</connectionString>. If your Cassandra server is running on a port other than the default port which is 9160, change the connection string by the port offset value defined in the <MB_HOME>/repository/conf/carbon.xml file. For example, if the port offset is 2, change the connection string to <connectionString>localhost:9162</connectionString>. 2. It doesn't say how to start the server in "Point WSO2 MB to Cassandra" step. Please review the whole documentation. -- Thanks & regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
