Version 26

    Testsuite errors and possible resolutions

     

    Where in the TS is the test XY run?

    See TestCaseTargetAndServerMapping


    Problem: Most of my tests are failing

     

    Possible cause & solution: You are having port conflicts with someone else. To check this, do something like:

     

    sudo /sbin/lsof -i -P | grep 1099

     

    If you see a process bound to : or to the address you are tyring to bind to, the testsuite will not be able to start JBoss correctly.

     


    Problem: Half of my tests are failing

     

    Possible cause & solution: The embedded HSQL DB might have a stale lock which prevents it from starting. Delete your data directory and try again.

     

    rm -r ../build/output/jboss-/server//data

     


    Problem: JaasSecurityDomainUnitTestCase is failing with a FileNotFoundException

     

    Possible cause & solution: There is a conflict with a previous run causing the JaasSecurityDomainUnitTestCase since the /tmp/tst.password cannot be created due to a permission problem.  Delete /tmp/tst.password

     


    Problem: "Exception creating identity: <hostname>" during startup

    Fix the hostname of the machine.

    Caused by: java.lang.RuntimeException: Exception creating identity: dell-r210-05.mw.lab.eng.brq.redhat.com: dell-r210-05.mw.lab.eng.brq.redhat.com
         at org.jboss.remoting.ident.Identity.get(Identity.java:211)
         at org.jboss.remoting.network.NetworkRegistry.preRegister(NetworkRegistry.java:268)
         at org.jboss.mx.server.AbstractMBeanInvoker.invokePreRegister(AbstractMBeanInvoker.java:966)
         at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:489)
         at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
         at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)
         ... 56 more
    

     


    Problem: All JACC tests fail

    Most probably, you have symlinked JBoss AS directory. JACC security checks fail if some path goes through a symlink.

     


    Problem: SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge

    Message: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge

     

    Possible cause and resolution (JBoss): This has been installed in the QA lab for /opt/j2sdk1.4.2_09

     

    Possible cause and resolution: The SRPLoginModuleUnitTestCase requires that the unlimited strength crypto package be installed:

    java15 java15 java14

     

    Download the zip file from the above location. The standard place for JCE jurisdiction policy JAR files is: $JAVA_HOME\lib\security

     


     

    Problem: JBoss 4.0.2 testsuite fails to run.

     

    Possible cause and resolution:  The jboss-4.0.2-src tarball does not have the file local.properties in the testsuite directory.  You can download it from http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/tags/JBoss_4_0_2/testsuite/local.properties?revision=54874.

     


    Problem: Having difficulties getting the clustering tests to pass:

     

    You have a few options here. Try adding a -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 where the test ips are one of the five (1-5) valid on a lab qa machine.   Also you can force the multicast address to point to a specific address.  -DudpGroup=239... where the are the starts a valid numbers from 1-255.

     

    Also, clustering tests seem to work best on dev04 qa machine which has a newer kernel version.

     

    Also, see TwoClustersSameNetwork

     


    Problem: Clustering tests fail on Windows:

     

    1. Make sure your firewall is disabled

    2. Disable MediaSense

     


    Problem OptimisticLockUnitTestCase fails

     

    Suite:       org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase

    Test:        testBug1006723

    Type:        error

    Exception:   javax.ejb.CreateException

    Message:     Error checking if entity exists:java.sql.SQLException: Column not found: \

    OIDCMP in statement SELECTCOUNTFROMENTITYAWHEREOIDCMP

     

    This test passes intermintently.  Run it a few times.

     

    Workaround: It is needed to stop jboss, delete data directory in server configuration, start server and run the test again.

     


    JBoss AS locks forever when run on a NFS drive

     

    When nfs lockd is not running, hsqldb locks the process. Ask IT to start it or you could remove hsql.jar

    On HP-UX lockd doesn't help. Use local drive (/tmp should be fine).

     


     

    JBoss AS 4.3.x - Classloaders unregistered: WEBAPP EJB3_SLSB

     

    You probably managed to run with JDK 6. Double-check.

     

     

     

     

     

     

     

    Here is a list of known to fail tests on the different versions of the Application Server:

     

    JBOSS 3.2.3

     

    org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase

    org.jboss.test.deadlock.test.BeanStressTestCase

    org.jboss.test.exception.EntityExceptionUnitTestCase

    org.jboss.test.exception.ExceptionUnitTestCase

    org.jboss.test.jmx.test.DeployServiceUnitTestCase

    org.jboss.test.jmx.test.MissingClassUnitTestCase

    org.jboss.test.management.test.JSR77SpecUnitTestCase

    org.jboss.test.naming.test.SecurityUnitTestCase

    org.jboss.test.naming.test.SimpleUnitTestCase

    org.jboss.test.security.test.HttpsUnitTestCase

    org.jboss.test.security.test.SRPUnitTestCase

    org.jboss.test.webservice.external.ExternalUnitTestCase

     

     

    JBOSS 3.2.5

     

    org.jboss.test.cache.test.replicated.AsyncUnitTestCase

    org.jboss.test.classloader.test.ScopingUnitTestCase

    org.jboss.test.management.test.JSR77SpecUnitTestCase

    org.jboss.test.naming.test.SecurityUnitTestCase

    org.jboss.test.naming.test.SimpleUnitTestCase

    org.jboss.test.testbeancluster.test.BeanUnitTestCase

    org.jboss.test.testbeancluster.test.CacheInvalidationUnitTestCase

     

     

    JBOSS 3.2.6

     

    org.jboss.test.classloader.test.ScopingUnitTestCase

    org.jboss.test.cluster.test.WebSessionTestCase

    org.jboss.test.jbossmx.compliance.monitor.BasicTestCase

    org.jboss.test.jbossnet.external.ExternalUnitTestCase

    org.jboss.test.jbossnet.external.RedeployUnitTestCase

    org.jboss.test.naming.test.SecurityUnitTestCase

    org.jboss.test.naming.test.SimpleUnitTestCase

     

    JBOSS 3.2.7

     

    success rate 100%

     

    JBOSS 3.2.8

     

    success rate 100%

     

    JBOSS 4.0.1SP1

     

    org.jboss.test.aop.test.RemotingUnitTestCase

     

    JBOSS 4.0.2

    success rate 100%, some expired security crtificates may cause certain tests to fail

     

    JBOSS 4.0.3

     

    success rate 100%

     

    JBOSS 4.0.3SP1

     

    org.jboss.test.cluster.test.ScopedAttrBasedTestCase(SyncModeNUseJvm-UDP)

     

    Test:        testInvalidate

     

    Suite:       org.jboss.test.testbeancluster.test.BeanUnitTestCase(SyncModeNUseJvm-UDP)

     

    Test:        testStatefulPassivationExpiration

     

    Suite:       org.jboss.test.webservice.secure.noenv.TransportOptionsTestCase

     

    Test:        testWithoutKeystore

     

    Suite:       org.jboss.test.messagedriven.test.SimpleTopicMessageDrivenUnitTestCase

     

    Test:        testSimpleNotSupported, testSimpleDLQ

     

    Suite:       org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC+SecurityMgr)

     

    Test:        testBasicSecuredServiceAccess, testRoleSecuredServiceAccess

     

    Suite:       org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC)

     

    Test:        testBasicSecuredServiceAccess, testRoleSecuredServiceAccess

     

    Suite:       org.jboss.test.webservice.ws4eesimple.ClientStubTestCase

     

    Test:        testClientStub