Resolve Amoeba Connection MySQL error solution

Amoeba is used to configure MySQL's master-slave replication today. From the installation to the start-up service, I deeply realized that student movement dimension is not easy.  

first is the installation of the wrong resolution, the connection of the wrong brother can be directly down. Installation Error

1. Java_home environment variable is not set appears.
But obviously the JDK has been successful, Java version shows the normal
Explain the problem must be on the amoeba configuration

[email protected] bin]#./-"1.8.0_102"1.8. 0_102-  25.102-b14, Mixed mode)

Solution:
Modify the/amoeba/bin/amoeba file to write directly to the JAVA_HOME environment variable at the beginning of the file

Java_home=/usr/local/src/java/jdk1. 8. 0_121

2 appearance of the stack size specified is too small, specify at least 228k
Description default configuration XSS is relatively small 128k, startup prompt is too small

The stack size specified is too small, specify at least 228kerror:could not create the Java Virtual machine.error:a fata L exception has occurred. Program would exit.

Also modify the/amoeba/bin/amoeba file, modify it to 256k

default_opts="-server-xms256m-xmx256m-xss256k"

This time, into the amoeba directory
Perform

./bin/amoeba Start

The success of the above screen shows that your amoeba has been successfully transferred.
But....
You think this is the end of it, once I was so naïve to think.
It was not until I spent n hours to connect amoeba and MySQL to a normal connection, and I hope my solution works for you.
The following is a solution to the Amoeba connection error.
Normal online We can search for two solutions.

Connection error

First Kind
Is Amoedb dbservers.xml in the password which is commented, careful little partner will not make this mistake, this solution is to go to the configuration file to eliminate the comments, and fill in the correct password.
For example, this brother is the mistake .
http://blog.csdn.net/lwei_998/article/details/7321880

The second kind
Is that access to the database is not enabled on the server where amoeba is located, causing amoeba to be unable to access the database
Solution: Go to the main database and enter MySQL from the database and enter the following command

GRANT all privileges on * * to ' root ' @ '% ' identified by ' password ' with GRANT OPTION;

Connect again.

Third Kind
That is, the landlord error, error is

Object, Cause:validateobject failed

A predecessor some toss, think is JDK and Emoeba between the conflict (actually not), he used is jdk1.8+emoeba2.2, so re-changed a jdk1.7+emoeba2.2, or appear the same mistake, he still don't forget, and change a jdk1.7+ emoeba3.0.4, it's the same mistake. Another test, very sure is emoeba problem, the database can be successfully connected to Emoeba, after the connection GG, began to look at the configuration file, a sentence to arouse his attention

<property name="schema">test</property>

What is this, this is a test database ah, my databases has a test database, and No.
A database of test is created in databases .

Connect again, Success!

Resolve Amoeba Connection MySQL error solution