View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050901124601
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:158: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050901131340
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:208: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050901134842
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:158: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050901130131
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:158: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050901161327Lbuild.360
BUILD COMPLETE-build.360Date of build:09/01/2005 16:13:27Time to build:17 minutes 30 seconds
Unit Tests: (0) Total
I think you have to do jndi lookups for other ejbs, no? I don't think
the specifications define how to reference remote EJBs.
Francisco Reverbel wrote:
Can an EJB3 have ejb-refs that refer to EJB3 components deployed in
other servers?
I am migrating some DTM recovery tests to EJB3. These
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050901163322
BUILD FAILEDAnt Error Message:build timeoutDate of build:09/01/2005 16:33:22Time to build:Last changed:09/01/2005 10:14:32Last log entry:merge server controller tasks in to 4.0
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050901184259Lbuild.558
BUILD COMPLETE-build.558Date of build:09/01/2005 18:42:59Time to build:18 minutes 35 secondsLast changed:09/01/2005 14:23:44Last log entry:Reverted to
Currently we have sequenceNumber as private in ServiceMBeanSupport, with
mbeans extending this baseclass to use
getNextNotificationSequenceNumber() to get sequence numbers when
emitting notifcations:
/** Sequence number for jmx notifications we send out. */
private SynchronizedLong
I hate to bring this up, given the trouble I've caused recently, but
it's been on my mind... Given the weird behavior of
EDU.oswego.cs.dl.util.concurrent.PooledExecutor to queue rather than
create new threads, wouldn't it be better to replace it with something
else that needs less idle threads.
10 matches
Mail list logo