RepoPilot

codingapi/tx-lcn

LCN distributed transaction framework, compatible with dubbo, spring cloud and Motan framework, supports various relational databases

Mixed

Stale — last commit 3y ago

MixedDependency

last commit was 3y ago; dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 3y ago; dependency CVE scan unavailable

  • Stale — last commit 3y ago
  • 10 active contributors
  • Distributed ownership (top contributor 31% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: codingapi/tx-lcn

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T00:48:01.121Z · commit f8ce807b8a82

Verdict

Mixed — Stale — last commit 3y ago

  • 10 active contributors
  • Distributed ownership (top contributor 31% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

TX-LCN is a distributed transaction coordination framework for Java microservices that uses a centralized Transaction Manager (TM) to coordinate local transactions across multiple services and databases. It handles the 2-phase commit protocol locally on each Transaction Client (TC) instance, supporting Dubbo, Spring Cloud, and Motan RPC frameworks without requiring XA or complex state machine logic. Maven monorepo: starter-txlcn-protocol and starter-txlcn-tc provide Spring Boot integration; txlcn-tm runs the central transaction manager; txlcn-tc implements the transaction client; txlcn-protocol defines message serialization; txlcn-p6spy intercepts JDBC for SQL logging. Example modules…

Start here

  • txlcn-tm: Central transaction manager service—orchestrates commit/rollback decisions; must be always-available
  • txlcn-tc: Transaction client library embedded in each microservice; handles local undo logs and phase-2 commits
  • txlcn-protocol: Message serialization spec for TC↔TM communication; protocol changes break compatibility across versions
  • txlcn-p6spy: JDBC event capture layer; extracts SQL for undo-log generation and rollback simulation
  • [example-protocol-a and example-protocol-b](https://github.com/codingapi/tx-lcn/blob/dev6.0/example-protocol-a and example-protocol-b): Runnable dual-service examples showing 2-phase commit in…

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/codingapi/tx-lcn.git && cd tx-lcn && mvn clean install. Configure MySQL and Redis per ./sql/init.sql, then: (1) start TM server, (2) configure example-tc and example-tc-2 in application.prop…

Daily commands:

Start TM: mvn spring-boot:run -pl txlcn-tm. Start TC instances: mvn spring-boot:run -pl example-tc and mvn spring-boot:run -pl example-tc-2. Verify: curl http://localhost:8090/save?name=test123 (triggers distributed wri…

…shortened for this brief.

Key cautions & unknowns

  • Stale — last commit 3y ago
  • TM server must start before any TC instance (discovery/heartbeat failure silent-fails transactions). Redis configuration in application.properties is optional but recommended for distributed cache consistency. P6Spy…
  • Published-advisory coverage was unavailable for the captured dependencies.
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.


For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Forkable" badge

Paste into your README — live-updates from the latest cached analysis.

Variant:
RepoPilot: Forkable
[![RepoPilot: Forkable](https://repopilot.app/api/badge/codingapi/tx-lcn?axis=fork)](https://repopilot.app/r/codingapi/tx-lcn)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/codingapi/tx-lcn on X, Slack, or LinkedIn.

Ask AI about codingapi/tx-lcn

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/codingapi/tx-lcn"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>