BootUI
Try it
Setup
Features
Workshop
Properties
AI agents
Ecosystem
GitHub
Try it
Setup
Features
Workshop
Properties
AI agents
Ecosystem
GitHub
  • Get started

    • Try the sample app
    • Setup
    • Spring WebFlux
    • Quarkus
    • Java agent
    • Activation and safety
    • Non-standard runtimes
    • Troubleshooting
  • Workshop

    • Workshop overview
    • 00 - Runtime understanding
    • 01 - Setup and tooling
    • 02 - Configuration and wiring
    • 03 - Runtime journal
    • 04 - Runtime Insights
    • 05 - Java instrumentation
    • 06 - Assessment and impact
    • 07 - Agent change loop
    • 08 - Going further
    • Participant worksheet
    • A - Prompts
    • B - Troubleshooting
    • C - Frameworks
    • D - Extensions
  • Features

    • All features
    • Scorecard
    • Live Activity
    • Runtime Insights
    • Advisors
    • Runtime
    • Configuration
    • Database
    • Security
    • Services
    • Diagnostics
    • Java Agent
    • Developer tools
  • Reference

    • Properties
    • Framework support
    • AI agents
    • Command line
    • BootUI family
    • Known limitations
  • Diagnostic checks

    • Architecture
    • REST API
    • Spring
    • Hibernate
    • Database
    • Security
    • Vulnerabilities
    • Memory
    • Pentesting
    • GraalVM readiness
    • CRaC readiness
    • Quarkus
    • Quarkus security
  • Contributing

    • Repository
    • Specification
    • Implementation plan
    • v2 plan
    • Try 2.0 early
    • v2 validation report
    • Releasing 2.0
    • Quarkus design notes
    • WebFlux design notes
  • Privacy

Appendix B - Troubleshooting

Use the smallest safe check first. Keep guards on and preserve your evidence. Tell the facilitator which checkpoint is incomplete; pairing is preferable to spending an entire chapter reinstalling tools.

Setup and connection

SymptomCheckRecovery
Missing commands/featuresRelease tag/SHA, CLI and Java agent versionsUse the workshop's 2.1.0 components, not a 1.x CLI or moving branch
JDK/toolchain failurejava -version, JAVA_HOME, wrapper outputUse a supported local JDK; early-access JDKs are not required
Maven cannot find BootUI modulesRepository root and isolated .m2Repeat Chapter 01's -am install warm build; then run just the sample
First build is slow/offlineDependency/toolchain download logsWarm beforehand; use a helper's prepared checkpoint or pair
8080 already belongs to another appExisting listener and application identityPick a free port; update launcher, browser, MCP, BOOTUI_URL, and curl
Console 404Profile, activation, root path, portReturn to the dev launch; do not force activation in production
CLI/traffic points at the wrong port after restartTerminal 2 BOOTUI_URL, browser and overview identityReuse the selected URL; a new terminal needs it set again
SQL says seed table missingStartup runners not finishedWait for the sample welcome/startup readiness, then retry once
Optional services startLauncher and active profilesUse the Chapter 01 MVC dev launch, not the all-services launch; Docker is not required for the core
CLI not foundInstaller location/new terminal PATHUse the reviewed installer guidance; do not reinstall the app
MCP tools absentOpt-in toggle, loopback URL, client format/trust, client reloadCopy the panel's config for that client and test a real read; use CLI fallback
MCP reset after JVM restartRuntime toggle/persisted configRe-enable MCP explicitly for the new workshop process
Local MCP/CLI gets 401/403Host app security, actual caller address, transport responsePreserve guards; do not add a wildcard remote allow rule to proceed
Skill not discoveredWhole consumer directory and client skill supportReload client and check bootui discovery; contributor skill is different

Runtime evidence

SymptomCheckRecovery
Empty activityJournal/source policy, exact port, agreed route trafficSend only the authorized workload and inspect Recording
Missing profile/exception detailCurrent id, retained journal vs panel bufferSelect a fresh profileable request; report eviction/missing rich details
No repeated SELECT observationShow all routes/search, >=3 qualifying requests, >=5 repeated SELECTsUse six sequential samples, allow processing, inspect SQL groups
Earlier advisor/import evidence disappearedChapter 05 full process restartUse labeled worksheet history, collect a new eager-order baseline; fresh scans need separate approval
PowerShell request loop failsInvoke-RestMethod -ErrorAction Stop and actual response errorStop immediately; do not count incomplete traffic as six samples
Windows agent jar path failsWarm build result, exact jar, comma in pathStop on missing jar; rebuild or use a supported path, never an empty agent argument
Quarkus Dev Services cannot startDocker/Podman and PostgreSQL prerequisitePrepare Appendix C's container runtime or local PostgreSQL separately
Missing time breakdownFive warm requests and capture coverageWarm/collect; unknown time is not proof of slow business code
Java Agent NOT_ATTACHEDCorrect agent launcher or startup -javaagentFull-stop and attach only at the Chapter 05 boundary
ARMED but sensor unavailableInstalled state and self-tests, packages, release/protocolRead reason; attachment alone does not prove capture
No Code PathInstrumented application bean/method, same run, row/depth limitsExercise the route; explain excluded or assembly-only work
Async work missingExecutors sensor, request identity, waited-for completionUse the exact fixture and allow one second; do not invent correlation
Probe has zero invocationsCorrect descriptor, active state, windowWait active, then send two calls; it stops at 20 invocations/60 seconds
Side Effects emptySensor installed/whole-run coverage, actual triggerAbsence with missing coverage is not a no-effects verdict

Change and comparison

SymptomCheckRecovery
Source saved but unchanged method inventoryRunning clone/classpath, compiler output, DevTools run idCompile the sample; observe actual same-JVM restart
Compiled but no restartChapter 05 trigger-file launch and marker timestampAfter compile/test finishes, touch .workshop-reload in sample target/classes
Changed but not exercisedOriginal route traffic in the new runSend agreed samples and refresh; this state is not a passed fix
Comparison unavailablePrior exercised run, same application/JVM, retained baselineRe-establish a baseline; label a lost comparison incomplete
Comparison points at an idle intermediate runMultiple compile/reload events and run idsRestore the reference query in your disposable clone, exercise, then redo one edit/reload
Side effects not comparableSensor switching, partial capture, configuration driftKeep settings stable; report not compared rather than no effects
Acceptance test initially fails with 17 statementsFailure is query-budget assertion onlyExpected red; apply the approved edit, rerun
Upstream eager fixture test fails after fixTest intentionally expects N+1 behaviorRecord known exercise incompatibility; use positive workshop acceptance, no silent skip
Test passes but live route still slowTest process vs running appVerify live run/method/request; test process is separate
Agent/provider offlineClient auth/network/provider policyPair or use the labeled transcript; mark live agent use incomplete

Restore only your own exercise edits, by reviewing/replacing the small service method. Do not use git reset --hard, discard another person's changes, clear all recordings, or erase a Maven repository as a recovery shortcut.

Return: Workshop overview.

Prev
A - Prompts
Next
C - Frameworks

© 2026 Julien Dubois