Hi,
I use JMS inside J2EE via a message-driven bean in a container-managed transaction. I use Borland Enterprise Server 5.0.1 that uses the SonicMQ JMS implementation.
Now I came across the following problem: When the transaction is set to rollback-only in the onMessage() function, SonicMQ immediately re-delivers the message to the bean again. How can I configure the system that re-delivering occurs in say 5 minutes and not immediately?
I can only think of three places where to configure this: 1) general param in container, 2) somewhere in the <message-driven> part of the deployment, or 3) in the JMS provider (SonicQ).
Thank's in advance for your help!
I use JMS inside J2EE via a message-driven bean in a container-managed transaction. I use Borland Enterprise Server 5.0.1 that uses the SonicMQ JMS implementation.
Now I came across the following problem: When the transaction is set to rollback-only in the onMessage() function, SonicMQ immediately re-delivers the message to the bean again. How can I configure the system that re-delivering occurs in say 5 minutes and not immediately?
I can only think of three places where to configure this: 1) general param in container, 2) somewhere in the <message-driven> part of the deployment, or 3) in the JMS provider (SonicQ).
Thank's in advance for your help!