[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 07:44:00 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 07:54:00 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 07:54:24 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS);
AW: [JBoss-dev] WebServer: howto obtain the host and port generic ally
-Ursprüngliche Nachricht- Von: Thomas Diesler [mailto:[EMAIL PROTECTED] Gesendet: Montag, 24. November 2003 15:12 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] WebServer: howto obtain the host and port generically Hallo Christoph, do we realy? In case of JSR109 is it not just a matter of feeding back the user suplied WSDL in webservices.xml? Yeah, but with adjusting all the port component addresses. You see, the general architecture of axis/jboss.net is like many transports hitting the same engine/service endpoint Transport1 (http, context http://localhost:8080/jboss-net/services/*) Transport2 (http, context http://localhost:8080/ws4eesimple/HelloPortComponentEJB) Transport2 (https, whatever context) Transport3 (smtp) ... Transportn (JMS or whatever) - AxisService/AxisEngine --- Service-Endpoint where the transports are a) configurable by the default axis-config.xml and (Transport1, Transport3 ... Transportn) b) setup dynamically in case of WAR-based WS (Transport2 for example) So each service is available under several addresses. It is quite easy to maintain the list of a) transports in AxisService. It should be also possible to register the b) contexts in the ws4ee meta-data. How can you define (in the spirit of JSR109) webservices that spawn ofer more than one endpoint? Sorry, my terminology was wrong. A ws4ee webservice consists of course of several port-components each of which has several addresses following above considerations. CGJ ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 08:06:07 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS);
Re: [JBoss-dev] Build in 3.2
Adrian Brock wrote: The big problem (which probably hit Bill) is that a cvs update doesn't pull down new jars in thirdparty. Are we going to keep everything separated in CVS modules, with CVSROOT/modules hacks and thirdparty magic? Or isn't it time for us to reconsider the repository organization? What do you think? I'd like to have everything under ONE module (jboss), and BRANCHes for every major release (3.0, 3.2, 4.0 or HEAD). Thirdparty is an example of how hacky our cvs setup is. I know jboss is a complex project, but we should try to make it easier for new developers to get their hands dirty and help us. The build process could be improved too. I'm not suggesting Maven, no, but maybe something in the middle between Ant copy/paste build files and Maven get the latest jar from ibilbio every build aproaches. What do you guys think? Ricardo Argüello --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Build in 3.2
From Ricardo Argüello: I'd like to have everything under ONE module (jboss), and BRANCHes for every major release (3.0, 3.2, 4.0 or HEAD). +1 :-) Heiko -- Heiko W. Rupp EMail: [EMAIL PROTECTED] Senior Consultant Telefon: +49 711 222 992 - 900 Cellent AG Finance SolutionsTelefax: +49 711 222 992 - 999 Calwer Str. 33 D-70173 Stuttgart --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 10:37:55 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS);
[JBoss-dev] FW: JSR 151: Final Release
-Original Message- From: JCP-INTEREST [mailto:[EMAIL PROTECTED] On Behalf Of Harold Ogle Sent: mardi, 25. novembre 2003 05:55 To: [EMAIL PROTECTED] Subject: JSR 151: Final Release The Expert Group for JSR-000151 Java 2 Platform, Enterprise Edition 1.4 has published the Final Release of its specification. The Final Release of the specification is available from the Java Community Process Web site at: http://jcp.org/en/jsr/stage?listBy=final and also from the JSR page: http://jcp.org/en/jsr/detail?id=151 === To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message signoff JCP-INTEREST. For general help, send email to [EMAIL PROTECTED] and include in the body of the message help. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 10:49:57 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS);
[JBoss-dev] [ jboss-Bugs-848815 ] CMP for a char-field
Bugs item #848815, was opened at 2003-11-25 09:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=848815group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Tim Lebedkov (hilt2) Assigned to: Nobody/Anonymous (nobody) Summary: CMP for a char-field Initial Comment: Hi, a char field in one of my entity beans is mapped to a CHAR(1) field in a Oracle 8 table. Each time I try to load such an EJB I get this error on JBoss console: 15:09:14,859 ERROR [STDERR] Caused by: javax.ejb.EJBException: null; CausedByExc eption is: Load failed; CausedByException is: Unable to load a ResultSet column 7 into a variable of type 'char': java .io.EOFException; nested exception is: javax.ejb.EJBException: Load failed; CausedByException is: Unable to load a ResultSet column 7 into a variable of type 'char': java .io.EOFException Does anybody knows what's wrong? Thank you -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=848815group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 11:34:00 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
Re: [JBoss-dev] Build in 3.2
The problem is that we do alternate release builds off the different slices of the cvs modules, nukes, jmx, jmx-remoting, jms, etc. I'm all for cleaning up the build, but there really is not one monolithic release. What is your suggestion for a reorg that allows for obtaining a jmx build that does not have to pulling in tens of uneeded MBs of code and thirdparty jars? -- Scott Stark Chief Technology Officer JBoss Group, LLC Ricardo Argüello wrote: Adrian Brock wrote: The big problem (which probably hit Bill) is that a cvs update doesn't pull down new jars in thirdparty. Are we going to keep everything separated in CVS modules, with CVSROOT/modules hacks and thirdparty magic? Or isn't it time for us to reconsider the repository organization? What do you think? I'd like to have everything under ONE module (jboss), and BRANCHes for every major release (3.0, 3.2, 4.0 or HEAD). Thirdparty is an example of how hacky our cvs setup is. I know jboss is a complex project, but we should try to make it easier for new developers to get their hands dirty and help us. The build process could be improved too. I'm not suggesting Maven, no, but maybe something in the middle between Ant copy/paste build files and Maven get the latest jar from ibilbio every build aproaches. What do you guys think? Ricardo Argüello --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 11:42:57 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
[JBoss-dev] [ jboss-Bugs-848815 ] CMP for a char-field
Bugs item #848815, was opened at 2003-11-25 11:54 Message generated for change (Comment added) made by loubyansky You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=848815group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Tim Lebedkov (hilt2) Assigned to: Alexey Loubyansky (loubyansky) Summary: CMP for a char-field Initial Comment: Hi, a char field in one of my entity beans is mapped to a CHAR(1) field in a Oracle 8 table. Each time I try to load such an EJB I get this error on JBoss console: 15:09:14,859 ERROR [STDERR] Caused by: javax.ejb.EJBException: null; CausedByExc eption is: Load failed; CausedByException is: Unable to load a ResultSet column 7 into a variable of type 'char': java .io.EOFException; nested exception is: javax.ejb.EJBException: Load failed; CausedByException is: Unable to load a ResultSet column 7 into a variable of type 'char': java .io.EOFException Does anybody knows what's wrong? Thank you -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-11-25 13:59 Message: Logged In: YES user_id=543482 What is the exact JBoss version you are using? Is default mapping mapping java-typejava.lang.Character/java-type jdbc-typeVARCHAR/jdbc-type sql-typeCHAR/sql-type /mapping working for you? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=848815group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 13:32:17 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 13:41:18 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 13:42:25 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS);
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 13:54:20 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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] /home/jbossci/jbossci2/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]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] /home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS);
Re: [JBoss-dev] Head testsuite compile errors
my bad, I'll fix this today Scott M Stark wrote: The jboss-head/testsuite is not compiling due to the following errors: [javac] /cvs/JBossHead/jboss-head/testsuite/src/main/org/jboss/test/cache/bean/TreeCacheTesterBean.java:118: incompatible types [javac] found : java.lang.String [javac] required: int [javac] return cache.getCacheMode(); [javac] ^ [javac] /cvs/JBossHead/jboss-head/testsuite/src/main/org/jboss/test/cache/bean/TreeCacheTesterBean.java:151: incompatible types [javac] found : java.lang.String [javac] required: int [javac] return cache.getLockingLevel(); -- Bela Ban http://www.jgroups.org Cell: (408) 316-4459 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: one way remoting
Sending to dev list now Tom Elrod wrote: Didn't realize this was going to cause a discussion, so we might need to move this to dev list. That aside, jboss remoting currently handles remote classloading in that when a invocation request is deserialized on the server (happens same way on client as well), if it can not find a class within the request (or result in case of client), it will go back across the wire and request the class (note that supports bi-directional classloading). This happens until all the classes are loaded on the far end. The classloader(s) used for the deserialization is controlled within the AbstractInvoker, where the different classloaders to be used can be programmatically set. Yes, this does work and has been tested. This obviously brings up security issues when allowing remote clients to ship bytecode across the wire and is something that needs to be addressed. I do believe that dynamic classloading is needed within remoting for certain cases (know we need it at Vocalocity), so don't want to get rid of it. Would prefer to add capability to ship principal across wire to validate requester if security is turned on (maybe by default). There is already a similar approach for this used within jsr 160 (jmx remoting). This part (security) probably warrants group discussion on list. The oneway question about performance that started this thread, however, should be straight forward. I personally feel the way I presented is acceptable in terms for performance. I need to reread your question on oneway, but I thought it would be implemented outside of JBoss Remoting and within AOP interceptors. Bill -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 10:24 AM To: Bill Burke Cc: [EMAIL PROTECTED] Subject: Re: one way remoting RMI can do bidirectional class loading if the objects being loaded are associated with a RMI stub so that there is an annotated codebase in the marshalling stream. You can prevent ClassLoaders from being created and classes from being loaded in specific package namespaces. You can certainly add new security checks to the UCL layer to extend this. Remote classes are not that big an issue when running with a security manager because the permissions are based on where code was loaded from. Priviledged ops are only going to be granted to known server codebases, not arbitrary clients who may be uploading code. Bill Burke wrote: Yes, that's what I meant. Nobody currently uses JBoss in this way anyways as we don't support it right now. (Or can RMI do this?). This may be pretty dangerous anyways. Can Java security prevent new classes from being created? Bill -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Fwd: JSR 88: Maintenance Release]
FYI Original Message Subject: JSR 88: Maintenance Release Date: Mon, 24 Nov 2003 21:14:41 -0800 From: Harold Ogle [EMAIL PROTECTED] Reply-To: Java Community Process (JCP) general information/announcement list [EMAIL PROTECTED] To: [EMAIL PROTECTED] The Maintenance Lead for JSR-88 J2EE Application Deployment has published a Maintenance Release of its specification. This updated Final Release of the specification is available from the Java Community Process Web site at: http://jcp.org/en/jsr/stage?listBy=final and also from the JSR page: http://jcp.org/en/jsr/detail?id=88 === To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message signoff JCP-INTEREST. For general help, send email to [EMAIL PROTECTED] and include in the body of the message help. -- Ricardo Argüello [EMAIL PROTECTED] www.ndeveloper.com --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Build in 3.2
Maybe we should give Maven a try then... I remember that someone successfully built JBoss using Maven. I can't remember who it was, or where was that documented. I'm not a Maven fan, but with jars not being part of the repository anymore, we could host different sub-projects in a hierarchical way: /cvsroot/jboss/projects/ /cvsroot/jboss/projects/jms /cvsroot/jboss/projects/nukes /cvsroot/jboss/projects/jboss /cvsroot/jboss/projects/jboss/common ... /cvsroot/jboss/projects/jboss/varia Each directory with it's own maven.xml I'm not a Maven wiz, maybe somebody who is could suggest a better layout. But if thidparty jars dependancy and innecessary jar downloads are our problems, then Maven is the solution, IMHO. We could solve 2 problems then: thirdparty hacks and build.xml redundancy. In the end, we could have ONE cvs module, like every one else hehe :-) Ricardo Argüello Scott M Stark wrote: The problem is that we do alternate release builds off the different slices of the cvs modules, nukes, jmx, jmx-remoting, jms, etc. I'm all for cleaning up the build, but there really is not one monolithic release. What is your suggestion for a reorg that allows for obtaining a jmx build that does not have to pulling in tens of uneeded MBs of code and thirdparty jars? --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Build in 3.2
I remember that someone successfully built JBoss using Maven. I can't remember who it was, or where was that documented. Here: http://marc.theaimsgroup.com/?l=jboss-developmentm=105734564109596w=2 Build files: http://www.monkeymachine.ltd.uk/jbossmaven.zip Maven site: http://monkeymachine.ath.cx/jboss/ Ricardo Argüello --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: one way remoting
Bill Burke wrote: I need to reread your question on oneway, but I thought it would be implemented outside of JBoss Remoting and within AOP interceptors. Bill You're throwing me here. I thought we wanted a oneway remote call that would return immediately when hits the far side so don't the client thread does not have to wait for all the server side processing when not expecting a return? JBoss remoting in currently returns a value in the invoke() method, thus client thread is blocked till server side processing completed. Shouldn't this be where we make the change? Otherwise, each of the sub-system handlers that sit on top of jboss remoting will have to have their own oneway implementations and will incur all the overhead of the server side remoting processing. -- AOPHandler | Client --- ClientInvoker --- Transport ---[network]--- Transport --- ServerInvoker --- JMXHandler | -- JMSHandler So, what I am suggesting is that the oneway calls return as soon as they hit the ServerInvoker (but after deserialization). The request will still be processed and forwarded onto the proper handler, but on a new thread. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: one way remoting
It should be configuration. Either client is as optimimal as possible, meaning as soon as method is called, it spawns a thread or enters a work queue, or we go to the server before the client returns. Bill Tom Elrod wrote: Bill Burke wrote: I need to reread your question on oneway, but I thought it would be implemented outside of JBoss Remoting and within AOP interceptors. Bill You're throwing me here. I thought we wanted a oneway remote call that would return immediately when hits the far side so don't the client thread does not have to wait for all the server side processing when not expecting a return? JBoss remoting in currently returns a value in the invoke() method, thus client thread is blocked till server side processing completed. Shouldn't this be where we make the change? Otherwise, each of the sub-system handlers that sit on top of jboss remoting will have to have their own oneway implementations and will incur all the overhead of the server side remoting processing. -- AOPHandler | Client --- ClientInvoker --- Transport ---[network]--- Transport --- ServerInvoker --- JMXHandler | -- JMSHandler So, what I am suggesting is that the oneway calls return as soon as they hit the ServerInvoker (but after deserialization). The request will still be processed and forwarded onto the proper handler, but on a new thread. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] No GROUP BY in JBoss-QL?
On Nov 25, 2003, at 10:33 PM, Bill Burke wrote: Unfortunately EJB QL only allows 1 item in the select statement so no GROUP BY. Use Hibernate. Even then GROUP BY on one table is useful. For example to change this: UserId LocationId LastLoginDate 1 1 2003-01-01 1 1 2003-01-10 1 1 2003-01-12 1 2 2003-02-01 1 2 2003-03-12 2 1 2003-03-03 2 1 2003-04-05 into this: UserId LocationId LastLoginDate 1 2 2003-03-12 2 1 2003-04-05 using something like: select * from Blah group by LocationId order by Date desc; There is no easy way to do this without GROUP BY. S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Hibernate Integration
Is the JBoss group going to add 'official' support for Hibernate to JBoss? I mean to bundle it in a .sar, integrate Hibernate Session management into the EJB container? All the stuff that is badly documented right now :-) S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] No GROUP BY in JBoss-QL?
You are misusing GROUP BY here. What would you like to get in the result? How does ORDER BY work here? GROUP BY is intended to be used with statistical functions. To get the result you wrote, I would write the query this way: SELECT UserId, LocationId, MAX(LastLoginDate) FROM Blah GROUP BY LocationId Stefan Arentz wrote: On Nov 25, 2003, at 10:33 PM, Bill Burke wrote: Unfortunately EJB QL only allows 1 item in the select statement so no GROUP BY. Use Hibernate. Even then GROUP BY on one table is useful. For example to change this: UserId LocationId LastLoginDate 1 1 2003-01-01 1 1 2003-01-10 1 1 2003-01-12 1 2 2003-02-01 1 2 2003-03-12 2 1 2003-03-03 2 1 2003-04-05 into this: UserId LocationId LastLoginDate 1 2 2003-03-12 2 1 2003-04-05 using something like: select * from Blah group by LocationId order by Date desc; There is no easy way to do this without GROUP BY. S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Hibernate Integration
Stefan Arentz wrote: Is the JBoss group going to add 'official' support for Hibernate to JBoss? Yes. I mean to bundle it in a .sar, integrate Hibernate Session management into the EJB container? Not sure. But, anyway, it is an implementation detail. All the stuff that is badly documented right now :-) S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] No GROUP BY in JBoss-QL?
On Nov 25, 2003, at 11:19 PM, Alexey Loubyansky wrote: You are misusing GROUP BY here. What would you like to get in the result? How does ORDER BY work here? GROUP BY is intended to be used with statistical functions. To get the result you wrote, I would write the query this way: SELECT UserId, LocationId, MAX(LastLoginDate) FROM Blah GROUP BY LocationId Ok I am no SQL king :-) But still ... wouldn't this be useful to have in JBossQL? S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 22:37:27 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Nov 25 22:47:04 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [javac] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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] D:\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]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116: warning: stop() in java.lang.Thread has been deprecated [javac] t2.stop(); [javac]^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] SSLContext sslCtx = null; [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated [javac] sslCtx = SSLContext.getInstance(TLS); [javac] ^ [javac] D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated [javac]
Re: [JBoss-dev] No GROUP BY in JBoss-QL?
Yes, sure. But I doubt it will be added to 3.2. Stefan Arentz wrote: On Nov 25, 2003, at 11:19 PM, Alexey Loubyansky wrote: You are misusing GROUP BY here. What would you like to get in the result? How does ORDER BY work here? GROUP BY is intended to be used with statistical functions. To get the result you wrote, I would write the query this way: SELECT UserId, LocationId, MAX(LastLoginDate) FROM Blah GROUP BY LocationId Ok I am no SQL king :-) But still ... wouldn't this be useful to have in JBossQL? S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Hibernate Integration
We have Hibernate support both development and production if you want it. We just haven't put up the marketing material, if that's what you mean. Gavin is working on a SAR and a Deployer for Hibernate. If you're interested in helping him with it talk to him. I have him in copy. He's already done some work on this I believe. Bill Stefan Arentz wrote: Is the JBoss group going to add 'official' support for Hibernate to JBoss? I mean to bundle it in a .sar, integrate Hibernate Session management into the EJB container? All the stuff that is badly documented right now :-) S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-849310 ] clusterView.jsp shows all hosts as localhost
Patches item #849310, was opened at 2003-11-25 17:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=849310group_id=22866 Category: JBossMX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Tim McCune (javajedi) Assigned to: Nobody/Anonymous (nobody) Summary: clusterView.jsp shows all hosts as localhost Initial Comment: Going to the cluster view at http://localhost:8080/jmx-console/cluster and then bootstrapping the cluster shows a list of hosts that all have the same hostname. I'm attaching the simple fix. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=849310group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Hibernate Integration
Yes :) marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Arentz Sent: Tuesday, November 25, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Hibernate Integration Is the JBoss group going to add 'official' support for Hibernate to JBoss? I mean to bundle it in a .sar, integrate Hibernate Session management into the EJB container? All the stuff that is badly documented right now :-) S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-665870 ] Memory Leak...somewhere...
Bugs item #665870, was opened at 2003-01-10 12:41 Message generated for change (Comment added) made by javajedi You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=665870group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Luttrell (objec) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak...somewhere... Initial Comment: JBoss3.0.5 RC1 I do a lot of hot deployments. I'm in the final stages of my project and am making a lot of little minor changes to the html and webapp in tons of different areas so i'm doing 150-200 deployments per day. My ear contains 2 wars a bunch of support jars and an ejb jar with 40-50 beans, entity, statelesssession, mdbs and one sar. I leave jboss running all the time, with the amount of deployments i'm doing JBoss gets an OutOfMemoryError about once a day. I have not changed the default memory setting. I guess the problem could be anywhere in jboss because i hit many, many areas...but it seams to be brought out by the number of deployments i do. -- Comment By: Tim McCune (javajedi) Date: 2003-11-25 18:14 Message: Logged In: YES user_id=62441 This looks like a dup of 435958. Can it be closed? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=665870group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Hibernate Integration
On Nov 25, 2003, at 11:58 PM, Bill Burke wrote: We have Hibernate support both development and production if you want it. We just haven't put up the marketing material, if that's what you mean. Gavin is working on a SAR and a Deployer for Hibernate. If you're interested in helping him with it talk to him. I have him in copy. He's already done some work on this I believe. I am definately interested in that. But the only thing I can do is just testing it. I am about to convert a fairly large EJB/CMP app to Hibernate, so the .sar would be very welcome. S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Wed Nov 26 00:01:35 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [copy] Copying 30 files to D:\jboss\jboss-head\build\output\testbuild\docs\examples\jca [copy] Copying 2 files to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'cluster'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\cluster\output\classes [mkdir] Created dir: D:\jboss\jboss-head\cluster\output\gen-src (XDocletMain.start 45 ) Running mbeaninterface/ [javac] Compiling 105 source files to D:\jboss\jboss-head\cluster\output\classes 13 warnings compile-rmi: [rmic] RMI Compiling 2 classes to D:\jboss\jboss-head\cluster\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\cluster\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\cluster\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\cluster\output\lib [jar] Building jar: D:\jboss\jboss-head\cluster\output\lib\jbossha.jar [jar] Building jar: D:\jboss\jboss-head\cluster\output\lib\jbossha-client.jar [jar] Building jar: D:\jboss\jboss-head\cluster\output\lib\jbossmqha.jar [jar] Building jar: D:\jboss\jboss-head\cluster\output\lib\ClusteredHttpSessionEB.jar [jar] Building jar: D:\jboss\jboss-head\cluster\output\lib\jbossha-httpsession.sar [touch] Creating D:\jboss\jboss-head\cluster\output\build-marker most: == == Finished with 'most' in module 'cluster'. == _module-cluster-most: [copy] Copying 2 files to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 2 files to D:\jboss\jboss-head\build\output\testbuild\client [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\deploy.last [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\deploy.last [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar [unjar] Expanding: D:\jboss\jboss-head\cluster\output\lib\jbossha-httpsession.sar into D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar [move] Moving 1 files to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar\ClusteredHttpSessionEB.jar [unjar] Expanding: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar\ClusteredHttpSessionEB.zip into D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar\ClusteredHttpSessionEB.jar [delete] Deleting: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jbossha-httpsession.sar\ClusteredHttpSessionEB.zip [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\farm [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\farm == == Executing 'most' in module 'jetty'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-bean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jetty\output\src === Wed Nov 26 00:01:35 GMTST 2003 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin
[JBoss-dev] JBoss Test Results: 94 % ( 1417 / 1500 ) - come on - pull your finger out. JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Wed Nov 26 02:24:06 GMT 2003 === 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: 1500 Successful tests: 1417 Errors:66 Failures: 17 [time of test: 2003-11-26.00-49 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-20.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.1_05/logtests/testresults/reports/html//2003-11-26.00-49 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: LocalUnitTestCase Test:testSetup Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: /home/jbossci/jbossci2/jboss-head-test/build/output/testbuild/server/all/tmp/sessions/test/TreeCacheAopTester-dngoc1gu-16/dngoc7as-19.ser (No such file or directory) - Suite: TxConcurrentUnitTestCase Test:testConcurrentAccess Type:failure Exception: junit.framework.AssertionFailedError Message: expected:21 but was:1000 - Suite: ScopedTransactionUnitTestCase Test:testScopedTransaction Type:error Exception: javax.naming.NameNotFoundException Message: ScopedTxTestSession not bound - Suite: ScopedTransactionUnitTestCase Test:testServerFound Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/scopedtx.jar - Suite: ScopedTransactionUnitTestCase Test:unknown Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/scopedtx.jar - Suite: ScopingUnitTestCase Test:testSingletons Type:failure Exception: junit.framework.AssertionFailedError Message: checkVersion(V2) is true === Wed Nov 26 02:24:06 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 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: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] No GROUP BY in JBoss-QL?
Yes, but in EJB QL/JBOSS QL you can only select one item, so group by is useless. Alexey Loubyansky wrote: You are misusing GROUP BY here. What would you like to get in the result? How does ORDER BY work here? GROUP BY is intended to be used with statistical functions. To get the result you wrote, I would write the query this way: SELECT UserId, LocationId, MAX(LastLoginDate) FROM Blah GROUP BY LocationId Stefan Arentz wrote: On Nov 25, 2003, at 10:33 PM, Bill Burke wrote: Unfortunately EJB QL only allows 1 item in the select statement so no GROUP BY. Use Hibernate. Even then GROUP BY on one table is useful. For example to change this: UserId LocationId LastLoginDate 1 1 2003-01-01 1 1 2003-01-10 1 1 2003-01-12 1 2 2003-02-01 1 2 2003-03-12 2 1 2003-03-03 2 1 2003-04-05 into this: UserId LocationId LastLoginDate 1 2 2003-03-12 2 1 2003-04-05 using something like: select * from Blah group by LocationId order by Date desc; There is no easy way to do this without GROUP BY. S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-847815 ] jmx-console problem with jetty / Java2ClassLoadingCompliance
Bugs item #847815, was opened at 2003-11-23 12:40 Message generated for change (Settings changed) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=847815group_id=22866 Category: JBossWeb Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Mike Moulton (mmoulton) Assigned to: Scott M Stark (starksm) Summary: jmx-console problem with jetty / Java2ClassLoadingCompliance Initial Comment: I recently configured JBoss-3.2.3RC1-jetty-4.2.14, after getting everything running for my environment I am getting a java.lang.IllegalStateException: No 'jboss' MBeanServer found! when I try to access the jmx-console. After a bunch of troubleshooting I have narrowed the problem down to 1 area. For some apps I run, I need the Java2ClassLoadingCompliance attribute in jetty's jboss- service.xml set to false. To do this I unpacked the .sar as it is not unpacked by default in this build. I then made my change to the jboss-service.xml where appropriate. After I make this change I am unable to access the jmx-console; while prior to the change, everything works fine. I narrowed the problem down to a jboss-jmx.jar located in the jmx-console.war. When I removed this jar everything seems to work fine. OS: Mac OS X 10.3.1 JDK: 1.4.1 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=847815group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-841085 ] Regression with RMIAdaptor replacement in 3.2.2
Bugs item #841085, was opened at 2003-11-12 16:02 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=841085group_id=22866 Category: JBossMX Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: Scott M Stark (starksm) Summary: Regression with RMIAdaptor replacement in 3.2.2 Initial Comment: The jmx-invoker-adaptor-server.sar which handles the returning the RMIAaptor interface when looking up the JNDI name jmx/rmi/RMIAdaptor which was previously handled by the jmx-rmi-adaptor.sar does not support the RMIAdaptor.addNotificationListener(ObjectName name, RMINotificationListener listener,NotificationFilter filter, Object handback) and so is not a complete replacement for clients who want to receive remote notifications. This needs to be corrected. -- Comment By: Scott M Stark (starksm) Date: 2003-11-25 19:42 Message: Logged In: YES user_id=175228 Support for adding RMINotificationListener has been added for 3.2.3. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=841085group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-651403 ] SingleSignOn does not work reliable
Bugs item #651403, was opened at 2002-12-10 04:26 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=651403group_id=22866 Category: CatalinaBundle Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jens Viebig (jsurf) Assigned to: Scott M Stark (starksm) Summary: SingleSignOn does not work reliable Initial Comment: Catlina SingleSignOn does not work with JBoss 3.0.4 - Tomcat 4.1.12. There are a lot of 403 Authentication Errors when SingleSignOn is used. Sometimes the requested pages are display right, sometimes not. Pressing the reload button very fast gives 403 Error most of the time. Seems to be a caching problem somewhere. Can't get Catalina Debug output working so i can't give more details. -- Comment By: Scott M Stark (starksm) Date: 2003-11-25 20:05 Message: Logged In: YES user_id=175228 The patch has been applied by Brian to the 3.2 codebase for the 3.2.3 release. -- Comment By: Brian Stansberry (bstansberry) Date: 2003-04-29 17:40 Message: Logged In: YES user_id=695688 Under the Patches section, see patch # 729923 for some stuff I wrote that may solve this problem. It's not a JBoss patch per se (i.e. doesn't require building JBoss to use); its installable code. -- Comment By: Brian Stansberry (bstansberry) Date: 2003-04-24 16:11 Message: Logged In: YES user_id=695688 If you're still having trouble getting Catalina debug output, see http://www.jboss.org/thread.jsp?forum=50thread=31763 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=651403group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-846551 ] expn in getConneciton makes pool count wrong
Bugs item #846551, was opened at 2003-11-21 04:45
Message generated for change (Settings changed) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=846551group_id=22866
Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Walter McConnell (waltermcconnell)
Assigned to: Adrian Brock (ejort)
Summary: expn in getConneciton makes pool count wrong
Initial Comment:
Red Hat 9 (2.4.20-6)
JDK 1.4.1_02
When a ResourceException is thrown from within the
getConnection method of a ManagedConnection, the pool
count becomes wrong. This happens because while a
permit is accepted in
InternalManagedConnecitonPool.getConnection() it is
never released in the case of an error.
BaseConnectionManager2 will never call returnConnection
on the connection manager in the case that
ManagedConnection.getConnecion() fails ..
its easy to reproduce .. just add this unit test to
BaseConnectionManagerUnitTestCase ... in order to get
the test to fail you will need to temporarily get the
TestManagedConnection to throw an exception in its
getConnecion method ..
public void
testExceptionInGetConnectionLeavesPoolCountWrong()
throws Exception
{
InternalManagedConnectionPool.PoolParams pp = new
InternalManagedConnectionPool.PoolParams();
pp.minSize = 0;
pp.maxSize = 5;
pp.blockingTimeout = 100;
pp.idleTimeout = 500;
ManagedConnectionFactory mcf = new
TestManagedConnectionFactory();
ManagedConnectionPool poolingStrategy = new
JBossManagedConnectionPool.OnePool(mcf, pp, log);
BaseConnectionManager2 cm = new
NoTxConnectionManager(ccm, poolingStrategy);
try{
Object mc = cm.allocateConnection(mcf, null);
} catch(Exception thrown) {
System.err.println(Caught Exception +
thrown.toString());
}
assertTrue(Wrong number of connections counted:
+ cm.getConnectionCount(), cm.getConnectionCount() == 0);
}
the fix seems pretty trivial too ... In
BaseConnectionManager2.allocateConnection() [line 473],
just wrap the call to mc.getConnection() with a
try/catch .. if it throws a ResoruceException then tell
the pooling strategy to return the connection, killing
it. Then re-throw the exception.
BaseConnectionManager2.java [Line 491 ]
try
{
Object connection = mc.getConnection(subject, cri);
registerAssociation(mc, connection);
if (ccm != null)
{
ccm.registerConnection(this, new
ConnectionRecord(mc, connection, cri));
} // end of if ()
return connection;
} catch(ResourceException thrown)
{
poolingStrategy.returnConnection(mc, true);
throw thrown;
}
I've also attached a test rar and a web app that will
show the problem in a running JBoss server .. after
deploying the lot into the deploy directory, then keep
an eye on the AvailableConnectionCount in the
ManagedConnectionPools MBean view .. you will see it
dropping towards 0 as you refresh the
http://localhost:8080/testwar page .. this is obviously
incorrect as when it hits 0, the pool will refuse
connections and the JBoss pool manager will blow ..
cheers,
Walter McConnell.
IONA Technologies.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=846551group_id=22866
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-843675 ] Distributed Cache Invalidation Issue
Bugs item #843675, was opened at 2003-11-17 05:03 Message generated for change (Settings changed) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=843675group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Julien Dubois (roullian) Assigned to: Sacha Labourey (slaboure) Summary: Distributed Cache Invalidation Issue Initial Comment: Hi, There's a bug in org.jboss.cache.invalidation.InvalidationsTxGrouper in JBoss 3.2.1. I've got a NPE on line 76, the same as this post in the JBoss forum : http://www.jboss.org/thread.jsp?forum=64thread=37584message=3796141#3796141 The problem comes from the tx object, which is null. I have a method which has its transaction option as NotSupported. After removing this option (the default is Supported according to the XDoclet doco), the problem disappeared. So I think that as this method is NotSupported, no transaction is created, hence giving us a null tx object in the InvalidationTxGrouper object. HTH, Julien Dubois. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=843675group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-827614 ] NPE, HTTPSession EJB is being destroyed and then stopped
Bugs item #827614, was opened at 2003-10-21 09:22 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=827614group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: Scott M Stark (starksm) Summary: NPE, HTTPSession EJB is being destroyed and then stopped Initial Comment: The HTTPSession EJB container is throwing an NPE on shutdown in 3.2.2 due to the fact that the container is being destroyed during the destruction of the cluster-service.xml sar, and then stopped by the EJBDeployer. How this is occuring needs to be looked into. 09:17:34,906 INFO [EjbModule] Stopping jboss.j2ee:module=ClusteredHttpSessionEB .jar,service=EjbModule 09:18:05,921 ERROR [EjbModule] unexpected exception stopping Container: jboss.j2ee:jndiName=clustering/HTTPSession,service=EJB java.lang.NullPointerException at org.jboss.ejb.EjbModule.stopService(EjbModule.java:346) ... The full exception is attached. -- Comment By: Scott M Stark (starksm) Date: 2003-11-25 21:08 Message: Logged In: YES user_id=175228 This is due to the ClusteredHttpSessionEB having a dependency on the cluster service and so it is being stopped twice, once when the cluster service is undeployed and stopped, and once when the ejb deployer is shutdown. The EjbModule cannot assume that the containers have not been stopped when its stop method is called. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=827614group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JMS benchmarking
Anybody know of a good benchmarking suite for JMS? If so, are you willing at all to help port it to JBoss? Thanks, Bill -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Tomcat session replication
Good job, But a clear job for AOP in JB4. The cache product is DYNAMITE. marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sacha Labourey Sent: Sunday, November 23, 2003 6:17 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [JBoss-dev] Tomcat session replication Hello, A few changes in the Tomcat HTTP Session replication code. First, some unnecessary synchronization has been removed. This should lead to better scalability and in some cases remove the impression that the replication is hanging. Second, the replication has been improved. Without using AOP-like frameworks, it is hard to determine when an HTTP session is modified. When setAttribute is called, the situation is (almost) obvious. However, if only getAttribute is called, you never know as something like that could occur: ( (HashMap)session.getAttribute (bla) ).put (newKey, newValue); In that case, the setAttribute is never called but the content of the session is modified. Consequently, it is up to the developer to help the container optimize its work. A new tag (session-replication-trigger) has been added to JBoss-web.xml: !ELEMENT jboss-web (class-loading?, security-domain?, context-root?, virtual-host?, use-session-cookies?, session-replication-trigger?, resource-env-ref*, resource-ref* , ejb-ref* , ejb-local-ref*, depends*) This tag determines when the container should consider that a session must be replicated accross the cluster. Possible values are: 1 - SET_AND_GET 2 - SET_AND_NON_PRIMITIVE_GET (default value) 3 - SET The first option is conservative but not optimal (performance-wise): it will replicate the session even if its content has not been modified but simply accessed (getAttribute). As shown above, there is no deterministic way to know if the content of an attribute is not itself modified. It WAS the default value in the past (simply because it was the only implementation available), which explain why the perf will be improved now. The second option is conservative but will only replicate if a non-primitive Object has been accessed (Integer, Long, Double, Short, String, etc. which are immutables). We can take that decision because the previous example cannot be used to modify a session without calling setAttribute (as the objects are immutable). It is the NEW default value. The third option considers that the developer will explicitely call setAttribute on the session otherwise it will not be automatically replicated. Tag examples: session-replication-triggerSET_AND_GET/session-replication-trigger or session-replication-triggerSET_AND_NON_PRIMITIVE_GET/sessio n-replication- trigger or session-replication-triggerSET/session-replication-trigger Furthermore, in the past, when a new session was created, two replications were occuring (one for the creation, one when setting the session). Now, these two steps are reduce to a single step = a single replication. These two changes should improve the performance of your current clustered Web Application (using Tomcat). Cheers, Sacha --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] No GROUP BY in JBoss-QL?
I noticed that there is no GROUP BY in JBoss-QL. Is that for a reason? Looking at the source of the EJB-QL compiler, is this something that can be added by using the ORDER BY code? The two are probably roughly the same? S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] No GROUP BY in JBoss-QL?
Unfortunately EJB QL only allows 1 item in the select statement so no GROUP BY. Use Hibernate. Bill Stefan Arentz wrote: I noticed that there is no GROUP BY in JBoss-QL. Is that for a reason? Looking at the source of the EJB-QL compiler, is this something that can be added by using the ORDER BY code? The two are probably roughly the same? S. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
