• Post Reply Bookmark Topic Watch Topic
  • New Topic

Logback ch.qos.logback.classic.AsyncAppender not working  RSS feed

 
venkata cotra
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In logback configuration ch.qos.logback.classic.AsyncAppender is used with ch.qos.logback.core.FileAppender.All the messages are not flushed out of queue
ch.qos.logback.classic.AsyncAppender class is used java.util.concurrent.ArrayBlockingQueue

Let me know if any one have experience this issue.

 
Campbell Ritchie
Marshal
Posts: 56581
172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I merged your stuff with the following thread. I hope that is okay by you.
 
venkata cotra
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By using logback - ch.qos.logback.classic.net.JMSQueueAppender we are connecting to JMS MQ Server,While logging messaged to queue if it reaches to max threshold lockback is not throwing any error.

Please let me know ,if any one haved faced this issue?
 
Campbell Ritchie
Marshal
Posts: 56581
172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the Ranch

Since those two questions appear to be closely related I have merged them into one discussion.
 
Paul Clapham
Sheriff
Posts: 22835
43
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You said the AsyncAppender was "not working" without saying what that meant. Then you said it was "not throwing any error" if its associated queue got full. When I read the API docs I don't see anything about throwing exceptions. I do see references to the fact that it may discard messages when the queue is full. So, what's the problem? What is happening, and what do you think should be happening instead, and why?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!