[JBoss-dev] [ jboss-Feature Requests-780043 ] EJB-QL to traverse CMR with different datasources
Feature Requests item #780043, was opened at 2003-07-30 09:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376688aid=780043group_id=22866 Category: JBossCMP Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ionel GARDAIS (ze_ioio) Assigned to: Nobody/Anonymous (nobody) Summary: EJB-QL to traverse CMR with different datasources Initial Comment: This feature will allow EJB-QL and JBOSS-QL queries to traverse relationship when beans on each CMR side have differents datasources. i.e : Bean A w/ datasource dsA Bean B w/ datasource dsB By now using BeanB inside BeanA works but a query that uses the relationship between these two beans fails. The exception thrown complains that BeanB's table is not present under dsA. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376688aid=780043group_id=22866 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-779351 ] HA-JNDI broken without autodiscovery
Bugs item #779351, was opened at 2003-07-29 05:26 Message generated for change (Settings changed) made by slaboure You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=779351group_id=22866 Category: Clustering Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: Rob Dickinson (rob_dickinson) Assigned to: Sacha Labourey (slaboure) Summary: HA-JNDI broken without autodiscovery Initial Comment: There appears to be a design flaw in HA-JNDI present in multiple versions of 3.0x and 3.2.1. This has been observed on Windows 2000/XP and several Linux distributions. I've tested under Java 1.4.1 and 1.4.2, but I do not believe it is JDK specific. When a list of urls is given to an InitialContext (disabling autodiscovery) there are cases where node events are never recognized by a client. Often the client JVM must be restarted in order to use valid partition nodes that would otherwise be found via discovery. The test case works perfectly if autodiscovery is enabled (so does not affect everyone). However, the defect is easily reproducible and a serious issue with HA- JNDI in situations where multicasts are not allowed. THE TEST CASE The HA-JNDI defect can be exposed with only a simple client. No server configuration changes are needed. The client repeatedly connects to the HA-JNDI service and performs a lookup on a system service (the DefaultPartition). (The full code for the test case is attached.) REPRODUCING THE PROBLEM 1. Run the client so it's polling. (see build.xml) 2. Start up JBoss... 3. Now the client will start working. 4. Shut down JBoss... 5. Now the client will start throwing exceptions. 6. Start up JBoss... 7. The client sees a stream of 'Service unavailable' exceptions (reproduced in trace.txt file) until the GC runs or the JVM is restarted. If autodiscovery is enabled you may see this exception a few times, but eventually the client will give up and use a multicast to find the server. If you use a cluster, you can produce more sophisticated variations. Failing the last node to join is a sure way to create client problems. WHAT'S THE WORKAROUND? The problem is that the NamingService implementation caches remote stubs, building an internal collection of stubs keyed on host and port. Only the first version of a stub from any given address is used (there is no way apart from discovery or a successful JNDI call to flush the local copy). These stubs are stored as WeakReferences, so they are cleared by the garbage collector (when it decides to run). Clients with frequent GC runs will experience fewer problems than those that do not. If you never call the GC, you may never be able to contact the HA services. Calling the GC directly, while certainly problematic on some JVMs and not very deterministic, does seem to provide a totally practical, although totally evil workaround. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=779351group_id=22866 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] www.cogito-info.com
Title: March 12, 2003 Not interested in our TrafficMagnet service? To be taken off our mailing list, please follow the instructions here.
[JBoss-dev] [ jboss-Bugs-780204 ] Verifier failing due to UCL scope
Bugs item #780204, was opened at 2003-07-30 13:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=780204group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jim Cook (oravecz) Assigned to: Nobody/Anonymous (nobody) Summary: Verifier failing due to UCL scope Initial Comment: I have two ear files, EAR1 and EAR2 and both contain EJB1 and EJB2 respectively. EJB2 makes a call to EJB1, and to facilitate this call EJB2 contains the classes it needs to access EJB1. These classes include the Home and Remote interfaces and any objects used as parameters or return values. These classes are also bundled in EAR1 since it needs these files to deploy and execute. This is a typicial setup for us, and the EARs are packaged according to J2EE standards, and deployed in this manner with jBoss 2.4.6. I am now deploying to jBoss 3.2.2RC2, and I am getting errors from the container. The errors are caused by the new UCL. The workaround is to remove duplicate classes from the two EAR files, but this should not be necessary. Steps == 1. Deploy the two EAR files. All of the classes are part of the same UCL repository since we do not specify any scoping using jboss-app.xml. Because the same class cannot appear multiple times in the repository, the server gives us warning regarding duplicate classes at deployment time. This is expected behavior and shouldn't affect the runtime usage of our beans. 2. However, the Verifier complains: Warning: The methods defined in the remote interface must have a matching method in the Bean's class with the same return type. Perhaps there is a bug in the Verifier? 3. Even though the verifier failed, setting the EJBDeployer's StrictVerifier to false allows the beans to deploy, and the unit tests execute properly. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=780204group_id=22866 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-780204 ] Verifier failing due to UCL scope
Bugs item #780204, was opened at 2003-07-30 06:10 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=780204group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jim Cook (oravecz) Assigned to: Scott M Stark (starksm) Summary: Verifier failing due to UCL scope Initial Comment: I have two ear files, EAR1 and EAR2 and both contain EJB1 and EJB2 respectively. EJB2 makes a call to EJB1, and to facilitate this call EJB2 contains the classes it needs to access EJB1. These classes include the Home and Remote interfaces and any objects used as parameters or return values. These classes are also bundled in EAR1 since it needs these files to deploy and execute. This is a typicial setup for us, and the EARs are packaged according to J2EE standards, and deployed in this manner with jBoss 2.4.6. I am now deploying to jBoss 3.2.2RC2, and I am getting errors from the container. The errors are caused by the new UCL. The workaround is to remove duplicate classes from the two EAR files, but this should not be necessary. Steps == 1. Deploy the two EAR files. All of the classes are part of the same UCL repository since we do not specify any scoping using jboss-app.xml. Because the same class cannot appear multiple times in the repository, the server gives us warning regarding duplicate classes at deployment time. This is expected behavior and shouldn't affect the runtime usage of our beans. 2. However, the Verifier complains: Warning: The methods defined in the remote interface must have a matching method in the Bean's class with the same return type. Perhaps there is a bug in the Verifier? 3. Even though the verifier failed, setting the EJBDeployer's StrictVerifier to false allows the beans to deploy, and the unit tests execute properly. -- Comment By: Scott M Stark (starksm) Date: 2003-07-30 09:15 Message: Logged In: YES user_id=175228 It was a problem with the scheduling of the load of the duplicate class in the presence of recursion to resolve classes referenced by the us.oh.state.dot.common.ejb.uid.UIDObject. This has been fixed for 3.2.2. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=780204group_id=22866 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-July-2003
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-July-2003 JBoss daily test results SUMMARY Number of tests run: 1462 Successful tests: 1454 Errors:6 Failures: 2 [time of test: 2003-07-30.18-34 GMT] [java.version: 1.4.2] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2-b28] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-9smp] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2003-07-30.18-34 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: MissingClassUnitTestCase Test:testDeployServiceWithoutClass Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: SecurityUnitTestCase Test:testSecureHttpInvoker Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: JSR77SpecUnitTestCase Test:testNotificationDeliver Type:failure Exception: junit.framework.AssertionFailedError Message: Not enough notifications received: 0 - Suite: JSR77SpecUnitTestCase Test:testNavigation Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar is not registered. - --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-779797 ] no bindaddress configuration for RMI JNDI
Bugs item #779797, was opened at 2003-07-29 12:19 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=779797group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Bill Burke (patriot1burke) Assigned to: Scott M Stark (starksm) Summary: no bindaddress configuration for RMI JNDI Initial Comment: There is no way to define the BindAddress for the RMI server object of the Naming service. -- Comment By: Scott M Stark (starksm) Date: 2003-07-30 14:29 Message: Logged In: YES user_id=175228 I was working around here so I fixed this. There is now an rmiBindAddress for the RMI Naming service. This will default to the bindAddress attribute as well so specifying a bindAddress for the jnp bootstrap socket will also set the RMI bind address unless overriden by the rmiBindAddress. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=779797group_id=22866 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-779797 ] no bindaddress configuration for RMI JNDI
Bugs item #779797, was opened at 2003-07-29 12:19 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=779797group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Bill Burke (patriot1burke) Assigned to: Scott M Stark (starksm) Summary: no bindaddress configuration for RMI JNDI Initial Comment: There is no way to define the BindAddress for the RMI server object of the Naming service. -- Comment By: Scott M Stark (starksm) Date: 2003-07-30 16:21 Message: Logged In: YES user_id=175228 I was working around here so I fixed this. There is now an rmiBindAddress for the RMI Naming service. This will default to the bindAddress attribute as well so specifying a bindAddress for the jnp bootstrap socket will also set the RMI bind address unless overriden by the rmiBindAddress. -- Comment By: Scott M Stark (starksm) Date: 2003-07-30 14:29 Message: Logged In: YES user_id=175228 I was working around here so I fixed this. There is now an rmiBindAddress for the RMI Naming service. This will default to the bindAddress attribute as well so specifying a bindAddress for the jnp bootstrap socket will also set the RMI bind address unless overriden by the rmiBindAddress. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=779797group_id=22866 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 4.609 sec [junit] Running org.jboss.test.jca.test.ReentrantUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 33.015 sec [junit] Running org.jboss.test.jca.test.UserTxUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 30.297 sec [junit] Running org.jboss.test.jca.test.WrapperSQLUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 7.797 sec [junit] Running org.jboss.test.jca.test.XAExceptionUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 29.954 sec [junit] Running org.jboss.test.jca.test.XAResourceUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 3.188 sec [junit] Running org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 11.218 sec [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 24.234 sec [junit] TEST org.jboss.test.jmsra.test.RaQueueUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 6.11 sec [junit] TEST org.jboss.test.jmsra.test.RaSyncRecUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 4.844 sec [junit] TEST org.jboss.test.jmsra.test.RaTopicUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.CPManifestUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 25.234 sec [junit] Running org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 15.031 sec [junit] TEST org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.DeployServiceUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 11.14 sec [junit] Running org.jboss.test.jmx.test.DeployXMBeanUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 4.281 sec [junit] Running org.jboss.test.jmx.test.EarDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 19.468 sec [junit] Running org.jboss.test.jmx.test.EjbDependencyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.5 sec [junit] Running org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.359 sec [junit] TEST org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.JavaBeanURIResolverUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.922 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnEJBUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.953 sec [junit] Running org.jboss.test.jmx.test.MissingClassUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.094 sec [junit] Running org.jboss.test.jmx.test.ServiceRsrcsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.25 sec [junit] Running org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 20.765 sec [junit] Running org.jboss.test.jmx.test.UnpackedDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 12.047 sec [junit] Running org.jboss.test.jrmp.test.CustomSocketsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 34.484 sec [junit] TEST org.jboss.test.jrmp.test.CustomSocketsUnitTestCase FAILED [junit] Running org.jboss.test.lock.test.SpinUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 49.61 sec [junit] Running org.jboss.test.mdb.test.MDBUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 2, Time elapsed: 29.125 sec [junit] TEST org.jboss.test.mdb.test.MDBUnitTestCase FAILED [junit] Running org.jboss.test.naming.test.EjbLinkUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 15.718 sec [junit] Running org.jboss.test.naming.test.ENCUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 67.828 sec [junit] Running org.jboss.test.naming.test.ExternalContextUnitTestCase
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: 96 % ( 784 / 815 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 815 Successful tests: 784 Errors:24 Failures: 7 [time of test: 2003-07-31.00-22 GMT] [java.version: 1.4.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] See http://jboss1.kimptoc.net/winxp/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: RemotingUnitTestCase Test:testClusteredRemotingDT2(org.jboss.test.aop.test.RemotingUnitTestCase) Type:error Exception: org.jboss.tm.JBossRollbackException Message: Unable to commit, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=2c571170edfbf9c6x73a7abxf6b583d790x-7fff/101, BranchQual=2c571170edfbf9c6x73a7abxf6b583d790x-7fff/] status=STATUS_ROLLEDBACK; - nested throwable: (java.lang.RuntimeException: Unexpected exception in commit of xid: XidImpl [FormatId=257, GlobalId=2c571170edfbf9c6x73a7abxf6b583d790x-7fff/101, BranchQual=2c571170edfbf9c6x73a7abxf6b583d790x-7fff/1], exception: java.lang.RuntimeException: Error processing InternalInvocation. Unable to process method commit) - Suite: ByHandUnitTestCase Test:java.net.MalformedURLException: unknown protocol: f Type:error Exception: java.net.MalformedURLException Message: unknown protocol: f - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - Suite: IndependentJarsUnitTestCase Test:testInterJarCall(org.jboss.test.cts.test.IndependentJarsUnitTestCase) Type:error Exception: java.rmi.ServerException Message: Unexpected errornull - Suite: IndependentJarsUnitTestCase Test: testCallByValueInSameJar(org.jboss.test.cts.test.IndependentJarsUnitTestCase) Type:error Exception: java.rmi.ServerException Message: Unexpected errornull - ===Thu Jul 31 02:15:42 GMTDT 2003 ===CYGWIN_NT-5.1 quarks2 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version 1.4.1_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02) Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode) --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === [junit] Running org.jboss.test.jca.test.DeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.111 sec [junit] Running org.jboss.test.jca.test.JCA15AdapterUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.355 sec [junit] Running org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 14.529 sec [junit] Running org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 15.933 sec [junit] TEST org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase FAILED [junit] Running org.jboss.test.jca.test.MessageEndpointUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 6.931 sec [junit] Running org.jboss.test.jca.test.ReentrantUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 17.636 sec [junit] Running org.jboss.test.jca.test.UserTxUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 14.817 sec [junit] Running org.jboss.test.jca.test.WrapperSQLUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.832 sec [junit] Running org.jboss.test.jca.test.XAExceptionUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 26.98 sec [junit] Running org.jboss.test.jca.test.XAResourceUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.868 sec [junit] Running org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 4.79 sec [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 4.494 sec [junit] TEST org.jboss.test.jmsra.test.RaQueueUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.839 sec [junit] TEST org.jboss.test.jmsra.test.RaSyncRecUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 8.34 sec [junit] TEST org.jboss.test.jmsra.test.RaTopicUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.CPManifestUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 13.352 sec [junit] Running org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 11.027 sec [junit] TEST org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.DeployServiceUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 14.085 sec [junit] Running org.jboss.test.jmx.test.DeployXMBeanUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 7.848 sec [junit] Running org.jboss.test.jmx.test.EarDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13.547 sec [junit] Running org.jboss.test.jmx.test.EjbDependencyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 9.06 sec [junit] Running org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 6.092 sec [junit] TEST org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.JavaBeanURIResolverUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.243 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.046 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnEJBUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.839 sec [junit] Running org.jboss.test.jmx.test.MissingClassUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.863 sec [junit] Running org.jboss.test.jmx.test.ServiceRsrcsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.061 sec [junit] Running org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 29.982 sec [junit] Running org.jboss.test.jmx.test.UnpackedDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 14.814 sec [junit] Running org.jboss.test.jrmp.test.CustomSocketsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 11.459 sec [junit] TEST
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 96 % ( 784 / 815 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 815 Successful tests: 784 Errors:25 Failures: 6 [time of test: 2003-07-31.01-15 GMT] [java.version: 1.4.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-18.7] See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: RemotingUnitTestCase Test:testClusteredRemotingDT2(org.jboss.test.aop.test.RemotingUnitTestCase) Type:error Exception: org.jboss.tm.JBossRollbackException Message: Unable to commit, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf6b5bbbffax-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf6b5bbbffax-7fff/] status=STATUS_ROLLEDBACK; - nested throwable: (java.lang.RuntimeException: Unexpected exception in commit of xid: XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf6b5bbbffax-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf6b5bbbffax-7fff/1], exception: java.lang.RuntimeException: Error processing InternalInvocation. Unable to process method commit) - Suite: Scheduler2UnitTestCase Test:testXMLScheduleProvider(org.jboss.test.util.test.Scheduler2UnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Not enough or too many (19) hits received: 10 - Suite: ByHandUnitTestCase Test:java.net.MalformedURLException: no protocol: /home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/jbossdo-byhand.jar Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/jbossdo-byhand.jar - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - Suite: IndependentJarsUnitTestCase Test:testInterJarCall(org.jboss.test.cts.test.IndependentJarsUnitTestCase) Type:error Exception: java.rmi.ServerException Message: Unexpected errornull - ===Thu Jul 31 02:24:10 BST 2003 ===Linux nog 2.4.20-18.7 #1 Thu May 29 08:32:50 EDT 2003 i686 unknown ===java version 1.4.1_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02) Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode) --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
