[JBoss-dev] jbpm-mysql-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-mysql-testsuite?log=log20060421012621 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:70: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 04/21/2006 01:26:21Time to build: 128 minutes 40 secondsLast changed: 04/20/2006 03:10:08Last log entry: seam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node Unit Tests: (251) Total Errors and Failures: (12)testSuspendorg.jbpm.graph.exe.SuspendAndResumeDbTesttestResumeorg.jbpm.graph.exe.SuspendAndResumeDbTesttestProcessEndEventorg.jbpm.persistence.db.ConcurrentUpdateDbTesttestDateorg.jbpm.context.exe.VariableInstanceDbTesttestDateUpdateLogorg.jbpm.context.log.VariableUpdateDbTesttestNodeLogEnterDateorg.jbpm.graph.log.NodeLogDbTesttestNodeLogLeaveDateorg.jbpm.graph.log.NodeLogDbTesttestProcessLogDateorg.jbpm.logging.log.ProcessLogDbTesttestSaveTimerorg.jbpm.scheduler.exe.TimerDbTesttestTimerCreationorg.jbpm.scheduler.exe.TimerDbTesttestTimerRepeatorg.jbpm.scheduler.exe.TimerDbTest Modifications since last build: (first 50 of 144)1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionTextTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionXmlTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.24modifiedtbaeyenssrc/java.webapp/org/jbpm/webapp/bean/TaskBean.javacleaned import1.8modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/svc/ServicesTest.javacleaned import1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javacleaned import1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmladded logging config test1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javaadded logging config1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javabranches: 1.1.2;finished configuration updates1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmlbranches: 1.1.2;finished configuration updates1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/TaskMailTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/test.mail.propertiesfinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mock/Jndi.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationDbTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbPojoTests.javafinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbServiceNoTxTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryDbTest.javafinished configuration updates1.4deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/taskmgmt/exe/TaskMgmtExeDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/taskmgmt/exe/TaskVariableAccessDbTest.javafinished configuration updates1.4modifiedtbaeyenssrc/userguide/en/modules/mail.xmlfinished configuration updates1.2modifiedtbaeyenssrc/resources/starters-kit/jbpm-designer/designer.batseparated cd from start1.2modifiedtbaeyenssrc/resources/jbpm-identity.jar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/resources/jbpm.jar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/resources/jbpm.sar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockConnection.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockSession.javaadded persistence db service testing
[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=log20060421030951 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: 04/21/2006 03:09:51Time to build: 52 minutes 45 secondsLast changed: 04/21/2006 00:23:35Last log entry: Moved detection sample for multicast into multicast package (as will be creating jndi detection sample package as well). Unit Tests: (184) Total Errors and Failures: (22)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(java_serialization)unknownorg.jboss.test.remoting.transporter.TransporterTestCase(java_serialization)testStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestServerStartsServer3Client1ClientClosesorg.jboss.test.remoting.transport.multiplex.InvokerGroupTestCase(java_serialization) Modifications since last build: (first 50 of 124)1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-365 - adding remoting user agent to header of http client invoker requests.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-365 - adding remoting user agent to header of http client invoker requests.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidatorClient.javaJBREM-380 - changed connector validator to only notifiy once of connection being lost.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-408 - fixed bug for lease update changing lease window by mistake.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/locator/InvokerLocatorTestCase.javaJBREM-406 - allow for : in the locator uri path1.1addedtelrodsrc/tests/org/jboss/test/remoting/detection/multicast/MulticastDetectorTestCase.javaJBREM-405 - fix for NPE when calling stop() more than once on multicast detector.1.2modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/ssl/.keystore.keystore and .truststore need to be in test src directory so they can get copied to test output directory.1.2modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/ssl/.truststore.keystore and .truststore need to be in test src directory so they can get copied to test output directory.1.3modifiedtimfoxsrc/main/org/jboss/remoting/util/TimerUtil.javaFixes to Connection pinging and leasing1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidationServer.javaJBREM-378 - fixed client connection ping so will properly indicate if server is dead and also not activate a new lease on the server side.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidatorClient.javaJBREM-378 - fixed client connection ping so will properly indicate if server is dead and also not activate a new lease on the server side.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.2modifiedtelrodsrc/main/org/jboss/remoting/util/TimerUtil
[JBoss-dev] jbpm-hsqldb-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-hsqldb-testsuite?log=log20060421041910 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:85: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:70: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 04/21/2006 04:19:10Time to build: 4 minutes 54 secondsLast changed: 04/20/2006 03:10:08Last log entry: seam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node Unit Tests: (268) Total Errors and Failures: (3)testSuspendorg.jbpm.graph.exe.SuspendAndResumeDbTesttestResumeorg.jbpm.graph.exe.SuspendAndResumeDbTest Modifications since last build: (first 50 of 144)1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionTextTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionXmlTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.24modifiedtbaeyenssrc/java.webapp/org/jbpm/webapp/bean/TaskBean.javacleaned import1.8modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/svc/ServicesTest.javacleaned import1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javacleaned import1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmladded logging config test1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javaadded logging config1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javabranches: 1.1.2;finished configuration updates1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmlbranches: 1.1.2;finished configuration updates1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/TaskMailTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/test.mail.propertiesfinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mock/Jndi.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationDbTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbPojoTests.javafinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbServiceNoTxTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryDbTest.javafinished configuration updates1.4deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/taskmgmt/exe/TaskMgmtExeDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/taskmgmt/exe/TaskVariableAccessDbTest.javafinished configuration updates1.4modifiedtbaeyenssrc/userguide/en/modules/mail.xmlfinished configuration updates1.2modifiedtbaeyenssrc/resources/starters-kit/jbpm-designer/designer.batseparated cd from start1.2modifiedtbaeyenssrc/resources/jbpm-identity.jar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/resources/jbpm.jar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/resources/jbpm.sar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockConnection.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockSession.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockSessionFactory.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockTransaction.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbServiceNoTxTest.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbServiceTest.javaadded persistence db
Re: [JBoss-dev] JTA / JTS question
No, there's no guaranteed order (it can be different between transaction instances and between commit phases). None of the standards provide for it (going back beyond X/Open), and in fact that's one of the reasons synchronizations were introduced as a separate protocol (to guarantee ordering). So JTA or JTS won't help you here. However, if you want to look at JBossTransactions specifics, then that can help you: we give you full control over the ordering of participants. Mark. Tim Fox wrote: One of you transaction gurus may know the answer: If I enlist 2 (or more) XAResources into a JTA transaction. Transaction tx = tm.getTransaction(); tx.enlistResource(res1); tx.enlistResource(res2); Then I rollback the transaction, which causes rollback() to be called on each of the XAResources. Are there any guarantees on the order in which rollback() is called on the resources, or is this up to the transaction manager implementation? E.g. is rollback always called in the same order the resources were enlisted? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] head not compiling
That's me. Sorry. Fixed now. Bill Burke wrote: org/jboss/ejb/plugins/EntityInstanceCache.java I'm commenting out the line until someboyd who broke it fixes it. --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jbpm-oracle-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-oracle-testsuite?log=log20060421050152 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:100: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:70: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 04/21/2006 05:01:52Time to build: 84 minutes 48 secondsLast changed: 04/20/2006 03:10:08Last log entry: seam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node Unit Tests: (257) Total Errors and Failures: (7)testSuspendorg.jbpm.graph.exe.SuspendAndResumeDbTesttestResumeorg.jbpm.graph.exe.SuspendAndResumeDbTesttestTimerExecutionRepeatorg.jbpm.taskmgmt.exe.TaskTimerExecutionDbTesttestVarUpdateorg.jbpm.taskmgmt.exe.TaskVariableAccessDbTesttestTimerExecutionorg.jbpm.taskmgmt.exe.TaskTimerExecutionDbTesttestTaskNodeTimerExecutionorg.jbpm.taskmgmt.exe.TaskTimerExecutionDbTest Modifications since last build: (first 50 of 144)1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionTextTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionXmlTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.24modifiedtbaeyenssrc/java.webapp/org/jbpm/webapp/bean/TaskBean.javacleaned import1.8modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/svc/ServicesTest.javacleaned import1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javacleaned import1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmladded logging config test1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javaadded logging config1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javabranches: 1.1.2;finished configuration updates1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmlbranches: 1.1.2;finished configuration updates1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/TaskMailTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/test.mail.propertiesfinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mock/Jndi.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationDbTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbPojoTests.javafinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbServiceNoTxTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryDbTest.javafinished configuration updates1.4deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/taskmgmt/exe/TaskMgmtExeDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/taskmgmt/exe/TaskVariableAccessDbTest.javafinished configuration updates1.4modifiedtbaeyenssrc/userguide/en/modules/mail.xmlfinished configuration updates1.2modifiedtbaeyenssrc/resources/starters-kit/jbpm-designer/designer.batseparated cd from start1.2modifiedtbaeyenssrc/resources/jbpm-identity.jar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/resources/jbpm.jar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/resources/jbpm.sar/manifest.mfbuilding the repository jars (with manifests and without version in filename)1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockConnection.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockSession.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockSessionFactory.javaadded persistence db service testing1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/MockTransaction.javaadded persis
Re: [JBoss-dev] JTA / JTS question
Thanks. This means that if I create 2 JMS XASessions, enlist them in a global tx, then receive messages 1, 2, 3 with session 1, and messages 4, 5, 6 in session2, then rollback the global tx, the messages will end up back in the queue, but for some transaction managers the order in the queue will be 1, 2, 3, 4, 5, 6, but for others it might be 4, 5, 6, 1, 2, 3. I guess this doesn't matter since the JMS message order guarantee doesn't apply after rollback anyway, but good to know. I guess some users (wrongly) might expect messages to go back in the queue in the order they were consumed. Mark Little wrote: No, there's no guaranteed order (it can be different between transaction instances and between commit phases). None of the standards provide for it (going back beyond X/Open), and in fact that's one of the reasons synchronizations were introduced as a separate protocol (to guarantee ordering). So JTA or JTS won't help you here. However, if you want to look at JBossTransactions specifics, then that can help you: we give you full control over the ordering of participants. Mark. Tim Fox wrote: One of you transaction gurus may know the answer: If I enlist 2 (or more) XAResources into a JTA transaction. Transaction tx = tm.getTransaction(); tx.enlistResource(res1); tx.enlistResource(res2); Then I rollback the transaction, which causes rollback() to be called on each of the XAResources. Are there any guarantees on the order in which rollback() is called on the resources, or is this up to the transaction manager implementation? E.g. is rollback always called in the same order the resources were enlisted? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060421060831 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: 04/21/2006 06:08:31Time to build: 137 minutes 32 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (353) Total Errors and Failures: (30)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.nullstore.NullStoreCallbackTestCase(jboss_serialization)unknownorg.jboss.test.remoting.stream.StreamingTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transporter.TransporterTestCase(java_serialization)unknownorg.jboss.test.remoting.transporter.TransporterTestCase(jboss_serialization)testStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCase Modifications since last build: (first 50 of 2375)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.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javabranches: 1.5.4;JBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/r
Re: [JBoss-dev] JTA / JTS question
Yes, that's pretty much it. If you want to guarantee ordering you'll have to do it with some intelligent interface between transactional participants and the backend "datastore" (queue in this case). Or, use JBossTS ;-) Mark. Tim Fox wrote: Thanks. This means that if I create 2 JMS XASessions, enlist them in a global tx, then receive messages 1, 2, 3 with session 1, and messages 4, 5, 6 in session2, then rollback the global tx, the messages will end up back in the queue, but for some transaction managers the order in the queue will be 1, 2, 3, 4, 5, 6, but for others it might be 4, 5, 6, 1, 2, 3. I guess this doesn't matter since the JMS message order guarantee doesn't apply after rollback anyway, but good to know. I guess some users (wrongly) might expect messages to go back in the queue in the order they were consumed. Mark Little wrote: No, there's no guaranteed order (it can be different between transaction instances and between commit phases). None of the standards provide for it (going back beyond X/Open), and in fact that's one of the reasons synchronizations were introduced as a separate protocol (to guarantee ordering). So JTA or JTS won't help you here. However, if you want to look at JBossTransactions specifics, then that can help you: we give you full control over the ordering of participants. Mark. Tim Fox wrote: One of you transaction gurus may know the answer: If I enlist 2 (or more) XAResources into a JTA transaction. Transaction tx = tm.getTransaction(); tx.enlistResource(res1); tx.enlistResource(res2); Then I rollback the transaction, which causes rollback() to be called on each of the XAResources. Are there any guarantees on the order in which rollback() is called on the resources, or is this up to the transaction manager implementation? E.g. is rollback always called in the same order the resources were enlisted? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] synchronization on non-final fields warning
A given instance of JaasSecurityManager never has its domainCache reset. Its set only on creation of JaasSecurityManager by the JaasSecurityManagerService when a lookup does not have an existing binding. This cannot be seen from the given JaasSecurityManager code fragment though. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Marlow Sent: Thursday, April 20, 2006 6:36 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] synchronization on non-final fields warning The problem in the JaasSecurityManager class example below is that the domainCache variable itself needs to be protected with synchronization since its non-final (for all domainCache read/write operations.) It is not fine as one thread could be performing updateCache(Principal), meanwhile, another thread assigns a new value to domainCache. The thread performing updateCache, wouldn't have a consistent memory view of the new domainCache and also violates atomicity. --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060421092907 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: 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: 04/21/2006 09:29:07Time to build: 93 minutes 25 seconds Unit Tests: (1524) Total Errors and Failures: (8)testAll_RWLockorg.jboss.cache.aop.LocalConcurrentTesttestPutObjectGraphAndEvictorg.jboss.cache.aop.eviction.PojoEvictionTesttestMultipleRefenceorg.jboss.cache.aop.loader.FileCacheLoaderObjectGraphAopTesttestSimpleEvictionorg.jboss.cache.aop.eviction.AopLRUPolicyTesttestRemoveEvictionorg.jboss.cache.aop.eviction.AopLRUPolicyTesttestUpdateEvictionorg.jboss.cache.aop.eviction.AopLRUPolicyUpdateEvictionTesttestPojoEvictionorg.jboss.cache.aop.loader.BdbjeCacheLoaderTesttestPojoEvictionorg.jboss.cache.aop.loader.FileCacheLoaderAopTest Modifications since last build: (first 50 of 0)
[JBoss-dev] jbpm-sybase-testsuite Build Timed Out
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-sybase-testsuite?log=log20060421063019 BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 04/21/2006 06:30:19Time to build: Last changed: 04/20/2006 03:10:08Last log entry: seam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 68)1.30modifiedtbaeyenssrc/java.jbpm/org/jbpm/jpdl/xml/JpdlXmlReader.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.6modifiedtbaeyenssrc/java.jbpm/org/jbpm/jpdl/xml/JpdlXmlWriter.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/JbpmDefaultConfigTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/graph/def/ProcessDefinitionDbTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/graph/exe/TokenDbTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.5modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/graph/node/StartStateDbTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionTextTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tdd/AuctionXmlTest.javaseam pageflow update. Changed type of ProcessDefinition.startState from StartState to Node1.24modifiedtbaeyenssrc/java.webapp/org/jbpm/webapp/bean/TaskBean.javacleaned import1.8modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/svc/ServicesTest.javacleaned import1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javacleaned import1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmladded logging config test1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javaadded logging config1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/jcr/JcrDbTest.javacleaned import1.19modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/jbpm.test.cfg.xmlremoved duplicate default configurations1.12modifiedtbaeyenssrc/java.jbpm/org/jbpm/msg/Message.javacleaned import1.5modifiedtbaeyenssrc/java.jbpm/org/jbpm/mail/Mail.javafinished configuration updates1.14modifiedtbaeyenssrc/java.jbpm/org/jbpm/persistence/db/DbPersistenceService.javafinished configuration updates1.15modifiedtbaeyenssrc/java.jbpm/org/jbpm/taskmgmt/def/TaskController.javafinished configuration updates1.16modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/AllPojoTests.javafinished configuration updates1.18modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/jbpm.test.cfg.xmlfinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/jcr/JcrDbTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/jcr/jbpm.jcr.cfg.xmlfinished configuration updates1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/LoggingConfigDbTest.javabranches: 1.1.2;finished configuration updates1.1addedtbaeyenssrc/java.jbpm.test/org/jbpm/logging/exe/nologging.jbpm.cfg.xmlbranches: 1.1.2;finished configuration updates1.4modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/TaskMailTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mail/test.mail.propertiesfinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/mock/Jndi.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationDbTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceConfigurationTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbPojoTests.javafinished configuration updates1.3modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbServiceNoTxTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceDbTests.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceDbTest.javafinished configuration updates1.2modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryDbTest.javafinished configuration updates1.4deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceFactoryTest.javafinished configuration updates1.7deletedtbaeyenssrc/java.jbpm.test/org/jbpm/persistence/db/PersistenceServiceTest.javafinished configuration updates1.7modifiedtbaeyenssrc/java.jbpm.test/org/jbpm/tas
[JBoss-dev] jboss-serialization dependent on trove.jar
Jboss-serialization is now dependent on trove.jar. I used that to solve circular dependencies, and it was way better to use TIntObjectHashMap and TObjectIntHashMap. And jboss-serialization is included into /client/jboss-all.jar. So, what should I do before GA? Basically I have three options: I – Remove jboss-serialization.jar from /jboss-all. Since JMS is using it, I don’t know if this is a good idea, but I’m considering this option. II – add trove.jar into jboss-all. Sincie it’s a third-party, I don’t know if we want to do that. III – Keep as is now
RE: [JBoss-dev] jboss-serialization dependent on trove.jar
Sorry about the crappy HTML post. My bad. Same post again, sorry about the duplication. Jboss-serialization is now dependent on trove.jar. I used that to solve circular dependencies, and it was way better to use TIntObjectHashMap and TObjectIntHashMap. And jboss-serialization is included into /client/jboss-all.jar. So, what should I do before GA? Basically I have three options: I - Remove jboss-serialization.jar from /jboss-all. Since JMS is using it, I don't know if this is a good idea, but I'm considering this option. II - add trove.jar into jboss-all. Sincie it's a third-party, I don't know if we want to do that. III - Keep as is now --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Using the latest jbossws
Hi Julien/Chris If you need to check whether I bugfix works for you in jboss-4.0.x, please follow the process documented here: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstall cheers -thomas
[JBoss-dev] javassist version problem
I'm having trouble tracking down the cause of this javassist version
problem:
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.2.0.CR1,com
patibles
[EMAIL PROTECTED],
version=3.2.0.CR1}],component=null,importingCompone
[EMAIL PROTECTED]/aop
atts={projecthome=http://www.jboss.org/product
s/aop, licensetype=lgpl}
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop
version=1.3.6 isLocal=false [EMAIL PROTECTED]
output=
C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar
type=null}, A
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdpa
rty\jboss\aop\lib\jboss-aop-jdk50.jar type=null},
[EMAIL PROTECTED]
instrumentor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\plu
ggable-instrumentor.jar type=null},
[EMAIL PROTECTED]
ntor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jdk14-plugg
able-instrumentor.jar type=null},
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop-jd
k50-cli
ent.jar type=null},
[EMAIL PROTECTED] outpu
t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-pluggable
-instrum
entor.jar type=null}] module=null location=null},fileResolved=true}
[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
atts={pro
jecthome=http://sourceforge.net/projects/jboss,
licensetype=mozilla-1.0.1.txt} o
utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.1RC2
isLocal=fa
lse [EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.
0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
location=null}
BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:845: The following error
occurred wh
ile executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:121: A versioning
problem
exists:
Component: javassist is at version: 3.1RC2
but it is also required to be compatible with:
[EMAIL PROTECTED], version=3.2.0.CR1}]
by: jboss/aop
The problem is, I don't see what is referencing javassist version
3.1RC2. Its not jboss-aop 1.3.6.
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] javassist version problem
Is your build-thirdparty.xml and jboss/aop/component-info.xml defining
the javaassist version to be 3.2.0.CR1?
Looks like you may have multiple lines of javaassist definitions in your
build-thirdparty.xml
Scott M Stark wrote:
I'm having trouble tracking down the cause of this javassist version
problem:
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.2.0.CR1,com
patibles
[EMAIL PROTECTED],
version=3.2.0.CR1}],component=null,importingCompone
[EMAIL PROTECTED]/aop
atts={projecthome=http://www.jboss.org/product
s/aop, licensetype=lgpl}
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop
version=1.3.6 isLocal=false [EMAIL PROTECTED]
output=
C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar
type=null}, A
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdpa
rty\jboss\aop\lib\jboss-aop-jdk50.jar type=null},
[EMAIL PROTECTED]
instrumentor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\plu
ggable-instrumentor.jar type=null},
[EMAIL PROTECTED]
ntor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jdk14-plugg
able-instrumentor.jar type=null},
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop-jd
k50-cli
ent.jar type=null},
[EMAIL PROTECTED] outpu
t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-pluggable
-instrum
entor.jar type=null}] module=null location=null},fileResolved=true}
[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
atts={pro
jecthome=http://sourceforge.net/projects/jboss,
licensetype=mozilla-1.0.1.txt} o
utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.1RC2
isLocal=fa
lse [EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.
0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
location=null}
BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:845: The following error
occurred wh
ile executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:121: A versioning
problem
exists:
Component: javassist is at version: 3.1RC2
but it is also required to be compatible with:
[EMAIL PROTECTED], version=3.2.0.CR1}]
by: jboss/aop
The problem is, I don't see what is referencing javassist version
3.1RC2. Its not jboss-aop 1.3.6.
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] javassist version problem
It looks like it is something local to your workspace.
Does the following command yield any hits?
find thirdparty -name "component-info.xml" | xargs grep '3.1RC2'
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anil
Saldhana
Sent: Friday, April 21, 2006 4:20 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] javassist version problem
Is your build-thirdparty.xml and jboss/aop/component-info.xml defining
the javaassist version to be 3.2.0.CR1?
Looks like you may have multiple lines of javaassist definitions in your
build-thirdparty.xml
Scott M Stark wrote:
>I'm having trouble tracking down the cause of this javassist version
>problem:
>
>[synchronizeinfo] Checking currentComponentRef:
>ComponentRef{id=javassist,name=j
>avassist,filename=component-info.xml,location=null,version=3.2.0.CR1,co
m
>patibles
>[EMAIL PROTECTED],
>version=3.2.0.CR1}],component=null,importingCompone
>[EMAIL PROTECTED]/aop
>atts={projecthome=http://www.jboss.org/product
>s/aop, licensetype=lgpl}
>output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop
> version=1.3.6 isLocal=false
[EMAIL PROTECTED]
>output=
>C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar
>type=null}, A
>[EMAIL PROTECTED]
>output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdpa
>rty\jboss\aop\lib\jboss-aop-jdk50.jar type=null},
>[EMAIL PROTECTED]
>instrumentor.jar
>output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\plu
>ggable-instrumentor.jar type=null},
>[EMAIL PROTECTED]
>ntor.jar
>output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jdk14-plugg
>able-instrumentor.jar type=null},
>[EMAIL PROTECTED]
>
>output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop-j
d
>k50-cli
>ent.jar type=null},
>[EMAIL PROTECTED] outpu
>t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-pluggabl
e
>-instrum
>entor.jar type=null}] module=null location=null},fileResolved=true}
>[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
>atts={pro
>jecthome=http://sourceforge.net/projects/jboss,
>licensetype=mozilla-1.0.1.txt} o
>utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.1RC2
>isLocal=fa
>lse [EMAIL PROTECTED]
>output=C:\cvs\JBoss4.0\jboss-4.
>0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
>location=null}
>
>BUILD FAILED
>C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:845: The following error
>occurred wh
>ile executing this line:
>C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:121: A
versioning
>problem
> exists:
>Component: javassist is at version: 3.1RC2
> but it is also required to be compatible with:
>[EMAIL PROTECTED], version=3.2.0.CR1}]
> by: jboss/aop
>
>The problem is, I don't see what is referencing javassist version
>3.1RC2. Its not jboss-aop 1.3.6.
>
---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] javassist version problem
No, I only have one in build-thirdparty.xml: I think the error message really is saying that something else already wanted javassist 3.1RC2, but that aop wants 3.2.0.CR1. I'll have to look at the build code I guess. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anil Saldhana Sent: Friday, April 21, 2006 2:20 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] javassist version problem Is your build-thirdparty.xml and jboss/aop/component-info.xml defining the javaassist version to be 3.2.0.CR1? Looks like you may have multiple lines of javaassist definitions in your build-thirdparty.xml --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] javassist version problem
Yes that's it. I guess javassist has been updated and some component is referencing it before javassist itself has been synchronized? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel Loehr Sent: Friday, April 21, 2006 2:28 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] javassist version problem It looks like it is something local to your workspace. Does the following command yield any hits? find thirdparty -name "component-info.xml" | xargs grep '3.1RC2' Ruel Loehr JBoss QA - 512-342-7840 ext 2011 Yahoo: ruelloehr Skype: ruelloehr AOL: dokoruel --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] javassist version problem
It looks like whatever component in your workspace that is requiring javassist 3.1RC2 is out of date. I don't see any components that require it when I do a fresh checkout and build. I'm not sure how it is possible to get into a "partially" updated repository state though. I would make sure the build-thirdparty.xml is uptodate and give it another shot. If the issue still persists, perhaps there is some sort of timestamp issue?? Ruel Loehr JBoss QA - 512-342-7840 ext 2011 Yahoo: ruelloehr Skype: ruelloehr AOL: dokoruel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Friday, April 21, 2006 4:32 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] javassist version problem Yes that's it. I guess javassist has been updated and some component is referencing it before javassist itself has been synchronized? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel Loehr Sent: Friday, April 21, 2006 2:28 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] javassist version problem It looks like it is something local to your workspace. Does the following command yield any hits? find thirdparty -name "component-info.xml" | xargs grep '3.1RC2' Ruel Loehr JBoss QA - 512-342-7840 ext 2011 Yahoo: ruelloehr Skype: ruelloehr AOL: dokoruel --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] javassist version problem
The issue was that I had a pre-existing thirdparty with an old javassist and I think the synchronization was looking at other component dependencies before synchronizing javassist with the current build-thirdparty.xml which has a newer javassit. It might have been a timestamp problem. No point in looking into it really as maven2 is where we are going. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel Loehr Sent: Friday, April 21, 2006 2:48 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] javassist version problem It looks like whatever component in your workspace that is requiring javassist 3.1RC2 is out of date. I don't see any components that require it when I do a fresh checkout and build. I'm not sure how it is possible to get into a "partially" updated repository state though. I would make sure the build-thirdparty.xml is uptodate and give it another shot. If the issue still persists, perhaps there is some sort of timestamp issue?? Ruel Loehr JBoss QA - 512-342-7840 ext 2011 Yahoo: ruelloehr Skype: ruelloehr AOL: dokoruel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Friday, April 21, 2006 4:32 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] javassist version problem Yes that's it. I guess javassist has been updated and some component is referencing it before javassist itself has been synchronized? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel Loehr Sent: Friday, April 21, 2006 2:28 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] javassist version problem It looks like it is something local to your workspace. Does the following command yield any hits? find thirdparty -name "component-info.xml" | xargs grep '3.1RC2' Ruel Loehr JBoss QA - 512-342-7840 ext 2011 Yahoo: ruelloehr Skype: ruelloehr AOL: dokoruel --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jbossweb build.37 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060421220025Lbuild.37 BUILD COMPLETE - build.37Date of build: 04/21/2006 22:00:25Time to build: 10 minutes 43 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 0)
[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060421231027 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: 04/21/2006 23:10:27Time to build: 117 minutes 34 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (354) Total Errors and Failures: (31)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)unknownorg.jboss.test.remoting.stream.StreamingTestCase(java_serialization)unknownorg.jboss.test.remoting.stream.StreamingTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transporter.TransporterTestCase(java_serialization)unknownorg.jboss.test.remoting.transporter.TransporterTestCase(jboss_serialization)testStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCase Modifications since last build: (first 50 of 2377)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.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javabranches: 1.5.4;JBREM-235 - add
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060422011853 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: 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: 04/22/2006 01:18:53Time to build: 39 minutes 57 secondsLast changed: 04/22/2006 01:09:38Last log entry: Add jboss-serialization.jar to classpath Unit Tests: (1558) Total Errors and Failures: (8)testAll_RWLockorg.jboss.cache.aop.LocalConcurrentTesttestMultipleRefenceorg.jboss.cache.aop.loader.FileCacheLoaderObjectGraphAopTesttestSharedCacheLoadingWithReplicationorg.jboss.cache.optimistic.OptimisticWithCacheLoaderTesttestSimpleEvictionorg.jboss.cache.aop.eviction.AopLRUPolicyTesttestRemoveEvictionorg.jboss.cache.aop.eviction.AopLRUPolicyTesttestUpdateEvictionorg.jboss.cache.aop.eviction.AopLRUPolicyUpdateEvictionTesttestPojoEvictionorg.jboss.cache.aop.loader.BdbjeCacheLoaderTesttestPojoEvictionorg.jboss.cache.aop.loader.FileCacheLoaderAopTest Modifications since last build: (first 50 of 514)1.1addedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransfer140Test.java[JBCACHE-537] Exclude _BUDDY_BACKUP_ from state transfer1.8modifiedbwangtests/scripts/bench.txtupd with additional lib1.2modifiedbwangtests/scripts/benchmark-pojocache.shupd with additional lib1.8modifiedbwangtests/scripts/benchmark.shupd with additional lib1.7modifiedbwangtests/scripts/readme.txtupd with additional lib1.2modifiedbwangtests/perf/org/jboss/cache/data/Student.javaJBCACHE-574 Optimize PojoCache in LOCAL mode: use _removeObject in switched to using List instead of Set.1.30modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.1addedbwangtests/scripts/benchmark-pojocache.shadded1.6modifiedbwangtests/scripts/readme.txtadded1.1addedbwangtests-50/functional/org/jboss/cache/aop/ReplicatedAnnotationAopTest.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/Address.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/Gadget.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/Link.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkAdmin.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkDomain.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkElement.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkNode.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/NodeManager.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/Person.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/Resource.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/SerializedAddress.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/SpecialAddress.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/Student.javaJBCACHE-451 & JBCACHE-454 @Transient and @Serializable support.1.7modifiedbwangtests/scripts/benchmark.shupd1.29modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.28modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.27modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.26modifiedbwangtests/perf/org/jboss/cache/Server.javaNeed to keep generate new pojo during putObject1.25modifiedbwangtests/perf/org/jboss/cache/Server.javacommented out output1.5modifiedbwangtests/scripts/readme.txtupd1.5modifiedbwangtests/scripts/bench.xmlupd1.4modifiedbwangtests/scripts/readme.txtupd1.24modifiedbwangtests/perf/org/jboss/cache/Server.javaAdded PojoCache tester1.2modifiedbwangtests/perf/org/jboss/cache/data/Address.javaAdded PojoCache tester1.2modifiedbwangtests/perf/org/jboss/cache/data/Course.javaAdded PojoCache tester1.2modifiedbwangtests/perf/org/jboss/cache/data/Person.javaAdded PojoCache tester1.7modifiedbwangtests/scripts/bench.txtAdded PojoCache test1.4modifiedbwangtests/scripts/bench.xmlAdded PojoCache test1.6modifiedbwangtests/scripts/benchma
