[ https://jira.jboss.org/jira/browse/JBAS-7946?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7946: ------------------------------------ http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... is still running but I peeked at the hornetq/log/server.log and saw the same failure (http://pastebin.com/b7sqzSXB). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7946?page=com.atlassian.jira.plug... ] Clebert Suconic commented on JBAS-7946: --------------------------------------- I have spent a lot of time investigating this, and so far I don't see how this could be related to HornetQ. I'm not sure if this is SECURITY-491, but it seems there's some issue with Security for sure. The only way to investigate that IMO would be through load. Someone would need to generate a test that would send a repetitive login requests in multi-thread to the SecurityManager in a way cache would be always evicted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7946?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7946: ------------------------------------ oops, I updated an out of date copy of the jira. I deleted my (invalid) comment that your "15/Apr/10 04:13 PM" is to. Just mentioning in case that causes confusion... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7946?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7946: ------------------------------------ Guessing at this is more fun than debugging, so my guess is an initialization bug that goes undetected. Perhaps in a MC bean that we create specifically for HornetQ (since other components security manager tests are passing). Maybe something like org.hornetq.integration.jboss.security.JBossASSecurityManager and its interaction with the JBoss security manager. I'll hack a multiple iteration single threaded test together locally and see if that shows anything. If my "initialization" theory is right, we might instead need to script together something to launch the AS multiple times in a loop, running the unit test once per launch (or something like that). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7946?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7946: ------------------------------------ Looking at the exception (which occurred on other profiles also), I'm wondering if we are missing a MC bean dependency. Does HornetQ depend on remoting by chance? That appears to be initialized after HornetQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7946?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7946: ------------------------------------ Great question, lets try to figure out if we are missing a dependency on security. Also, I failed to get a multi iteration test going (always failed on the second iteration). Instead, I tried starting two unit tests at the same, from two shell windows. Very low tech multi-threading :) I did a ./build.sh one-test -Dtest=org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase And a /build.sh one-test -Dtest=org.jboss.test.messagedriven.test.JMSContainerInvokerTopicMessageDrivenUnitTestCase Both tests failed. The AS server.log contained the following errors (they continued to repeat but pastebin didn't like me pasting the entire file): http://pastebin.com/BLt62591 Both of these tests pass standalone (just ran them again with the same AS instance without restarting after the previous failure). Perhaps the two tests are walking on each others deployments and causing the java.lang.NoClassDefFoundError: Could not initialize class org.jboss.test.messagedriven.mbeans.TestMessageDrivenManagementMBean. I'll assume that is the case for now and ignore this test result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira