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.
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 ?
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