11 Replies Latest reply on Oct 4, 2009 9:50 AM by Dee Kay

    Beans disappear in Global JNDI Namespace after running a lon

    Dee Kay Newbie

      Hi 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

        • 1. Re: Beans disappear in Global JNDI Namespace after running a
          Dee Kay Newbie

          The topic should be

          "Beans disappear in Global JNDI Namespace after running a longer time"

          :-)

          • 2. Re: Beans disappear in Global JNDI Namespace after running a
            jaikiran pai Master

            Strange one! Can you look into server.log (for DEBUG level logs) to see if you find more information? Logs like bean being undeployed or removed from JNDI? And is it always after 24000 calls that you see this issue? I mean, if those 24000 calls happen in a single day, do you still see this issue? Which version and vendor of Java do you use? Can you post a sample stateful bean code (with the annotations) and any corresponding xml configuration files for these beans?

            • 3. Re: Beans disappear in Global JNDI Namespace after running a
              Dee Kay Newbie

              I'm running on

              - opensuse 11.1 64bit (also reproducable on 32bit)
              - Java 1.6.0_01-b06 (sun)
              - jboss-5.1.0.Beta1

              I tested this issue yesterday again and started a really stressing test (ca 750 Sessions permanently open).
              It really works fine for about 99000 sessions without any warnings or exceptions.
              After stopping the stress-tool (JMeter) the JNDI namespace looks also as expected.
              Now after 3 hours of sleep the namespace is damaged again.....

              As you can see below my application and beans are still known.
              This is the full output of the JNDI-view from the jmx-console:

              Other components with java:comp namespace:
              
              java:comp namespace of the component jboss.j2ee:ear=CSDatabase.ear,jar=CSDatabaseEJB.jar,name=ServerExportManager,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- de.myapplication.general.database.server.services.ServerExportManager (class: org.jnp.interfaces.NamingContext)
               | | +- em (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
               | +- em (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
              
              
              java:comp namespace of the component jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- org.jboss.profileservice.ejb.SecureProfileServiceBean (class: org.jnp.interfaces.NamingContext)
               | | +- mgtView[link -> SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView] (class: javax.naming.LinkRef)
               | | +- delegate[link -> ProfileService] (class: javax.naming.LinkRef)
               | +- profileService[link -> ProfileService] (class: javax.naming.LinkRef)
              
              
              java:comp namespace of the component jboss.j2ee:ear=CSDatabase.ear,jar=CSDatabaseEJB.jar,name=ServerWebClientRemote,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
               | +- de.myapplication.general.database.server.services.ServerWebClientRemote (class: org.jnp.interfaces.NamingContext)
               | | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
              
              
              java:comp namespace of the component jboss.j2ee:ear=CSDatabase.ear,jar=CSDatabaseEJB.jar,name=ServerDatabaseManager,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
               | +- de.myapplication.general.database.server.services.DatabaseManager (class: org.jnp.interfaces.NamingContext)
               | | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
              
              
              java:comp namespace of the component jboss.j2ee:ear=CSDatabase.ear,jar=CSDatabaseEJB.jar,name=TopicListener,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- de.myapplication.general.database.server.services.TopicListener (class: org.jnp.interfaces.NamingContext)
               | | +- msgDrivCtx[link -> java:comp/EJBContext] (class: javax.naming.LinkRef)
              
              
              java:comp namespace of the component jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- org.jboss.profileservice.ejb.SecureManagementView (class: org.jnp.interfaces.NamingContext)
               | | +- profileService[link -> ProfileService] (class: javax.naming.LinkRef)
               | +- profileService[link -> ProfileService] (class: javax.naming.LinkRef)
              
              
              java:comp namespace of the component jboss.j2ee:ear=CSDatabase.ear,jar=CSDatabaseEJB.jar,name=ServerImportManager,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
               | +- de.myapplication.general.database.server.services.ServerImportManager (class: org.jnp.interfaces.NamingContext)
               | | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
              
              
              java:comp namespace of the component jboss.j2ee:ear=CSDatabase.ear,jar=CSDatabaseEJB.jar,name=ServerClientRequestManager,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
               | +- de.myapplication.general.database.server.services.ServerClientRequestManager (class: org.jnp.interfaces.NamingContext)
               | | +- entityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
              
              
              java:comp namespace of the component jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3 :
              
               +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
               +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
               +- EJBContext (class: javax.ejb.EJBContext)
               +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
               +- env (class: org.jnp.interfaces.NamingContext)
               | +- org.jboss.profileservice.ejb.SecureDeploymentManager (class: org.jnp.interfaces.NamingContext)
               | | +- profileService[link -> ProfileService] (class: javax.naming.LinkRef)
               | +- profileService[link -> ProfileService] (class: javax.naming.LinkRef)
              
              
              
              
              
              
              
              java: Namespace
              
               +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory)
               +- timedCacheFactory (class: javax.naming.Context)
              Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy cannot be cast to javax.naming.NamingEnumeration
               +- policyRegistration (class: org.jboss.security.plugins.JBossPolicyRegistration)
               +- securityManagement (class: org.jboss.security.integration.JNDIBasedSecurityManagement)
               +- DefaultJMSProvider (class: org.jboss.jms.jndi.JNDIProviderAdapter)
               +- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple)
               +- TransactionManager (class: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate)
               +- TransactionPropagationContextImporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
               +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- TransactionPropagationContextExporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
               +- MyApplicationEntityManager (class: org.jboss.jpa.tx.TransactionScopedEntityManager)
               +- MyApplicationDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
               +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
               +- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl)
               +- jaas (class: javax.naming.Context)
               | +- profileservice (class: org.jboss.security.plugins.SecurityDomainContext)
               | +- messaging (class: org.jboss.security.plugins.SecurityDomainContext)
               | +- HsqlDbRealm (class: org.jboss.security.plugins.SecurityDomainContext)
               | +- jboss-web-policy (class: org.jboss.security.plugins.SecurityDomainContext)
               +- comp (class: javax.namingMain.Context)
               +- Mail (class: javax.mail.Session)
              
              
              
              
              
              
              
              Global JNDI Namespace
              
               +- 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#MyApplicationDatabasePU (class: org.hibernate.impl.SessionFactoryImpl)
               +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
               +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- UserTransactionSessionFactory (proxy: $Proxy136 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)
               | +- MyApplication (class: org.jboss.jms.destination.JBossTopic)
              
              
              




              The declaration of my beans only use standard annotations.

              @Remote
              public interface IServerWebClientRemote {
              ....
              }
              
              
              @Stateful
              public class ServerWebClientRemote implements IServerWebClientRemote {
              
               @PersistenceContext(unitName = "MyDatabasePU", type=PersistenceContextType.TRANSACTION)
               private EntityManager entityManager;
              
               @Remove
               public synchronized void disconnect() {
               // Nothing special here, don't call other objects, only instance counting....
               }
              }
              


              I don't use JBOSS-sepcific jars in my project. Only the standard libs delivered from JavaEE5

              - javaee.jar
              - jsf-impl.jar
              - jsf-api.jar
              - jsf-impl.jar
              



              The AS has also closed all connections to my underlying Database (MySQL 5) which have been established by MyApplicationDS.
              And again: No errors, execeptions or warnings!.


              Thanks in advance for your help.

              Daniel


              • 4. Re: Beans disappear in Global JNDI Namespace after running a
                TJ Thinakaran Newbie

                I'm having the same problem. After running a long time, half my JMS and Bean definitions have disappeared from the Global JNDI namespace. This is amajor issue because it happens in high-volume which also means by that time, the application is already in production.

                • 5. Re: Beans disappear in Global JNDI Namespace after running a
                  TJ Thinakaran Newbie

                  I also wanted to add that this is happening on Jboss 4.2.3 on Cent OS 5.1

                  • 6. Re: Beans disappear in Global JNDI Namespace after running a
                    jaikiran pai Master

                    Daniel,

                    Can you just give it a try against @Stateless beans? See if that too shows the same behaviour. The nature of this issue which involves the running the AS for a long period of time makes it a bit difficult to reproduce on my system.

                    • 7. Re: Beans disappear in Global JNDI Namespace after running a
                      TJ Thinakaran Newbie

                      JaiKiran,
                      I don't think it's bean related at all. It's JNDI losing entries randomly.

                      I've documented my problem here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155839
                      Cheers,
                      TJ

                      • 8. Re: Beans disappear in Global JNDI Namespace after running a
                        TJ Thinakaran Newbie

                        happy_robot, did you ever get a response to your problem?

                        • 9. Re: Beans disappear in Global JNDI Namespace after running a
                          Dee Kay Newbie

                          yes, i solved it! i had a jndi.properties file in my EJB-project, after removing this it solved the problem.

                          it seems a little bit curios to me, but running a local JBOSS with my project with this jndi.properties file (targeting to my i-net JBOSS instance running the same project) kills all registered beans on my i-net JBoss on shutdown.

                          greetings and thanks for your help

                          • 10. Re: Beans disappear in Global JNDI Namespace after running a
                            jaikiran pai Master

                             

                            "happy_robot" wrote:

                            it seems a little bit curios to me, but running a local JBOSS with my project with this jndi.properties file (targeting to my i-net JBOSS instance running the same project) kills all registered beans on my i-net JBoss on shutdown.



                            So you have 2 systems A and B with application myapp deployed on both. myapp has a jndi.properties pointing to B. And on shutting down A, the beans deployed in B get unregistered?