Skip to content

Load Testing phoss-ap #68

Description

@laithtawabini

Hi, I was wondering if there are any recommendations for configurations / infrastructure to keep in mind / consider when load testing with heavy amounts of Incoming AS4 messages / invoices (looking at 300+ TPS).

What is the recommended approach to load testing. We are looking to load test using 2 instances with the same test certificate, one to send and one to receive + send back MLS (through API Call which handles MLS after forwarding and validation, phoss-ap default MLS sending is disabled), is this a valid approach? Also if any recommendations to track any errors and root causes.

FYI:

currently running on docker image phoss-ap:0.10.4

Configuration

server.forward-headers-strategy=native
spring.application.name=phoss-ap
management.endpoints.web.exposure.include=health,info
management.endpoint.health.probes.enabled=true
peppol.stage=test

org.apache.wss4j.crypto.merlin.keystore.type=pkcs12
org.apache.wss4j.crypto.merlin.truststore.type=pkcs12
org.apache.wss4j.crypto.merlin.truststore.file=truststore/2025/ap-test-truststore.p12
smpclient.truststore.type=pkcs12
smpclient.truststore.path=truststore/2025/smp-test-truststore.p12
smpclient.truststore.password=peppol
phossap.jdbc.database-type=postgresql
phossap.jdbc.driver=org.postgresql.Driver


storage.mode=s3

storage.inbound.path=inbound
storage.outbound.path=outbound


forwarding.mode=http_post_async

phase4.dump.path=/var/phoss-ap/data/phase4-dumps/
peppol.reporting.schedule.enabled=true
startup.recovery.enabled=true
phossap.jdbc.debug.sql=false
phossap.jdbc.debug.transactions=false
phossap.jdbc.debug.connections=false
phase4.send.timeout.connect=30000
phase4.send.timeout.read=180000
phase4.send.duplicate-check.enabled=true
phase4.send.duplicate-check.disposal-ms=600000
mls.sending.enabled=false

Appreciate it.

Metadata

Metadata

Assignees

Labels

questionFurther information is requested

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions