RE: [JBoss-dev] O'Reilly JBoss 3.2 workbook
Whoops, it would be nice if I gave the actuall URL. 3.2 Workbook is free BTW. http://www.oreilly.com/catalog/entjbeans3/workbooks/index.html Bill > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Bill > Burke > Sent: Friday, June 06, 2003 5:59 PM > To: Jboss-Dev; JBoss 2 > Subject: [JBoss-dev] O'Reilly JBoss 3.2 workbook > > > The Title still says 3.0, but the O'Reilly 3.2 companion workbook for > O'Reilly 3rd edition. Look for more stuff with O'Reilly in the future. > > Best regards, > > Sacha and Bill > > > > --- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 95 % ( 883 / 921 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === JBoss daily test results SUMMARY Number of tests run: 921 Successful tests: 883 Errors:26 Failures: 12 [time of test: 2003-06-07.02-47 GMT] [java.version: 1.4.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_02-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-18.7] See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: Scheduler2UnitTestCase Test:testXMLScheduleProvider(org.jboss.test.util.test.Scheduler2UnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Not enough or too many (19) hits received: 10 - Suite: SchedulerUnitTestCase Test:testDefaultScheduler(org.jboss.test.util.test.SchedulerUnitTestCase) Type:error Exception: java.lang.InternalError Message: Test timeout - Suite: TreeCacheAopUnitTestCase Test:testSet(org.jboss.test.cache.test.aop.TreeCacheAopUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: ReplTreeCacheUnitTestCase Test: testSyncRepl(org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: java.lang.NullPointerException - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - ===Sat Jun 7 04:34:51 BST 2003 ===Linux quarks2 2.4.20-18.7 #1 Thu May 29 06:51:53 EDT 2003 i686 unknown ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] at org.apache.log4j.LogManager.(LogManager.java:145) [junit] at org.jboss.logging.Log4jLoggerPlugin.init(Log4jLoggerPlugin.java:63) [junit] at org.jboss.logging.Logger.getDelegatePlugin(Logger.java:319) [junit] at org.jboss.logging.Logger.(Logger.java:78) [junit] at org.jboss.logging.Logger.getLogger(Logger.java:291) [junit] at org.jboss.test.aop.bean.AOPTester.(AOPTester.java:34) [junit] at org.jboss.test.aop.nonjunit.StandaloneTest.(StandaloneTest.java:36) [junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [junit] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [junit] at java.lang.reflect.Constructor.newInstance(Constructor.java:274) [junit] at junit.framework.TestSuite.addTestMethod(TestSuite.java:102) [junit] at junit.framework.TestSuite.(TestSuite.java:66) [junit] at org.jboss.test.aop.nonjunit.StandaloneTest.suite(StandaloneTest.java:93) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:324) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.(JUnitTestRunner.java:257) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.(JUnitTestRunner.java:210) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:520) [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 17.115 sec tests-client-unit: [junit] Running org.jboss.test.jrmp.test.DynLoadingUnitTestCase [junit] TEST org.jboss.test.jrmp.test.DynLoadingUnitTestCase FAILED (timeout) tests-security-basic-unit: [junit] Running org.jboss.test.security.test.EJBSpecUnitTestCase [junit] TEST org.jboss.test.security.test.EJBSpecUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.HttpsUnitTestCase [junit] TEST org.jboss.test.security.test.HttpsUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.LoginContextUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 9.883 sec [junit] Running org.jboss.test.security.test.LoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 6.103 sec [junit] Running org.jboss.test.security.test.NamespacePermissionsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.554 sec [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.398 sec [junit] Running org.jboss.test.security.test.XMLLoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 5.063 sec tests-standard-stress: [junit] Running org.jboss.test.bank.test.BankEJB20StressTestCase [junit] TEST org.jboss.test.bank.test.BankEJB20StressTestCase FAILED (timeout) [junit] Running org.jboss.test.bank.test.BankStressTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 89.287 sec [junit] TEST org.jboss.test.bank.test.BankStressTestCase FAILED [junit] Running org.jboss.test.cache.test.perf.ReplicatedAsyncStressTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 42.771 sec [junit] Running org.jboss.test.cache.test.perf.ReplicatedSyncStressTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 58.975 sec [junit] Running org.jboss.test.cache.test.perf.TransientStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.216 sec [junit] Running org.jboss.test.cts.test.StatelessSessionStressTestCase [junit] TEST org.jboss.test.cts.test.StatelessSessionStressTestCase FAILED (timeout) [junit] Running org.jboss.test.deadlock.test.BeanStressTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 54.854 sec [junit] TEST org.jboss.test.deadlock.test.BeanStressTestCase FAILED [junit] Running org.jboss.test.hello.test.HelloTimingStressTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 25.964 sec [junit] Running org.jboss.test.invokers.test.InvokerPerformanceStressTestCase [junit] TEST org.jboss.test.invokers.test.InvokerPerformanceStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: 96 % ( 1286 / 1337 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === JBoss daily test results SUMMARY Number of tests run: 1337 Successful tests: 1286 Errors:29 Failures: 22 [time of test: 2003-06-07.00-28 GMT] [java.version: 1.4.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_02-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] See http://jboss1.kimptoc.net/winxp/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: StandaloneTest Test:testFieldInterception(org.jboss.test.aop.nonjunit.StandaloneTest) Type:error Exception: java.lang.InternalError Message: Test timeout - Suite: BankStressTestCase Test:org.jboss.deployment.DeploymentException: Could not create deployment: file:/F:/jboss/jboss-head-test/testsuite/output/lib/bankiiop.jar; - nested throwable: (MBeanException: org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/F:/jboss/jboss-head-test/testsuite/output/lib/bankiiop.jar; - nested throwable: (java.lang.NullPointerException) Cause: org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/F:/jboss/jboss-head-test/testsuite/output/lib/bankiiop.jar; - nested throwable: (java.lang.NullPointerException)) Type:error Exception: org.jboss.deployment.DeploymentException Message: Could not create deployment: file:/F:/jboss/jboss-head-test/testsuite/output/lib/bankiiop.jar; - nested throwable: (MBeanException: org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/F:/jboss/jboss-head-test/testsuite/output/lib/bankiiop.jar; - nested throwable: (java.lang.NullPointerException) Cause: org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/F:/jboss/jboss-head-test/testsuite/output/lib/bankiiop.jar; - nested throwable: (java.lang.NullPointerException)) - Suite: TreeCacheAopUnitTestCase Test:testSet(org.jboss.test.cache.test.aop.TreeCacheAopUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: ReplTreeCacheUnitTestCase Test: testSyncRepl(org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: java.lang.NullPointerException - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - ===Sat Jun 7 01:37:06 GMTDT 2003 ===CYGWIN_NT-5.1 nog 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] Running org.jboss.test.lock.test.EnterpriseEntityStressTestCase [junit] Tests run: 15, Failures: 2, Errors: 2, Time elapsed: 12.298 sec [junit] TEST org.jboss.test.lock.test.EnterpriseEntityStressTestCase FAILED [junit] Running org.jboss.test.perf.test.PerfStressTestCase [junit] Tests run: 7, Failures: 0, Errors: 2, Time elapsed: 14.701 sec [junit] TEST org.jboss.test.perf.test.PerfStressTestCase FAILED [junit] Running org.jboss.test.pooled.test.BeanStressTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 2.504 sec [junit] TEST org.jboss.test.pooled.test.BeanStressTestCase FAILED tests-security-basic-stress: [junit] Running org.jboss.test.perf.test.SecurePerfStressTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 4.967 sec [junit] TEST org.jboss.test.perf.test.SecurePerfStressTestCase FAILED tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 1, Errors: 2, Time elapsed: 35.211 sec [junit] TEST org.jboss.test.management.test.JSR77SpecUnitTestCase FAILED tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.302 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 1.291 sec [junit] Running org.jboss.test.util.test.Scheduler2UnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 37.283 sec [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.026 sec [junit] Running org.jboss.test.util.test.ServerSideExampleUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.655 sec tests-jbossmx-compliance: [junit] Running org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.432 sec [junit] Running org.jboss.test.jbossmx.compliance.monitor.BasicTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 8.192 sec [junit] Running org.jboss.test.jbossmx.compliance.notcompliant.NCMBeanTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.593 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.BasicTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.821 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.CanonicalTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.981 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase [junit] Tests run: 53, Failures: 0, Errors: 0, Time elapsed: 4.577 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.PatternTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 1.462 sec [junit] Running org.jboss.test.jbossmx.compliance.registration.RegistrationTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.292 sec [junit] Running org.jboss.test.jbossmx.compliance.relation.BasicTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.42 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerFactoryTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.742 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 2.693 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase [junit] Tests run: 38, Failures: 0, Errors: 0, Time elapsed: 2.804 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InheritanceTestCase [junit] Tests run: 21, Failures: 0, Errors: 0, Time elapsed: 1.813 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.TrivialTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.583 sec [junit] Running org.jboss.test.jbossmx.compliance.timer.BasicTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 31.265 sec tests-jbossmx-implementation: [junit] Running org.jboss.test.jbossmx.implementation.persistence.OnTimerPersistenceTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 11.667 sec [junit] Running org.jboss.test.jbossmx.implementation.server.ContextCLTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.362 sec [junit] Running org.jboss.test.jbossmx.implementation.util.AgentIDTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.312 sec
[JBoss-dev] >>>WORK AT HOME...START TODAY...MAKE BIG $$$
GET STARTED WORKING FROM HOME TODAY! This message contains valuable information about our organization and qualified specialists who have extensive knowledge and experience in WORKING FROM HOME. We have spent the last decade researching home employment options available to the public. After spending thousands of hours in research, we can confidently promise you that NO ONE has better information on this subject. ---WORK IN THE COMFORT OF YOUR OWN HOME--- ***WIDE SELECTION OF JOBS...TOP PAY*** --REAL JOBS WITH REAL COMPANIES-- Plus receive your very own "Computer Cash Disk" FREE! Every day thousands of people just like you are getting started working at home in fields of computer work, sewing, assembling products, crafts, typing, transcribing, mystery shopping, getting paid for their opinion, telephone work and much more! WHO ARE HOME WORKERS? They are regular, ordinary people who earn an excellent living working at their own pace and make their own hours. They are fortunate people who have found an easier way to make a living. They had absolutely no prior experience in this field. They earn a good weekly income in the comfort of their own home and you can be next! Companies all over the United States want to hire you as an independent home-worker. You are a valuable person to these companies because you will actually be saving them a great amount of money. These companies want to expand their business, but do not want to hire more office people. If they hired more office employees, they would have to supervise them, rent more office space, pay more taxes and insurance, all involving more paperwork. It is much easier for them to set it up so you can earn an excellent income working in the comfort of your own home. ---LIVE ANYWHERE You can live anywhere and work for most of these companies. The companies themselves can be located anywhere. For computer work, the companies provide you with assignments, usually data entry or similar tasks. You then complete the project and get paid for each task. You receive step by step instructions to make it easier for you and to insure you successfully complete the job. After you're finished, you ship the completed assignments back to the company at no charge to yourself. Upon receiving your assignments, the company will then mail you a check along with more assignments. It's that easy! All the other home-based work (sewing, merchandising, surveys, product assembly, typing, telephone work, transcribing, and mystery shopping) are done in a similar way. After contacting the companies you will be given step by step instructions and information on what you need to do. Upon completion of the task, they mail you a check. You have the potential to work for nearly every company in our guide. The only jobs that require equipment is computer work (computer needed), typing (typewriter or computer). All other work requires no equipment of your own. $$$EARN EXTRA INCOME AT HOME$$$ All business can be done by mail , phone, or online. You can START THE SAME DAY you receive "The Guide to Genuine Home Employment." *ONLY REAL COMPANIES OFFERING REAL JOBS!* The companies in our guide are legitimate and really need home workers. There is over two hundred of the top companies included in our guide offering an opportunity for you to make extra income at home. Unlike other insulting booklets or lists you may see, our guide only includes up to date information of companies who pay top dollar for your services and will hire you. WITHOUT CHARGING YOU FEES TO WORK FOR THEM, GUARANTEED! **UPDATE.Now our guide explains and goes into detail about each company and what they have to offer you! You are guaranteed to find home based work in our guide. No problem! **UPDATE.Our new edition offers an entirely new category of work. It reveals a new, unique way to get paid for your opinion online. Just surf to the proper website and get paid to fill out opinion surveys! What could be easier! We urge you to consider this extraordinary opportunity. Don't delay or you could miss out! This is like no other offer you've ever seen. This is an opportunity to become an independent HOME WORKER. Remember, this is NOT a get-rich- quick-scheme. It is an easy way for you to earn money while filling the needs of a company who needs you. This makes it easy to work at your OWN PACE and in the comfort of YOUR HOME. ***HERE'S HOW TO GET STARTED IMMEDIATELY*** Print the form below, fill in your information and mail it to us, along with the small one time fee for the guide. We will ship the "Guide To Genuine Home Employment" out the same day we receive your reply form! Order within 15 days and the complete, updated, sure-fire, Genuine Home Employment Guide is yours for the special low price of just $29.95! That's over 27% off ou
[JBoss-dev] O'Reilly JBoss 3.2 workbook
The Title still says 3.0, but the O'Reilly 3.2 companion workbook for O'Reilly 3rd edition. Look for more stuff with O'Reilly in the future. Best regards, Sacha and Bill --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 95 % ( 742 / 773 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === JBoss daily test results SUMMARY Number of tests run: 773 Successful tests: 742 Errors:19 Failures: 12 [time of test: 2003-06-06.01-19 GMT] [java.version: 1.4.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_02-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-18.7] See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: Scheduler2UnitTestCase Test:testXMLScheduleProvider(org.jboss.test.util.test.Scheduler2UnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Not enough or too many (19) hits received: 10 - Suite: TreeCacheAopUnitTestCase Test:testSet(org.jboss.test.cache.test.aop.TreeCacheAopUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: ReplTreeCacheUnitTestCase Test: testStateTransfer(org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: "age" should be 38 expected:<38> but was: - Suite: ReplTreeCacheUnitTestCase Test: testSyncRepl(org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: java.lang.NullPointerException - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - ===Fri Jun 6 02:29:15 BST 2003 ===Linux quarks2 2.4.20-18.7 #1 Thu May 29 06:51:53 EDT 2003 i686 unknown ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.735 sec [junit] Running org.jboss.test.jca.test.BootstrapContextUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 3.423 sec [junit] TEST org.jboss.test.jca.test.BootstrapContextUnitTestCase FAILED [junit] Running org.jboss.test.jca.test.CachedConnectionSessionUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 9.061 sec [junit] Running org.jboss.test.jca.test.ConnectionFactorySerializationUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.325 sec [junit] Running org.jboss.test.jca.test.DeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.175 sec [junit] Running org.jboss.test.jca.test.JCA15AdapterUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.998 sec [junit] Running org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.684 sec [junit] Running org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 7.771 sec [junit] Running org.jboss.test.jca.test.MessageEndpointUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 24.475 sec [junit] Running org.jboss.test.jca.test.ReentrantUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13.865 sec [junit] Running org.jboss.test.jca.test.UserTxUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 13.088 sec [junit] Running org.jboss.test.jca.test.WrapperSQLUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 2.327 sec [junit] Running org.jboss.test.jca.test.XAExceptionUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 9.058 sec [junit] Running org.jboss.test.jca.test.XAResourceUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 1.245 sec [junit] Running org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 5.41 sec [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 15.698 sec [junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.833 sec [junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 68.978 sec [junit] Running org.jboss.test.jmx.test.CPManifestUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 18.972 sec [junit] Running org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.51 sec [junit] Running org.jboss.test.jmx.test.DeployServiceUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 10.596 sec [junit] Running org.jboss.test.jmx.test.DeployXMBeanUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 79.564 sec [junit] Running org.jboss.test.jmx.test.EarDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 12.303 sec [junit] Running org.jboss.test.jmx.test.EjbDependencyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.201 sec [junit] Running org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.632 sec [junit] Running org.jboss.test.jmx.test.JavaBeanURIResolverUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.546 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 57.389 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnEJBUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.374 sec [junit] Running org.jboss.test.jmx.test.MissingClassUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.896 sec [junit] Running org.jboss.test.jmx.test.ServiceRsrcsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.559 sec [junit] Running org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 13.453 sec [junit] Running org.jboss.test.jmx.test.UnpackedDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 59.797 sec [junit] Running org.jboss.test.jrmp.test.CustomSocketsUnitTestCase
RE: [JBoss-dev] missing docs on web site
from projects, developers links, guides, there's a 'cvs administration' link that seems to point to the page you list. but from projects, developers links, source code, there's a 'cvs administration guide' link that goes nowhere: http://www.jboss.org/index.html?module=html&op=userdisplay&id=guides/develop ers/guides/cvs-admin looks like a stray 'guides/' in there... thanks for the proper pointer! > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2003 12:42 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] missing docs on web site > > > Which page are you looking at? > > Here is the information you want. > http://www.jboss.org/index.html?module=html&op=userdisplay&id= > developers > /guides/cvs-admin > > Regards, > Adrian > > > > Adrian Brock > Director of Support > Back Office > JBoss Group, LLC > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Rod Burgett > > Sent: 06 June 2003 14:33 > > To: [EMAIL PROTECTED] > > Subject: [JBoss-dev] missing docs on web site > > > > > > I'm looking for cvs versioning and branching information. > > The developer's > > page includes this: > > > > For our policies on CVS versioning and branching see the CVS > > Administration > > Guide. > > > > but the link is broken. Attempts to follow it yield 'not found'. > > > > > > > > > > Rod Burgett > > Senior Software Engineer > > > > webMethods, Inc. > > 3930 Pender Drive > > Fairfax, VA 22030 USA > > Ph: 703.460.5819 (tty only) > > > > "It's all just 0s & 1s - > > the trick is getting them lined up in the proper order" > > > > > > > > --- > > This SF.net email is sponsored by: Etnus, makers of > > TotalView, The best > > thread debugger on the planet. Designed with thread > debugging features > > you've never dreamed of, try TotalView 6 free at www.etnus.com. > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > --- > This SF.net email is sponsored by: Etnus, makers of > TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: 97 % ( 1206 / 1240 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === JBoss daily test results SUMMARY Number of tests run: 1240 Successful tests: 1206 Errors:16 Failures: 18 [time of test: 2003-06-05.23-20 GMT] [java.version: 1.4.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_02-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] See http://jboss1.kimptoc.net/winxp/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: TreeCacheAopUnitTestCase Test:testSet(org.jboss.test.cache.test.aop.TreeCacheAopUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: ReplTreeCacheUnitTestCase Test: testStateTransfer(org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: "age" should be 38 expected:<38> but was: - Suite: ReplTreeCacheUnitTestCase Test: testSyncRepl(org.jboss.test.cache.test.replicated.ReplTreeCacheUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: java.lang.NullPointerException - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - Suite: StatefulSessionUnitTestCase Test: testLocalInterfacePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - ===Fri Jun 6 01:23:31 GMTDT 2003 ===CYGWIN_NT-5.1 nog 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] Running org.objectweb.jtests.jms.conform.session.SessionTest [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 8.683 sec [junit] Running org.objectweb.jtests.jms.conform.session.TopicSessionTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 9.173 sec [junit] Running org.objectweb.jtests.jms.conform.topic.TemporaryTopicTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.859 sec tests-client-unit: [junit] Running org.jboss.test.jrmp.test.DynLoadingUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 7.862 sec [junit] TEST org.jboss.test.jrmp.test.DynLoadingUnitTestCase FAILED tests-security-basic-unit: [junit] Running org.jboss.test.security.test.EJBSpecUnitTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 15.923 sec [junit] Running org.jboss.test.security.test.HttpsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 6.549 sec [junit] TEST org.jboss.test.security.test.HttpsUnitTestCase FAILED [junit] Running org.jboss.test.security.test.LoginContextUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.246 sec [junit] Running org.jboss.test.security.test.LoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 5.278 sec [junit] Running org.jboss.test.security.test.NamespacePermissionsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.103 sec [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.963 sec [junit] Running org.jboss.test.security.test.XMLLoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 9.103 sec tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 1, Errors: 2, Time elapsed: 31.886 sec [junit] TEST org.jboss.test.management.test.JSR77SpecUnitTestCase FAILED tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.713 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 1.282 sec [junit] Running org.jboss.test.util.test.Scheduler2UnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 41.249 sec [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.455 sec [junit] Running org.jboss.test.util.test.ServerSideExampleUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.665 sec tests-jbossmx-compliance: [junit] Running org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.603 sec [junit] Running org.jboss.test.jbossmx.compliance.monitor.BasicTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 8.542 sec [junit] Running org.jboss.test.jbossmx.compliance.notcompliant.NCMBeanTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.502 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.BasicTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.842 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.CanonicalTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.561 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase [junit] Tests run: 53, Failures: 0, Errors: 0, Time elapsed: 3.716 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.PatternTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 1.062 sec [junit] Running org.jboss.test.jbossmx.compliance.registration.RegistrationTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.282 sec [junit] Running org.jboss.test.jbossmx.compliance.relation.BasicTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.411 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerFactoryTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.743 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 2.674 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase [junit] Tests run: 38, Failures: 0, Errors: 0, Time elapsed: 2.814 sec [junit] Running org.jboss.test.jbossmx.compl
RE: [JBoss-dev] missing docs on web site
Which page are you looking at? Here is the information you want. http://www.jboss.org/index.html?module=html&op=userdisplay&id=developers /guides/cvs-admin Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Rod Burgett > Sent: 06 June 2003 14:33 > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] missing docs on web site > > > I'm looking for cvs versioning and branching information. > The developer's > page includes this: > > For our policies on CVS versioning and branching see the CVS > Administration > Guide. > > but the link is broken. Attempts to follow it yield 'not found'. > > > > > Rod Burgett > Senior Software Engineer > > webMethods, Inc. > 3930 Pender Drive > Fairfax, VA 22030 USA > Ph: 703.460.5819 (tty only) > > "It's all just 0s & 1s - > the trick is getting them lined up in the proper order" > > > > --- > This SF.net email is sponsored by: Etnus, makers of > TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] 3.0.8 Release is available from SF
The 3.0.8 release is available from sourceforge. http://sourceforge.net/project/showfiles.php?group_id=22866 The release notes are available here: http://sourceforge.net/project/shownotes.php?release_id=163197 -- Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] missing docs on web site
I'm looking for cvs versioning and branching information. The developer's page includes this: For our policies on CVS versioning and branching see the CVS Administration Guide. but the link is broken. Attempts to follow it yield 'not found'. Rod Burgett Senior Software Engineer webMethods, Inc. 3930 Pender Drive Fairfax, VA 22030 USA Ph: 703.460.5819 (tty only) "It's all just 0s & 1s - the trick is getting them lined up in the proper order" --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: [JBoss-user] JBoss 3.0.7 Windows installer available
In case others would like something similar on Linux, the Community Edition of Out-of-the-Box works on both Windows and Linux. It optionally installs JDK 1.4.1_02, JBoss 3.2.0, MySQL 4.0.12, Ant 1.5.3, JUnit, and a bunch of other projects. It starts both JBoss and MySQL as a service on either Windows or Linux. It's free, does not expire, and does not require registration. Here's a direct link to the download page: http://www.ejbsolutions.com/downloads/obox/community/index.html BTW, we also offer technical support and consulting services for JBoss, Tomcat, Apache, Ant, MySQL, PostgreSQL, Hibernate, and the rest of the 100+ Open Source projects included in Out-of-the-Box. Happy Installing, Rod Rod Cope EJB Solutions, Inc. [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marcel Ammerlaan Sent: Thursday, June 05, 2003 11:43 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-user] JBoss 3.0.7 Windows installer available Hi, When deploying one of our applications for our clients, we needed an installer for JBoss on the windows platform so we developed one. This installer is now available (without the application itself) for everyone to enjoy. It basically installs JBoss 3.0.7 with an optional JRE and starts JBoss as a service (on Win2k+). The installer can be downloaded here: http://www.artefact.com/?src=jboss&zone=maatwerk (the pages are in dutch, but the installer and readme file are in english). regards, Marcel Ammerlaan Artefact Software & Consultancy. --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-742633 ] JBOSS 3.2.1 / Jetty and Tag Support
Bugs item #742633, was opened at 2003-05-24 04:12
Message generated for change (Comment added) made by lhankins
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742633&group_id=22866
Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: roberto (rroberto)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBOSS 3.2.1 / Jetty and Tag Support
Initial Comment:
The servlet engine doesn't call the release method on
tags every time is used from jsp pages.
This because a pool is used .
this is the servlet code generated from a jsp
private org.apache.jasper.runtime.TagHandlerPool
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope;
/* ABSTag:CustomButton */
com.dat.abs.web.tags.ABSCustomButtonTag
_jspx_th_ABSTag_CustomButton_0 =
(com.dat.abs.web.tags.ABSCustomButtonTag)
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope.get
(com.dat.abs.web.tags.ABSCustomButtonTag.class);
_jspx_th_ABSTag_CustomButton_0.setPageContext
(pageContext);
_jspx_th_ABSTag_CustomButton_0.setParent
(_jspx_th_ABSTag_ButtonBody_0);
_jspx_th_ABSTag_CustomButton_0.setXmlDocument
(vXmlDocument);
_jspx_th_ABSTag_CustomButton_0.setScope(vScope);
int _jspx_eval_ABSTag_CustomButton_0 =
_jspx_th_ABSTag_CustomButton_0.doStartTag();
if (_jspx_th_ABSTag_CustomButton_0.doEndTag() ==
javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
return;
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope.reuse(_jspx_th_ABSTag_CustomButton_0)
the method "reuse" on TagHandlerPool is..
/**
* Adds the given tag handler to this tag handler pool,
unless this tag
* handler pool has already reached its capacity, in which
case the tag
* handler's release() method is called.
*
* @param handler Tag handler to add to this tag handler
pool
*/
public synchronized void reuse(Tag handler) {
if (current < (handlers.length - 1))
handlers[++current] = handler;
else
handler.release();
}
so only when handler pool has already reached its
capacity the tag's release() method is called.
>From the sun javadoc about interface
javax.servlet.jsp.tagext.Tag:
"Called on a Tag handler to release state. The page
compiler guarantees that JSP page implementation
objects will invoke this method on all tag handlers".
This cause that the global internal variable of the tag are
not "clear".
It's a jetty bug ? or i can't use internal variable (or i must
reset it)
There is no problem this optional tag attributes, because
a pool is created for each combination of tag/arguments
passed.
ty
Roberto
--
Comment By: Lance Warren Hankins (lhankins)
Date: 2003-06-05 14:16
Message:
Logged In: YES
user_id=108347
This is definitely a bug (and a serious problem). Its
caused me major pain in migrating our application from Jboss
3.0.4 to JBoss 3.2.1.
The net effect of this problem is that many custom tags will
not work correctly (as they are being pooled, but never
re-initialized properly after first use).
This can cause serious errors in the custom tags. For
example, I have a custom tag that represents a Tabbed panel.
It has one nested tag for each Tab. For example :
The tabbedPanel tag implementation keeps a list with all its
child tab definitions in it (the child tags add themselves
to their parent's list during their doStart method).
In the custom tag's release method, I clear the list.
When this tag is used with 3.2.1, it basically just keeps
expanding (keeps accumulating tabs), because release is
never called (so the list just keeps growing and growing).
--
Comment By: Greg Wilkins (gregwilkins)
Date: 2003-06-01 17:17
Message:
Logged In: YES
user_id=44062
I don't think this is not a jetty bug.
I think it is a jakarta-jasper2 "feature".
I think there are some JspServlet init parameters that you can
use to change this behaviour (you'd have to check the jasper
mailing archives). But I think you will find that the spec
will change in future to match jasper.
regards
--
Comment By: Jan Bartel (janb)
Date: 2003-05-28 09:15
Message:
Logged In: YES
user_id=45251
Roberto,
AFAIK, all jsp stuff is handled by JASPER, not Jetty itself.
This issue may be better off raised on the Jakarta Tomcat lists.
Jan
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742633&group_id=22866
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
Jboss-de
RE: Antwort: RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head
Yes, It means applying the patch to more branches. The next branch from head probably won't be until the end of this year. Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 06 June 2003 12:58 To: [EMAIL PROTECTED] Subject: Antwort: RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head Ok, but just for info: is my assumption right, that updates to a branch without also applying them to HEAD will not show up in the following branch ? Regards Ulf "Adrian Brock" <[EMAIL PROTECTED]> Gesendet von: [EMAIL PROTECTED] 06.06.2003 13:39 Bitte antworten an jboss-development An:<[EMAIL PROTECTED]> Kopie: Thema:RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head Hi Ulf, People use different strategies. Some apply fixes at the same time, others apply them in bulk. I tend to mix the two, keeping the diffs of things I've not applied to head. Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 06 June 2003 12:25 To: [EMAIL PROTECTED] Subject: [JBoss-dev] Updates to CVS-Branch and CVS-Head Should all updates (bugfix/feature) for a branch also be applied to HEAD ? There are some updates that have only been applied to Branch_3_2, although they don't seem to be specific only for that Branch. According to my ( not very sophisticated... ) understanding of JBoss branch policy these updates will be lost for the next upcomming branch ( because that branch uses HEAD as starting point ) ?!? Regards Ulf --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Transactions from outside the jboss jvm
Title: Transactions from outside the jboss jvm I'm having trouble working with UserTransactions from outside the jboss jvm. My situation is this: On application server A I have a servlet that performs some work via stateless session beans deployed on application server A. The servlet also performs some work via stateless session beans deployed on application server B. server A is weblogic, server B is jboss 3.0.6. Presumably I must have two separate transactions since the application servers are different, that's fine. the transaction on server A works fine, but when I attempt to begin a transaction on server B (jboss), I get the following error: javax.transaction.SystemException: java.lang.RuntimeException: UT factory lookup failed: javax.naming.NameNotFoundException: 'UserTransactionSessionFactory'; remaining name 'UserTransactionSessionFactory' at org.jboss.tm.usertx.client.ClientUserTransaction.begin(ClientUserTransaction.java:107) The only information that i could find was a post on this list: From: Scott M Stark Subject: Re: [JBoss-dev] UserTransaction requires jndi.properties??? Date: Sun, 30 Mar 2003 08:20:53 -0800 Its just a limitiation of how the ClientUserTransaction will look to JNDI to obtain the UserTransactionSessionFactory. This class should allow this info to be assigned as a static property of the class so that ths UserTransactionSessionFactory can be looked up once from the JBoss JNDI namespace and set, or something like that. If I understand correctly, since ClientUserTransaction calls new InitalContext(), it'll pick up the InitialContext from the jvm in which it is running, in my case, server A's (weblogic) context. In my case, this is the incorrect context. Is there a work around? Thanks Greg
Antwort: RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head
Ok, but just for info: is my assumption right, that updates to a branch without also applying them to HEAD will not show up in the following branch ? Regards Ulf "Adrian Brock" <[EMAIL PROTECTED]> Gesendet von: [EMAIL PROTECTED] 06.06.2003 13:39 Bitte antworten an jboss-development An: <[EMAIL PROTECTED]> Kopie: Thema: RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head Hi Ulf, People use different strategies. Some apply fixes at the same time, others apply them in bulk. I tend to mix the two, keeping the diffs of things I've not applied to head. Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 06 June 2003 12:25 To: [EMAIL PROTECTED] Subject: [JBoss-dev] Updates to CVS-Branch and CVS-Head Should all updates (bugfix/feature) for a branch also be applied to HEAD ? There are some updates that have only been applied to Branch_3_2, although they don't seem to be specific only for that Branch. According to my ( not very sophisticated... ) understanding of JBoss branch policy these updates will be lost for the next upcomming branch ( because that branch uses HEAD as starting point ) ?!? Regards Ulf --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Updates to CVS-Branch and CVS-Head
I think if the code, the fixes/features were applied to, is supposed to be used in other branches, then these branches should be updated too. alex Friday, June 06, 2003, 2:25:21 PM, ulf schroeter wrote: usmd> Should all updates (bugfix/feature) for a branch also be applied to HEAD ? usmd> There are some updates that have only been applied to Branch_3_2, although usmd> they don't seem to be specific only for that Branch. According to my ( not usmd> very sophisticated... ) understanding of JBoss branch policy these updates usmd> will be lost for the next upcomming branch ( because that branch uses HEAD usmd> as starting point ) ?!? usmd> Regards usmd> Ulf --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head
Hi Ulf, People use different strategies. Some apply fixes at the same time, others apply them in bulk. I tend to mix the two, keeping the diffs of things I've not applied to head. Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 06 June 2003 12:25 To: [EMAIL PROTECTED] Subject: [JBoss-dev] Updates to CVS-Branch and CVS-Head Should all updates (bugfix/feature) for a branch also be applied to HEAD ? There are some updates that have only been applied to Branch_3_2, although they don't seem to be specific only for that Branch. According to my ( not very sophisticated... ) understanding of JBoss branch policy these updates will be lost for the next upcomming branch ( because that branch uses HEAD as starting point ) ?!? Regards Ulf --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-747650 ] Security Flaw on Windows
Bugs item #747650, was opened at 2003-06-02 17:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=747650&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Filipe Lima de Souza (jerkolino) Assigned to: Nobody/Anonymous (nobody) Summary: Security Flaw on Windows Initial Comment: This may be a Jetty flaw. Using JBoss 3.0.6 on Windows, if you access any jsp using caps on the extension (.jsp), you will receive the source code of the page in your browser Like: http://localhost:8080/test/test.jsp will return OK, but http://localhost:8080/test/test.JSP http://localhost:8080/test/test.Jsp http://localhost:8080/test/test.jsP will return the JSP SOURCE CODE!!! -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=747650&group_id=22866 --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Updates to CVS-Branch and CVS-Head
Should all updates (bugfix/feature) for a branch also be applied to HEAD ? There are some updates that have only been applied to Branch_3_2, although they don't seem to be specific only for that Branch. According to my ( not very sophisticated... ) understanding of JBoss branch policy these updates will be lost for the next upcomming branch ( because that branch uses HEAD as starting point ) ?!? Regards Ulf
RE: [JBoss-dev] deploy.last is not very clean
Title: Message if you have more services, then put them like this: deploy/deploy.last/service1.xml deploy/deploy.last/service2.xml deploy/deploy.last/service3.xml deploy/deploy.last/service4.xml deploy/deploy.last/service5.xml deploy/deploy.last/service6.xml If you don't like "last", simply put "zip", the result is the same, no other trick has been implemented, just an alias. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David KlimekSent: jeudi, 5. juin 2003 19:46To: [EMAIL PROTECTED]Subject: [JBoss-dev] deploy.last is not very clean Sacha Labourey wrote: > User: slaboure > Date: 03/06/05 06:26:17 > > Modified:src/main/org/jboss/deployment Tag: Branch_3_2 >DeploymentSorter.java SubDeployerSupport.java > Log: > Add features that allows to have JAR (dir or file) deployment that ends in ".last" and that are deployed after everything in deploy > > This is necessary as some components do need to be deployed after everything (such as the farm service, so that every other component is already started before deployed what is in farm). > > consequently, as part of "all" we now have a folder named "deploy.last" that contains farm-service.xml > > > Hi, it seems to me like a unclean hack. What if I will have more services that should be deployed last? Than I must set dependencies between them manualy. Also I am afraid of all/ directory looking in future like: all/deploy.beforefirst all/deploy.first all/deploy.afterfirst all/deploy.before all/deploy all/deploy.after all/deploy.beforelast all/deploy.last all/deploy.afterlast If there is such a dependency between components, it should be handled through more universal dependency or ordering mechanism. David -- http://www.sweb.cz/david.klimek
[JBoss-dev] JBoss 3.0.7 Windows installer available
Hi, When deploying one of our applications for our clients, we needed an installer for JBoss on the windows platform so we developed one. This installer is now available (without the application itself) for everyone to enjoy. It basically installs JBoss 3.0.7 with an optional JRE and starts JBoss as a service (on Win2k+). The installer can be downloaded here: http://www.artefact.com/?src=jboss&zone=maatwerk (the pages are in dutch, but the installer and readme file are in english). regards, Marcel Ammerlaan Artefact Software & Consultancy. --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] deploy.last is not very clean
Sacha Labourey wrote: > User: slaboure > Date: 03/06/05 06:26:17 > > Modified:src/main/org/jboss/deployment Tag: Branch_3_2 >DeploymentSorter.java SubDeployerSupport.java > Log: > Add features that allows to have JAR (dir or file) deployment that ends in ".last" and that are deployed after everything in deploy > > This is necessary as some components do need to be deployed after everything (such as the farm service, so that every other component is already started before deployed what is in farm). > > consequently, as part of "all" we now have a folder named "deploy.last" that contains farm-service.xml > > > Hi, it seems to me like a unclean hack. What if I will have more services that should be deployed last? Than I must set dependencies between them manualy. Also I am afraid of all/ directory looking in future like: all/deploy.beforefirst all/deploy.first all/deploy.afterfirst all/deploy.before all/deploy all/deploy.after all/deploy.beforelast all/deploy.last all/deploy.afterlast If there is such a dependency between components, it should be handled through more universal dependency or ordering mechanism. David -- http://www.sweb.cz/david.klimek
[JBoss-dev] AW: How to run testcases in jboss.net & UDDI Related
Hi Anil, Sorry for not answering earlier. Needed to do some in-house priority 1 support. > -Ursprüngliche Nachricht- > Von: Anil Saldhana [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 2. Juni 2003 06:49 > An: christoph > Betreff: UDDI Related > > > Dr.CGJ, > here are some new factoids after my research - > basically search and search and no coding. > > 1) JUDDI developers are saying that JAXR will work > with them if we use the Java WS Dev Pack version from > Sun. > Also JUDDI has identified some bugs wrt JAXR support. > I am not sure what the timeline will be from JUDDI to > deliver a jaxr compliant jUDDI. I have posted a > question to them. > > 2) Here is my idea: > > Users will provide JBoss with the following config > data: > a) Name of the Web Service. > b) Inquiry.URL > c) publish.URL plus / > d) Name of Business. > e) Description > f) Contact > > They can also give the publish.url of the internal > JBoss UDDI server(if they do not want external one). > The username/password is used to get the > Authentication Token. > > The user will enter these for each web service. > > Can you suggest a good location in jboss.net to allow > the user to place this config data? I could not find a > config file for this. If I have to create a new config > file, please suggest a name and location... I would tend to extend the web-service.xml (wsdd) for that purpose. As with all deployment descriptors it becomes more and more common use to embed tags of a different namespace describing these extensions such that they are close to the data that they "descorate". Your suggestions wrt the structure of that data sound very good. Except perhaps username/password (I am no JBoss security expert, but it would be fantastic in the end, if the deployment itself could be signed and identified such that we could publish the stuff Using the credentials of the deployed package/its creator!). But I guess we need to do that until we have such a solution. BTW, reading through the WSDL->UDDI document (I sent the link to you) it came to my mind, that we maybe should separate (also in the descriptors) the issues of registering -business/category -service interface (WSDL) -and concrete location of a service with a link to WSDL The web-service.xml should have different elements for these things with links between, such that they can be individually setup and looked up. For example, it could be possible to just Publish the location of the just deployed service in an already registered business with an already specified interface. The jboss.net tests are not part of the official testsuite (historical issue, we became "default" not until JBoss4DR1). You can run them with jboss.net/testsuite/build.bat Some of them (Security and External Webservices) will not succeed until you have configured JBoss with appropriate user.properties, role.properties, appropriate system properties for proxy settings for outbound http if you are behind a firewall, and a system property containing a valid google key. Best, 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: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-749586 ] jnp.discoveryPort is not evaluated correctly
Bugs item #749586, was opened at 2003-06-05 17:08
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=749586&group_id=22866
Category: Clustering
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin Renner (martinrenner)
Assigned to: Nobody/Anonymous (nobody)
Summary: jnp.discoveryPort is not evaluated correctly
Initial Comment:
Hi.
The following code sequence is leading to a
CommunicationException with JBoss 3.2.1 (although JBoss
is listening on port 12345):
Properties env = new Properties();
env.put("jnp.discoveryPort", "12345");
Context ctx = new InitialContext(env);
ctx.lookup("something");
The cause for this exception is in the file
org.jnp.interfaces.NamingContext in the method
"discoverServer()":
In line 1003, the value of "jnp.discoveryPort" is
assigned to the local variable "group". It should be
"port".
A workaround is to specify
env.put("jnp.discoveryPort", "230.0.0.4:12345");
In this case, the value of the port is assigned
correctly to the local variable "port".
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=749586&group_id=22866
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Thread management
Simple thread management, no transaction stuff. Basically, for an SMTP server the request handlers will have to be thread managed of course. The streams will then need to be closed. I don't really need it to be managed separately from the SMTP service and I'm not sure I want it to be. -Andy On 6/5/03 1:22 AM, "David Jencks" <[EMAIL PROTECTED]> wrote: > What do you need? I'd rather avoid having 895 different thread pool > implementations for the 65 actual uses. The particular interface in the > work package is spec mandated, but that doesn't mean we can't have shared > infrastructure. > > david jencks > > On 2003.06.04 22:45 Andrew C. Oliver wrote: >> Isn't quite what I need, no biggy. I'll roll my own. >> >> On 6/4/03 5:04 PM, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: >> >>> Thanks man. >>> >>> On 6/4/03 12:16 PM, "Adrian Brock" <[EMAIL PROTECTED]> wrote: >>> jboss-head in the connector module org.jboss.resource.work Adrian Brock Director of Support Back Office JBoss Group, LLC > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Andrew C. Oliver > Sent: 04 June 2003 17:05 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Thread management > > > Thanks Adrian, > > Any idea on module/dir/tag? > > -Andy > > On 6/4/03 11:27 AM, "Adrian Brock" <[EMAIL PROTECTED]> wrote: > >> Hi Andrew, >> >> David has been working on some thread management stuff >> for the Work contract in jca 1.5 >> I think it is still very simple at the moment. >> >> Regards, >> Adrian >> >> >> Adrian Brock >> Director of Support >> Back Office >> JBoss Group, LLC >> >> >> >>> -Original Message- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On >>> Behalf Of Andrew C. Oliver >>> Sent: 04 June 2003 16:05 >>> To: [EMAIL PROTECTED] >>> Subject: [JBoss-dev] Thread management >>> >>> >>> I'm getting very close to needing to work on multi-threading >>> the JMX SMTP >>> service for Jboss. My approach is to steal what I can from >>> Apache JAMES, >>> though I've re-written a good part of it, ripped out all of >>> the Avalon stuff >>> (even the Avalon folks whine that JAMES uses Avalon >>> "incorrectly", but then >>> again they whine about that for every existing use of >>> Avalon). Its a 70-80% >>> rewrite, 10-20% refactor and 10-20% copy (though its mostly >>> dumb stuff like >>> stream subclasses). >>> >>> In doing this I've ripped out the Watchdog stuff and hence the >>> thread-management. I have my own crazy ideas for how threads >>> should be >>> handled, but first I want to check to see if Jboss has some >>> tried-and-true >>> generic thread management code lying around that I can use? >>> Nothing jumped >>> out at me in perusing the sources. Any pointers would be >>> much appreciated. >>> >>> If enough caffeine finds me, I should have an "alpha" by JavaONE. >>> >>> Thanks, >>> >>> Andy >>> >>> PS. If you're bored you can read about it >>> >>> here: >>> http://linuxintegrators.com/hl30/blog/general?permalink=JBoss+ >> Mail%3A+SMTP.h >> tml >> here: >> > http://linuxintegrators.com/hl30/blog/technology?permalink=JBo ss+Mail.ht > ml > here: > http://linuxintegrators.com/hl30/blog/technology?permalink=JBoss+Mail%2C > +the > +more+I+think+about+it.html > and > here: > http://linuxintegrators.com/hl30/blog/technology?permalink=So+quit+whini > ng+a > nd+just+do+it.html > > Note that my time estimates were a bit under in part because I have a > different audience than "just want to use as my mail server, do as > little > work as possible", in part because they just were ;-) >> >> >> >> -- >> Andrew C. Oliver >> http://www.superlinksoftware.com/poi.jsp >> Custom enhancements and Commercial Implementation for Jakarta POI >> >> http://jakarta.apache.org/poi >> For Java and Excel, Got POI? >> >> >> >> --- >> This SF.net email is sponsored by: Etnus, makers of TotalView, The best >> thread debugger on the planet. Designed with thread debugging features >> you've never dreamed of, try TotalView 6 free at www.etnus.com. >> ___ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > --- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best >
[JBoss-dev] [ jboss-Bugs-733173 ] Farm deployment doesn't work after restart
Bugs item #733173, was opened at 2003-05-06 11:53
Message generated for change (Comment added) made by slaboure
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=733173&group_id=22866
Category: Clustering
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Christian Bjørnbak (bjornbak)
Assigned to: Sacha Labourey (slaboure)
Summary: Farm deployment doesn't work after restart
Initial Comment:
I'm using JBoss 3.2.1 on Linux (kernel 2.4.20). JDK
1.4.1_02
I have succesfully installed two JBoss instances on the
machine and have them running with our ear file in each
server's deploy directory.
The ear file contains an jar file (with 15+ ejbs) and
two war files.
Then I started using farming by:
1) Remove the ear file from deploy.
2) Restart the servers to get rid of the old deployment
directories.
3) Move the ear file to one of the servers' farm directory.
Now it works correctly until I restart one of the
servers then I get three series of errors:
1) First (opposite to when doing normal deployment) the
war can't find any of the classes packaged in the jar
file. (This might not be a bug, but at least it should
work consistently compared to doing a normal deployment)
2) Then I get following error:
2003-05-06 10:21:10,484:[DEBUG]
FarmMemberService - Watch URL for:
file:/srv/jboss/app/jboss-3.2.1/server/all/farm/TouristOnline.ear
->
file:/srv/jboss/app/jboss-3.2.1/server/all/farm/TouristOnline.ear
2003-05-06 10:21:10,485:[ERROR]
FarmMemberService - MBeanException: Exception in MBean
operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[EMAIL PROTECTED] {
url=file:/srv/jboss/app/jboss-3.2.1/server/all/deploy/jbossha-httpsession.sar/ClusteredHttpSessionEB.jar/
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/srv/jboss/app/jboss-3.2.1/server/all/deploy/jbossha-httpsession.sar/ClusteredHttpSessionEB.jar/
lastDeployed: 1052209257007
lastModified: 1052087735000
mbeans:
.. See attachment from line 5021
3) And last the EJB's can't find the datasource no
matter if I deploy oracle-ds.xml in deploy or farm
directories. I get an error like this for each EntityBean:
2003-05-06 10:21:22,382:[ERROR]
EntityContainer - Starting failed
org.jboss.deployment.DeploymentException: Error: can't
find data source: java:/jdbc/OracleDS; - nested
throwable: (javax.naming.NameNotFoundException: jdbc
not bound)
See attachment from line 7476
/Christian Bjørnbak
--
>Comment By: Sacha Labourey (slaboure)
Date: 2003-06-05 15:28
Message:
Logged In: YES
user_id=95900
Can you check with a fresh checkout from Branch_3_2: now
the farm-service.xml file is no more in /deploy but
in /deploy/deploy.last which is deployed after everything.
Consequently, all services and other required app will already
be loaded.
--
Comment By: Christian Bjørnbak (bjornbak)
Date: 2003-05-06 12:01
Message:
Logged In: YES
user_id=651367
The submit denied the attachment trying again with extract...
The new line numbers are line 1 and line 247.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=733173&group_id=22866
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Testsuite Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:161: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ExceptionListenerTest.java:63: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:75: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:129: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:133: warning: stop() in java.lang.Thread has been deprecated [javac] tf.stop(); [javac]^ [javac] F:\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] F:\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] F:\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] F:\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] F:\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] F:\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] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\test\SecurityUnitTestCase.java:606: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\test\SecurityUnitTestCase.java:641: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\test\SecurityUnitTestCase.java:921: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\test\SecurityUnitTestCase.java:970: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\test\SecurityUnitTestCase.java:1035: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\test\SecurityUnitTestCase.java:1085: warning: stop() in java.lang.Thread has been deprecated [javac] t1.stop(); [javac]^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\service\HttpsClient.java:86: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated [javac] if( conn instanceof HttpsURLConnection ) [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\service\HttpsClient.java:91: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated [javac] HttpsURLConnection httpsConn = (HttpsURLConnection) conn; [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\service\HttpsClient.java:91: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated [javac] HttpsURLConnection httpsConn = (HttpsURLConnection) conn; [javac] ^ [javac] F:\jboss\jboss-head\testsuite\src\main\org\j
