JRS 10.0.0 Docker: cannot save JDBC Data Source, REST returns mandatory.parameter.error "resource body" missing

[ErClode]

Environment:

• Repository: TIBCOSoftware/js-docker
• JasperReports Server: 10.0.0 PRO
• Docker deployment using jaspersoft-containers/Docker/jrs
• Webapp image: jasperserver-webapp:10.0.0
• Buildomatic image: jasperserver-buildomatic:10.0.0
• PostgreSQL repository: postgres:12
• Tomcat base image from .env: tomcat:10.1.43-jdk17-temurin
• JDK base image from .env: eclipse-temurin:17-jdk-noble

Issue:
Saving a JDBC Data Source fails with HTTP 400.

The JDBC connection test works correctly from the UI, but when saving the Data Source, the request fails with:

{
"message": "The mandatory parameter "resource body" is missing.",
"errorCode": "mandatory.parameter.error",
"parameters": [
"resource body"
],
"properties": [
{
"key": "propertyPath",
"value": "resource body"
}
]
}

Reproduction:

1. Deploy a clean JasperReports Server 10.0.0 Docker environment using js-docker.
2. Use a clean PostgreSQL repository volume, no migration/import from older Jasper versions.
3. Login as superuser/superuser.
4. Create a new JDBC Data Source from the UI.
5. Use the internal PostgreSQL repository database:
   • Driver: PostgreSQL (org.postgresql.Driver)
   • Host: repository
   • Port: 5432
   • Database: jasperserver
   • URL: jdbc:postgresql://repository:5432/jasperserver
   • Username: postgres
   • Password: postgres
6. Click "Test Connection": connection succeeds.
7. Click "Save": save fails with HTTP 400 and mandatory.parameter.error "resource body" missing.

REST reproduction:
Creating a folder via REST works:

PUT /jasperserver-pro/rest_v2/resources/public/Rest_Folder_Test
Content-Type: application/repository.folder+json

Result: HTTP 201

Creating a JDBC Data Source via REST fails:

PUT /jasperserver-pro/rest_v2/resources/public/PG_Repo_DS_Clean_Test?createFolders=false&overwrite=true
Content-Type: application/repository.jdbcDataSource+json
Accept: application/repository.jdbcDataSource+json

Body:
{
"label": "PG_Repo_DS_Clean_Test",
"uri": "/public/PG_Repo_DS_Clean_Test",
"driverClass": "org.postgresql.Driver",
"username": "postgres",
"password": "postgres",
"connectionUrl": "jdbc:postgresql://repository:5432/jasperserver",
"timezone": ""
}

Result:
HTTP 400

{
"message": "The mandatory parameter "resource body" is missing.",
"errorCode": "mandatory.parameter.error",
"parameters": [
"resource body"
],
"properties": [
{
"key": "propertyPath",
"value": "resource body"
}
]
}

Additional tests:

• Same issue happens in a custom image and in a clean vanilla image.
• Same issue happens with a clean repository, without importing content from JasperReports Server 7.
• Same issue happens with SQL Server and PostgreSQL JDBC Data Sources.
• GET of existing JDBC Data Sources works.
• Test connection works.
• PUT folder works.
• PUT JDBC Data Source fails.
• Using Content-Type: application/json saves a generic JSON file resource, not a JDBC Data Source, so it is not a valid workaround.

Expected behavior:
A JDBC Data Source should be saved as a repository jdbcDataSource resource.

Actual behavior:
Saving fails with HTTP 400 and "resource body" missing.

I also reproduced the issue from the clean UI:

• Login: superuser/superuser
• Create JDBC Data Source under /public
• PostgreSQL driver: org.postgresql.Driver
• Host: repository
• Port: 5432
• Database: jasperserver
• Test Connection: successful
• Save: fails with HTTP 400

Network response:

{
"message": "The mandatory parameter "resource body" is missing.",
"errorCode": "mandatory.parameter.error",
"parameters": [
"resource body"
],
"properties": [
{
"key": "propertyPath",
"value": "resource body"
}

]
}

