Right, that is what I would like to understand. I know this can be fixed by updating the ds.xml config, but wanted to find out why the failure is not consistent. The current JBM version in jbossas trunk is 1.4.1.CR1 Ales Justin wrote: > > Workaround is simple just add the correct config to the file. > > What is the correct config? :-) > Or why it works on Fedora9, but not on OSX and Winz? > > Tim Fox wrote: >> This was a bug in the default HSQL config. I believe Clebert fixed >> it some time back - I'm not sure what version you are using? >> >> Sorry - didn't see this thread since don't read all of dev list. >> >> We don't test against HSQL since we don't support it (it doesn't >> have transactions etc). >> >> Apparently this one slipped through EAP testing too. >> >> Workaround is simple just add the correct config to the file. >> >> Ales Justin wrote: >> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Yeah, this also makes smoke-tests pass on my Winz box. Scott Stark wrote: > Attached is an example > all/deploy/messaging/hsqldb-persistence-service.xml that allows the > all config to startup and the smoke-tests pass on my osx system. > > Scott Stark wrote: >> Right, that is what I would like to understand. I know this can be >> fixed by updating the ds.xml config, but wanted to find out why the >> failure is not consistent. The current JBM version in jbossas trunk >> is 1.4.1.CR1 >> >> Ales Justin wrote: >>> > Workaround is simple just add the correct config to the file. >>> >>> What is the correct config? :-) >>> Or why it works on Fedora9, but not on OSX and Winz? >>> >>> Tim Fox wrote: >>>> This was a bug in the default HSQL config. I believe Clebert fixed >>>> it some time back - I'm not sure what version you are using? >>>> >>>> Sorry - didn't see this thread since don't read all of dev list. >>>> >>>> We don't test against HSQL since we don't support it (it doesn't >>>> have transactions etc). >>>> >>>> Apparently this one slipped through EAP testing too. >>>> >>>> Workaround is simple just add the correct config to the file. >>>> >>>> Ales Justin wrote: >>>> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development >

