[jboss-user] [Beginners Corner] - Re: JBoss installing Problem
Where do i usually find that -ds.xml file or where do i have to create one? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4133640#4133640 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4133640 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Beginners Corner] - JBoss installing Problem
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
[jboss-user] [Beginners Corner] - Re: JBoss installing Problem
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 = principalyourprincipal/module-option | module-option name = userNameyourusername/module-option | module-option name = passwordyourpassword/module-option | module-option name = managedConnectionFactoryNamejboss.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=SecurityDomainJndiNameDB2DbRealm/attribute | -- | depends optional-attribute-name=ManagedConnectionFactoryName | !--embedded mbean-- | mbean code=org.jboss.resource.connectionmanager.RARDeployment name=jboss.jca:service=LocalTxDS,name=DB2ISIPDS | attribute name=JndiNameDB2ISIPDS/attribute | attribute name=ManagedConnectionFactoryProperties | properties | config-property name=ConnectionURL type=java.lang.Stringjdbc:db2:isip2/config-property | config-property name=DriverClass type=java.lang.StringCOM.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.Stringmy db-user/config-property | config-property name=Password type=java.lang.Stringmy db-user-pw/config-property | /properties | /attribute | !--Below here are advanced properties -- | !--hack-- | depends optional-attribute-name=OldRarDeploymentjboss.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=MinSize0/attribute | attribute name=MaxSize50/attribute | attribute name=BlockingTimeoutMillis5000/attribute | attribute name=IdleTimeoutMinutes15/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=CriteriaByContainer/attribute | /mbean | /depends | depends optional-attribute-name=CachedConnectionManagerjboss.jca:service=CachedConnectionManager/depends | depends optional-attribute-name=JaasSecurityManagerServicejboss.security:service=JaasSecurityManager/depends | attribute
[jboss-user] [Beginners Corner] - Re: JBoss installing Problem
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? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4133140#4133140 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4133140 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
