I just did a full build and then deleted and created domain1. I.e.
brand-new domain with no "junk" leftovers in it.
Ran QL tests. MDB tests failed exactly like last night. On WinXP.
Why?
test.mdb.MDBTests:runJMSAppTest
Run appclient against JMS APP failed ... expected:<true> but was:<false>
org.testng.Assert.fail(Assert.java:84)
at org.testng.Assert.failNotEquals(Assert.java:438)
at org.testng.Assert.assertEquals(Assert.java:108)
at org.testng.Assert.assertEquals(Assert.java:239)
at test.mdb.MDBTests.runJMSAppTest(MDBTests.java:80)
23 lines not shown
On 11/12/2010 3:18 PM, Byron Nevins wrote:
> I always create a new domain before running QL. I saw the same MDB
> tests fail with a brand-new build, brand new installation and unused
> brand new domain
>
>
> On 11/12/2010 2:18 PM, Bill Shannon wrote:
>> Yes, there were old resources left behind.
>>
>> Here's what I did...
>>
>> I did a full clean build.
>> I ran quicklook.
>> There were a bunch of errors. Nothing new, quicklook just fails
>> sometimes.
>> I ran quicklook again.
>> I ran quicklook again.
>>
>> I guess the first spurious run of quicklook left behind garbage that the
>> other runs didn't clean up.
>>
>> I hate it that quicklook still fails randomly from time to time,
>> often right after a clean build.
>>
>> Anyway, removing the left over JMS resources allowed quicklook to run
>> successfully.
>>
>> Thanks, Cheng!
>>
>> Cheng Fang wrote on 11/12/10 01:18 PM:
>>> I suspect the jms resources from previous test runs were not
>>> deleted, so the
>>> current test run failed to create as they already exist.
>>>
>>> You can check with "asadmin list-jms-resources"
>>>
>>> On 11/12/10 3:59 PM, Bill Shannon wrote:
>>>> I'm getting pretty tired of updating, building, and running quicklook
>>>> over and over again hoping to get a clean quicklook run so that I can
>>>> start making changes of my own. I've gotten this failure twice in a
>>>> row. Anyone have any idea what it is?
>>>>
>>>> [testng] FAILED: createJMSRscTest("ejb/mdb/create_resources.asadmin")
>>>> [testng] java.lang.AssertionError: Create JMS resource failed ...
>>>> expected:<true> but was:<false>
>>>> [testng] at test.mdb.MDBTests.createJMSRscTest(MDBTests.java:61)
>>>> [testng] ... Removed 26 stack frames
>>>> [testng] SKIPPED: deployJMSAppTest
>>>> [testng] SKIPPED: runJMSAppTest
>>>> [testng] SKIPPED: undeployJMSAppTest
>>>> [testng] SKIPPED: deleteJMSRscTest
>>>> [testng]
>>>> [testng] ===============================================
>>>> [testng] MDB_tests
>>>> [testng] Tests run: 5, Failures: 1, Skips: 4
>>>> [testng] ===============================================
>>>>
>>>>
>>>> Yes, I'm doing a clean build every time. Please don't tell me it's
>>>> time
>>>> to throw away my .m2 again.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188