> Maybe what you're seeing is just old caching of the JAR at your system? What exactly should I nuke to see the results/effect? Since I don't wanna nuke my whole Maven repo ... > Ales Justin wrote: >> Yeah, this also makes smoke-tests pass on my Winz box. >> >> Scott Stark wrote: >>> Attached is an example >>> all/deploy/messaging/hsqldb-persistence-service.xml that allows the >>> all config to startup and the smoke-tests pass on my osx system. >>> >>> Scott Stark wrote: >>>> Right, that is what I would like to understand. I know this can be >>>> fixed by updating the ds.xml config, but wanted to find out why the >>>> failure is not consistent. The current JBM version in jbossas trunk >>>> is 1.4.1.CR1 >>>> >>>> Ales Justin wrote: >>>>> > Workaround is simple just add the correct config to the file. >>>>> >>>>> What is the correct config? :-) >>>>> Or why it works on Fedora9, but not on OSX and Winz? >>>>> >>>>> Tim Fox wrote: >>>>>> This was a bug in the default HSQL config. I believe Clebert >>>>>> fixed it some time back - I'm not sure what version you are using? >>>>>> >>>>>> Sorry - didn't see this thread since don't read all of dev list. >>>>>> >>>>>> We don't test against HSQL since we don't support it (it doesn't >>>>>> have transactions etc). >>>>>> >>>>>> Apparently this one slipped through EAP testing too. >>>>>> >>>>>> Workaround is simple just add the correct config to the file. >>>>>> >>>>>> Ales Justin wrote: >>>>>> >>>> >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> > > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I've tried to compile trunk to validate this.. and I get this: compile-classes: [javac] Compiling 5 source files to /work/projects/jboss5/cluster/output/classes /work/projects/jboss5/cluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.java:811: type java.rmi.MarshalledObject does not take parameters MarshalledObject<Naming> replyStub = new MarshalledObject<Naming>(DetachedHANamingService.this.stub); ^ /work/projects/jboss5/cluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.java:811: type java.rmi.MarshalledObject does not take parameters MarshalledObject<Naming> replyStub = new MarshalledObject<Naming>(DetachedHANamingService.this.stub); I had a fresh checkout.. fresh Maven... Any ideas? /work/projects/jboss5$ svn info Path: . URL: https://svn.jboss.org/repos/jbossas/trunk Repository Root: https://svn.jboss.org/repos/jbossas Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1 Revision: 74705 Node Kind: directory Schedule: normal Last Changed Author: alesj Last Changed Rev: 74700 Last Changed Date: 2008-06-17 11:05:19 -0500 (Tue, 17 Jun 2008) Ales Justin wrote: >> Maybe what you're seeing is just old caching of the JAR at your system? > > What exactly should I nuke to see the results/effect? > Since I don't wanna nuke my whole Maven repo ... > >> Ales Justin wrote: >>> Yeah, this also makes smoke-tests pass on my Winz box. >>> >>> Scott Stark wrote: >>>> Attached is an example >>>> all/deploy/messaging/hsqldb-persistence-service.xml that allows the >>>> all config to startup and the smoke-tests pass on my osx system. >>>> >>>> Scott Stark wrote: >>>>> Right, that is what I would like to understand. I know this can be >>>>> fixed by updating the ds.xml config, but wanted to find out why >>>>> the failure is not consistent. The current JBM version in jbossas >>>>> trunk is 1.4.1.CR1 >>>>> >>>>> Ales Justin wrote: >>>>>> > Workaround is simple just add the correct config to the file. >>>>>> >>>>>> What is the correct config? :-) >>>>>> Or why it works on Fedora9, but not on OSX and Winz? >>>>>> >>>>>> Tim Fox wrote: >>>>>>> This was a bug in the default HSQL config. I believe Clebert >>>>>>> fixed it some time back - I'm not sure what version you are using? >>>>>>> >>>>>>> Sorry - didn't see this thread since don't read all of dev list. >>>>>>> >>>>>>> We don't test against HSQL since we don't support it (it doesn't >>>>>>> have transactions etc). >>>>>>> >>>>>>> Apparently this one slipped through EAP testing too. >>>>>>> >>>>>>> Workaround is simple just add the correct config to the file. >>>>>>> >>>>>>> Ales Justin wrote: >>>>>>> >>>>>

That's because Paul broke the build. I reverted the change (do an update in cluster dir). Anil Saldhana wrote: > For one of my workspaces, I was getting this "type XXX does not take > parameters " issue using the mvn release plugin (but mvn clean install > would go fine). > > You have to look at the dependencies and fix them accordingly. > > Clebert Suconic wrote: >> I've tried to compile trunk to validate this.. >> >> and I get this: >> >> compile-classes: >> [javac] Compiling 5 source files to >> /work/projects/jboss5/cluster/output/classes >> /work/projects/jboss5/cluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.java:811: >> type java.rmi.MarshalledObject does not take parameters >> MarshalledObject<Naming> replyStub = new >> MarshalledObject<Naming>(DetachedHANamingService.this.stub); >> ^ >> /work/projects/jboss5/cluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.java:811: >> type java.rmi.MarshalledObject does not take parameters >> MarshalledObject<Naming> replyStub = new >> MarshalledObject<Naming>(DetachedHANamingService.this.stub); >> >> >> >> I had a fresh checkout.. fresh Maven... >> >> >> Any ideas? >> >> >> /work/projects/jboss5$ svn info >> Path: . >> URL: https://svn.jboss.org/repos/jbossas/trunk >> Repository Root: https://svn.jboss.org/repos/jbossas >> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1 >> Revision: 74705 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: alesj >> Last Changed Rev: 74700 >> Last Changed Date: 2008-06-17 11:05:19 -0500 (Tue, 17 Jun 2008) >> >> >> >> Ales Justin wrote: >>>> Maybe what you're seeing is just old caching of the JAR at your system? >>> >>> What exactly should I nuke to see the results/effect? >>> Since I don't wanna nuke my whole Maven repo ... >>> >>>> Ales Justin wrote: >>>>> Yeah, this also makes smoke-tests pass on my Winz box. >>>>> >>>>> Scott Stark wrote: >>>>>> Attached is an example >>>>>> all/deploy/messaging/hsqldb-persistence-service.xml that allows >>>>>> the all config to startup and the smoke-tests pass on my osx system. >>>>>> >>>>>> Scott Stark wrote: >>>>>>> Right, that is what I would like to understand. I know this can >>>>>>> be fixed by updating the ds.xml config, but wanted to find out >>>>>>> why the failure is not consistent. The current JBM version in >>>>>>> jbossas trunk is 1.4.1.CR1 >>>>>>> >>>>>>> Ales Justin wrote: >>>>>>>> > Workaround is simple just add the correct config to the file. >>>>>>>> >>>>>>>> What is the correct config? :-) >>>>>>>> Or why it works on Fedora9, but not on OSX and Winz? >>>>>>>> >>>>>>>> Tim Fox wrote: >>>>>>>>> This was a bug in the default HSQL config. I believe Clebert >>>>>>>>> fixed it some time back - I'm not sure what version you are using? >>>>>>>>> >>>>>>>>> Sorry - didn't see this thread since don't read all of dev list. >>>>>>>>> >>>>>>>>> We don't test against HSQL since we don't support it (it >>>>>>>>> doesn't have transactions etc). >>>>>>>>> >>>>>>>>> Apparently this one slipped through EAP testing too. >>>>>>>>> >>>>>>>>> Workaround is simple just add the correct config to the file. >>>>>>>>> >>>>>>>>> Ales Justin wrote: >>>>>>>>> >>>>>>> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

> Workaround is simple just add the correct config to the file. What is the correct config? :-) Or why it works on Fedora9, but not on OSX and Winz?

