Beans disappear in Global JNDI Namespace after running a lon
happy_robot May 7, 2009 4:59 AMHi all,
i'm currently using JBoss 5.1.0 Beta 1 and there seems to be a problem with a mutating Global JNDI Namespace and it's reproducable.
My EJ3-Beans (all statefull) are successfully bound at startup and visible on the Console using the JNDIView-service.
After running my app for 3 days and finally 24000 calls to my beans and without any reported exceptions or memory leaks these entries disappear in the global namespace. My application is still installed and running and i can see now only these beans of my application which i've never called.
I get now exceptions during the whole lifecycle! The simply disappear!
And last but not least they'are still visible on the jmx-console under the j2ee-list.......!?!?
Global JNDI Namespace at startup (Application-part=red, Beans=blue):
+- UserTransactionSessionFactory (proxy: $Proxy136 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory) +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory) +- SecureManagementView (class: org.jnp.interfaces.NamingContext) | +- remote-org.jboss.deployers.spi.management.ManagementView (class: Proxy for: org.jboss.deployers.spi.management.ManagementView) | +- remote (class: Proxy for: org.jboss.deployers.spi.management.ManagementView) +- SecureDeploymentManager (class: org.jnp.interfaces.NamingContext) | +- remote-org.jboss.deployers.spi.management.deploy.DeploymentManager (class: Proxy for: org.jboss.deployers.spi.management.deploy.DeploymentManager) | +- remote (class: Proxy for: org.jboss.deployers.spi.management.deploy.DeploymentManager) +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory) +- persistence.unit:unitName=CSDatabase.ear (class: org.jnp.interfaces.NamingContext) | +- CSDatabaseEJB.jar#OrbizDatabasePU (class: org.hibernate.impl.SessionFactoryImpl) +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- topic (class: org.jnp.interfaces.NamingContext) | +- orbiz (class: org.jboss.jms.destination.JBossTopic) +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- ProfileService (class: AOPProxy$0) +- SecureProfileService (class: org.jnp.interfaces.NamingContext) | +- remote (class: Proxy for: org.jboss.profileservice.spi.ProfileService) | +- remote-org.jboss.profileservice.spi.ProfileService (class: Proxy for: org.jboss.profileservice.spi.ProfileService) +- CSDatabase (class: org.jnp.interfaces.NamingContext) | +- ServerImportManager (class: org.jnp.interfaces.NamingContext) | | +- remote-de.myapplication.general.database.server.services.ServerImportManagerRemote (class: Proxy for: de.myapplication.general.database.server.services.ServerImportManagerRemote) | | +- remote (class: Proxy for: de.myapplication.general.database.server.services.ServerImportManagerRemote) | +- ServerExportManager (class: org.jnp.interfaces.NamingContext) | | +- remote-de.myapplication.general.database.server.services.ServerExportManagerRemote (class: Proxy for: de.myapplication.general.database.server.services.ServerExportManagerRemote) | | +- remote (class: Proxy for: de.myapplication.general.database.server.services.ServerExportManagerRemote) | +- ServerClientRequestManager (class: org.jnp.interfaces.NamingContext) | | +- remote-de.myapplication.general.database.server.services.ServerClientRequestManagerRemote (class: Proxy for: de.myapplication.general.database.server.services.ServerClientRequestManagerRemote) | | +- remote (class: Proxy for: de.myapplication.general.database.server.services.ServerClientRequestManagerRemote) | +- ServerWebClientRemote (class: org.jnp.interfaces.NamingContext) | | +- remote (class: Proxy for: de.myapplication.general.database.server.services.IServerWebClientRemote) | | +- remote-de.myapplication.general.database.server.services.IServerWebClientRemote (class: Proxy for: de.myapplication.general.database.server.services.IServerWebClientRemote) | +- ServerDatabaseManager (class: org.jnp.interfaces.NamingContext) | | +- remote (class: Proxy for: de.myapplication.general.database.server.services.ServerDatabaseManagerRemote) | | +- remote-de.myapplication.general.database.server.services.ServerDatabaseManagerRemote (class: Proxy for: de.myapplication.general.database.server.services.ServerDatabaseManagerRemote) +- queue (class: org.jnp.interfaces.NamingContext) | +- DLQ (class: org.jboss.jms.destination.JBossQueue) | +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue) +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction) +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- jmx (class: org.jnp.interfaces.NamingContext) | +- invoker (class: org.jnp.interfaces.NamingContext) | | +- RMIAdaptor (proxy: $Proxy138 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt) | +- rmi (class: org.jnp.interfaces.NamingContext) | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef) +- TomcatAuthenticators (class: java.util.Properties) +- console (class: org.jnp.interfaces.NamingContext) | +- PluginManager (proxy: $Proxy140 implements org.jboss.console.manager.PluginManagerMBean (no security manager: RMI class loader disabled))
Global JNDI Namespace after 3 days:
+- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction) +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory) +- persistence.unit:unitName=CSDatabase.ear (class: org.jnp.interfaces.NamingContext) | +- CSDatabaseEJB.jar#OrbizDatabasePU (class: org.hibernate.impl.SessionFactoryImpl) +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory) +- CSDatabase (class: org.jnp.interfaces.NamingContext) | +- ServerImportManager (class: org.jnp.interfaces.NamingContext) | | +- remote (class: Proxy for: de.myapplication.general.database.server.services.ServerImportManagerRemote) | | +- remote-de.myapplication.general.database.server.services.ServerImportManagerRemote (class: Proxy for: de.myapplication.general.database.server.services.ServerImportManagerRemote) +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- UserTransactionSessionFactory (proxy: $Proxy137 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory) +- console (class: org.jnp.interfaces.NamingContext) | +- PluginManager (proxy: $Proxy140 implements org.jboss.console.manager.PluginManagerMBean (no security manager: RMI class loader disabled)) +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) +- TomcatAuthenticators (class: java.util.Properties) +- ProfileService (class: AOPProxy$0) +- jmx (class: org.jnp.interfaces.NamingContext) | +- invoker (class: org.jnp.interfaces.NamingContext) | | +- RMIAdaptor (proxy: $Proxy138 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt) | +- rmi (class: org.jnp.interfaces.NamingContext) | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef) +- queue (class: org.jnp.interfaces.NamingContext) | +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue) | +- DLQ (class: org.jboss.jms.destination.JBossQueue) +- topic (class: org.jnp.interfaces.NamingContext) | +- orbiz (class: org.jboss.jms.destination.JBossTopic)
All are still visible in the j2ee-view!
Any ideas? Thanks in advance
Daniel