apache / apache/incubator-seata-samples

Deployment of Dubbo microservices for seata.

Open
#580 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2.4k
Forks
2k
PR merge metrics
No merged PRs in 30d

Description

Hi team,
I am trying deployment of Dubbo microservices for seata using following steps:

**1. Startup Seata Server**
`docker run --name seata-server -p 8091:8091 -p 7091:7091 seataio/seata-server:1.5.0`

**logs_startup_seata_server:** [seata-sample.txt](https://github.com/seata/seata-samples/files/9948718/seata-sample.txt)

**UI interface for seata-server:** ![seata-s](https://user-images.githubusercontent.com/92078754/200247681-61592aef-f5ab-4f09-8c33-0557213d595c.jpg)

**2. Startup Zookeeper**
`docker run --name zookeeper -p 2181:2181 -p 2888:2888 -p 3888:3888 -d zookeeper` this command is running successfully for me.

**3.Execute SQL under seata-samples\dubbo\src\main\resources\sql**
I am stuck on how to execute microservices under above mentioned path step, I also tried to run these .java files (AccountService.java, BusinessService.java, OrderService.java, StockService.java) directly by using `javac filename.java` but not able to start them and failed with this error
**Error_logs:** [error.txt](https://github.com/seata/seata-samples/files/9948772/error.txt)

Could you please have a look and provide your feedback regarding the same.

Contributor guide

Open the contributing guide

Research direction

Start by reading seata-samples/dubbo/src/main/resources/sql and the entry points AccountService.java, BusinessService.java, OrderService.java, and StockService.java, then review the attached error log. Determine how this sample is intended to start its services instead of compiling individual files with javac. Done means the SQL step is completed and the Dubbo microservices start successfully with Seata and ZooKeeper.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
devops, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.