Keeping a message audit trail
Hi all. We're planning to use the Sun JMS Broker -- as long as we get a few reliability issues sorted -- as our primary JMS provider. And we'd like to keep an audit trail of messages passing through the broker.
Background: we use MQ Series for a bunch of stuff; messages passing through MQ are logged to a "history database" by turning them into BLOBs and storing them in a purpose-built table (in an Oracle DB). We have a browser program which shows both current (unconsumed) messages and historical messages. Very useful for support, very useful when users blame middleware for losing messages.
So, we'd like to do the same with Sun JMS. Does anyone do something similar? If so, how? We've had problems with triggers and LONG RAW columns and such so if anyone is already doing this, I'm most interested to find out how. If you can tell me :-)
