[jboss-jira] [JBoss JIRA] Updated: (JBAS-4637) Fix org.jboss.test.messaging.* tests

Shelly McGowan (JIRA) jira-events at lists.jboss.org
Mon Dec 3 22:02:51 EST 2007


     [ http://jira.jboss.com/jira/browse/JBAS-4637?page=all ]

Shelly McGowan updated JBAS-4637:
---------------------------------


Looking at the test failures in Hudson for org.jboss.test.jbossmessaging.ra. are all passing for me locally.    The issue that is seen during the Hudson runs are that deployment fails due to:
java.lang.IllegalStateException: Cannot set paging params when active
I am unable to get much system information/server.log from Hudson when these errors were encountered but it seems that there may be some issues with paging/swapping during a full test run or insufficiently configured for such?

one-test:
    [junit] Running org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.418 sec
    
   [junit] Running org.jboss.test.jbossmessaging.ra.RaQueueUnitTestCase
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 24.29 sec

    [junit] Running org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.392 sec

    [junit] Running org.jboss.test.jbossmessaging.ra.RaTopicUnitTestCase
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 6.861 sec


The test failures  in: org.jboss.test.jmsra.test.Ra*UnitTestCase are reproducable in my local environment and will investigate further:

javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
	at javax.naming.InitialContext.lookup(InitialContext.java:351)


> Fix org.jboss.test.messaging.* tests
> ------------------------------------
>
>                 Key: JBAS-4637
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4637
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-sun-1.5/20070825220010/results/index.html
> The failing messaging tests need to be looked-up and further qualified or fixed. The failures are not necessarily messaging related:
> SecurityUnitTestCase 30 0 9 21.235 
> SecurityUnitTestCase(tests-jbossmessaging) 30 0 10 33.938 
> SessionCloseStressTestCase(tests-standard-stress) 1 1 0 0.000 
> UnackedUnitTestCase

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list