Comprehensive debugging techniques for Guidewire InsuranceSuite including Gosu debugging, Cloud API tracing, log analysis, and performance profiling.
Configure Log4j2 with DEBUG level for gw.custom, gw.plugin, gw.api.rest, gw.api.database, and gw.integration categories. Use rolling file appender with 100 MB size limit.
Use the DebugHelper class for method tracing, entity state dumps, and query profiling. Set breakpoints in IntelliJ and attach to the debug port (5005).
export JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005" # 5005 = configured value
./gradlew runServer
In IntelliJ: Run > Edit Configurations > Remote JVM Debug (localhost:5005).
Add axios interceptors to log request/response details with unique request IDs and Guidewire trace IDs (x-gw-trace-id).
Use Lucene queries in Guidewire Cloud Console Observability > Logs to search for errors by claim number, slow API calls, auth failures, or integration errors.
Profile queries with QueryPlanExplainer to detect full table scans and slow queries exceeding 1 second.
Monitor JVM memory usage and dump thread state when investigating performance issues or deadlocks.
For detailed code implementations (Log4j2 config, Gosu helpers, TypeScript tracing, query analysis), load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Issue | Cause | Solution |
|---|---|---|
| No debug logs | Wrong log level | Set categories to DEBUG |
| Debugger won't attach | Wrong port or firewall | Verify JAVA_OPTS and port |
| Slow query undetected | No profiling | Wrap queries with profileQuery |
| Missing trace IDs | Headers not logged | Add response interceptor |
For rate limiting information, see guidewire-rate-limits.
Basic usage: Apply guidewire debug bundle to a standard project setup with default configuration options.
Advanced scenario: Customize guidewire debug bundle for production environments with multiple constraints and team-specific requirements.