-
1. Re: Logging level for
svadu Feb 29, 2008 6:02 AM (in response to svadu)Sorry for bad subject, the forums cut it off...
-
2. Re: Logging level for
adrian.brock Mar 10, 2008 11:17 PM (in response to svadu)You can't use the DLQHandler unless the messages have message ids.
-
3. Re: Logging level for
svadu Mar 11, 2008 5:06 AM (in response to svadu)Hi Adrian,
Thanks for the replying. Yes, I've looked through the code and understand that the DLQ handler must have messages with IDs in order to process them.
However what I have is that messages are not sent to DLQ yet (no rollbacks) and still I get this logging.
The problem is mainly the log file size which grows extremely fast if all messages are logged and the log level for that particular message is 'error'. If I set logging to fatal I will miss error messages which I do want to see...
Is this still working 'by design'? -
4. Re: Logging level for
adrian.brock Mar 21, 2008 12:07 PM (in response to svadu)"svadu" wrote:
Is this still working 'by design'?
No, its not working by design and telling you so. :-)
I don't see why other messages from DLQHandler would be interesting to you
since it can't possibly work as configured. -
5. Re: Logging level for
svadu Mar 21, 2008 5:44 PM (in response to svadu)Hi Adrian,
Thanks for replying again. I am not really interested in messages from DLQHandler, but because of the null id it dumps complete message content in the the log which makes it grow at extreme rates.
I've got a workaround with using JBoss DLQ and null id's by manually resending messages that have to be rolled back to the queue which forces Tibco EMS to assign proper id's (it's just some specifics of importing messages from TIB/RV). It has kind of 'maxResend + 1' effect.
So, after the message is resent and get's ID I would expect that DLQ handler to actually do it's job and it seems to be doing so...
But in my case DLQHandler 'spits' content of JMS messages into the server.log even if there is no rollback (with my current data load the log files reach 10+Gb in a few days). I had to put logging level to FATAL to avoid it but I may miss actually a lot of needed data in the log when the actual rollback happens.
Should I create a JIRA issue for that?