[JBoss-dev] [ jboss-Bugs-626893 ] Suggestion to CMP (relations read-ahead)
Bugs item #626893, was opened at 2002-10-22 12:58 Message generated for change (Settings changed) made by echofloripa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=626893&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: None Priority: 8 Submitted By: Emerson Cargnin (echofloripa) Assigned to: Nobody/Anonymous (nobody) Summary: Suggestion to CMP (relations read-ahead) Initial Comment: I have a suggestion regarding to CMP : why not create a configuration to a find method to allow the container to load the relationships of a bean? This could be useful in the cases you have to read all the beans(or a good amount of then) and all (or almost all) relationships of them. eg : in a report you will have a sql to finding the pk's, one (at least) to load the bean data and one sql to each relation you have to report (for each bean). I think that one of the worse problem with CMP is that : database overhead. CMP generates too much sql commands that in some cases could be handled by fewer (if not one) sql commands. The DBA's in my company didn't like very much the trace they saw in the database for a very simple app. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=626893&group_id=22866 --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment
I've modified the deployment system to allow for multiple xml deployment descriptors. XSLSubDeployer can be configured via the Properties valued DdNameToKeyMap property to import the specified dds and store them in the DeploymentInfo under the specified key. The properties lines look like =KEY. I've also added the new DeploymentInfoURIResolverFactory which can resolve uris to documents in the current deployment info or documents in other DeploymentInfo mbeans. URIs are of the form jboss-di://##. The deployment-info-name and xpath-expression are optional. The DeploymentInfoDocumentURIResolver is now obsolete. I've discovered that use of two # characters in a URI is ungrammatical so the first will be changed to ! shortly. I've simplified the ejb container mbeans to remove common code to the Container class and allow deployment of MDBs with arbitrary interfaces per the ejb 2.1 spec. However, only jms MessageListener MDBs can be deployed at the moment. Deployment proceeds by constructing and deploying an ActivationSpec xmbean instance from the ejb 2.0 mdb dd. Finally, I've modified message delivery to always use the jmsra jca 1.5 adapter and correspondingly removed the asf classes. thanks david jencks /** * David Jencks * Partner * Core Developers Network * http://www.coredevelopers.net **/ --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-755107 ] Clustered Singleton and Scheduler
Change Notes item #755107, was opened at 2003-06-16 02:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=755107&group_id=22866 Category: Clustering Group: v3.2 Status: Open Priority: 5 Submitted By: Ivelin Atanasoff Ivanov (ivelin) Assigned to: Nobody/Anonymous (nobody) Summary: Clustered Singleton and Scheduler Initial Comment: When a Singleton MBean is deployed in a cluster, it is guaranteed that only one of the nodes will run the desired service. When the node that runs the service fails, another one takes over. The Scheduler service continues to work as in standalone mode even when it is deployed in a cluster. Detailed description of the new features is described at http://www.cocoonhive.org/articles/jboss/20030610/ha singleton.html . -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=755107&group_id=22866 --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 96 % ( 1122 / 1161 ) - 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: 1161 Successful tests: 1122 Errors:28 Failures: 11 [time of test: 2003-06-16.02-17 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 - ===Mon Jun 16 03:27:52 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: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] Running org.objectweb.jtests.jms.conform.selector.SelectorSyntaxTest [junit] TEST org.objectweb.jtests.jms.conform.selector.SelectorSyntaxTest FAILED (timeout) [junit] Running org.objectweb.jtests.jms.conform.selector.SelectorTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 95.495 sec [junit] Running org.objectweb.jtests.jms.conform.session.QueueSessionTest [junit] TEST org.objectweb.jtests.jms.conform.session.QueueSessionTest FAILED (timeout) [junit] Running org.objectweb.jtests.jms.conform.session.SessionTest [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 78.263 sec [junit] Running org.objectweb.jtests.jms.conform.session.TopicSessionTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 17.347 sec [junit] Running org.objectweb.jtests.jms.conform.topic.TemporaryTopicTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 7.112 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: 11.561 sec [junit] Running org.jboss.test.security.test.LoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 48.837 sec [junit] Running org.jboss.test.security.test.NamespacePermissionsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.826 sec [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.423 sec [junit] Running org.jboss.test.security.test.XMLLoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 4.4 sec tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] TEST org.jboss.test.management.test.JSR77SpecUnitTestCase FAILED (timeout) tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.063 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 0.631 sec [junit] Running org.jboss.test.util.test.Scheduler2UnitTestCase [junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 146.387 sec [junit] TEST org.jboss.test.util.test.Scheduler2UnitTestCase FAILED [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] TEST org.jboss.test.util.test.SchedulerUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.util.test.ServerSideExampleUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 4.99 sec tests-jbossmx-compliance: [junit] Running org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.657 sec [junit] Running org.jboss.test.jbossmx.compliance.monitor.BasicTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 7.617 sec [junit] Running org.jboss.test.jbossmx.compliance.notcompliant.NCMBeanTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.323 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.BasicTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.412 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.CanonicalTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.305 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase [junit] Tests run: 53, Failures: 0, Errors: 0, Time elapsed: 1.768 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.PatternTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 2.02 sec [junit] Running org.jboss.test.jbossmx.compliance.registration.RegistrationTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 2.194 sec [junit] Running org.jboss.test.jbossmx.compliance.relation.BasicTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.835 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerFactoryTestCase [junit] Tests run: 7, Failures: 0, Errors
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: 97 % ( 1216 / 1249 ) - 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: 1249 Successful tests: 1216 Errors:15 Failures: 18 [time of test: 2003-06-16.00-16 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: 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: StatefulSessionUnitTestCase Test: testLocalInterfacePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test: testSessionRefPassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test: testSessionHandlePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - ===Mon Jun 16 01:28:56 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: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 8.832 sec [junit] Running org.objectweb.jtests.jms.conform.session.QueueSessionTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 7.631 sec [junit] Running org.objectweb.jtests.jms.conform.session.SessionTest [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 13.299 sec [junit] Running org.objectweb.jtests.jms.conform.session.TopicSessionTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 7.751 sec [junit] Running org.objectweb.jtests.jms.conform.topic.TemporaryTopicTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.369 sec tests-client-unit: [junit] Running org.jboss.test.jrmp.test.DynLoadingUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 8.112 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: 17.405 sec [junit] Running org.jboss.test.security.test.HttpsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 7.09 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.306 sec [junit] Running org.jboss.test.security.test.LoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 5.328 sec [junit] Running org.jboss.test.security.test.NamespacePermissionsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.203 sec [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.574 sec [junit] Running org.jboss.test.security.test.XMLLoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 6.65 sec tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 1, Errors: 2, Time elapsed: 34.119 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.362 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.674 sec [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.876 sec [junit] Running org.jboss.test.util.test.ServerSideExampleUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 4.567 sec tests-jbossmx-compliance: [junit] Running org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.462 sec [junit] Running org.jboss.test.jbossmx.compliance.monitor.BasicTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 7.391 sec [junit] Running org.jboss.test.jbossmx.compliance.notcompliant.NCMBeanTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 2.744 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.57 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase [junit] Tests run: 53, Failures: 0, Errors: 0, Time elapsed: 3.705 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.PatternTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 1.652 sec [junit] Running org.jboss.test.jbossmx.compliance.registration.RegistrationTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.261 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: 2.654 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time e
[JBoss-dev] [ jboss-Bugs-754096 ] EmbeddedCatalinaService41MBean missing UseJBossWebLoader
Bugs item #754096, was opened at 2003-06-13 10:11 Message generated for change (Settings changed) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=754096&group_id=22866 Category: JBossWeb Group: CVS HEAD >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Dima Berastau (alduin) Assigned to: Nobody/Anonymous (nobody) Summary: EmbeddedCatalinaService41MBean missing UseJBossWebLoader Initial Comment: setting true in jboss- service.xml of EmbeddedCatalinaService41 fails because org.jboss.web.catalina.EmbeddedCatalinaService41MBean is missing a pair of getters and setters, namely: public boolean getUseJBossWebLoader(); public void setUseJBossWebLoader(); if someone could patch up the relevant MBean interface that would be great. affected version: JBoss 3.2.2RC1-tomcat-4.1.24 regards, dima -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=754096&group_id=22866 --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] DTD links to Jboss website broken
Ok, fixed. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Stefan Reich" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 13, 2003 5:27 PM Subject: [JBoss-dev] DTD links to Jboss website broken > A recent change broke the links to > http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_2.dtd and other DTDs. > > Stefan > --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