[pravallikavadd]

Thanks for reaching out. We were unable to reproduce the issue on our side. We tested saving the JDBC Data Source successfully through the UI and also verified the same using the REST API where the PUT request completed successfully and the data source was saved without issues.

REST API tested:

PUT http://localhost:8080/jasperserver-pro/rest_v2/resources/public/PG_Repo_DS_Clean_Test?createFolders=false&overwrite=true&expanded=false&dry-run=false
Content-Type: application/repository.jdbcDataSource+json
Accept: application/repository.jdbcDataSource+json

{ "label": "PG_Repo_DS_Clean_Test", "uri": "/public/PG_Repo_DS_Clean_Test", "driverClass": "org.postgresql.Driver", "username": "postgres", "password": "postgres", "connectionUrl": "jdbc:postgresql://repository:5432/jasperserver", "timezone": "" }

Could you please check once in your environment for any file permission-related issues or recent container/Dockerfile changes related to user/ownership/permissions? Also, please try with a fresh setup after cleaning the existing configuration/resources and verify if the issue still persists.

[ErClode]

@pravallikavadd
Thanks.

I repeated the test from a completely fresh clone to avoid any ambiguity from my previous working tree.

Fresh reproduction environment:

• Fresh clone of https://github.com/TIBCOSoftware/js-docker.git
• Commit: 776501a
• Fresh image names:
  • jasperserver-webapp-fresh:10.0.0-fresh
  • jasperserver-buildomatic-fresh:10.0.0-fresh
• Fresh Docker Compose project: jrs_fresh
• Fresh PostgreSQL volume: jrs-fresh-repository-vol
• Repository initialized again with buildomatic
• No docker-compose.override.yml from my previous tests
• No Dockerfile.cami
• No custom JAR mounts
• No import from JasperReports Server 7
• No reused previous webapp/buildomatic image

The only functional configuration changes made for the Docker Compose test were:

• dbHost=repository
• scalableQueryEngine.enabled=false
• different host ports and volume name to avoid conflicts with the previous test environment

Buildomatic completed successfully:

BUILD SUCCESSFUL
Total time: 7 minutes 44 seconds

I then retried the same REST call:

PUT http://localhost:28080/jasperserver-pro/rest_v2/resources/public/PG_Repo_DS_Fresh_Test_Exact?createFolders=false&overwrite=true&expanded=false&dry-run=false

Headers:

Content-Type: application/repository.jdbcDataSource+json
Accept: application/repository.jdbcDataSource+json

Body:

{
"label": "PG_Repo_DS_Fresh_Test_Exact",
"uri": "/public/PG_Repo_DS_Fresh_Test_Exact",
"driverClass": "org.postgresql.Driver",
"username": "postgres",
"password": "postgres",
"connectionUrl": "jdbc:postgresql://repository:5432/jasperserver",
"timezone": ""
}

Result:

HTTP/1.1 400

{
"message": "The mandatory parameter "resource body" is missing.",
"errorCode": "mandatory.parameter.error",
"parameters": [
"resource body"
],
"properties": [
{
"key": "propertyPath",
"value": "resource body"
}
]
}

So the issue is still reproducible from a completely fresh clone, with fresh images and a fresh repository volume.

Could you please confirm:

1. the exact js-docker commit used on your side;
2. the exact JasperReports Server 10.0.0 installer/build used;
3. whether any additional configuration files differ from the repository defaults;
4. whether you also changed dbHost to repository for Docker Compose?

another information

Client: Docker Engine - Community
Version: 29.4.1
API version: 1.54
Go version: go1.26.2
Git commit: 055a478
Built: Mon Apr 20 16:32:37 2026
OS/Arch: linux/amd64
Context: default
permission denied while trying to connect to the docker API at unix:///var/run/docker.sock
Docker Compose version v5.1.3
Linux ubuntu24protest 6.17.0-20-generic #20~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 19 01:28:37 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble