1 Reply Latest reply on Jun 14, 2011 3:36 PM by Christian Sadilek

    Continuous Error Message in the server.log

    Swarn Dhaliwal Newbie

      I was running asyncdemo example which is shipped as part of the

      errai-1.2.2.FINAL distribution.

       

      While invoking the demo application, everything seems to work fine until the browser is up and running. However, if the browser window is closed without stopping all the tasks started by the browser session, the following error is continuously being printed in the server.log.

       

      2011-06-13 15:41:02,426 ERROR [STDERR] (Dispatch Worker Thread) org.jboss.errai.bus.server.QueueUnavailableException: no queue available to send. (queue or session may have expired)

      2011-06-13 15:41:02,427 ERROR [STDERR] (Dispatch Worker Thread)           at org.jboss.errai.bus.server.ServerMessageBusImpl.getQueueByMessage(ServerMessageBusImpl.java:822)

      2011-06-13 15:41:02,427 ERROR [STDERR] (Dispatch Worker Thread)           at org.jboss.errai.bus.server.ServerMessageBusImpl.send(ServerMessageBusImpl.java:380)

      2011-06-13 15:41:02,428 ERROR [STDERR] (Dispatch Worker Thread)           at org.jboss.errai.bus.server.Worker.deliverToBus(Worker.java:139)

      2011-06-13 15:41:02,429 ERROR [STDERR] (Dispatch Worker Thread)           at org.jboss.errai.bus.server.Worker.run(Worker.java:109)

       

      Is this the intended behaviour or is the error message should stop at some point.  Otherwise it keeps filling up the server log and no other messages can be seen.

       

      May be I am missing some configuration setting?

       

      In addition, when I opened multiple tabs in the browser window (Google Chrome), the following message began to apper the the log.

       

      16:08:20,719 INFO  [STDOUT] New task started: Task0

      16:08:21,557 INFO  [STDOUT] New task started: Task1

      16:08:22,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:23,558 INFO  [STDOUT] New task started: Task2

      16:08:23,594 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:24,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:25,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:26,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:27,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:28,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:28,600 ERROR [STDERR] [Warning: A queue has become saturated and performance is now being degraded.]

      16:08:29,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:30,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:31,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:32,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:33,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:34,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:35,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:36,595 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:37,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:38,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:39,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:40,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:41,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:42,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:43,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:44,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:45,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:46,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:47,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:48,596 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:49,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:50,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:51,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:52,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:52,604 ERROR [STDERR] [Warning: A queue has become saturated and performance is now being degraded.]

      16:08:53,597 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:54,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:55,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:56,599 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:56,604 ERROR [STDERR] [Warning: A queue has become saturated and performance is now being degraded.]

      16:08:57,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:08:58,598 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:29,243 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:29,291 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:29,300 INFO  [STDOUT] Error : too many undelievered messages in queue: cannot dispatch message.

      16:10:29,307 INFO  [STDOUT] Error : too many undelievered messages in queue: cannot dispatch message.

      16:10:29,308 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:29,310 ERROR [STDERR] [Warning: A queue has become saturated and performance is now being degraded.]

      16:10:29,314 ERROR [STDERR] [Warning: A queue has become saturated and performance is now being degraded.]

      16:10:29,607 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:30,608 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:31,607 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:32,608 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:33,607 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

      16:10:34,607 INFO  [STDOUT] WARN [JBossCometServlet] No active events to resume with

       

      These messages are continously being printed.

       

      Regards,

      Swarn

        • 1. Re: Continuous Error Message in the server.log
          Christian Sadilek Master

          Well, this is the intended behaviour if no error handling is specified. Asyncdemo calls .noErrorHandling (AsyncService:57) which is why these exceptions are uncatched and end up in your server.log. To avoid this behaviour, register an error handler using .errorsHandledBy and decide what to do. You could stop producing messages if no client is connected or just log an info message instead etc.