On 2/22/25 17:21, GADIWAN, IRFAN wrote:
Hi,
We are using Apache qpid jms client 0.53.0 and we are seeing
org.apache.qpid.jms.provider.ConservativeProviderFuture.sync() getting called,
even when we are using
The forceAsyncSend property to true. We are using a transacted session and
persistent delivery mode, but using connectionfactory with forceAsyncSend=true.
Is it the correct behavior ?
This is correct, the future is a sync point between the client thread
and the IO thread that manages the AMQP handling and does not have a
direct relation to the async send options, that communication needs to
occur regardless. In the stack trace the client is syncing on a
transaction commit which is a natural sync point for committing a batch
of sends which were sent using async sends as you are.
Below is the stacktrace we are seeing :
acsi.gddn.util.net.components.jms.internal.AbstractJmsComponent.commitTransaction(AbstractJmsComponent.java:718)
acsi.gddn.service.jms.impl.session.JmsSessionWrapperImpl.commit(JmsSessionWrapperImpl.java:249)
acsi.gddn.jms20.Jms20SessionWrapper.commit(Jms20SessionWrapper.java:229)
org.apache.qpid.jms.JmsSession.commit(JmsSession.java:258)
org.apache.qpid.jms.JmsLocalTransactionContext.commit(JmsLocalTransactionContext.java:186)
org.apache.qpid.jms.JmsConnection.commit(JmsConnection.java:847)
org.apache.qpid.jms.provider.ConservativeProviderFuture.sync(ConservativeProviderFuture.java:116)
java.lang.Object.wait(Object.java:502)
java.lang.Object.wait(Native Method)
Thanks,
Irfan Gadiwan.
GDDN DevSecOps
AT&T Services, Inc
Rethink Possible
P: 470 559 3442
--
Tim Bish
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
