-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
JumpWatch edited this page Apr 23, 2026
·
1 revision
ServerFabric uses internal managed JDKs for builds.
Check:
- template version
- build log file
tools-cache/jdks/
Check:
build-cache/<template>/<version>/buildlog.txt
Make sure the proxy/client status watch logic is working and that the host actually reports the clean exit.
Check protocol changes across:
- client write order
- proxy read order
- response packet structure
Disk usage may be cached on the host side.
This is normal and reduces heavy filesystem walking.
Check:
-
ServerFabricProxyis installed and enabled - the plugin depends on the proxy
- the API is not being shaded into the consumer plugin