Solution and summary of the crash problem when opening various Seata in distributed transaction processing

When I was learning Seata today, after various configurations were completed, when I clicked seata-server, a flashback effect appeared.

 

After the flashback appears, open the control page in the current directory.

 

Enter:  seata-server.bat   command.

 

You can view the current error log.

 

I will summarize three situations here.

 

Through the above log view, you can know:

 

1. The memory of the machine is too small, modify the configuration file of the running file. Modify related attributes.

The steps are as follows:

Open edit mode.

 

Modify these three parameters to a smaller value. (As shown in the picture, I modified it to 256m, you can adjust it according to your own machine.)

 

Second, the corresponding configuration Log file cannot be found.

Solution:

In the seata directory, create a new folder------->logs file.

 

Third, the mysql connection version conflict and format error in the configuration file. (I made this mistake, and it took me two hours to find and solve this error)

Some friends Mysql version is 8.0 or higher. Two major changes are required.

 

1. When connecting to mysql in the configuration file, modify the mysql related driver.

Under the conf folder:

 

Enter edit mode:

 

Find the database connection:

1. Add "cj" to the driver (this is the change of mysql in the high version... helpless)

2. Add the time zone discrimination after the url: serverTimezone = UTC.

 

Then go back to the lib directory of seata:

Look for the mysql-connector-java jar package, whether it is above 8.0. (I am the problem, the original 5.6 has always been the default, after modifying it to 8.0, the startup is successful!)

 

The jar package can be downloaded directly from the MYSQL official website.

 

Then start nacos first.

 

After nacos starts successfully, start the seata program.

At this point, all configuration and startup are complete! ! !

 

Hereby record.

 

 

 

 

Guess you like

Origin blog.csdn.net/m0_46405589/article/details/115027462