Re: [jboss-dev] AS5 boot screwed up

Let me do it. I'm nearly there in getting a minimum of rollbacks to make the server boot. Once I've done that I'll commit it so that others can work, then I'll do the rest afterwards. On Thu, 2007-10-04 at 17:04 +0300, Dimitris Andreadis wrote: > I'll try to see if reverting those changes locally works, then try a rollback in a single > commit. > > Adrian wrote: >> I think you're correct, there's lots of little commits. :-( >> >> After reverting the transaction module change, I've now got >> problems with the MDB's ServerSessionPool. >> >> Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: >> org.jboss.jms.asf.ServerSessionPoolLoader >> at >> org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306) >> at >> org.jboss.mx.loading.UnifiedClassLoader.loadClassImpl(UnifiedClassLoader.java:290) >> >> >> An alternative strategy would be try to complete Francisco's >> change by fixing the main configuration of the server. >> >> But this will leave lots of broken tests in the testsuite >> until they are also updated with the correct configuration. >> >> e.g. MDB tests with specific JMSContainerInvoker configuration >> will fail until they are updated to use the JCA 1.5 inbound resource >> adapter config. >> >> e.g.2 There's still lots of tests using the now >> non-existant org.jboss.tm.TxManager on the client side. >> >> Also, the embedded project is broken since it hasn't yet been >> updated to use the new TM. >> >> On Thu, 2007-10-04 at 16:47 +0300, Dimitris Andreadis wrote: >>> Those are the revision numbers (first one was last): >>> >>> Should we revert one by one in reverse order? >>> >>> 65826, 65825, 65820, 65819, 65818, 65817, 65816, 65815, 65814, 65813, 65812, 65811, 65810, >>> 65809, 65808, 65807, 65806 >>> >>> Dimitris Andreadis wrote: >>>> I just noticed Franscisco's check-ins this morning. I think we need to >>>> revert the changes for now, but unfortunately the check-ins done were >>>> multiple. >>>> >>>> Adrian wrote: >>>>> Why has the transaction module been removed? >>>>> >>>>> The stuff required to make this work properly is still WIP: >>>>> http://jira.jboss.com/jira/browse/JBAS-4516 >>>>> >>>>> In fact, I'm currently working on fixing up the testsuite >>>>> to make this possible at all. >>>>> >>>>> The XIDFactory stuff is expected as per the subtask: >>>>> http://jira.jboss.com/jira/browse/JBAS-4517 >>>>> >>>>> On Thu, 2007-10-04 at 16:12 +0300, Dimitris Andreadis wrote: >>>>>> After the removal of the transaction module, booting the 'default' >>>>>> and 'all' configs complains initially for the missing >>>>>> org.jboss.tm.XidFactory, then about missing jbossts libs... >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>> _______________________________________________ >>> 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