Urgent Issue : Error 500 Fixing - Java Expert Required ($2000) -- 2
Budget: $1,500 – $3,000 USD
We’re looking for an experienced Java backend engineer (Jetty 9 + Jersey) who can quickly diagnose and fix a 500 error on a large JSON PUT request in our production app. Ideal candidate is full-stack and can also make small UI tweaks. This is an immediate need with potential for ongoing support.
Our Stack
Reverse proxy: Nginx
App server: Jetty 9 (Jersey/JAX-RS, Jackson)
Database: PostgreSQL
Frontend: Angular (modern), vanilla JS
Auth: Bearer tokens
Infra: Linux
The Problem (condensed)
A ~125 KB JSON PUT to our configs endpoint is returning an upstream 500 from Jetty. Nginx shows:
PUT /projects/configs/314 ... - 500
req_len=124890 rt=0.400 upstream=127.0.0.1:8080 us=500 urt=0.401
(referrer https://geome-db.org, token redacted)
We need root-cause + fix (likely schema/validation/exception mapping). Also want better error handling (return 4xx for validation/size issues) and request/response logging to avoid silent 500s.
The codebase is publicly available at https://github.com/biocodellc/geome-db
What You’ll Do (Deliverables)
Reproduce & diagnose the 500 (add targeted logging if needed).
Implement the fix, which may include:
Adjusting JSON body handling (Jersey/Jackson), request filters, or Jetty limits (if applicable).
Adding ExceptionMapper(s) so invalid/oversized payloads return non 500 error code
Enabling Jersey LoggingFeature (bounded body size) for clear server logs.
Give a PR with changes that fix the issue.
Verification:
Provide curl/Postman steps and a short README of what changed.
Add a lightweight integration test if feasible.
(Nice to have) Minor UI adjustments in Angular (e.g., friendlier error messages for large payloads).
Must-Have Qualifications
5+ years with Java; deep experience with Jetty 9 and Jersey/JAX-RS.
Comfortable with Jackson, request filters, providers, and ExceptionMapper patterns.
Strong PostgreSQL skills (schema design, constraints, JSON/JSONB).
Familiarity with Nginx proxying and upstream diagnostics.
Solid debugging chops; can deliver quickly with minimal hand-holding.
Nice-to-Haves
Angular experience for small UI changes.
Experience hardening APIs (rate limits, structured logging, correlation IDs).
CI/test familiarity to add a simple failing test and make it pass.
Engagement
Start: ASAP (today/this week)
Fixed-price for the immediate fix: $2,000–$2,500, depending on scope after first diagnostic.
Ongoing support: small monthly retainer or hourly as needed.
How to Apply (please include)
A one-paragraph summary of similar Jetty/Jersey issues you’ve solved.
A brief note on how you’d triage this (tools/logging/config you’d add first).
Your availability in the next 48 hours and preferred engagement (hourly/fixed).
Links to relevant repos or code snippets (ExceptionMapper, Jersey logging, JSONB migrations).
Our Stack
Reverse proxy: Nginx
App server: Jetty 9 (Jersey/JAX-RS, Jackson)
Database: PostgreSQL
Frontend: Angular (modern), vanilla JS
Auth: Bearer tokens
Infra: Linux
The Problem (condensed)
A ~125 KB JSON PUT to our configs endpoint is returning an upstream 500 from Jetty. Nginx shows:
PUT /projects/configs/314 ... - 500
req_len=124890 rt=0.400 upstream=127.0.0.1:8080 us=500 urt=0.401
(referrer https://geome-db.org, token redacted)
We need root-cause + fix (likely schema/validation/exception mapping). Also want better error handling (return 4xx for validation/size issues) and request/response logging to avoid silent 500s.
The codebase is publicly available at https://github.com/biocodellc/geome-db
What You’ll Do (Deliverables)
Reproduce & diagnose the 500 (add targeted logging if needed).
Implement the fix, which may include:
Adjusting JSON body handling (Jersey/Jackson), request filters, or Jetty limits (if applicable).
Adding ExceptionMapper(s) so invalid/oversized payloads return non 500 error code
Enabling Jersey LoggingFeature (bounded body size) for clear server logs.
Give a PR with changes that fix the issue.
Verification:
Provide curl/Postman steps and a short README of what changed.
Add a lightweight integration test if feasible.
(Nice to have) Minor UI adjustments in Angular (e.g., friendlier error messages for large payloads).
Must-Have Qualifications
5+ years with Java; deep experience with Jetty 9 and Jersey/JAX-RS.
Comfortable with Jackson, request filters, providers, and ExceptionMapper patterns.
Strong PostgreSQL skills (schema design, constraints, JSON/JSONB).
Familiarity with Nginx proxying and upstream diagnostics.
Solid debugging chops; can deliver quickly with minimal hand-holding.
Nice-to-Haves
Angular experience for small UI changes.
Experience hardening APIs (rate limits, structured logging, correlation IDs).
CI/test familiarity to add a simple failing test and make it pass.
Engagement
Start: ASAP (today/this week)
Fixed-price for the immediate fix: $2,000–$2,500, depending on scope after first diagnostic.
Ongoing support: small monthly retainer or hourly as needed.
How to Apply (please include)
A one-paragraph summary of similar Jetty/Jersey issues you’ve solved.
A brief note on how you’d triage this (tools/logging/config you’d add first).
Your availability in the next 48 hours and preferred engagement (hourly/fixed).
Links to relevant repos or code snippets (ExceptionMapper, Jersey logging, JSONB migrations).
Related categories:
Business, Accounting, Human Resources & Legal
JavaScript
Linux
Nginx
Node.js
PostgreSQL
JSON
Angular