Tim Fox wrote: > This was a bug in the default HSQL config. I believe Clebert fixed it > some time back - I'm not sure what version you are using? > > Sorry - didn't see this thread since don't read all of dev list. > > We don't test against HSQL since we don't support it (it doesn't have > transactions etc). > > Apparently this one slipped through EAP testing too. > > Workaround is simple just add the correct config to the file. > > Ales Justin wrote: >> JBM guys, any ideas why this is random on diff OSs? >> >> -------- Original Message -------- >> Subject: Re: [jboss-dev] AS testsuite >> Date: Mon, 16 Jun 2008 11:39:57 -0700 >> From: Scott Stark <sstark(a)redhat.com&gt; >> Reply-To: JBoss.org development list <jboss-development(a)lists.jboss.org&gt; >> To: JBoss.org development list <jboss-development(a)lists.jboss.org&gt; >> >> That is the error I have been seeing as well. As far as I can see the >> default hard coded ddl for the hsqldb setup of the tables is broken as I >> reported in a previous msg. It fails under my osx system, but passes on >> an fedora 9 system. I have not taken time to figure out how the one >> system does not fail. >> >> The previous msg I sent on this: >> http://lists.jboss.org/pipermail/jboss-development/2008-June/012123.html >> >> Ales Justin wrote: >>> Resending this. >>> >>> -------- Original Message -------- >>> Subject: Re: [jboss-dev] AS testsuite >>> Date: Mon, 16 Jun 2008 17:02:21 +0200 >>> From: Ales Justin <ales.justin(a)gmail.com&gt; >>> To: JBoss.org development list <jboss-development(a)lists.jboss.org&gt; >>> >>>> On Fri, 2008-06-13 at 17:24 +0300, Dimitris Andreadis wrote: >>>>> and I see more fixes coming in from Adrian...) >>>>> >>>> >>>> Those were just to get the smoke-tests to 100% >>> >>> Should I now see 100%? >>> >>> Since I'm still getting failures: >>> >>> AS5_trunk_all boot: >>> >>> 16:57:48,323 ERROR [ProfileServiceBootstrap] Failed to load profile: >>> Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): >>> >>> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required >>> State:Actual State} >>> >>> jboss.jca:name=JmsXA,service=ConnectionFactoryBinding >>> -> jboss.jca:name=JmsXA,service=TxCM{Create:Configured} >>> >>> jboss.jca:name=JmsXA,service=ManagedConnectionFactory >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> >>> jboss.jca:name=JmsXA,service=ManagedConnectionPool >>> -> >>> jboss.jca:name=JmsXA,service=ManagedConnectionFactory{Create:Configured} >>> >>> >>> jboss.jca:name=JmsXA,service=TxCM >>> -> >>> jboss.jca:name=JmsXA,service=ManagedConnectionPool{Create:Configured} >>> >>> jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> -> jboss.messaging:service=PostOffice{Create:Configured} >>> >>> jboss.messaging.connectionfactory:service=ClusteredConnectionFactory >>> -> jboss.messaging:service=PostOffice{Create:Configured} >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> >>> jboss.messaging.connectionfactory:service=ConnectionFactory >>> -> jboss.messaging:service=PostOffice{Create:Configured} >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> >>> jboss.messaging.destination:name=DLQ,service=Queue >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> -> jboss.messaging:service=PostOffice{Create:Configured} >>> >>> jboss.messaging.destination:name=ExpiryQueue,service=Queue >>> -> jboss.messaging:service=PostOffice{Create:Configured} >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> >>> jboss.messaging:service=PostOffice >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> >>> jboss.mq:service=DestinationManager >>> -> jboss.messaging:service=ServerPeer{Create:**ERROR**} >>> >>> >>> *** CONTEXTS IN ERROR: Name -> Error >>> >>> jboss.messaging:service=ServerPeer -> **ERROR** | >>> java.sql.SQLException: >>> Table not found in statement [SELECT CNTR, ID FROM JBM_ID_CACHE WHERE >>> NODE_ID = ?] >>> >>> Smoke tests raw: >>> >>> C:\projects\jboss5\trunk\testsuite>build smoke-tests-raw >>> Calling ..\tools\bin\ant.bat smoke-tests-raw >>> Buildfile: build.xml >>> Overriding previous definition of reference to xerces.xerces.classpath >>> Overriding previous definition of reference to apache.commons.classpath >>> Overriding previous definition of reference to sax.classpath >>> Overriding previous definition of reference to xdoclet.task.classpath >>> Overriding previous definition of reference to gjt.jpl-util.classpath >>> Overriding previous definition of reference to >>> opennms.joesnmp.classpath >>> Overriding previous definition of reference to jacorb.idl.classpath >>> Overriding previous definition of reference to sleepycat.classpath >>> Overriding previous definition of reference to >>> apache.tomcat55.classpath >>> Overriding previous definition of reference to trove.classpath >>> Overriding previous definition of reference to qdox.classpath >>> Overriding previous definition of reference to javassist.classpath >>> Overriding previous definition of reference to hibernate3.classpath >>> Overriding previous definition of reference to odmg.classpath >>> Overriding previous definition of reference to cglib.classpath >>> Overriding previous definition of reference to >>> ejb3-persistence.classpath >>> Overriding previous definition of reference to spring.classpath >>> Overriding previous definition of reference to apache.ant.classpath >>> Overriding previous definition of reference to jboss.test.classpath >>> >>> init: >>> >>> smoke-tests-raw: >>> [echo] >>> [echo] junit.timeout: 300000 >>> [echo] jbosstest.iterationcount: 10 >>> [echo] jbosstest.threadcount: 5 >>> [echo] jbosstest.beancount: 5 >>> [echo] >>> [junit] Running org.jboss.test.aop.test.AOPUnitTestCase >>> [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: >>> 15,016 sec >>> [junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase >>> [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: >>> 5,781 sec >>> [junit] Running org.jboss.test.cts.test.BmpUnitTestCase >>> [junit] Tests run: 11, Failures: 0, Errors: 11, Time elapsed: >>> 1,438 sec >>> [junit] Test org.jboss.test.cts.test.BmpUnitTestCase FAILED >>> [junit] Running org.jboss.test.cts.test.CmpUnitTestCase >>> [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 0,89 >>> sec >>> [junit] Test org.jboss.test.cts.test.CmpUnitTestCase FAILED >>> [junit] Running org.jboss.test.cts.test.CtsCmp2OptionDUnitTestCase >>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: >>> 1,078 sec >>> [junit] Test org.jboss.test.cts.test.CtsCmp2OptionDUnitTestCase >>> FAILED >>> [junit] Running org.jboss.test.cts.test.CtsCmp2UnitTestCase >>> [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: >>> 4,828 sec >>> [junit] Running org.jboss.test.cts.test.IndependentJarsUnitTestCase >>> [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: >>> 0,984 sec >>> [junit] Test org.jboss.test.cts.test.IndependentJarsUnitTestCase >>> FAILED >>> [junit] Running org.jboss.test.cts.test.MDBUnitTestCase >>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: >>> 0,875 sec >>> [junit] Test org.jboss.test.cts.test.MDBUnitTestCase FAILED >>> [junit] Running >>> org.jboss.test.cts.test.StatelessSessionBrokenCreateUnitTestCase >>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: >>> 0,797 sec >>> [junit] Test >>> org.jboss.test.cts.test.StatelessSessionBrokenCreateUnitTestCase FAILED >>> [junit] Running >>> org.jboss.test.cts.test.StatelessSessionUnitTestCase >>> [junit] Tests run: 8, Failures: 0, Errors: 8, Time elapsed: >>> 0,875 sec >>> [junit] Test org.jboss.test.cts.test.StatelessSessionUnitTestCase >>> FAILED >>> [junit] Running org.jboss.test.ejb3.test.SimpleSessionUnitTestCase >>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: >>> 2,031 sec >>> [junit] Running >>> org.jboss.test.jbossmessaging.test.JBossMessagingJoramUnitTestCase >>> [junit] Tests run: 198, Failures: 0, Errors: 196, Time elapsed: >>> 3,281 sec >>> [junit] Test >>> org.jboss.test.jbossmessaging.test.JBossMessagingJoramUnitTestCase >>> FAILED >>> [junit] Running >>> org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase >>> [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: >>> 26,875 sec >>> [junit] Running org.jboss.test.jca.test.PoolingUnitTestCase >>> [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: >>> 0,781 sec >>> [junit] Running org.jboss.test.jca.test.XADSUnitTestCase >>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,5 sec >>> [junit] Running org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase >>> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: >>> 0,438 sec >>> [junit] Test org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase >>> FAILED >>> [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase >>> [junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: >>> 1,859 sec >>> [junit] Test org.jboss.test.jmsra.test.RaQueueUnitTestCase FAILED >>> [junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase >>> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: >>> 0,515 sec >>> [junit] Test org.jboss.test.jmsra.test.RaSyncRecUnitTestCase FAILED >>> [junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase >>> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: >>> 0,406 sec >>> [junit] Test org.jboss.test.jmsra.test.RaTopicUnitTestCase FAILED >>> [junit] Running org.jboss.test.naming.test.SimpleUnitTestCase >>> [junit] Tests run: 10, Failures: 0, Errors: 4, Time elapsed: >>> 17,375 sec >>> [junit] Test org.jboss.test.naming.test.SimpleUnitTestCase FAILED >>> [junit] Running >>> org.jboss.test.tm.test.TransactionManagerUnitTestCase >>> [junit] Tests run: 28, Failures: 0, Errors: 0, Time elapsed: >>> 1,14 sec >>> [junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase >>> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: >>> 3,047 sec >>> [junit] Test org.jboss.test.web.test.WebIntegrationUnitTestCase >>> FAILED >>> >>> BUILD SUCCESSFUL >>> Total time: 1 minute 59 seconds >>> >>>>> (Beer - why didn't I think about this before? ;) >>>> >>>> We could set up a trading system where people that break the testsuite >>>> pay beers to those that fix it. :-) >>> >>> Nice cheap way to get beer during EURO. >>> If only it could be wired to Du Cerf. :-) >>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development >> >