Hi Nigel,
Thanks for your help :)
I've executed the command on imq broker and for my surprise it says that no
durable subscription were found. I'm using the follow activation property on
my MDB's:
MessageDriven(name="xyz", mappedName="jms/xyz", activationConfig=
{
@ActivationConfigProperty(
propertyName="Durability",
propertyValue="Durable")
}
)
The corret for property name isn't that? I've see some examples using '
subscriptionDurability' as propertyName so now I'm confuse.
To create the topics/queues I'm using the follow entries on my domain.xml:
<admin-object-resource enabled="true"
jndi-name="jms/NPMessageReceiverTopic" object-type="user"
res-adapter="jmsra" res-type="javax.jms.Topic">
<property name="Name" value="NPMessageReceiverTopic" />
</admin-object-resource>
<admin-object-resource enabled="true"
jndi-name="jms/NPMessageReplyQueue" object-type="user"
res-adapter="jmsra"
res-type="javax.jms.Queue">
<property name="Name" value="NPMessageReplyQueue" />
</admin-object-resource>
<admin-object-resource enabled="true"
jndi-name="jms/NPAlarmHandlerQueue" object-type="user"
res-adapter="jmsra"
res-type="javax.jms.Queue">
<property name="Name" value="NPAlarmHandlerQueue" />
</admin-object-resource>
<admin-object-resource enabled="true"
jndi-name="jms/NPAlarmNotifierTopic" object-type="user"
res-adapter="jmsra"
res-type="javax.jms.Topic">
<property name="Name" value="NPAlarmNotifierTopic" />
</admin-object-resource>
<admin-object-resource enabled="true"
jndi-name="jms/NPEventChannelTopic" object-type="user"
res-adapter="jmsra"
res-type="javax.jms.Topic">
<property name="Name" value="NPEventChannelTopic" />
</admin-object-resource>
<connector-resource enabled="true"
jndi-name="jms/NPMessageReceiverConnectionFactory"
object-type="user"
pool-name="jms/NPMessageReceiverConnectionFactory" />
<connector-resource enabled="true"
jndi-name="jms/NPMessageReplyConnectionFactory"
object-type="user"
pool-name="jms/NPMessageReplyConnectionFactory" />
<connector-resource enabled="true"
jndi-name="jms/NPAlarmHandlerConnectionFactory"
object-type="user"
pool-name="jms/NPAlarmHandlerConnectionFactory" />
<connector-resource enabled="true"
jndi-name="jms/NPAlarmNotifierConnectionFactory"
object-type="user"
pool-name="jms/NPAlarmNotifierConnectionFactory" />
<connector-resource enabled="true"
jndi-name="jms/NPEventChannelConnectionFactory"
object-type="user"
pool-name="jms/NPEventChannelConnectionFactory" />
Could this problem (not persisting messages on broker) be related to my main
problem? (consumers not be calling).
Thanks.
On 10/8/09 6:51 AM, "Nigel Deakin" <Nigel.Deakin_at_Sun.COM> wrote:
> Paulo,
>
> Paulo Cesar Reis wrote:
>> Hi Niege,
>>
>> More information for you, when messages are received the jMS print the
>> configurations for that messages so maybe it can help:
>>
>> [MessageReceiverBean] :: Message (
>> Class: com.sun.messaging.jmq.jmsclient.MessageImpl
>> getJMSMessageID():
>> ID:4140-10.1.1.20(eb:b1:29:0:c8:2d)-55764-1254929259059
>> getJMSTimestamp(): 1254929259059
>> getJMSCorrelationID(): null
>> JMSReplyTo: null
>> JMSDestination: NPMessageReceiverTopic
>> getJMSDeliveryMode(): PERSISTENT
>> getJMSRedelivered(): false
>> getJMSType(): null
>> getJMSExpiration(): 0
>> getJMSPriority(): 4
>> Properties: {my message confidential data}) was sent successful via
>> JMS. Others middle-ware applications should care about the next steps...
>> |#]
>>
>> After that nothin' happens, no consumers called. Why the messages aren't
>> available after restart? The imq is not saving them.
>
> Let's double-check you really do have a durable subscription. Run
>
> imqcmd list dur
>
> to check.
>
>