mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; Performance Tools 389 The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

mean, there's an initial WARN log that shouldn't be ignored: It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its are blocked ? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

Enable confirmationWindowSize to receive acks from server! It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its threads are blocked? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically

Enable confirmationWindowSize to receive acks from server! It shows two things: 1. the load generator uses async message producers 2. confirmationWindowSize is an Artemis CORE protocol specific setting; producer(s) to consumer(s) The perf commands uses JMS 2 async message producers that allow the load generator to accumulate in-flight sent messages and depending on the protocol implementation, may block its threads are blocked? Although the load back-pressure mechanism is non-blocking, given that the load generator cannot push further load while back-pressured by the protocol client, the load is semantically