ejb3-testsuite is working again. I say rollback 78961 & 78963. Carlo Carlo de Wolf wrote: > Also reverting 78963 by jhalliday: Uncommented service binding manager > integration for JBossTS, as the new JBossTS 4.4.0.GA now supports it. > JBAS-5919 with a side order of JBAS-5192. > > Carlo > > Carlo de Wolf wrote: >> The clustered configs aren't working because of: >> >> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... >> >> >> TransactionManager -> com.arjuna.ats.arjuna.exceptions.FatalError: >> [com.arjuna.ats.internal.arjuna.utils.SocketProcessId_2] - >> SocketProcessId.getpid could not get unique port. >> >> My guess is 78961 by jhalliday: Upgraded JBossTS to 4.4.0.GA, adding >> JTS elements in the process. JBAS-5919 >> >> I'm going to do a revert locally and another run of ejb3-testsuite. >> If that one is the culprit, I'll vote roll back at that time. >> >> Carlo >> >> _______________________________________________ >> 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

We haven't announced the new policy yet, so it would be unfair to do it. I'll start a discussion thread on it since it was my idea originally. On Wed, 2008-10-01 at 12:02 +0200, Carlo de Wolf wrote: > ejb3-testsuite is working again. > > I say rollback 78961 & 78963. > > Carlo > > Carlo de Wolf wrote: > > Also reverting 78963 by jhalliday: Uncommented service binding manager > > integration for JBossTS, as the new JBossTS 4.4.0.GA now supports it. > > JBAS-5919 with a side order of JBAS-5192. > > > > Carlo > > > > Carlo de Wolf wrote: > >> The clustered configs aren't working because of: > >> > >> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... > >> > >> > >> TransactionManager -> com.arjuna.ats.arjuna.exceptions.FatalError: > >> [com.arjuna.ats.internal.arjuna.utils.SocketProcessId_2] - > >> SocketProcessId.getpid could not get unique port. > >> > >> My guess is 78961 by jhalliday: Upgraded JBossTS to 4.4.0.GA, adding > >> JTS elements in the process. JBAS-5919 > >> > >> I'm going to do a revert locally and another run of ejb3-testsuite. > >> If that one is the culprit, I'll vote roll back at that time. > >> > >> Carlo > >> > >> _______________________________________________ > >> 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