The issue is that the cancelation of the timer is not removing its
association from the java.util.Timer as the TimerTask.cancel just marks
the TimerTask.state as cancelled, but its not removed until the timer
actually expires. This was leading to a huge list of transaction timeout
objects and the a
1.5 added a java.util.Timer.purge()
I didn't realise Elias had changed TimeoutFactory to use a Timer.
He said he was just changing it so it can be used as something
other than a singleton:
http://jira.jboss.com/jira/browse/JBAS-2205
>From the cvs commit, it looks like he did this because the
old
So how should the be addressed when using 1.4? I just added used of
Timer for client side leases within remoting.
Adrian Brock wrote:
1.5 added a java.util.Timer.purge()
I didn't realise Elias had changed TimeoutFactory to use a Timer.
He said he was just changing it so it can be used as som
On Sun, 2006-01-22 at 08:30, Tom Elrod wrote:
> So how should the be addressed when using 1.4? I just added used of
> Timer for client side leases within remoting.
>
I think we should reinstate the old code for TimeoutFactory
and add a shutdown method.
Avoid using java.util.Timer
Even that pur
I'd just like to thank the person (you know who you are)
that created the jboss-xml-binding.jar
for breaking the microcontainer standalone build
and probably a few other standalone builds that
expect jbossxb to be in jboss-common.jar
--
Adrian Brock
Chief Scientist
JBo
Also this code is in 3.2.x so we need to get it sorted before
3.2.8 goes out.
On Sun, 2006-01-22 at 08:48, Adrian Brock wrote:
> On Sun, 2006-01-22 at 08:30, Tom Elrod wrote:
> > So how should the be addressed when using 1.4? I just added used of
> > Timer for client side leases within remoting.
The priority queue should be factored out of the old code and JBAS-2205
reopened as the commits for the current changes do not show up in jira
version control tab. Also, the previous author tag was dropped so
@author Ole Husgaard needs to be restored.
JBAS-2205 has been reopened and this forum for
We need agreement from all projects to accept and adhere to the version
conventions discussed here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=75175
Scott Stark
VP Architecture & Technology
JBoss Inc.
-
java.util.Timer's is a PIECE OF POOP!
Adrian Brock wrote:
On Sun, 2006-01-22 at 08:30, Tom Elrod wrote:
So how should the be addressed when using 1.4? I just added used of
Timer for client side leases within remoting.
I think we should reinstate the old code for TimeoutFactory
and add a
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060122131732
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of build: 01/22
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060122143730
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:191: The following error occurred while executing this line: /services/cruisecontrol/work/scripts
The current ejb3 testfailure is due to an incomplete
integration of the remoting:
http://jira.jboss.com/jira/browse/JBAS-2698
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 22, 2006
10:47 AM
To: Adrian Brock; Bill Decoste; Bill Burke; Gavin King;
jbos
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20060122203606
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.2-testsuite?log=log20060122203834
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log2006010340
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060122231846
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 01/22/2006 23:18:46Time to build: Last changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientP
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060123022009
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:118: The following error occurred while executing this line: /services/cruisecontrol/wor
17 matches
Mail list logo
