3 Replies Latest reply on Jul 29, 2009 7:22 AM by kaba

    Problems with "management - esb"

    garuda

      Hello experts,

      I get the following exception when trying to deploy management.esb:

      org.jboss.soa.esb.couriers.CourierException: javax.jms.JMSException: There is no administratively defined queue with name:queue/DataFilerQueue
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:360)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:188)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:201)
      at org.jboss.soa.esb.monitoring.client.DataCollectorAction.collectStatistics(DataCollectorAction.java:91)
      at sun.reflect.GeneratedMethodAccessor226.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
      at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
      at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

      I found out that the DataFilerQueue is a queue that is used by the JBoss SOA monitoring console (management - esb). As the monitoring console is installed by default, I wonder why I get this exception during re - deployment. Furthermore I already had a look in management.esb/jbm-queue-service and */META-INF/deployment.xml with result that the DataFilerQueue is defined.

      Can anybody help ?

      Best regards,

      Dennis

        • 1. Re: Problems with
          tfennelly

          Hi Dennis.

          Would need more details. What version of the ESB? How are you deploying - on the AS or ESB Server? If deploying on the AS, what version? Can you check your server log for other errors. Perhaps that queue is failing deployment.

          • 2. Re: Problems with
            garuda

            Hi,

            the problems I had was mainly caused by the management esb console. The queue of this service was overfilled, which caused a Java heap space. The first solution was to restrict the queue size, still I had further problems: tablespace full etc.

            The service writes too much statistics and you can't really configure what should be written (expect the statistic collection interval). So actually you would need to write a service that deletes old statistics, which we did. This can cause performance problems, because of mass data - deletion without good database indexes.

            Finally after weighing disadvantages against advantages of management esb console, I removed it and everything is fine now.

            Is it possible to make the statistic collector of management console more configurable in the future ?

            Best regards,

            Dennis

            • 3. Re: Problems with
              kaba

              I had the same problem some month ago.
              My solution was to remove the management.esb and delete management.esb directory unter deploy all togeher.
              The problem is the database tablespaces are running aout of space very quickly

              the radical solution ist to undeploy the management.esb by simply deleting it