I can't because it is an jboss-as-arquillian2-container-managed test
that is failing. Now I have been able to hold the test framework from
exiting by putting it in the debugger, so perhaps I can look through the
other vms when this happens.
On 5/23/11 10:54 AM, Jason T. Greene wrote:
On 5/23/11 12:49 PM, Scott Stark wrote:
> I have caused a circularity somewhere, but the log does not contain what
> the associated dependency graph is. This is during the boot of the
> server so I can't go into jmx and look at things. Is there a way to get
> more information on this in the log? Setting everything to trace level
> in the logging.properties is not adding anything about the error.
You should still be able to attach jconsole to the server via a direct
process attach. From there using the jboss.msc mbeans you should be able
to get a direct dep list.