[JBoss-dev] New class loading architecture doc available
An excerpt on the class loading architecture from the 3.0.5RC1 version of the JBoss Administration and Development book has been made available on SourceForge here: http://prdownloads.sourceforge.net/jboss/ClassLoading.pdf?download It contains a discussion of the Java type system and how class loading fits in along with common class loading problems such as ClassCastExceptions, IllegalAccessExceptions and LinkageErrors. Send any feedback to [EMAIL PROTECTED] Scott Stark Chief Technology Officer JBoss Group, LLC --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-660405 ] ServiceController.create( ObjectName, Collectio
Bugs item #660405, was opened at 2002-12-31 15:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: Nobody/Anonymous (nobody) Summary: ServiceController.create( ObjectName, Collectio Initial Comment: SHORT VERSION: If I set my user MBeans to be dependent on the LocalTxConnectionManager, I can no longer successfully recycle my connection pool. LONG VERSION: (I am running JBoss 3.0.4, JDK 1.4.1_01, Win2K) I am using an MBean configuration file, sybase- service.xml, which is laid out almost identically to the hsqldb-service.xml file. It contains a LocalTxCM MBean, which is dependent on a LocalTxDS MBean and a LocalTXPool MBean. Normally, if I touch sybase-service.xml everything works great. ServiceController.install() is called with LocalTxCM, LocalTxDS, and LocalTxPool. ServiceController.create() is called with LocalTxCM, but it waits because the iDependOn beans haven't been created yet. After LocalTxPool is created, we iterate through the dependsOnMe mbeans and the LocalTxCM MBean is created. All is good. But if I introduce my own MBeans that are dependent on the database connection pool, then the ServiceController.create() method behaves differently. I use the following tag in my user MBeans: dependsjboss.jca:service=LocalTxCM,name=sybaseD S/depends Now I can start the JBoss server just fine. But if I recycle the connection pool, here is what happens: ServiceController.install() is called just as before. The ServiceContexts for all three MBeans look fine. In particular, the iDependOn and the dependsOnMe lists are correct, and my userMBeans have been added to the dependsOnMe list for LocalTxCM. When ServiceController.create() method is called on LocalTxCM, it defers again. When ServiceController.create() is called on the other two MBeans, it seems to succeed. The create() methods are successfully executed on these MBeans. Thanks to dependsOnMe, ServiceController.create() is called on LocalTxCM again. But now when we get the ServiceContexts in the iDependOn list for LocalTxCM, they are all defined as state: NOTYETINSTALLED. So LocalTxCM still fails to create because it believes its dependent MBeans have not yet been created. This leads to the predictable log message: ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()' Cause: Incomplete Deployment listing: Packages waiting for a deployer: none Incompletely deployed packages: none MBeans waiting for classes: none MBeans waiting for other MBeans: ... ObjectName: jboss.jca:service=LocalTxCM,name=sybaseDS state: CONFIGURED I Depend On: jboss.jca:service=LocalTxDS,name=sybaseDS jboss.jca:service=LocalTxPool,name=sybaseDS jboss.jca:service=CachedConnectionManager jboss.security:service=JaasSecurityManager jboss.jca:service=RARDeployer jboss.jca:service=LocalTxDS,name=sybaseDS jboss.jca:service=LocalTxPool,name=sybaseDS Depends On Me: (My User MBeans) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-660405 ] ServiceController.create( ObjectName, Collectio
Bugs item #660405, was opened at 2002-12-31 15:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: David Jencks (d_jencks) Summary: ServiceController.create( ObjectName, Collectio Initial Comment: SHORT VERSION: If I set my user MBeans to be dependent on the LocalTxConnectionManager, I can no longer successfully recycle my connection pool. LONG VERSION: (I am running JBoss 3.0.4, JDK 1.4.1_01, Win2K) I am using an MBean configuration file, sybase- service.xml, which is laid out almost identically to the hsqldb-service.xml file. It contains a LocalTxCM MBean, which is dependent on a LocalTxDS MBean and a LocalTXPool MBean. Normally, if I touch sybase-service.xml everything works great. ServiceController.install() is called with LocalTxCM, LocalTxDS, and LocalTxPool. ServiceController.create() is called with LocalTxCM, but it waits because the iDependOn beans haven't been created yet. After LocalTxPool is created, we iterate through the dependsOnMe mbeans and the LocalTxCM MBean is created. All is good. But if I introduce my own MBeans that are dependent on the database connection pool, then the ServiceController.create() method behaves differently. I use the following tag in my user MBeans: dependsjboss.jca:service=LocalTxCM,name=sybaseD S/depends Now I can start the JBoss server just fine. But if I recycle the connection pool, here is what happens: ServiceController.install() is called just as before. The ServiceContexts for all three MBeans look fine. In particular, the iDependOn and the dependsOnMe lists are correct, and my userMBeans have been added to the dependsOnMe list for LocalTxCM. When ServiceController.create() method is called on LocalTxCM, it defers again. When ServiceController.create() is called on the other two MBeans, it seems to succeed. The create() methods are successfully executed on these MBeans. Thanks to dependsOnMe, ServiceController.create() is called on LocalTxCM again. But now when we get the ServiceContexts in the iDependOn list for LocalTxCM, they are all defined as state: NOTYETINSTALLED. So LocalTxCM still fails to create because it believes its dependent MBeans have not yet been created. This leads to the predictable log message: ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()' Cause: Incomplete Deployment listing: Packages waiting for a deployer: none Incompletely deployed packages: none MBeans waiting for classes: none MBeans waiting for other MBeans: ... ObjectName: jboss.jca:service=LocalTxCM,name=sybaseDS state: CONFIGURED I Depend On: jboss.jca:service=LocalTxDS,name=sybaseDS jboss.jca:service=LocalTxPool,name=sybaseDS jboss.jca:service=CachedConnectionManager jboss.security:service=JaasSecurityManager jboss.jca:service=RARDeployer jboss.jca:service=LocalTxDS,name=sybaseDS jboss.jca:service=LocalTxPool,name=sybaseDS Depends On Me: (My User MBeans) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 31-December-2002
JBoss daily test results SUMMARY Number of tests run: 1004 Successful tests: 998 Errors:5 Failures: 1 [time of test: 2002-12-31.12-10 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1_03-69] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.2.3] See http://users.jboss.org/~starksm/Branch_3_0/2002-12-31.12-10 for details 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: LocalWrapperCleanupUnitTestCase Test: testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: Row committed, autocommit still on! - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: SimpleUnitTestCase Test:testSecureHttpInvoker(org.jboss.test.naming.test.SimpleUnitTestCase) Type:error Exception: javax.security.auth.login.LoginException Message: Missing users.properties file. - Suite: SimpleUnitTestCase Test:testLoginInitialContext(org.jboss.test.naming.test.SimpleUnitTestCase) Type:error Exception: javax.naming.AuthenticationException Message: Failed to login using protocol=testLoginInitialContext - Suite: HttpsUnitTestCase Test:testHttpsURL(org.jboss.test.security.test.HttpsUnitTestCase) Type:error Exception: java.io.IOException Message: Failed to get SSLContext for TLS algorithm - Suite: BeanStressTestCase Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: expected a client deadlock for AB BA - --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-660405 ] ServiceController.create( ObjectName, Collectio
Bugs item #660405, was opened at 2002-12-31 15:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: David Jencks (d_jencks) Summary: ServiceController.create( ObjectName, Collectio Initial Comment: SHORT VERSION: If I set my user MBeans to be dependent on the LocalTxConnectionManager, I can no longer successfully recycle my connection pool. LONG VERSION: (I am running JBoss 3.0.4, JDK 1.4.1_01, Win2K) I am using an MBean configuration file, sybase- service.xml, which is laid out almost identically to the hsqldb-service.xml file. It contains a LocalTxCM MBean, which is dependent on a LocalTxDS MBean and a LocalTXPool MBean. Normally, if I touch sybase-service.xml everything works great. ServiceController.install() is called with LocalTxCM, LocalTxDS, and LocalTxPool. ServiceController.create() is called with LocalTxCM, but it waits because the iDependOn beans haven't been created yet. After LocalTxPool is created, we iterate through the dependsOnMe mbeans and the LocalTxCM MBean is created. All is good. But if I introduce my own MBeans that are dependent on the database connection pool, then the ServiceController.create() method behaves differently. I use the following tag in my user MBeans: dependsjboss.jca:service=LocalTxCM,name=sybaseD S/depends Now I can start the JBoss server just fine. But if I recycle the connection pool, here is what happens: ServiceController.install() is called just as before. The ServiceContexts for all three MBeans look fine. In particular, the iDependOn and the dependsOnMe lists are correct, and my userMBeans have been added to the dependsOnMe list for LocalTxCM. When ServiceController.create() method is called on LocalTxCM, it defers again. When ServiceController.create() is called on the other two MBeans, it seems to succeed. The create() methods are successfully executed on these MBeans. Thanks to dependsOnMe, ServiceController.create() is called on LocalTxCM again. But now when we get the ServiceContexts in the iDependOn list for LocalTxCM, they are all defined as state: NOTYETINSTALLED. So LocalTxCM still fails to create because it believes its dependent MBeans have not yet been created. This leads to the predictable log message: ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()' Cause: Incomplete Deployment listing: Packages waiting for a deployer: none Incompletely deployed packages: none MBeans waiting for classes: none MBeans waiting for other MBeans: ... ObjectName: jboss.jca:service=LocalTxCM,name=sybaseDS state: CONFIGURED I Depend On: jboss.jca:service=LocalTxDS,name=sybaseDS jboss.jca:service=LocalTxPool,name=sybaseDS jboss.jca:service=CachedConnectionManager jboss.security:service=JaasSecurityManager jboss.jca:service=RARDeployer jboss.jca:service=LocalTxDS,name=sybaseDS jboss.jca:service=LocalTxPool,name=sybaseDS Depends On Me: (My User MBeans) -- Comment By: Corby (corby) Date: 2002-12-31 21:03 Message: Logged In: YES user_id=25032 The attached files comprise a test case which illustrates the bug -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
