Q1 : you can have a look at JBossMessage class.
Q2 : If a message is failed to be delivered by JBM for a certain times, it will
go to DLQ if specified.
Q3 : no. I don't think you need it if your messages never expire.
Q4 : see Q2 for reference.
View the original post :
Thanks gaohoward. I still need some explanations:
Q1: Is there a configurable way to define default message headers from JBoss?
Q2: How do you define 'delivery'? Is it delivery between internal components
of JBoss? Or is it delivery between external clients and JBoss?
View the original
Q1: Is there a configurable way to define default message headers from JBoss?
--- I don't think it has a way to configure default values for message headers.
Q2: How do you define 'delivery'? Is it delivery between internal components of
JBoss? Or is it delivery between external clients and
gaohoward wrote : Q1: Is there a configurable way to define default message
headers from JBoss?
|
| --- I don't think it has a way to configure default values for message
headers.
|
|
Actually you can probably do this by providing an AOP interceptor in JBM 1.x.
In JBM 2.0
Another question:
I'm using a JMS client to drop messages in JBM 1.4. Although the client is
changing the message header properties (expiry and priority), these changes are
not taking effects on JBM. For example, the client is setting the message
expiry to 1 second but JBM is keeping the
Hi, I think about those values you should consult JMS spec. Some of them are
determined only when the message is sent. for example in the spec
anonymous wrote :
| JMSPriority
| The JMSPriority header field contains the messageâs priority.
| When a message is sent, this field is
You're right gaohoward. The priority should be set at the method level (send
method) rather than at the message level. But I still can't control the expiry
of the message even from the send() method. I will review the specs as you
suggested. Thanks.
View the original post :
