4 Replies Latest reply on Apr 13, 2010 2:10 AM by Kobi Ianko

    jboss 5.0 and ejb 2.1 deployments

    Roelof Naude Newbie

      hi all,

      in the process of migrating to jboss 5.0 i 've run into the following when deploying ejb 2.1 beans (entities and stateless session).

      the console prints several message like this:
      10:38:39,554 INFO [EjbDeployer] installing bean: ejb/mtnusa_stats-6.7-SNAPSHOT.jar#CommandLog,uid1092787950
      10:38:39,554 INFO [EjbDeployer] with dependencies:
      10:38:39,554 INFO [EjbDeployer] and supplies:
      10:38:39,554 INFO [EjbDeployer] jndi:mtn_usa/commandlog/CommandLog
      10:38:39,554 INFO [EjbDeployer] jndi:CommandLog

      but; viewing the jndi tree via the jmx-console's JNDIView does not reflect the above mappings.

      the lookups in our code also fails miserably, e.g.:
      javax.naming.NameNotFoundException: mtn_usa not bound

      any idea on how to debug this? is there anything specific that needs to be done? rewriting all the beans as ejb3 compliant beans is not yet possible at this stage.

      anything else i can try?

        • 1. Re: jboss 5.0 and ejb 2.1 deployments
          jaikiran pai Master

          Which exact version of JBoss-5.0 do you use? And which version of Java? Please post the contents of your JNDI tree. Also, do you have a jboss.xml where you specify the JNDI names for your EJBs? If yes, then post that too.


          While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window. Please hit the preview button to see that you post a properly formatted.

          • 2. Re: jboss 5.0 and ejb 2.1 deployments
            Roelof Naude Newbie

             

            "jaikiran" wrote:
            Which exact version of JBoss-5.0 do you use?

            08:14:45,650 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171046)
            


            "jaikiran" wrote:

            And which version of Java? Please post the contents of your JNDI tree. Also, do you have a jboss.xml where you specify the JNDI names for your EJBs? If yes, then post that too.


            08:14:50,553 INFO [ServerInfo] Java version: 1.5.0_12,Sun Microsystems Inc.
            08:14:50,553 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_12-b04,Sun Microsystems Inc.
            08:14:50,554 INFO [ServerInfo] OS-System: Linux 2.6.23.17-88.fc7,amd64
            


            i cannot provide a jndi tree at this stage as trying to access to the jmx-console fails. during this time jboss is also running at 100% cpu.

            the relevant entry from the jboss.xml file:
            <entity>
             <ejb-name>CommandLog</ejb-name>
             <local-jndi-name>mtn_usa/commandlog/CommandLog</local-jndi-name>
             <method-attributes/>
            </entity>
            


            • 3. Re: jboss 5.0 and ejb 2.1 deployments
              Roelof Naude Newbie

               

              "jaikiran" wrote:
              Please post the contents of your JNDI tree.


              The jndi tree:
              java: Namespace
              
               +- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl)
               +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
               +- policyRegistration (class: org.jboss.security.plugins.JBossPolicyRegistration)
               +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory)
               +- comp (class: javax.namingMain.Context)
               +- JBossCorbaPOA (class: org.omg.PortableServer.POA)
               +- JBossCorbaORB (class: org.omg.CORBA.ORB)
               +- TransactionPropagationContextExporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
               +- TransactionManager (class: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate)
               +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- timedCacheFactory (class: javax.naming.Context)
              Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy
               +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- jaas (class: javax.naming.Context)
               | +- HsqlDbRealm (class: org.jboss.security.plugins.SecurityDomainContext)
               +- JBossCorbaInterfaceRepositoryPOA (class: org.omg.PortableServer.POA)
               +- JBossCorbaNaming (class: org.omg.CosNaming.NamingContextExt)
               +- TransactionPropagationContextImporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
               +- CacheManager (class: org.jboss.ha.cachemanager.CacheManager)
               +- Mail (class: javax.mail.Session)
               +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- USA3_ConfigDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
               +- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple)
               +- DefaultJMSProvider (class: org.jboss.jms.jndi.JNDIProviderAdapter)
               +- securityManagement (class: org.jboss.security.integration.JNDIBasedSecurityManagement)
              
              Global JNDI Namespace
              
               +- UserTransactionSessionFactory (proxy: $Proxy150 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
               +- jmx (class: org.jnp.interfaces.NamingContext)
               | +- rmi (class: org.jnp.interfaces.NamingContext)
               | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
               | +- invoker (class: org.jnp.interfaces.NamingContext)
               | | +- RMIAdaptor (proxy: $Proxy149 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
               +- queue (class: org.jnp.interfaces.NamingContext)
               | +- DLQ (class: org.jboss.jms.destination.JBossQueue)
               | +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue)
               +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
               +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- HASessionState (class: org.jnp.interfaces.NamingContext)
               | +- Default (class: org.jboss.ha.hasessionstate.server.HASessionStateImpl)
               +- console (class: org.jnp.interfaces.NamingContext)
               | +- PluginManager (proxy: $Proxy152 implements interface org.jboss.console.manager.PluginManagerMBean)
               +- HAPartition (class: org.jnp.interfaces.NamingContext)
               | +- DefaultPartition (class: org.jboss.ha.framework.server.ClusterPartition)
               +- topic (class: org.jnp.interfaces.NamingContext)
               +- JAXR (class: org.apache.ws.scout.registry.ConnectionFactoryImpl)
               +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
               +- invokers (class: org.jnp.interfaces.NamingContext)
               | +- segfault.localdomain (class: org.jnp.interfaces.NamingContext)
               | | +- iiop (class: org.jboss.invocation.iiop.IIOPInvoker)
               +- TomcatAuthenticators (class: java.util.Properties)
               +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
               +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
              
              


              • 4. Re: jboss 5.0 and ejb 2.1 deployments
                Kobi Ianko Apprentice

                Hi,

                got the same problem on JBoss 5.1 with ejb2.1,

                have you found any solution for this?

                 

                10x,

                Kobi