6 Replies Latest reply on Mar 3, 2008 10:38 AM by jaikiran pai

    JBoss installing Problem

    Malte Poltermann Newbie

      Hi everybody,

      we have actually a JBoss 3.0.4 running on a RH Advanced Server 2 with a DB2 7.2 Database. We are going to move this JBoss on a new machine, which is running RHEL 5 with a DB2 8.2 Database.

      Some facts to the Server: 8 GB RAM, Dual Quad-Core Xeon, 64bit RHEL 5.

      I installed the new Sun JAVA SDK and copied the whole JBoss 3.0.4 to the new Server.

      After starting the JBoss, i have only one instance running and JBoss doesnt connect to the DB.

      i get the following WARN-message

      16:04:00,361 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:jndiName=isip/fundFreigabe,service=EJB
      org.jboss.deployment.DeploymentException: Error: can't find data source: java:/DB2ISIPDS; - nested throwable: (javax.naming.NameNotFoundException: DB2ISIPDS not bound)
       at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.<init>(JDBCEntityBridge.java:99)
       at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:397)
       at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:339)
       at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:198)
       at org.jboss.ejb.EntityContainer.start(EntityContainer.java:376)
       at org.jboss.ejb.Container.invoke(Container.java:756)
       at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1058)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy5.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:398)
       at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
       at $Proxy18.start(Unknown Source)
       at org.jboss.ejb.EjbModule.startService(EjbModule.java:430)
       at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
       at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy5.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:398)
       at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
       at $Proxy10.start(Unknown Source)
       at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:395)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
       at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:224)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.deployment.SubDeployerSupport.startService(SubDeployerSupport.java:98)
       at org.jboss.ejb.EJBDeployer.startService(EJBDeployer.java:131)
       at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
       at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy5.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:398)
       at org.jboss.system.ServiceController.start(ServiceController.java:418)
       at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
       at $Proxy3.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
       at $Proxy4.deploy(Unknown Source)
       at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
       at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
       at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
       at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
       at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:398)
       at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
       at $Proxy3.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:569)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
       at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
       at org.jboss.Main.boot(Main.java:148)
       at org.jboss.Main$1.run(Main.java:381)
       at java.lang.Thread.run(Thread.java:534)
      Caused by: javax.naming.NameNotFoundException: DB2ISIPDS not bound
       at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
       at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
       at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
       at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:464)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:443)
       at javax.naming.InitialContext.lookup(InitialContext.java:347)
       at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.<init>(JDBCEntityBridge.java:96)
       ... 111 more
      


      Does anyone have a clue what i can do to make JBoss working? Is the JBoss 3.0.4 not compatible with RHEL5? If not, can anyone give me some official infos for this fact.

      many greets from germany,

      Malte Poltermann

        • 1. Re: JBoss installing Problem
          jaikiran pai Master

           

          org.jboss.deployment.DeploymentException: Error: can't find data source: java:/DB2ISIPDS; - nested t
          hrowable: (javax.naming.NameNotFoundException: DB2ISIPDS not bound)


          Did you deploy your datasource (*-ds.xml file)? Usually you place this *-ds.xml file in the deploy folder. Make sure you have deployed the datasource. In case you have the *-ds.xml in the deploy folder, then post the contents here.


          • 2. Re: JBoss installing Problem
            Malte Poltermann Newbie

            Hi,

            yes, i deployed the datasource. This is the content of the datasource.

            my db2-service.xml

            <?xml version="1.0" encoding="UTF-8"?>
            <!-- ==================================================================== -->
            <!-- ConnectionManager setup for default IBM DB2 -->
            <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
            <!-- ==================================================================== -->
            <server>
             <!-- Database Connection for ISIP Database -->
             <mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=DB2ISIPDS">
             <!-- Include a login module configuration named DB2DbRealm.
             Update your login-conf.xml, here is an example for a
             ConfiguredIdentityLoginModule:
            
             <application-policy name = "DB2DbRealm">
             <authentication>
             <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
             <module-option name = "principal">yourprincipal</module-option>
             <module-option name = "userName">yourusername</module-option>
             <module-option name = "password">yourpassword</module-option>
             <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DB2ISIPDS</module-option>
             </login-module>
             </authentication>
             </application-policy>
            
             NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
             module-option name = "managedConnectionFactoryName"
             must match the object name of the ConnectionManager you are configuring here.
             -->
             <!--uncomment out this line if you are using the DB2DbRealm above
             <attribute name="SecurityDomainJndiName">DB2DbRealm</attribute>
             -->
             <depends optional-attribute-name="ManagedConnectionFactoryName">
             <!--embedded mbean-->
             <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=DB2ISIPDS">
             <attribute name="JndiName">DB2ISIPDS</attribute>
             <attribute name="ManagedConnectionFactoryProperties">
             <properties>
             <config-property name="ConnectionURL" type="java.lang.String">jdbc:db2:isip2</config-property>
             <config-property name="DriverClass" type="java.lang.String">COM.ibm.db2.jdbc.app.DB2Driver</config-property>
             <!--set these only if you want only default logins, not through JAAS -->
             <config-property name="UserName" type="java.lang.String">my db-user</config-property>
             <config-property name="Password" type="java.lang.String">my db-user-pw</config-property>
             </properties>
             </attribute>
             <!--Below here are advanced properties -->
             <!--hack-->
             <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper</depends>
             </mbean>
             </depends>
             <depends optional-attribute-name="ManagedConnectionPool">
             <!--embedded mbean-->
             <mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" name="jboss.jca:service=LocalTxPool,name=DB2ISIPDS">
             <attribute name="MinSize">0</attribute>
             <attribute name="MaxSize">50</attribute>
             <attribute name="BlockingTimeoutMillis">5000</attribute>
             <attribute name="IdleTimeoutMinutes">15</attribute>
             <!--
             criteria indicates if Subject (from security domain) or app supplied
             parameters (such as from getConnection(user, pw)) are used to distinguish
             connections in the pool. Choices are
             ByContainerAndApplication (use both),
             ByContainer (use Subject),
             ByApplication (use app supplied params only),
             ByNothing (all connections are equivalent, usually if adapter supports
             reauthentication)-->
             <attribute name="Criteria">ByContainer</attribute>
             </mbean>
             </depends>
             <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
             <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
             <attribute name="TransactionManager">java:/TransactionManager</attribute>
             <!--make the rar deploy! hack till better deployment-->
             <depends>jboss.jca:service=RARDeployer</depends>
             </mbean>
            
            
             <!-- Database Connection for PSM Database -->
             <mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=DB2PSMDS">
             <!-- Include a login module configuration named DB2DbRealm.
             Update your login-conf.xml, here is an example for a
             ConfiguredIdentityLoginModule:
            
             <application-policy name = "DB2DbRealm">
             <authentication>
             <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
             <module-option name = "principal">yourprincipal</module-option>
             <module-option name = "userName">yourusername</module-option>
             <module-option name = "password">yourpassword</module-option>
             <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DB2PSMDS</module-option>
             </login-module>
             </authentication>
             </application-policy>
            
             NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
             module-option name = "managedConnectionFactoryName"
             must match the object name of the ConnectionManager you are configuring here.
             -->
             <!--uncomment out this line if you are using the DB2DbRealm above
             <attribute name="SecurityDomainJndiName">DB2DbRealm</attribute>
             -->
             <depends optional-attribute-name="ManagedConnectionFactoryName">
             <!--embedded mbean-->
             <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=DB2PSMDS">
             <attribute name="JndiName">DB2PSMDS</attribute>
             <attribute name="ManagedConnectionFactoryProperties">
             <properties>
             <config-property name="ConnectionURL" type="java.lang.String">jdbc:db2:psm</config-property>
             <config-property name="DriverClass" type="java.lang.String">COM.ibm.db2.jdbc.app.DB2Driver</config-property>
             <!--set these only if you want only default logins, not through JAAS -->
             <config-property name="UserName" type="java.lang.String">db2admin</config-property>
             <config-property name="Password" type="java.lang.String">db2admin</config-property>
             </properties>
             </attribute>
             <!--Below here are advanced properties -->
             <!--hack-->
             <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper</depends>
             </mbean>
             </depends>
             <depends optional-attribute-name="ManagedConnectionPool">
             <!--embedded mbean-->
             <mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" name="jboss.jca:service=LocalTxPool,name=DB2PSMDS">
             <attribute name="MinSize">0</attribute>
             <attribute name="MaxSize">50</attribute>
             <attribute name="BlockingTimeoutMillis">5000</attribute>
             <attribute name="IdleTimeoutMinutes">15</attribute>
             <!--
             criteria indicates if Subject (from security domain) or app supplied
             parameters (such as from getConnection(user, pw)) are used to distinguish
             connections in the pool. Choices are
             ByContainerAndApplication (use both),
             ByContainer (use Subject),
             ByApplication (use app supplied params only),
             ByNothing (all connections are equivalent, usually if adapter supports
             reauthentication)-->
             <attribute name="Criteria">ByContainer</attribute>
             </mbean>
             </depends>
             <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
             <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
             <attribute name="TransactionManager">java:/TransactionManager</attribute>
             <!--make the rar deploy! hack till better deployment-->
             <depends>jboss.jca:service=RARDeployer</depends>
             </mbean>
            </server>
            


            • 3. Re: JBoss installing Problem
              jaikiran pai Master

               

              yes, i deployed the datasource. This is the content of the datasource.

              my db2-service.xml


              Actually, this is not how a datasource is deployed. You have to create a file named *-ds.xml with a < datasource> element. See these for details:

              http://wiki.jboss.org/wiki/Wiki.jsp?page=DSdotXML

              http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources



              • 4. Re: JBoss installing Problem
                Malte Poltermann Newbie

                On the current system where the jboss is running there is no -ds.xml (if i looked right) file and its running fine.

                I copied the whole directory including subdirectory to the new server. if there is a -ds.xml file, it should be on the new system too.

                where can i find this -ds.xml file?

                • 5. Re: JBoss installing Problem
                  Malte Poltermann Newbie

                  Where do i usually find that -ds.xml file or where do i have to create one?

                  • 6. Re: JBoss installing Problem
                    jaikiran pai Master

                    The -ds.xml file is usually in the deploy folder or in your application package(Ex: .ear file).