[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 95 % ( 780 / 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: 780 Errors:27 Failures: 8 [time of test: 2003-07-26.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=11d1def534ea1be0x123b25cxf69bfbe334x-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf69bfbe334x-7fff/] status=STATUS_ROLLEDBACK; - nested throwable: (java.lang.RuntimeException: Unexpected exception in commit of xid: XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf69bfbe334x-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf69bfbe334x-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: TransientMBeanUnitTestCase Test:testPutTx(org.jboss.test.cache.test.trans.TransientMBeanUnitTestCase) Type:error Exception: java.rmi.ServerException Message: EJBException:; nested exception is: javax.ejb.EJBException: Application Error: tried to enter Stateful bean with different tx context, contextTx: TransactionImpl:XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf69bfbe334x-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf69bfbe334x-7fff/1], methodTx: null - Suite: TransientMBeanUnitTestCase Test:testRollbackTx(org.jboss.test.cache.test.trans.TransientMBeanUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: MBeanException: org.jboss.cache.LockingException: IdentityLock.attempt(); - nested throwable: (java.lang.InterruptedException) Cause: org.jboss.cache.LockingException: IdentityLock.attempt(); - nested throwable: (java.lang.InterruptedException) - Suite: TransientTreeCacheLockingUnitTestCase Test: testConcurrentAccess(org.jboss.test.cache.test.trans.TransientTreeCacheLockingUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: org.jboss.cache.TimeoutException: IdentityLock.acquireReadLock(): lock could not be acquired after 1ms (lock is owned by null) - 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 - ===Sat Jul 26 02:23:06 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-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: 5.884 sec [junit] Running org.jboss.test.jca.test.JCA15AdapterUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.159 sec [junit] Running org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 12.866 sec [junit] Running org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 16.518 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: 7.338 sec [junit] Running org.jboss.test.jca.test.ReentrantUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 16.698 sec [junit] Running org.jboss.test.jca.test.UserTxUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 19.398 sec [junit] Running org.jboss.test.jca.test.WrapperSQLUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.794 sec [junit] Running org.jboss.test.jca.test.XAExceptionUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 15.919 sec [junit] Running org.jboss.test.jca.test.XAResourceUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 1.02 sec [junit] Running org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 5.602 sec [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.817 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.814 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: 3.878 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.182 sec [junit] Running org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 13.224 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.149 sec [junit] Running org.jboss.test.jmx.test.DeployXMBeanUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 6.943 sec [junit] Running org.jboss.test.jmx.test.EarDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 19.721 sec [junit] Running org.jboss.test.jmx.test.EjbDependencyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 9.272 sec [junit] Running org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 6.132 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: 5.113 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.311 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnEJBUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 11.844 sec [junit] Running org.jboss.test.jmx.test.MissingClassUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.344 sec [junit] Running org.jboss.test.jmx.test.ServiceRsrcsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.031 sec [junit] Running org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 21.472 sec [junit] Running org.jboss.test.jmx.test.UnpackedDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 15.145 sec [junit] Running org.jboss.test.jrmp.test.CustomSocketsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 11.883 sec [junit] T
[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: 10, Failures: 0, Errors: 0, Time elapsed: 3.414 sec [junit] Running org.jboss.test.cache.test.LockMapUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.003 sec [junit] Running org.jboss.test.cache.test.ReadWriteLockWithUpgradeUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.822 sec [junit] Running org.jboss.test.cache.test.replicated.ReplicatedTxUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 26.033 sec [junit] Running org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 16.025 sec [junit] Running org.jboss.test.cache.test.trans.TransientMBeanUnitTestCase [junit] Tests run: 4, Failures: 1, Errors: 1, Time elapsed: 12.265 sec [junit] TEST org.jboss.test.cache.test.trans.TransientMBeanUnitTestCase FAILED [junit] Running org.jboss.test.cache.test.trans.TransientTreeCacheLockingUnitTestCase [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 22.306 sec [junit] TEST org.jboss.test.cache.test.trans.TransientTreeCacheLockingUnitTestCase FAILED [junit] Running org.jboss.test.cache.test.trans.TransientTreeCacheUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.193 sec [junit] Running org.jboss.test.cache.test.trans.TransientUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 2.632 sec [junit] Running org.jboss.test.classloader.test.CircularityUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 2.883 sec [junit] Running org.jboss.test.classloader.test.ClasspathExtensionUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.851 sec [junit] Running org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 4.261 sec [junit] Running org.jboss.test.cmp.ejbql.EJBQL20CompilerUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.707 sec [junit] Running org.jboss.test.cmp.ejbql.EJBQL20ParserUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.394 sec [junit] Running org.jboss.test.cmp.ejbql.EJBQL20toSQL92UnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 1.691 sec [junit] Running org.jboss.test.cmp.jbossdo.byhand.ByHandUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 0.11 sec [junit] TEST org.jboss.test.cmp.jbossdo.byhand.ByHandUnitTestCase FAILED [junit] Running org.jboss.test.cmp.jbossdo.collection.CollectionUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 8.004 sec [junit] Running org.jboss.test.cmp.jbossdo.complextypes.ComplexTypesUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.321 sec [junit] Running org.jboss.test.cmp.jbossdo.extent.ExtentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.211 sec [junit] Running org.jboss.test.cmp.jbossdo.identity.IdentityUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.112 sec [junit] Running org.jboss.test.cmp.jbossdo.instancecallbacks.InstanceCallbacksUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.211 sec [junit] Running org.jboss.test.cmp.jbossdo.jdoql.JDOQLCompilerUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.363 sec [junit] Running org.jboss.test.cmp.jbossdo.jdoql.JDOQLParserUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.206 sec [junit] Running org.jboss.test.cmp.jbossdo.jdoql.JDOQLtoSQL92UnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.284 sec [junit] Running org.jboss.test.cmp.jbossdo.maketransient.MakeTransientUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.653 sec [junit] Running org.jboss.test.cmp.jbossdo.one2onebi.BiOne2OneUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.853 sec [junit] Running org.jboss.test.cmp.jbossdo.one2oneuni.UniOne2OneUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 4.104 sec [junit] Running org.jboss.test.cmp.jbossdo.query.QueryUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.665 sec [junit] Running org.jboss.test.cmp.jbossdo.state.PersistentStateTransitionEventUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 1.112 sec [junit] Running org.jboss.test.cmp.jbossdo.state.Persisten
[JBoss-dev] [AUTOMATED] JBoss (Branch_3_2/winxp) Testsuite Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === init: compile-classes: [mkdir] Created dir: F:\jboss\jboss-head\compatibility\output\classes [javac] Compiling 1 source file to F:\jboss\jboss-head\compatibility\output\classes compile: most: == == Finished with 'most' in module 'compatibility'. == _module-compatibility-most: make-compat: check-compat: modules-most: partition-build: [move] Moving 37 files to F:\jboss\jboss-head\build\output\testbuild\server\all\lib [mkdir] Created dir: F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\management [move] Moving 3 files to F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\management [mkdir] Created dir: F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jms [move] Moving 12 files to F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jms [delete] Deleting directory F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossmq-httpil.sar [copy] Copying 185 files to F:\jboss\jboss-head\build\output\testbuild\server\default [delete] Deleting 4 files from F:\jboss\jboss-head\build\output\testbuild\server\default\lib [delete] Deleting 25 files from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy [delete] Deleted 18 directories from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy [delete] Deleting 17 files from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy\jboss-net.sar [delete] Deleted 7 directories from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy\jboss-net.sar [delete] Deleting 1 files from F:\jboss\jboss-head\build\output\testbuild\server\default\conf [delete] Deleting directory F:\jboss\jboss-head\build\output\testbuild\server\default\deploy\deploy.last [mkdir] Created dir: F:\jboss\jboss-head\build\output\testbuild\server\minimal\deploy [copy] Copying 3 files to F:\jboss\jboss-head\build\output\testbuild\server\minimal\conf [move] Moving 1 files to F:\jboss\jboss-head\build\output\testbuild\server\minimal\conf [copy] Copying 4 files to F:\jboss\jboss-head\build\output\testbuild\server\minimal\lib [copy] Copying 1 file to F:\jboss\jboss-head\build\output\testbuild\server\minimal\deploy [copy] Copying 1 file to F:\jboss\jboss-head\build\output\testbuild\server\minimal\lib [mkdir] Created dir: F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\concurrent.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-common-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-iiop-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-j2ee.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-jsr77-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-net-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-system-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-transaction-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbossha-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbossmq-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbossmqha.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbosssx-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jmx-connector-client-factory.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jmx-ejb-connector-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jmx-invoker-adaptor-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbu
[JBoss-dev] [AUTOMATED] JBoss (Branch_3_2/winxp) Testsuite Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === init: compile-classes: [mkdir] Created dir: F:\jboss\jboss-head\compatibility\output\classes [javac] Compiling 1 source file to F:\jboss\jboss-head\compatibility\output\classes compile: most: == == Finished with 'most' in module 'compatibility'. == _module-compatibility-most: make-compat: check-compat: modules-most: partition-build: [move] Moving 37 files to F:\jboss\jboss-head\build\output\testbuild\server\all\lib [mkdir] Created dir: F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\management [move] Moving 3 files to F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\management [mkdir] Created dir: F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jms [move] Moving 12 files to F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jms [delete] Deleting directory F:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossmq-httpil.sar [copy] Copying 185 files to F:\jboss\jboss-head\build\output\testbuild\server\default [delete] Deleting 4 files from F:\jboss\jboss-head\build\output\testbuild\server\default\lib [delete] Deleting 25 files from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy [delete] Deleted 18 directories from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy [delete] Deleting 17 files from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy\jboss-net.sar [delete] Deleted 7 directories from F:\jboss\jboss-head\build\output\testbuild\server\default\deploy\jboss-net.sar [delete] Deleting 1 files from F:\jboss\jboss-head\build\output\testbuild\server\default\conf [delete] Deleting directory F:\jboss\jboss-head\build\output\testbuild\server\default\deploy\deploy.last [mkdir] Created dir: F:\jboss\jboss-head\build\output\testbuild\server\minimal\deploy [copy] Copying 3 files to F:\jboss\jboss-head\build\output\testbuild\server\minimal\conf [move] Moving 1 files to F:\jboss\jboss-head\build\output\testbuild\server\minimal\conf [copy] Copying 4 files to F:\jboss\jboss-head\build\output\testbuild\server\minimal\lib [copy] Copying 1 file to F:\jboss\jboss-head\build\output\testbuild\server\minimal\deploy [copy] Copying 1 file to F:\jboss\jboss-head\build\output\testbuild\server\minimal\lib [mkdir] Created dir: F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\concurrent.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-common-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-iiop-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-j2ee.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-jsr77-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-net-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-system-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jboss-transaction-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbossha-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbossmq-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbossmqha.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jbosssx-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jmx-connector-client-factory.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jmx-ejb-connector-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbuild\client\jmx-invoker-adaptor-client.jar into F:\jboss\jboss-head\build\build [unjar] Expanding: F:\jboss\jboss-head\build\output\testbu
[JBoss-dev] [AUTOMATED] JBoss (Branch_3_2/linux1) Testsuite Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === init: compile-classes: [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/compatibility/output/classes [javac] Compiling 1 source file to /home/jbossci/jbossci/jboss-head/compatibility/output/classes compile: most: == == Finished with 'most' in module 'compatibility'. == _module-compatibility-most: make-compat: check-compat: modules-most: partition-build: [move] Moving 37 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/lib [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/management [move] Moving 3 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/management [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/jms [move] Moving 12 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/jms [delete] Deleting directory /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/jbossmq-httpil.sar [copy] Copying 185 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default [delete] Deleting 4 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/lib [delete] Deleting 25 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy [delete] Deleted 18 directories from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy [delete] Deleting 17 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy/jboss-net.sar [delete] Deleted 7 directories from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy/jboss-net.sar [delete] Deleting 1 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/conf [delete] Deleting directory /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy/deploy.last [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/deploy [copy] Copying 3 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/conf [move] Moving 1 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/conf [copy] Copying 4 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/lib [copy] Copying 1 file to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/deploy [copy] Copying 1 file to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/lib [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-common-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-system-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-j2ee.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jnp-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-transaction-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-invoker-adaptor-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-ejb-connector-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-connector-client-factory.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-rmi-connector-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/concurrent.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jbosssx-client.jar into /home/jbossci/jbo
[JBoss-dev] [AUTOMATED] JBoss (Branch_3_2/linux1) Testsuite Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === init: compile-classes: [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/compatibility/output/classes [javac] Compiling 1 source file to /home/jbossci/jbossci/jboss-head/compatibility/output/classes compile: most: == == Finished with 'most' in module 'compatibility'. == _module-compatibility-most: make-compat: check-compat: modules-most: partition-build: [move] Moving 37 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/lib [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/management [move] Moving 3 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/management [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/jms [move] Moving 12 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/jms [delete] Deleting directory /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/all/deploy/jbossmq-httpil.sar [copy] Copying 185 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default [delete] Deleting 4 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/lib [delete] Deleting 25 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy [delete] Deleted 18 directories from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy [delete] Deleting 17 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy/jboss-net.sar [delete] Deleted 7 directories from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy/jboss-net.sar [delete] Deleting 1 files from /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/conf [delete] Deleting directory /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/default/deploy/deploy.last [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/deploy [copy] Copying 3 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/conf [move] Moving 1 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/conf [copy] Copying 4 files to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/lib [copy] Copying 1 file to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/deploy [copy] Copying 1 file to /home/jbossci/jbossci/jboss-head/build/output/testbuild/server/minimal/lib [mkdir] Created dir: /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-common-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-system-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-j2ee.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jnp-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-transaction-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jboss-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-invoker-adaptor-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-ejb-connector-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-connector-client-factory.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jmx-rmi-connector-client.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/concurrent.jar into /home/jbossci/jbossci/jboss-head/build/build [unjar] Expanding: /home/jbossci/jbossci/jboss-head/build/output/testbuild/client/jbosssx-client.jar into /home/jbossci/jbo
[JBoss-dev] [ jboss-Bugs-777412 ] Redeploy of WAR files : EJBs become "null" in JNDI
Bugs item #777412, was opened at 2003-07-25 01:26 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) Assigned to: Scott M Stark (starksm) Summary: Redeploy of WAR files : EJBs become "null" in JNDI Initial Comment: OS : Win2K JDK : Sun 1.4.2 with -server I have a war file (war A), and an ear file (ear A) which contains a bunch of EJBs. I have a second ear file (ear B) which contains another war file (war B). (In this second case war B is included in ear B, I also tested with war B outside of ear B, but I still had the same exact problems). war A is just accessing ear A, and has done so successfully for several months. war B is accessing EJBs included in ear A and ear B. Hot redeploy of war A is ok. But hot redeploy of ear B (which contains war B) causes every code accessing ear A to fail (including war A). This only occur when hot redeploying ear B (a clean start works, for example). And if I'm using some EJB from ear A during the hot redeploy of ear B, this EJB will still work afterwards (however the other EJBs from EAR A will stop working...). This is clearly a very strange behavior, and I *need* to have several apps deployed in JBoss... Here is the way I access EJBs : XDoclet-generated "util" file, with the "physical" (ie JNDI) access. I'm currently testing with the "logical" (ie java:comp/env) access. Here is a typical error : A ClassCastException, when doing the JNDI lookup. In fact, it seems that JNDI is returning null, which causes the the ClassCastException. No NamingException returned. And the EJB is still visible in the JNDI tree, but was not accessed (according to the stats in the JBoss web console). I can send you the various WARs/EARs if it can help, of course. -- >Comment By: Scott M Stark (starksm) Date: 2003-07-25 08:02 Message: Logged In: YES user_id=175228 Send me the original problem archives anyway as I want to see what people are trying to do that is conflicting with the class loading model. -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 07:22 Message: Logged In: YES user_id=79744 Hi Scott, I found a workaround (see my previous post), so it's ok with me for the moment. Besides, I found I could hot deploy JAR files in the deploy/ directory, so I don't need to redefine the classpath of my ejb-jar files. Thanx for the help! -- Comment By: Scott M Stark (starksm) Date: 2003-07-25 05:55 Message: Logged In: YES user_id=175228 Send the ears/wars in question to [EMAIL PROTECTED] if they will not fit as an attachment so I can look into the behavior. -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 02:11 Message: Logged In: YES user_id=79744 OK, after careful reading of bug #734736, I needed to remove the class-path entries in my MANIFEST files. This sucks, because I can't put my own JARs in the class-path of my ears (not just log4j & co). This seems to work with just one EAR (and its MANIFEST), but when adding a second EAR, and hot redeploying it once, everything crashes Very very strange behavior indeed, very annoying (can't put my own JARs in a EAR's classpath), and very difficult to find out -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 01:33 Message: Logged In: YES user_id=79744 This seems to link to bug #734736. I'm also having several libs (log4j.jar, several jakarta commons JARs) included in the manifest class-path of EAR B. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_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/winxp) Testsuite Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === [jmxdoclet] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jmx\mbean\TestMBClassLoader.java --> TestMBClassLoaderMBean qualified to org.jboss.test.jmx.mbean.TestMBClassLoaderMBean [jmxdoclet] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jmx\missingclass\MissingClassTest.java --> MissingClassTestMBean qualified to org.jboss.test.jmx.missingclass.MissingClassTestMBean compile-proxycompiler-bean-sources: [mkdir] Created dir: F:\jboss\jboss-head\testsuite\output\resources\proxycompiler\META-INF [ejbdoclet] Generating Remote interface for 'org.jboss.test.proxycompiler.beans.ejb.ProxyCompilerTestBean'. [ejbdoclet] Generating Local interface for 'org.jboss.test.proxycompiler.beans.ejb.ProxyCompilerTestBean'. [ejbdoclet] Generating Home interface for 'org.jboss.test.proxycompiler.beans.ejb.ProxyCompilerTestBean'. [ejbdoclet] Generating Local Home interface for 'org.jboss.test.proxycompiler.beans.ejb.ProxyCompilerTestBean'. [ejbdoclet] Generating EJB deployment descriptor (ejb-jar.xml). [ejbdoclet] Generating jboss.xml. [ejbdoclet] Generating jbosscmp-jdbc.xml. compile-classes-only: [mkdir] Created dir: F:\jboss\jboss-head\testsuite\output\classes [javac] Compiling 1237 source files to F:\jboss\jboss-head\testsuite\output\classes [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:12: warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has been deprecated [javac] import org.jboss.mx.loading.UnifiedLoaderRepository2; [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:40: warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has been deprecated [javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:40: warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has been deprecated [javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\cmp2\idxandusersql\test\IdxAndUsersqlUnitTestCase.java:137: cannot resolve symbol [javac] symbol : constructor Exception (javax.naming.NamingException) [javac] location: class java.lang.Exception [javac] throw new Exception(e1); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ClientFailTest.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t.stop(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:77: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:121: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:143: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:161: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ExceptionListenerTest.java:63: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:75: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:129: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:133: warning: stop() in java.lang.Thread has been deprecated [javac] tf.stop(); [javac]
[JBoss-dev] [ jboss-Bugs-777412 ] Redeploy of WAR files : EJBs become "null" in JNDI
Bugs item #777412, was opened at 2003-07-25 08:26 Message generated for change (Comment added) made by roullian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) Assigned to: Scott M Stark (starksm) Summary: Redeploy of WAR files : EJBs become "null" in JNDI Initial Comment: OS : Win2K JDK : Sun 1.4.2 with -server I have a war file (war A), and an ear file (ear A) which contains a bunch of EJBs. I have a second ear file (ear B) which contains another war file (war B). (In this second case war B is included in ear B, I also tested with war B outside of ear B, but I still had the same exact problems). war A is just accessing ear A, and has done so successfully for several months. war B is accessing EJBs included in ear A and ear B. Hot redeploy of war A is ok. But hot redeploy of ear B (which contains war B) causes every code accessing ear A to fail (including war A). This only occur when hot redeploying ear B (a clean start works, for example). And if I'm using some EJB from ear A during the hot redeploy of ear B, this EJB will still work afterwards (however the other EJBs from EAR A will stop working...). This is clearly a very strange behavior, and I *need* to have several apps deployed in JBoss... Here is the way I access EJBs : XDoclet-generated "util" file, with the "physical" (ie JNDI) access. I'm currently testing with the "logical" (ie java:comp/env) access. Here is a typical error : A ClassCastException, when doing the JNDI lookup. In fact, it seems that JNDI is returning null, which causes the the ClassCastException. No NamingException returned. And the EJB is still visible in the JNDI tree, but was not accessed (according to the stats in the JBoss web console). I can send you the various WARs/EARs if it can help, of course. -- >Comment By: Julien Dubois (roullian) Date: 2003-07-25 14:22 Message: Logged In: YES user_id=79744 Hi Scott, I found a workaround (see my previous post), so it's ok with me for the moment. Besides, I found I could hot deploy JAR files in the deploy/ directory, so I don't need to redefine the classpath of my ejb-jar files. Thanx for the help! -- Comment By: Scott M Stark (starksm) Date: 2003-07-25 12:55 Message: Logged In: YES user_id=175228 Send the ears/wars in question to [EMAIL PROTECTED] if they will not fit as an attachment so I can look into the behavior. -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 09:11 Message: Logged In: YES user_id=79744 OK, after careful reading of bug #734736, I needed to remove the class-path entries in my MANIFEST files. This sucks, because I can't put my own JARs in the class-path of my ears (not just log4j & co). This seems to work with just one EAR (and its MANIFEST), but when adding a second EAR, and hot redeploying it once, everything crashes Very very strange behavior indeed, very annoying (can't put my own JARs in a EAR's classpath), and very difficult to find out -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 08:33 Message: Logged In: YES user_id=79744 This seems to link to bug #734736. I'm also having several libs (log4j.jar, several jakarta commons JARs) included in the manifest class-path of EAR B. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_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-Patches-777534 ] support for ejbCreate of Stateful Session Beans
Patches item #777534, was opened at 2003-07-25 22:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=777534&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: George P Simon (gpsjp) Assigned to: Nobody/Anonymous (nobody) Summary: support for ejbCreate of Stateful Session Beans Initial Comment: Abstract: - It's a slight J2EE spec compliance issue. - create is not supported in Stateful Session Beans. - This patch enables create in SFSBs. - Applicable to JBoss v3.2.1 (and v3.2.2, both RC1 and RC2, as well) Description: In terms of J2EE spec compliance, ejbCreate should be supported for EJB2.x Beans. The version 3 lines of JBoss has been already implemented this feature according to the Tracker of SourceForge.net (see *1). But, in fact, the situation is that something has happened and support for create in Stateful Session Beans is somehow dropped off in JBoss v3.2.1 and/or later. So I've hacked around the code and made a quick patch, based upon Neale's work (see *2; thank you, Neale :-). Attached is the patch and simple test application in a tar + gzip'ed file. To be honest, I'm not quite sure if this patch is adequate and thorough. Your further examination on this case would be very much appreciated. Thank you. Best regards, G. P. Simon (from Japan) *1) patch #526086 https://sourceforge.net/tracker/?group_id=22866&atid=376687&func=detail&aid=526086 *2) patch #521469 https://sourceforge.net/tracker/download.php?group_id=22866&atid=376687&file_id=18252&aid=521469 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=777534&group_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-777386 ] mbean attribute value only uses first XML Text node
Bugs item #777386, was opened at 2003-07-24 23:39 Message generated for change (Settings changed) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777386&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Brian Wallis (bwallis42) >Assigned to: Scott M Stark (starksm) Summary: mbean attribute value only uses first XML Text node Initial Comment: Mandrake Linux 9.1, 2.4.7 kernel, JDK 1.4.1_01 and JBoss 3.0.7 I'm trying to configure an MBean that has an attribute that requires a value in XML format. The MBean is defined in jboss-service.xml in the conf directory something like...
[JBoss-dev] [ jboss-Bugs-777412 ] Redeploy of WAR files : EJBs become "null" in JNDI
Bugs item #777412, was opened at 2003-07-25 01:26 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) >Assigned to: Scott M Stark (starksm) Summary: Redeploy of WAR files : EJBs become "null" in JNDI Initial Comment: OS : Win2K JDK : Sun 1.4.2 with -server I have a war file (war A), and an ear file (ear A) which contains a bunch of EJBs. I have a second ear file (ear B) which contains another war file (war B). (In this second case war B is included in ear B, I also tested with war B outside of ear B, but I still had the same exact problems). war A is just accessing ear A, and has done so successfully for several months. war B is accessing EJBs included in ear A and ear B. Hot redeploy of war A is ok. But hot redeploy of ear B (which contains war B) causes every code accessing ear A to fail (including war A). This only occur when hot redeploying ear B (a clean start works, for example). And if I'm using some EJB from ear A during the hot redeploy of ear B, this EJB will still work afterwards (however the other EJBs from EAR A will stop working...). This is clearly a very strange behavior, and I *need* to have several apps deployed in JBoss... Here is the way I access EJBs : XDoclet-generated "util" file, with the "physical" (ie JNDI) access. I'm currently testing with the "logical" (ie java:comp/env) access. Here is a typical error : A ClassCastException, when doing the JNDI lookup. In fact, it seems that JNDI is returning null, which causes the the ClassCastException. No NamingException returned. And the EJB is still visible in the JNDI tree, but was not accessed (according to the stats in the JBoss web console). I can send you the various WARs/EARs if it can help, of course. -- >Comment By: Scott M Stark (starksm) Date: 2003-07-25 05:55 Message: Logged In: YES user_id=175228 Send the ears/wars in question to [EMAIL PROTECTED] if they will not fit as an attachment so I can look into the behavior. -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 02:11 Message: Logged In: YES user_id=79744 OK, after careful reading of bug #734736, I needed to remove the class-path entries in my MANIFEST files. This sucks, because I can't put my own JARs in the class-path of my ears (not just log4j & co). This seems to work with just one EAR (and its MANIFEST), but when adding a second EAR, and hot redeploying it once, everything crashes Very very strange behavior indeed, very annoying (can't put my own JARs in a EAR's classpath), and very difficult to find out -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 01:33 Message: Logged In: YES user_id=79744 This seems to link to bug #734736. I'm also having several libs (log4j.jar, several jakarta commons JARs) included in the manifest class-path of EAR B. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_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-777194 ] CMR Problem in 3.2.2RC2
Bugs item #777194, was opened at 2003-07-24 23:52
Message generated for change (Comment added) made by loubyansky
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777194&group_id=22866
Category: JBossCMP
Group: v3.2
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Gavin Matthews (gavinmatthews)
>Assigned to: Alexey Loubyansky (loubyansky)
Summary: CMR Problem in 3.2.2RC2
Initial Comment:
(Resubmitting - typo in last bugs Summary)
Hi,
I posted this to the group a couple of weeks ago when
trying to get 3.2.2RC1 working. Alex had a look at it and
figured it was fixed for RC2. As RC2 was only a couple of
weeks away I decided it'd be easier for me to wait for
RC2 than build it, my mistake, I've just grabbed RC2 -
it's still there. (I'll log a bug this time).
gavin
> -Original Message-
> From: Gavin Matthews
> Sent: Thursday, July 03, 2003 7:05 PM
> To: [EMAIL PROTECTED]
> Cc: '[EMAIL PROTECTED]'
> Subject: CMR Problem in 3.2.2?
>
>
> Hi,
> I posted yesterday and last week about a problem I
was
> having with CMR when I upgraded from 3.2.0 to 3.2.2.
I've
> done more investigation and I don't think my previous
mails
> were entirely accurate (or very clear) so let me start
over.
>
> The Problem:
> I'm experiencing NPE in our app because the CMR
> relationships are (apparently) not being created. This
didn't
> occur with our app in 3.2.0.
>
> I have a sample case which I believe is representitive
of
> the problem I'm seeing in our app. The beans are Foo
& Bar
> (sorry about the naming). The relationship is N-Foo-1-
Bar.
> The relation is being set in post create:
>
> public abstract class FooEJB extends
AbstractEntityBean {
> ...
> public void ejbPostCreate(BarLocal bar, String
fooValue)
> throws CreateException {
> sLog.debug("ejbPostCreate(" + getId() + ")");
>
> this.setBar(bar);
> }
> ...
> }
>
> And I have a test session which does the following:
>
> ...
> BarLocal bar = createBar("This is a bar");
> FooLocal foo = createFoo(bar, "This is a foo");
>
> sLog.info
("")
;
> sLog.info("Bar id through foo: " + foo.getBar
().getId());
> sLog.info("Bar id through bars foos: ");
>
> Collection foos = bar.getFoos();
> sLog.info("Number of foos associated with
bar: "
> + foos.size());
>
> Iterator fooIter = bar.getFoos().iterator();
> while (fooIter.hasNext()) {
> FooLocal tmpFoo = (FooLocal) fooIter.next
();
> sLog.info("Foo id: " + tmpFoo.getId());
> sLog.info("Bar id: " + tmpFoo.getBar().getId
());
> }
> sLog.info
("")
;
> ...
>
> I'd expect the output of this test case to be:
>
> 18:58:38,875 INFO [FooBarSessionEJB]
>
> 18:58:38,890 INFO [FooBarSessionEJB] Bar id through
foo: 1011
> 18:58:38,890 INFO [FooBarSessionEJB] Bar id through
bars foos:
> 18:58:38,890 INFO [FooBarSessionEJB] Number of
foos
> associated with bar: 1
> 18:58:38,906 INFO [FooBarSessionEJB] Foo id: 1017
> 18:58:38,906 INFO [FooBarSessionEJB] Bar id: 1011
> 18:58:38,906 INFO [FooBarSessionEJB]
>
>
> What I'm actually seeing is:
>
> 18:58:38,875 INFO [FooBarSessionEJB]
>
> 18:58:38,890 INFO [FooBarSessionEJB] Bar id through
foo: 1011
> 18:58:38,890 INFO [FooBarSessionEJB] Bar id through
bars foos:
> 18:58:38,890 INFO [FooBarSessionEJB] Number of
foos
> associated with bar: 0
> 18:58:38,906 INFO [FooBarSessionEJB]
>
**
*
>
> If I add a finder call after the beans are created
(which
> forces the beans to be synchronized to the database)
then I
> get the results I expect. This makes me think that
there's a
> problem with the caching - the "bar" returned by the
> create() call is not the same Bar instance as returned
by
> foo.getBar(). Which means that I have 2 instances of
the same
> bean within the same transaction which have different
state -
> seems like a bug to me, I'd have expected the
foo.getBar()
> call to return the same "bar" as was passed to the
create() call.
>
> I've attached the source. For the sample, let me know
what you think,
>
> thanks,
> gavin
>
--
>Comment By: Alexey Loubyansky (loubyansky)
Date: 2003-07-25 14:36
Message:
Logged In: YES
user_id=543482
Despite it worked for me, I marked it as 'Invalid'.
Unknown pk should have unique name and primkey-field
should be omitted and prim-key-class should be
java.lang.Object.
You can use pk generation with "known" pk by marking the pk
field as in jbosscmp-jdbc.xml.
-
[JBoss-dev] [ jboss-Bugs-777412 ] Redeploy of WAR files : EJBs become "null" in JNDI
Bugs item #777412, was opened at 2003-07-25 08:26 Message generated for change (Comment added) made by roullian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) Assigned to: Nobody/Anonymous (nobody) Summary: Redeploy of WAR files : EJBs become "null" in JNDI Initial Comment: OS : Win2K JDK : Sun 1.4.2 with -server I have a war file (war A), and an ear file (ear A) which contains a bunch of EJBs. I have a second ear file (ear B) which contains another war file (war B). (In this second case war B is included in ear B, I also tested with war B outside of ear B, but I still had the same exact problems). war A is just accessing ear A, and has done so successfully for several months. war B is accessing EJBs included in ear A and ear B. Hot redeploy of war A is ok. But hot redeploy of ear B (which contains war B) causes every code accessing ear A to fail (including war A). This only occur when hot redeploying ear B (a clean start works, for example). And if I'm using some EJB from ear A during the hot redeploy of ear B, this EJB will still work afterwards (however the other EJBs from EAR A will stop working...). This is clearly a very strange behavior, and I *need* to have several apps deployed in JBoss... Here is the way I access EJBs : XDoclet-generated "util" file, with the "physical" (ie JNDI) access. I'm currently testing with the "logical" (ie java:comp/env) access. Here is a typical error : A ClassCastException, when doing the JNDI lookup. In fact, it seems that JNDI is returning null, which causes the the ClassCastException. No NamingException returned. And the EJB is still visible in the JNDI tree, but was not accessed (according to the stats in the JBoss web console). I can send you the various WARs/EARs if it can help, of course. -- >Comment By: Julien Dubois (roullian) Date: 2003-07-25 09:11 Message: Logged In: YES user_id=79744 OK, after careful reading of bug #734736, I needed to remove the class-path entries in my MANIFEST files. This sucks, because I can't put my own JARs in the class-path of my ears (not just log4j & co). This seems to work with just one EAR (and its MANIFEST), but when adding a second EAR, and hot redeploying it once, everything crashes Very very strange behavior indeed, very annoying (can't put my own JARs in a EAR's classpath), and very difficult to find out -- Comment By: Julien Dubois (roullian) Date: 2003-07-25 08:33 Message: Logged In: YES user_id=79744 This seems to link to bug #734736. I'm also having several libs (log4j.jar, several jakarta commons JARs) included in the manifest class-path of EAR B. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_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-777412 ] Redeploy of WAR files : EJBs become "null" in JNDI
Bugs item #777412, was opened at 2003-07-25 08:26 Message generated for change (Comment added) made by roullian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) Assigned to: Nobody/Anonymous (nobody) Summary: Redeploy of WAR files : EJBs become "null" in JNDI Initial Comment: OS : Win2K JDK : Sun 1.4.2 with -server I have a war file (war A), and an ear file (ear A) which contains a bunch of EJBs. I have a second ear file (ear B) which contains another war file (war B). (In this second case war B is included in ear B, I also tested with war B outside of ear B, but I still had the same exact problems). war A is just accessing ear A, and has done so successfully for several months. war B is accessing EJBs included in ear A and ear B. Hot redeploy of war A is ok. But hot redeploy of ear B (which contains war B) causes every code accessing ear A to fail (including war A). This only occur when hot redeploying ear B (a clean start works, for example). And if I'm using some EJB from ear A during the hot redeploy of ear B, this EJB will still work afterwards (however the other EJBs from EAR A will stop working...). This is clearly a very strange behavior, and I *need* to have several apps deployed in JBoss... Here is the way I access EJBs : XDoclet-generated "util" file, with the "physical" (ie JNDI) access. I'm currently testing with the "logical" (ie java:comp/env) access. Here is a typical error : A ClassCastException, when doing the JNDI lookup. In fact, it seems that JNDI is returning null, which causes the the ClassCastException. No NamingException returned. And the EJB is still visible in the JNDI tree, but was not accessed (according to the stats in the JBoss web console). I can send you the various WARs/EARs if it can help, of course. -- >Comment By: Julien Dubois (roullian) Date: 2003-07-25 08:33 Message: Logged In: YES user_id=79744 This seems to link to bug #734736. I'm also having several libs (log4j.jar, several jakarta commons JARs) included in the manifest class-path of EAR B. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_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-777412 ] Redeploy of WAR files : EJBs become "null" in JNDI
Bugs item #777412, was opened at 2003-07-25 08:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) Assigned to: Nobody/Anonymous (nobody) Summary: Redeploy of WAR files : EJBs become "null" in JNDI Initial Comment: OS : Win2K JDK : Sun 1.4.2 with -server I have a war file (war A), and an ear file (ear A) which contains a bunch of EJBs. I have a second ear file (ear B) which contains another war file (war B). (In this second case war B is included in ear B, I also tested with war B outside of ear B, but I still had the same exact problems). war A is just accessing ear A, and has done so successfully for several months. war B is accessing EJBs included in ear A and ear B. Hot redeploy of war A is ok. But hot redeploy of ear B (which contains war B) causes every code accessing ear A to fail (including war A). This only occur when hot redeploying ear B (a clean start works, for example). And if I'm using some EJB from ear A during the hot redeploy of ear B, this EJB will still work afterwards (however the other EJBs from EAR A will stop working...). This is clearly a very strange behavior, and I *need* to have several apps deployed in JBoss... Here is the way I access EJBs : XDoclet-generated "util" file, with the "physical" (ie JNDI) access. I'm currently testing with the "logical" (ie java:comp/env) access. Here is a typical error : A ClassCastException, when doing the JNDI lookup. In fact, it seems that JNDI is returning null, which causes the the ClassCastException. No NamingException returned. And the EJB is still visible in the JNDI tree, but was not accessed (according to the stats in the JBoss web console). I can send you the various WARs/EARs if it can help, of course. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=777412&group_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
Re: [JBoss-dev] Re: JBossDO
Hello Steve, SL> Yes, that makes total sense. In memory you have both SL> a representation (in Java objects) of the JDO schema SL> and the SQL schema, and there is a mapping between the SL> two. That means in order to generate the tables, I SL> should go off the SQL schema, specifically the Table SL> class could generate itself. Exactly. You can constract "mock" SQL schema, i.e. w/o JDO or CMP schema and play with it. alex Friday, July 25, 2003, 5:45:12 AM, Steve Lewis wrote: SL> Alexey: My comments below. SL> Hello Steve, SL> Tuesday, July 22, 2003, 4:59:04 AM, Steve Lewis wrote: SL>> Alexey, SL>> Do you have any plans for what you might want to SL>> re-use between the CMP engine and JBossdO? The SL> front SL>> end interfaces will be different SL>> (org.jboss.persistence.schema and SL>> org.jboss.persistence.sql) but can we encapsulate SL>> anything behind the front API for reuse? A>> I assume, it is off schema generation topic. Not A> SL> for JBossDO. Because, A>> there is just no need. For new CMP engine, A>> perhaps, the answer is yes. SL> Ok. SL>> What exactly do you think will be the major points SL> of SL>> difference between CMP and JBossDO for table SL>> generation? A>> I think, everything except JDBC calls will be SL> different. The point A>> is not to write from scratch. The point is, SL> actually, reuse. But in A>> our case, it is more reuse of experience rather SL> than the codebase. A>> Have a look at CMP schema generation. It does its SL> job just fine. A>> But can you reuse the code? Can you take out some SL> code for reuse? Not A>> easily. Because it is CMP-architecture-oriented, SL> loosely coupled with A>> "bridges" and specific metadata classes. But you SL> could reuse some A>> ideas. SL> Ok. SL>> Obviously there won't be a 1-1 SL>> relationship, so we'll have to grab the object SL> graph SL>> and create tables as we move through it. A>> No. You need to look at SQL schema API. There is SL> Table which has A>> Column's. When an application is deployed (no SL> matter what type, e.g. A>> JDO or CMP), at least two schemas are built: JDO or SL> CMP schema and SQL A>> schema. There is a mapping between JDO/CMP schema SL> and SQL schema. A>> What you need is to actually generate database SL> schema based on A>> existing SQL schema. Do you understand me? A>> There could be various approaches to do that. You SL> could add a method A>> generate() to Table class or use some helper SL> classes. We'll discuss it A>> later. SL> Yes, that makes total sense. In memory you have both SL> a representation (in Java objects) of the JDO schema SL> and the SQL schema, and there is a mapping between the SL> two. That means in order to generate the tables, I SL> should go off the SQL schema, specifically the Table SL> class could generate itself. SL>> Although maybe we'll want to get the entire object SL>> graph in memory and then use some sort of SL> heuristic SL>> for generating the tables. (We could presumably SL> have SL>> more tables than object types, depending on how we SL>> want to use foreign keys.) A>> Sorry, what do you mean by object graph? A>> Of course, there could be more tables than object A>> types. Or even LESS. A>> But these problems don't belong to schema SL> generation. We generate A>> schema based on SQL schema. A>> The problems you touched belong to mapping from SL> JDO/CMP schemas to SQL A>> schema. They are not trivial and this area will SL> need more work also. SL> By object graph I just mean basic POJO business SL> objects where one business object contains others. By SL> object graph I'm also implying that JDO can define SL> deep hierarchies unlike CMP. SL>> Just trying to get in the correct mode of thought SL> for SL>> tackling this thing. A>> Keep on! ;) A>> Thank you, A>> alex SL> Steve --- 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
