[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 11 07:10:22 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === tests-standard-stress: [junit] Running org.jboss.test.bank.test.BankEJB20StressTestCase [junit] TEST org.jboss.test.bank.test.BankEJB20StressTestCase FAILED (timeout) [junit] Running org.jboss.test.bank.test.BankStressTestCase [junit] TEST org.jboss.test.bank.test.BankStressTestCase FAILED (timeout) [junit] Running org.jboss.test.cache.stress.LocalStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 85.307 sec [junit] Running org.jboss.test.cache.stress.ReadWriteLockWithUpgradeStressTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.569 sec [junit] Running org.jboss.test.cmp2.cmrstress.CMRStressTestCase [junit] TEST org.jboss.test.cmp2.cmrstress.CMRStressTestCase FAILED (timeout) [junit] Running org.jboss.test.cts.test.StatelessSessionStressTestCase [junit] TEST org.jboss.test.cts.test.StatelessSessionStressTestCase FAILED (timeout) [junit] Running org.jboss.test.deadlock.test.BeanStressTestCase [junit] TEST org.jboss.test.deadlock.test.BeanStressTestCase FAILED (timeout) [junit] Running org.jboss.test.hello.test.HelloClusteredHttpStressTestCase [junit] TEST org.jboss.test.hello.test.HelloClusteredHttpStressTestCase FAILED (timeout) [junit] Running org.jboss.test.hello.test.HelloHttpStressTestCase [junit] TEST org.jboss.test.hello.test.HelloHttpStressTestCase FAILED (timeout) [junit] Running org.jboss.test.hello.test.HelloTimingStressTestCase [junit] TEST org.jboss.test.hello.test.HelloTimingStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.JBossMQPerfStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.JBossMQPerfStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.OILInvocationLayerStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 11.053 sec [junit] Running org.jboss.test.jbossmq.perf.RMIInvocationLayerStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 11.205 sec [junit] Running org.jboss.test.jbossmq.perf.SendReplyPerfStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.SendReplyPerfStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.UIL2InvocationLayerStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 16.133 sec [junit] Running org.jboss.test.jca.test.BaseConnectionManagerStressTestCase [junit] Tests run: 7, Failures: 2, Errors: 0, Time elapsed: 19.578 sec [junit] TEST org.jboss.test.jca.test.BaseConnectionManagerStressTestCase FAILED [junit] Running org.jboss.test.jca.test.CachedConnectionBankStressTestCase [junit] TEST org.jboss.test.jca.test.CachedConnectionBankStressTestCase FAILED (timeout) [junit] Running org.jboss.test.lock.test.EnterpriseEntityStressTestCase [junit] TEST org.jboss.test.lock.test.EnterpriseEntityStressTestCase FAILED (timeout) [junit] Running org.jboss.test.naming.test.NamingStressTestCase [junit] TEST org.jboss.test.naming.test.NamingStressTestCase FAILED (timeout) [junit] Running org.jboss.test.perf.test.PerfStressTestCase [junit] TEST org.jboss.test.perf.test.PerfStressTestCase FAILED (timeout) [junit] Running org.jboss.test.pooled.test.BeanStressTestCase [junit] TEST org.jboss.test.pooled.test.BeanStressTestCase FAILED (timeout) tests-client-stress: tests-security-basic-stress: [junit] Running org.jboss.test.jmx.test.SecureJMXInvokerUnitTestCase [junit] TEST org.jboss.test.jmx.test.SecureJMXInvokerUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.perf.test.SecurePerfStressTestCase [junit] TEST org.jboss.test.perf.test.SecurePerfStressTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.SecurityMgrStressTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.965 sec tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] TEST org.jboss.test.management.test.JSR77SpecUnitTestCase
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 11 07:10:45 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBOSS SHUTDOWN FAILED === Sun Jan 11 07:10:46 GMT 2004 === Linux nog.kimptoc.net 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown === java -version --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: % ( / ) - . JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 11 07:21:39 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === === Sun Jan 11 07:21:39 GMT 2004 === Linux nog.kimptoc.net 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 11 10:10:29 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [junit] Running org.jboss.test.cmp2.simple.PageSizeUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 7.784 sec [junit] TEST org.jboss.test.cmp2.simple.PageSizeUnitTestCase FAILED [junit] Running org.jboss.test.cmp2.simple.SimpleUnitTestCase [junit] Tests run: 44, Failures: 0, Errors: 44, Time elapsed: 18.645 sec [junit] TEST org.jboss.test.cmp2.simple.SimpleUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.BmpUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 12, Time elapsed: 77.996 sec [junit] TEST org.jboss.test.cts.test.BmpUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.CmpUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 29.181 sec [junit] TEST org.jboss.test.cts.test.CmpUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.CtsCmp2UnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 126.927 sec [junit] Running org.jboss.test.cts.test.IndependentJarsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 16.013 sec [junit] TEST org.jboss.test.cts.test.IndependentJarsUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.MDBUnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 1, Time elapsed: 87.056 sec [junit] TEST org.jboss.test.cts.test.MDBUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.StatefulSessionUnitTestCase [junit] Tests run: 19, Failures: 0, Errors: 19, Time elapsed: 61.974 sec [junit] TEST org.jboss.test.cts.test.StatefulSessionUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.StatelessSessionUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 8, Time elapsed: 18.267 sec [junit] TEST org.jboss.test.cts.test.StatelessSessionUnitTestCase FAILED [junit] Running org.jboss.test.dbtest.test.DbTypesUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 64.47 sec [junit] Running org.jboss.test.ejbconf.test.MetaDataUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.645 sec [junit] Running org.jboss.test.ejbconf.test.ReadOnlyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 10.519 sec [junit] Running org.jboss.test.entity.test.EJBLoadUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 7.892 sec [junit] Running org.jboss.test.entity.test.EntityUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 8.767 sec [junit] Running org.jboss.test.entity.test.PathologicalUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 11.111 sec [junit] Running org.jboss.test.entityexc.test.EntityExcUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 15.74 sec [junit] Running org.jboss.test.exception.EntityExceptionUnitTestCase [junit] Tests run: 62, Failures: 0, Errors: 62, Time elapsed: 15.273 sec [junit] TEST org.jboss.test.exception.EntityExceptionUnitTestCase FAILED [junit] Running org.jboss.test.exception.ExceptionUnitTestCase [junit] Tests run: 27, Failures: 0, Errors: 27, Time elapsed: 11.326 sec [junit] TEST org.jboss.test.exception.ExceptionUnitTestCase FAILED [junit] Running org.jboss.test.ha.jmx.test.HAServiceMBeanSupportUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 17.129 sec [junit] Running org.jboss.test.ha.singleton.test.HASingletonControllerUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 4.221 sec [junit] Running org.jboss.test.ha.singleton.test.HASingletonSupportUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 5.671 sec [junit] Running org.jboss.test.hello.test.HelloCachedUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 32.562 sec [junit] Running org.jboss.test.idgen.test.IdGenUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 18.042 sec [junit] Running org.jboss.test.invokers.test.MultiInvokersUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 69.403 sec [junit] Running
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 11 10:12:01 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 10:11:56,209 WARN [NamingContext] Failed to connect to localhost:1099 javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:215) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1181) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:190) ... 5 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:452) at java.net.Socket.connect(Socket.java:402) at java.net.Socket.init(Socket.java:309) at java.net.Socket.init(Socket.java:211) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:186) ... 5 more Exception in thread main javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1115) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1192) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Caused by: java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:711) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1093) ... 5 more JBOSS SHUTDOWN FAILED === Sun Jan 11 10:12:01 GMT 2004 === Linux nog.kimptoc.net 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 59 % ( 426 / 712 ) - skipping class too much. JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 11 10:22:46 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 712 Successful tests: 426 Errors:256 Failures: 30 [time of test: 2004-01-11.10-11 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-28.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.2_01/logtests/testresults/reports/html//2004-01-11.10-11 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: org.jboss.test.aop.test.AOPUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.aop.test.RemotingUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.aop.test.SecurityUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.aop.test.SimpleBeanUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.aop.test.TxLockUnitTestCase Test:testAll Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=TxLockTester is not registered. - Suite: org.jboss.test.aop.test.TxLockUnitTestCase Test:testServerFound Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/aoptest.sar; - nested throwable: (org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.UndeclaredThrowableException)) === Sun Jan 11 10:22:46 GMT 2004 === Linux nog.kimptoc.net 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Survey: Motivations to Contribute
Hi all! I'm doing a research project on the motives of free software / open source software developers. This survey follows a somewhat different approach than some earlier studies and tries to incorporate concepts of social psychology to better understand the internal motivation of developers. The questionnaire consists of 44 questions which should be scored on a scale from 1 to 7. According to test runs, completion of the questionnaire should take about 6 minutes. No registration required. The questionnaire and more information about the survey can be found here: *** http://foss-survey.at.tf *** The survey will be online until the end of January. I hope to have the results online by mid February. If you want to be notified, please enter your email address in the appropriate box. If you have questions or comments about this survey, please CC me or email me directly, because I won't be able to follow all the lists/forums. Thank you. Your help is greatly appreciated. ralph --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-874163 ] Error compiling EJB-QL with JDK 1.3.1
Bugs item #874163, was opened at 2004-01-10 01:17 Message generated for change (Comment added) made by loubyansky You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=874163group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Invalid Priority: 5 Submitted By: Raphael Drüner (rdruener) Assigned to: Alexey Loubyansky (loubyansky) Summary: Error compiling EJB-QL with JDK 1.3.1 Initial Comment: OS: Windows XP JDK: SUN 1.3.1 JBOSS: 3.2.3 Hi, the class JDBCEJBQLCompiler uses the method public StringBuffer append(StringBuffer sb) from the StringBuffer Class which is not available in JDK prior to version 1.4. It's quite easy to reproduce as even simple SELECT queries leads to the following deployment exception: java.lang.NoSuchMethodError at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit (JDBCEJBQLCompiler.java:932) at org.jboss.ejb.plugins.cmp.ejbql.ASTSelect.jjtAccept (ASTSelect.java:25) at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit (JDBCEJBQLCompiler.java:487) ... Bye, Raphael -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-01-11 16:27 Message: Logged In: YES user_id=543482 It is definitely not a bug in JBoss. StringBuffer in 1.3.1 still has append(Object obj). The problem is that you are running Java code compiled with 1.4 compiler in 1.3.1 machine. If you recompile JBoss with 1.3.1 the problem will go away. I believe, there were performance reasons (avoid toString()) to add append(StringBuffer sb) while already having append(Object o). I am not going to fix it right now unless someone convinces me that I should. In general, I think, it is a good practice to compile the application with the compiler compliant with the target machine. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=874163group_id=22866 --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-872889 ] CMP using audit-updated-by failing to deploy in v3.2.3
Bugs item #872889, was opened at 2004-01-08 09:46 Message generated for change (Comment added) made by loubyansky You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=872889group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Carlos Villegas (cvill) Assigned to: Alexey Loubyansky (loubyansky) Summary: CMP using audit-updated-by failing to deploy in v3.2.3 Initial Comment: A have a CMP bean working on 3.2.2. The bean uses the audit features. If I try to deploy the same bean in 3.2.3 it fails on creating the table. The error is that the updated-by column is duplicated in the SQL statement sent to the database, e.g. CREATE TABLE mytable ( col1 type1, ... updated_by TEXT, ... updated_by TEXT ) If I create the table manually, some queries give the same type of SQL syntax errors, the updated-by column is duplicated. It works correctly in v3.2.2. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-01-11 17:11 Message: Logged In: YES user_id=543482 It is fixed in Branch_3_2 (JBoss-3.2.4RC1) and HEAD. Thanks. -- Comment By: Carlos Villegas (cvill) Date: 2004-01-11 05:17 Message: Logged In: YES user_id=165693 I attached a testcase. Just deploy in 3.2.2 and 3.2.3. It includes the sources. I tested in Windows and JDK 1.4.2 with no changes to the jboss distribution. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-01-08 11:59 Message: Logged In: YES user_id=543482 Please, provide your auditing configuration. Thanks. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=872889group_id=22866 --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: master worked feverishly fihczyl
The ultimate digital cable filter The filter will allow you to receive all the channels that you order with your remove control! payperviews, adult movies,sport events,special events! see now! erfgr urydaxtr i jfnhrdmbs ko tului
[JBoss-dev] [ jboss-Bugs-845157 ] ClassCastException with PortableRemoteObject.narrow using jb
Bugs item #845157, was opened at 2003-11-19 15:38
Message generated for change (Comment added) made by dobytek
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=845157group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 7
Submitted By: Kevin Gilpin (kgilpin)
Assigned to: Nobody/Anonymous (nobody)
Summary: ClassCastException with PortableRemoteObject.narrow using jb
Initial Comment:
I have 2 EJB applications which are each deployed with
a jboss-app.xml file so that they will have separate
classloader hierarchies. The reason for this is that
the two applications share some common JAR files such
as some base utilities, Hibernate beans, and 3rd party
ones such as struts.
Both applications have an EJB session bean which
implements the same home and session interfaces. These
beans register themselves in JNDI, and a common UI
finds them in a generic manner and exposes a UI for
invoking them (the session interface is IScriptRemote).
The problem occurs when the first application looks up
the IScriptRemote from the second application in the
following code. A ClassCastException occurs on the last
line you see here. Before I created the jboss-app.xml
files, no exception occurred (but I had other problems
with LinkerErrors).
InitialContext ic = J2EEUtil.getInitialContext(port,
principal, credentials);
try {
NamingEnumeration e = ic.listBindings(JNDI_SCRIPT_ROOT);
while ( e.hasMoreElements() ) {
Binding binding = (Binding)e.next();
Object obj = binding.getObject();
LOG.debug(Got object , obj, from binding , binding);
try {
if ( obj instanceof EJBHome ) {
IScriptRemoteHome home =
(IScriptRemoteHome)PortableRemoteObject.narrow(obj,
IScriptRemoteHome.class);
The reported exception is:
15:24:30,609 WARN [Repository] Exception processing
binding ReloadMetadataScriptHome:
$Proxy44:ikp/script/ReloadMetadataScriptHomeHome
java.lang.ClassCastException
at
com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
at
javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at com.ipi.script.Repository.findAll(Repository.java:102)
--
Comment By: Paul Anderson (dobytek)
Date: 2004-01-12 00:03
Message:
Logged In: YES
user_id=948886
I have a similar scenario - multiple EAR files, configured
with their own class repositories in jboss-app.xml, to avoid
conflicts with library jars.
I also have separate WAR files that I'd like to keep outside
EARs. These have the home and remote interfaces in
WEB-INF/lib. I was using JBoss 3.2.1.
When calling an EJB from a webapp I kept getting
ClassCastExceptions, either with a straight cast or
PortableRemoteObject.narrow of the home interface stub
returned by JNDI. Removing the interfaces from WEB-INF/lib
just caused ClassNotFoundException.
This did not happen when the EARs used the global
repository, but then of course there were library problems..
I checked the ClassLoaders that loaded the stub home
interface and the version in my servlet code. The stub and
its home interface were loaded by a JBoss
UnifiedClassLoader, the servlet version of the home
interface by a Tomcat classloader. Configuring servlet
2.3/Java 2 classloading behaviour or a JBoss
UnifiedClassLoader for WEB-INF/lib didn't change much, as
the EAR dedicated UnifiedClassLoader version of the class
was not accessible anyway.
Upgrading to 3.2.3 made no difference.
This JNDI behaviour for the proxy made no sense for RMI so I
assumed in-VM optimisation was happening for JNDI and the
invocation.
I specifically configured use of jrmp for the EJB with
bean-invoker and home-invoker in the JBoss-specific EJB
deployment descriptor. No effect - presumably automatic
optimisation to 'local' was happening.
I then configured JNDI in conf to force RMI
(jndi.properties, java.naming.provider.url=localhost). This
meant that the stub classes were loaded by the same
classloader as my servlet lib and the ClassCastException
stopped.
However, now there was an InvocationException when invoking
the EJB's create method on the home interface - check
deployment packaging.
I guessed that because in-VM optimisation required
additional access to the bean implementation class, this
class (and therefore the method) couldn't be loaded by the
webapp. (I put only the EJB interfaces in the webapp).
In the stack trace I could see the local invoker being used,
not jrmp.
Trying to disable the optimisation, I put
container-invoker-conf|Optimized as false into
standardjboss.xml (could have put into jboss.xml) for
stateless session beans. This seemed to be ignored - the
local invoker was still used and the stub was still returned
by reference from JNDI.
I had found many references to this option on the Internet,
so I guessed it had been dropped in recent JBoss versions.
The element had gone from the jboss_3_2.dtd compared with
jboss_3_0.dtd.
So I guessed that a cleaner
[JBoss-dev] [ jboss-Bugs-874163 ] Error compiling EJB-QL with JDK 1.3.1
Bugs item #874163, was opened at 2004-01-10 00:17 Message generated for change (Comment added) made by rdruener You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=874163group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Invalid Priority: 5 Submitted By: Raphael Drüner (rdruener) Assigned to: Alexey Loubyansky (loubyansky) Summary: Error compiling EJB-QL with JDK 1.3.1 Initial Comment: OS: Windows XP JDK: SUN 1.3.1 JBOSS: 3.2.3 Hi, the class JDBCEJBQLCompiler uses the method public StringBuffer append(StringBuffer sb) from the StringBuffer Class which is not available in JDK prior to version 1.4. It's quite easy to reproduce as even simple SELECT queries leads to the following deployment exception: java.lang.NoSuchMethodError at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit (JDBCEJBQLCompiler.java:932) at org.jboss.ejb.plugins.cmp.ejbql.ASTSelect.jjtAccept (ASTSelect.java:25) at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit (JDBCEJBQLCompiler.java:487) ... Bye, Raphael -- Comment By: Raphael Drüner (rdruener) Date: 2004-01-12 02:00 Message: Logged In: YES user_id=947652 Thanks for your answer. Your right that it's not a bug in the source code. I rather mean a bug in the binary distribution. The download page at jboss.org is imho misleading as it states that version 3.2 runs on jdk 1.3. My understanding of that statement is that the compiled download version runs on JDK 1.3. The J2EE Spec 1.3 requires JDK 1.3 as runtime environment, so it's not quite obvious why JBoss 3.2 dist is compiled with 1.4. It *can* be very time consuming to build such a complex system like JBoss. So I think that most people who download JBoss just start with the compiled version and will possibly run into that problem... -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-01-11 15:27 Message: Logged In: YES user_id=543482 It is definitely not a bug in JBoss. StringBuffer in 1.3.1 still has append(Object obj). The problem is that you are running Java code compiled with 1.4 compiler in 1.3.1 machine. If you recompile JBoss with 1.3.1 the problem will go away. I believe, there were performance reasons (avoid toString()) to add append(StringBuffer sb) while already having append(Object o). I am not going to fix it right now unless someone convinces me that I should. In general, I think, it is a good practice to compile the application with the compiler compliant with the target machine. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=874163group_id=22866 --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: under the horses c
The ultimate digital cable filter The filter will allow you to receive all the channels that you order with your remove control! payperviews, adult movies,sport events,special events! see now! zjnscu k mbkljsxdycvvuewu zgm uyeefpku nup yb gtbuf vdm
[JBoss-dev] JBoss Test Results: 95 % ( 1496 / 1567 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 12 01:36:18 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1567 Successful tests: 1496 Errors:54 Failures: 17 [time of test: 2004-01-12.00-48 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.1_05/logtests/testresults/reports/html//2004-01-12.00-48 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: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlySetFK Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] === Mon Jan 12 01:36:18 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1493 / 1566 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 12 02:29:53 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1566 Successful tests: 1493 Errors:55 Failures: 18 [time of test: 2004-01-12.00-48 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-28.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.1_05/logtests/testresults/reports/html//2004-01-12.00-48 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: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/oldxerces.war - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] === Mon Jan 12 02:29:53 GMT 2004 === Linux nog.kimptoc.net 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1490 / 1566 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 12 03:01:20 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1566 Successful tests: 1490 Errors:57 Failures: 19 [time of test: 2004-01-12.02-11 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.2_01/logtests/testresults/reports/html//2004-01-12.02-11 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: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly Associates')] === Mon Jan 12 03:01:20 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
