Hi Adrian, Thanks for your reaction.
"[EMAIL PROTECTED]" wrote : "svadu" wrote : | | Can someone give me a clue on the problem (I hope I described the problem more or less accurately)? | | | JMSXDeliveryCount is a property set by the JMS provider (Tibco) not JBoss. | We just use it to determine number of redeliveries when it exists (it is optional). | Considering that GenericDLQHandler doesn't increment it I came to the same conclusion. anonymous wrote : | Perhaps it is a property Tibco doesn't support, but the message originated | in some other system that does set the property. i.e. Tibco just copied it? | Well it's imported from other messaging system (TIBCO specific) which doesn't know about JMSXDeliveryCount. But TIBCO EMS (which performes the import) does support the property. anonymous wrote : | anonymous wrote : | | Do I need to rely (would require even more vendor specific configuration) on the external JMS server (Tibco in this case) to handle redelivery counts? | | | | No idea. But I'd imagine Tibco has internal support for DLQs or | some other poisened message handler?. | Yes in fact it does, but the queue is not configurable (and I like being able to configure DLQ name per queue, for example). anonymous wrote : | So you probably don't need to configure a DLQ handler in JBoss at all? | | * Set the activation-config-property useDLQ=false | * Configure a DLQ (or whatever mechanism they have) for your queue/topic in Tibco. | Not using the DLQ at all might see the most portable option here, I don't like relying on TIBCO's dlq even more... Fortunately, it seemed that the problem was due to very high load in TIBCO EMS (or corrupt data). Anyway I set max delivery to 1 in the MDB so that if the counter is greater 1 (it was 2 in my case) it is delivered to DLQ. It works so far (and for new messages it is increasing for some reason). May be the problem was queue settings (queues can be made synchronized for better thread safety when writing to the file system). Anyway, the problem is, somewhat resolved. anonymous wrote : | The only reason the DLQ handler exists in the MDB is because JBossMQ | doesn't support them internally. Most other JMS providers do support them | inside the server. I hope it stays this way (the generic DLQ support). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130857#4130857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130857 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
