[JBoss-dev] jboss-seam-testsuite Build Completed With Testsuite Errors
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/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 01/23/2006 02:20:09Time to build: 2 minutes 1 secondLast changed: 01/22/2006 19:50:24Last log entry: cleaned up stuff about PC jndi lookup Unit Tests: (15) Total Errors and Failures: (0)All Tests Passed Modifications since last build: (first 50 of 870)1.11modifiedgavinsrc/main/org/jboss/seam/core/ManagedHibernateSession.javacleaned up stuff about PC jndi lookup1.8modifiedgavinsrc/main/org/jboss/seam/core/ManagedPersistenceContext.javacleaned up stuff about PC jndi lookup1.40modifiedgavinsrc/main/org/jboss/seam/core/Manager.javacleaned up stuff about PC jndi lookup1.13modifiedgavinsrc/test/misc/org/jboss/seam/test/InitializationTest.javafixed tests1.38modifiedgavinsrc/main/org/jboss/seam/init/Initialization.javaalways install debug components1.4modifiedgavinsrc/main/org/jboss/seam/debug/Introspector.javaadded toString() to debug attributes1.3modifiedgavinsrc/main/org/jboss/seam/debug/Introspector.javaadded toString() to debug attributes1.2modifiedgavinsrc/main/org/jboss/seam/debug/Contexts.javaadded process context to debugger1.2modifiedgavinsrc/main/org/jboss/seam/debug/Introspector.javaimproved introspector1.1addedgavinsrc/main/org/jboss/seam/debug/Contexts.javaadded online debug support1.1addedgavinsrc/main/org/jboss/seam/debug/Introspector.javaadded online debug support1.11modifiedgavinsrc/main/org/jboss/seam/core/Conversation.javasome improvements to make the issues demo slicker1.7modifiedgavinsrc/main/org/jboss/seam/core/ConversationList.javasome improvements to make the issues demo slicker1.4modifiedgavinsrc/main/org/jboss/seam/core/ConversationStack.javasome improvements to make the issues demo slicker1.39modifiedgavinsrc/main/org/jboss/seam/core/Manager.javasome improvements to make the issues demo slicker1.9modifiedgavinsrc/main/org/jboss/seam/core/Switcher.javasome improvements to make the issues demo slicker1.6modifiedgavinsrc/main/org/jboss/seam/core/ManagedJbpmContext.javadon't roll back jbpm contexts if jbpm is not doing tx managementcope with system exceptions from SFSBs1.9modifiedgavinsrc/main/org/jboss/seam/interceptors/RemoveInterceptor.javadon't roll back jbpm contexts if jbpm is not doing tx managementcope with system exceptions from SFSBs1.17modifiedgavinsrc/main/org/jboss/seam/Seam.javahandle inner class ejbname1.7modifiedgavinsrc/main/org/jboss/seam/util/Strings.javahandle inner class ejbname1.38modifiedgavinsrc/main/org/jboss/seam/core/Manager.javamove conversation timeout to post-seam-txn-commit1.58modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javamove conversation timeout to post-seam-txn-commit1.6modifiedgavinsrc/main/org/jboss/seam/annotations/IfInvalid.javaadded ability to refresh entities when constraints are violated1.5modifiedgavinsrc/main/org/jboss/seam/interceptors/RollbackInterceptor.javaadded ability to refresh entities when constraints are violated1.10modifiedgavinsrc/main/org/jboss/seam/interceptors/ValidationInterceptor.javaadded ability to refresh entities when constraints are violated1.10modifiedgavinsrc/main/org/jboss/seam/jsf/SeamNavigationHandler.javaadded ability to refresh entities when constraints are violated1.15modifiedtbaeyenssrc/main/org/jboss/seam/core/Jbpm.javareplaced snapshot of jbpm jar with the 3.1 beta 2 release version1.2modifiedtbaeyenssrc/main/org/jboss/seam/jbpm/SeamVariableResolver.javareplaced snapshot of jbpm jar with the 3.1 beta 2 release version1.37modifiedgavinsrc/main/org/jboss/seam/core/Manager.javaadd leaveConversation()1.9modifiedgavinsrc/main/org/jboss/seam/jsf/SeamExtendedManagedPersistencePhaseListener.javaend transactions *before* cleanup of contexts1.17modifiedgavinsrc/main/org/jboss/seam/jsf/SeamTransactionManagedPersistencePhaseListener.javaend transactions *before* cleanup of contexts1.12modifiedgavinsrc/main/org/jboss/seam/servlet/SeamExceptionFilter.javaend transactions *before* cleanup of contexts1.15modifiedgavinsrc/main/org/jboss/seam/core/Init.javaadded jndiPattern1.84modifiedgavinsrc/main/org/jboss/seam/Component.javaadded jndiPattern1.83modifiedgavinsrc/main/org/jboss/seam/Component.javaadded jndiPattern1.16modifiedgavinsrc/main/org/jboss/seam/Seam.javaadded jndiPattern1.14modifiedgavinsrc/main/org/jboss/seam/core/Init.javaadded jndiPattern1.6modifiedgavinsrc/main/org/jboss/seam/util/Strings.javaadded jndiPattern1.6deletedgavinsrc/main/org/jboss/seam/jbpm/SeamDecisionHandler.javaremoved obsoelete1.14modifiedgavinsrc/main/org/jboss/seam/
[JBoss-dev] jboss-remoting-testsuite-1.5 Build Timed Out
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 (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 1852)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/SocketInvokerTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/raw/RawClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/raw/RawServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/SSLInvokerConstants.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead of http server invoker. Also adding many fixes so now only ssl related http tests are failing within the tests suite.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.keystoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.truststoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ss
[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors
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/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 01/22/2006 22:03:40Time to build: 18 minutes 59 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (132) Total Errors and Failures: (3)testStartorg.jboss.test.remoting.marshall.dynamic.remote.http.HTTPMarshallerLoadingTestCasetestStartorg.jboss.test.remoting.marshall.dynamic.remote.socket.SocketMarshallerLoadingTestCasetestClientConfigurationorg.jboss.test.remoting.configuration.HTTPConfigurationTestCase(java_serialization) Modifications since last build: (first 50 of 1852)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/SocketInvokerTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/raw/RawClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/raw/RawServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/SSLInvokerConstants.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead of http server invoker. Also adding many fixes so now only ssl related http tests are failing within the tests suite.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.keystoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transpor
[JBoss-dev] jboss-portal-2.2-testsuite Build Completed With Testsuite Errors
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/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:278: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 01/22/2006 20:38:34Time to build: 2 minutes 23 secondsLast changed: 12/31/2005 01:43:25Last log entry: - added repository config in DB by default Unit Tests: (72) Total Errors and Failures: (32)testServiceorg.jboss.portal.test.cms.TestRepositoryBootStraptestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestNullKeyThrowsIllegalArgumentExceptionorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestReadorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestWriteorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestNullWriteorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestIsReadOnlyorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestMaporg.jboss.portal.test.portlet.PortletPreferencesTestCasetestPreferencesCanBeSetToNullorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestPreferencesMapModificationDoesNotModifyPreferencesValuesorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestResetPreferenceHavingNoDefaultValueDeletesItorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestReadOnlyPreferenceCannotBeModifiedorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestStoreMustPersistAllChangesorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestChangesMadeButNotStoredAreDiscardedorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestStoreCalledDuringRenderThrowsIllegalArgumentExceptionorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestCanModifyNonReadOnlyPreferenceorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestDynamicPreferenceTreatedLikeModifiablePreferenceorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestCreateASingleInstanceOfValidatororg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestInvalidationCancelsStoreorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestValidationStoresorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCase Modifications since last build: (first 50 of 3275)1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPEngine.javabranches: 1.2.4;removed my obsolete overengineered code1.3modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/engine/WSRPEngineImpl.javabranches: 1.3.4;removed my obsolete overengineered code1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/RequestController.javaJBPORTAL-550 : Need to update the lgpl headers1.3modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPEngine.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPInterceptor.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPRequest.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPRequestContext.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPResponse.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/WSRPResponseContext.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/aspects/engine/ControllerInterceptor.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/aspects/engine/RegistrationInterceptor.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/aspects/engine/UserInterceptor.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/endpoints/MarkupServiceEndpoint.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/endpoints/ServiceDescriptionEndpoint.javaJBPORTAL-550 : Need to update the lgpl headers1.4modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/engine/WSRPEngineImpl.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/invocation/AxisEngineUtil.javaJBPORTAL-550 : Need to update the lgpl headers1.2modifiedjulienwsrp/src/main/org/jboss/portal/wsrp/
[JBoss-dev] jboss-portal-2.0-testsuite Build Completed With Testsuite Errors
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/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:278: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 01/22/2006 20:36:06Time to build: 2 minutes 7 secondsLast changed: 12/28/2005 00:15:42Last log entry: - targetWindowRef rename Unit Tests: (67) Total Errors and Failures: (25)testAorg.jboss.portal.test.cms.stress.ConcurrentTestCasetestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestFindUser1org.jboss.portal.test.core.RoleModelTestCasetestFindUser2org.jboss.portal.test.core.RoleModelTestCasetestFindUsersorg.jboss.portal.test.core.RoleModelTestCasetestCreateUserorg.jboss.portal.test.core.RoleModelTestCasetestCreateRoleorg.jboss.portal.test.core.RoleModelTestCasetestCountUserorg.jboss.portal.test.core.RoleModelTestCasetestRemoveNonExistingRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveUserorg.jboss.portal.test.core.RoleModelTestCasetestFindRolesorg.jboss.portal.test.core.RoleModelTestCasetestFindRoleMembersorg.jboss.portal.test.core.RoleModelTestCasetestResourceBundleorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestResourceBundleCascadeorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestGetResourceBundleDuringInitorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCase Modifications since last build: (first 50 of 2147)1.3modifiedjulienthirdparty/jboss-cache/README.txtupdate jboss cache jars to those of 4.0.3SP11.6modifiedjulienthirdparty/jboss-cache/lib/jboss-cache.jarupdate jboss cache jars to those of 4.0.3SP11.5deletedjulienthirdparty/jboss-cache/lib/jboss-remoting.jarupdate jboss cache jars to those of 4.0.3SP11.5modifiedjulienthirdparty/jboss-cache/lib/jgroups.jarupdate jboss cache jars to those of 4.0.3SP11.24modifiedjulientools/etc/buildfragments/libraries.entbranches: 1.24.2; 1.24.4;update jboss cache jars to those of 4.0.3SP11.23modifiedjulientools/etc/buildfragments/libraries.entswitching to facelets that provide a decent support for inclusion and thus enable reusability of JSF sub trees1.7modifiedjulientools/etc/buildfragments/modules.entadded the faces modules to the build1.7modifiedjulienthirdparty/jboss-system/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-system/lib/jboss-common.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-system/lib/jboss-jmx.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-system/lib/jboss-system.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-j2ee/lib/jboss-j2ee.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-server/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-server/lib/jboss.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-sx/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-sx/lib/jbosssx.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.5modifiedjulienthirdparty/jboss-client/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.5modifiedjulienthirdparty/jboss-client/lib/jbossall-client.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-j2ee/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the d
[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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; jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel Loehr; Scott M Stark; Thomas Diesler Subject: ejb3-4.0-testsuite Build Failed Importance: High View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060122131732 BUILD FAILED Ant 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/2006 13:17:32 Time to build: 28 minutes 56 seconds Last changed: 12/31/2005 16:46:08 Last log entry: call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false
[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors
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/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 01/22/2006 14:37:30Time to build: 48 minutes 45 secondsLast changed: 01/22/2006 03:20:20Last log entry: Clear the TimeoutImpl references in cancel to limit the scope of references between the time of cancellation and when the timer is garbage collected. Unit Tests: (1822) Total Errors and Failures: (1)testAsynchTopicReceiveRollBackorg.jboss.test.jbossmq.test.RollBackUnitTestCase Modifications since last build: (first 50 of 25)1.1.4.5modifiedstarksmcommon/src/main/org/jboss/util/timeout/TimeoutFactory.javaClear the TimeoutImpl references in cancel to limit the scope of references between the time of cancellation and when the timer is garbage collected.1.1.2.29modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.jpp[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.2.6modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/PreparedStatementCache.java[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.2.19modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/WrappedConnection.jpp[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.2.5modifiedadriantestsuite/src/main/org/jboss/test/jca/ejb/JDBCStatementTestsConnectionSessionBean.java[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.4.3modifiedadriantestsuite/src/main/org/jboss/test/jca/ejb/PreparedStatementBean.java[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.4.3modifiedadriantestsuite/src/main/org/jboss/test/jca/interfaces/PreparedStatementRemote.java[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.2.4modifiedadriantestsuite/src/main/org/jboss/test/jca/jdbc/TestConnection.java[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.4.3modifiedadriantestsuite/src/main/org/jboss/test/jca/test/PSCacheUnitTestCase.java[JBAS-2304] - Add support for prepare[Statement|Call] with result set type and concurrency parameters.Based on patch provided by andrey belomutskiy.1.1.2.14modifiedadriantestsuite/imports/code-generation.xmlWhen I say -Dnoxdoclet that means don't run xdoclet1.17.2.4modifieddimitrisserver/src/main/org/jboss/ejb/plugins/MetricsInterceptor.javaJBAS-2656, report a warning if MetricsInterceptor is activated, avoid enqueueing metrics if publisher thread has exited1.42.2.29modifiedadrianconnector/build.xmlBackport [JBAS-2682] to 3.2.x1.1.2.28modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.jppBackport [JBAS-2682] to 3.2.x1.1.2.1modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/CachedCallableStatement.jppBackport [JBAS-2682] to 3.2.x1.1.2.11modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/CachedPreparedStatement.jppBackport [JBAS-2682] to 3.2.x1.1.2.5modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/PreparedStatementCache.javaBackport [JBAS-2682] to 3.2.x1.1.2.18modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/WrappedConnection.jppBackport [JBAS-2682] to 3.2.x1.1.4.2modifiedadriantestsuite/src/main/org/jboss/test/jca/ejb/PreparedStatementBean.javaBackport [JBAS-2682] to 3.2.x1.1.4.2modifiedadriantestsuite/src/main/org/jboss/test/jca/interfaces/PreparedStatementRemote.javaBackport [JBAS-2682] to 3.2.x1.1.4.2modifiedadriantestsuite/src/main/org/jboss/test/jca/test/PSCacheUnitTestCase.javaBackport [JBAS-2682] to 3.2.x1.1.4.1modifiedadriantestsuite/src/resources/jca/pscache/ejb-jar.xmlBackport [JBAS-2682] to 3.2.x1.11.2.13modifiedadrianserver/src/main/org/jboss/ejb/plugins/jms/DLQHandler.javaBackport [JBAS-2684] from jboss-head1.50.2.22modifiedadrianserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.javaBackport [JBAS-2684] from jboss-head1.4.2.9modifieddimitrisbuild/build-thirdparty.xmlJBAS-2694, use HSQLDB 1.8.0.2 compiled for jdk1.31.1.4.7modifiedbstansberrytestsuite/src/main/org
[JBoss-dev] ejb3-4.0-testsuite Build Failed
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/2006 13:17:32Time to build: 28 minutes 56 secondsLast changed: 12/31/2005 16:46:08Last log entry: call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 3530)1.3modifiedbillsrc/test/org/jboss/ejb3/test/tableperinheritance/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.7modifiedbillsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.6modifiedbillsrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaEJBs and Persistence can now be within a .jar file1.3modifiedbillsrc/test/org/jboss/ejb3/test/xmlcfg/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.4modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaapplication-exception support1.7modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaapplication-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorAppException.javabranches: 1.1.2;application-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorCheckedRollbackException.javabranches: 1.1.2;application-exception support1.5modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaapplication-exception support1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javabranches: 1.2.2;activateConfig to activationConfig1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javabranches: 1.2.2;activateConfig to activationConfig1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/unit/EmbeddedEjb3TestCase.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/Customer.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOBean.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOLocal.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAORemote.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/EmbeddedEJB3.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/JndiTest.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javatest for embedded EJB3 in WLS1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/Customer.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTest.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTestBean.javaUpdate the jboss LGPL headers1.4modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTester.javaUpdate the jboss LGPL headers1.9modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean21.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AnnotatedAppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/CheckedRollbackException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRuntimeException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRuntimeException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/SimpleEntity.javaUpdate the jboss LGPL headers1.4m
Re: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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 shutdown method. Avoid using java.util.Timer Even that purge() method has poor performance semantics. It scans all the registrations everytime. 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 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 implementation didn't have a "shutdown" method: http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common/src/main/org/jboss/util/timeout/TimeoutFactory.java See version 1.4 On Sun, 2006-01-22 at 03:18, Scott M Stark wrote: 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 associated object graph. Clearing the TimeoutImpl refs in cancel restricts the transient buildup to just the TimeoutImpl. I don't see a way to immeadiate disassociate the TimeoutImpl from the java.util.Timer internals. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Saturday, January 21, 2006 10:12 PM To: jboss-development@lists.sourceforge.net; Bill Burke Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed So after profiling this the problem looks to be recent changes in org.jboss.util.timeout.TimeoutFactory as the leaks are related to transaction timeouts. By clearing the TimeoutFactory$TimeoutImpl references the test gets past the OME, but there are 73k TimeoutFactory$TimeoutImpl left after the test has completed and has been undeployed. One gc root is the java.util.TimerThread task queue. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Saturday, January 21, 2006 2:17 PM To: Bill Burke Cc: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed This is just the org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase requiring too much memory. Memory usage during this test goes from 40m to 130m even using the default config so the memory usage of this needs to be looked at. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Need closure on the version convention
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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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 discussion created: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918930 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Adrian Brock > Sent: Sunday, January 22, 2006 5:49 AM > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > 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 purge() method has poor performance semantics. > It scans all the registrations everytime. > > > 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 > 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 implementation didn't have a "shutdown" method: > > > > http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common/src/main/o > > > rg/jboss/util/timeout/TimeoutFactory.java > > > See version 1.4 > > > > > > On Sun, 2006-01-22 at 03:18, Scott M Stark wrote: > > > > > >>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 associated object graph. > > >>Clearing the TimeoutImpl refs in cancel restricts the transient > > >>buildup to just the TimeoutImpl. I don't see a way to immeadiate > > >>disassociate the TimeoutImpl from the java.util.Timer internals. > > >> > > >> > > >>>-Original Message- > > >>>From: [EMAIL PROTECTED] > > >>>[mailto:[EMAIL PROTECTED] > On Behalf Of > > >>>Scott M Stark > > >>>Sent: Saturday, January 21, 2006 10:12 PM > > >>>To: jboss-development@lists.sourceforge.net; Bill Burke > > >>>Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > >>> > > >>>So after profiling this the problem looks to be recent > changes in > > >>>org.jboss.util.timeout.TimeoutFactory as the leaks are > related to > > >>>transaction timeouts. By clearing the TimeoutFactory$TimeoutImpl > > >>>references the test gets past the OME, but there are 73k > > >>>TimeoutFactory$TimeoutImpl left after the test has completed and > > >>>has been undeployed. One gc root is the > java.util.TimerThread task > > >>>queue. > > >>> > > >>> > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > On Behalf > > Of Scott M Stark > > Sent: Saturday, January 21, 2006 2:17 PM > > To: Bill Burke > > Cc: jboss-development@lists.sourceforge.net > > Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > > > This is just the > > >>> > > >>>org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase > > >>> > > requiring too much memory. Memory usage during this test > > >>> > > >>>goes from 40m > > >>> > > to 130m even using the default config so the memory > usage of this > > needs to be looked at. > > >>> > > >>> > > >>>--- > > >>>This SF.net email is sponsored by: Splunk Inc. Do you > grep through > > >>>log files for problems? Stop! Download the new AJAX > search engine > > >>>that makes searching your log files as easy as surfing > the web. > > >>>DOWNLOAD SPLUNK! > > >>>http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > > >>>___ > > >>>JBoss-Development mailing list > > >>>JBoss-Development@lists.sourceforge.net > > >>>https://lists.sourceforge.net/lists/listinfo/jboss-development > > >>> > > >> > > >> > > >>--- > > >>This SF.net email is sponsored by: Splunk Inc. Do you > grep through > > >>log files for problems? Stop! Download the new AJAX > search engine > > >>that makes searching your log files as easy as surfing > the web. DOWNLOAD SPLUNK! > > >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > > >>___ > > >>JBoss-Development mailing list > > >>JBoss-Development@lists.sourceforge.net > > >>https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > -
Re: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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. > > > > I think we should reinstate the old code for TimeoutFactory > and add a shutdown method. > > Avoid using java.util.Timer > Even that purge() method has poor performance semantics. > It scans all the registrations everytime. > > > 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 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 implementation didn't have a "shutdown" method: > > > http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common/src/main/org/jboss/util/timeout/TimeoutFactory.java > > > See version 1.4 > > > > > > On Sun, 2006-01-22 at 03:18, Scott M Stark wrote: > > > > > >>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 associated object graph. Clearing the TimeoutImpl refs > > >>in cancel restricts the transient buildup to just the TimeoutImpl. I > > >>don't see a way to immeadiate disassociate the TimeoutImpl from the > > >>java.util.Timer internals. > > >> > > >> > > >>>-Original Message- > > >>>From: [EMAIL PROTECTED] > > >>>[mailto:[EMAIL PROTECTED] On > > >>>Behalf Of Scott M Stark > > >>>Sent: Saturday, January 21, 2006 10:12 PM > > >>>To: jboss-development@lists.sourceforge.net; Bill Burke > > >>>Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > >>> > > >>>So after profiling this the problem looks to be recent > > >>>changes in org.jboss.util.timeout.TimeoutFactory as the leaks > > >>>are related to transaction timeouts. By clearing the > > >>>TimeoutFactory$TimeoutImpl references the test gets past the > > >>>OME, but there are 73k TimeoutFactory$TimeoutImpl left after > > >>>the test has completed and has been undeployed. One gc root > > >>>is the java.util.TimerThread task queue. > > >>> > > >>> > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Scott M Stark > > Sent: Saturday, January 21, 2006 2:17 PM > > To: Bill Burke > > Cc: jboss-development@lists.sourceforge.net > > Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > > > This is just the > > >>> > > >>>org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase > > >>> > > requiring too much memory. Memory usage during this test > > >>> > > >>>goes from 40m > > >>> > > to 130m even using the default config so the memory usage of this > > needs to be looked at. > > >>> > > >>> > > >>>--- > > >>>This SF.net email is sponsored by: Splunk Inc. Do you grep > > >>>through log files for problems? Stop! Download the new AJAX > > >>>search engine that makes searching your log files as easy as > > >>>surfing the web. DOWNLOAD SPLUNK! > > >>>http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > > >>>___ > > >>>JBoss-Development mailing list > > >>>JBoss-Development@lists.sourceforge.net > > >>>https://lists.sourceforge.net/lists/listinfo/jboss-development > > >>> > > >> > > >> > > >>--- > > >>This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > >>files > > >>for problems? Stop! Download the new AJAX search engine that makes > > >>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > > >>___ > > >>JBoss-Development mailing list > > >>JBoss-Development@lists.sourceforge.net > > >>https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > --- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development -- xxx
[JBoss-dev] Thanks for the half-a-job
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 JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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 purge() method has poor performance semantics. It scans all the registrations everytime. > 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 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 implementation didn't have a "shutdown" method: > > http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common/src/main/org/jboss/util/timeout/TimeoutFactory.java > > See version 1.4 > > > > On Sun, 2006-01-22 at 03:18, Scott M Stark wrote: > > > >>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 associated object graph. Clearing the TimeoutImpl refs > >>in cancel restricts the transient buildup to just the TimeoutImpl. I > >>don't see a way to immeadiate disassociate the TimeoutImpl from the > >>java.util.Timer internals. > >> > >> > >>>-Original Message- > >>>From: [EMAIL PROTECTED] > >>>[mailto:[EMAIL PROTECTED] On > >>>Behalf Of Scott M Stark > >>>Sent: Saturday, January 21, 2006 10:12 PM > >>>To: jboss-development@lists.sourceforge.net; Bill Burke > >>>Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > >>> > >>>So after profiling this the problem looks to be recent > >>>changes in org.jboss.util.timeout.TimeoutFactory as the leaks > >>>are related to transaction timeouts. By clearing the > >>>TimeoutFactory$TimeoutImpl references the test gets past the > >>>OME, but there are 73k TimeoutFactory$TimeoutImpl left after > >>>the test has completed and has been undeployed. One gc root > >>>is the java.util.TimerThread task queue. > >>> > >>> > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Scott M Stark > Sent: Saturday, January 21, 2006 2:17 PM > To: Bill Burke > Cc: jboss-development@lists.sourceforge.net > Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > This is just the > >>> > >>>org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase > >>> > requiring too much memory. Memory usage during this test > >>> > >>>goes from 40m > >>> > to 130m even using the default config so the memory usage of this > needs to be looked at. > >>> > >>> > >>>--- > >>>This SF.net email is sponsored by: Splunk Inc. Do you grep > >>>through log files for problems? Stop! Download the new AJAX > >>>search engine that makes searching your log files as easy as > >>>surfing the web. DOWNLOAD SPLUNK! > >>>http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > >>>___ > >>>JBoss-Development mailing list > >>>JBoss-Development@lists.sourceforge.net > >>>https://lists.sourceforge.net/lists/listinfo/jboss-development > >>> > >> > >> > >>--- > >>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > >>for problems? Stop! Download the new AJAX search engine that makes > >>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > >>___ > >>JBoss-Development mailing list > >>JBoss-Development@lists.sourceforge.net > >>https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > --- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
Re: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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 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 implementation didn't have a "shutdown" method: http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common/src/main/org/jboss/util/timeout/TimeoutFactory.java See version 1.4 On Sun, 2006-01-22 at 03:18, Scott M Stark wrote: 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 associated object graph. Clearing the TimeoutImpl refs in cancel restricts the transient buildup to just the TimeoutImpl. I don't see a way to immeadiate disassociate the TimeoutImpl from the java.util.Timer internals. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Saturday, January 21, 2006 10:12 PM To: jboss-development@lists.sourceforge.net; Bill Burke Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed So after profiling this the problem looks to be recent changes in org.jboss.util.timeout.TimeoutFactory as the leaks are related to transaction timeouts. By clearing the TimeoutFactory$TimeoutImpl references the test gets past the OME, but there are 73k TimeoutFactory$TimeoutImpl left after the test has completed and has been undeployed. One gc root is the java.util.TimerThread task queue. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Saturday, January 21, 2006 2:17 PM To: Bill Burke Cc: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed This is just the org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase requiring too much memory. Memory usage during this test goes from 40m to 130m even using the default config so the memory usage of this needs to be looked at. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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 implementation didn't have a "shutdown" method: http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common/src/main/org/jboss/util/timeout/TimeoutFactory.java See version 1.4 On Sun, 2006-01-22 at 03:18, Scott M Stark wrote: > 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 associated object graph. Clearing the TimeoutImpl refs > in cancel restricts the transient buildup to just the TimeoutImpl. I > don't see a way to immeadiate disassociate the TimeoutImpl from the > java.util.Timer internals. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Scott M Stark > > Sent: Saturday, January 21, 2006 10:12 PM > > To: jboss-development@lists.sourceforge.net; Bill Burke > > Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > > > So after profiling this the problem looks to be recent > > changes in org.jboss.util.timeout.TimeoutFactory as the leaks > > are related to transaction timeouts. By clearing the > > TimeoutFactory$TimeoutImpl references the test gets past the > > OME, but there are 73k TimeoutFactory$TimeoutImpl left after > > the test has completed and has been undeployed. One gc root > > is the java.util.TimerThread task queue. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of > > > Scott M Stark > > > Sent: Saturday, January 21, 2006 2:17 PM > > > To: Bill Burke > > > Cc: jboss-development@lists.sourceforge.net > > > Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > > > > > This is just the > > org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase > > > requiring too much memory. Memory usage during this test > > goes from 40m > > > to 130m even using the default config so the memory usage of this > > > needs to be looked at. > > > > > > --- > > This SF.net email is sponsored by: Splunk Inc. Do you grep > > through log files for problems? Stop! Download the new AJAX > > search engine that makes searching your log files as easy as > > surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
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 associated object graph. Clearing the TimeoutImpl refs in cancel restricts the transient buildup to just the TimeoutImpl. I don't see a way to immeadiate disassociate the TimeoutImpl from the java.util.Timer internals. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Saturday, January 21, 2006 10:12 PM > To: jboss-development@lists.sourceforge.net; Bill Burke > Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > So after profiling this the problem looks to be recent > changes in org.jboss.util.timeout.TimeoutFactory as the leaks > are related to transaction timeouts. By clearing the > TimeoutFactory$TimeoutImpl references the test gets past the > OME, but there are 73k TimeoutFactory$TimeoutImpl left after > the test has completed and has been undeployed. One gc root > is the java.util.TimerThread task queue. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Scott M Stark > > Sent: Saturday, January 21, 2006 2:17 PM > > To: Bill Burke > > Cc: jboss-development@lists.sourceforge.net > > Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > > > This is just the > org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase > > requiring too much memory. Memory usage during this test > goes from 40m > > to 130m even using the default config so the memory usage of this > > needs to be looked at. > > > --- > This SF.net email is sponsored by: Splunk Inc. Do you grep > through log files for problems? Stop! Download the new AJAX > search engine that makes searching your log files as easy as > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
