aspose file tools*
The moose likes JBoss/WildFly and the fly likes Connecting to MySql in JBOSS5.1.0.GA Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Connecting to MySql in JBOSS5.1.0.GA" Watch "Connecting to MySql in JBOSS5.1.0.GA" New topic
Author

Connecting to MySql in JBOSS5.1.0.GA

Sasidhar Madhira
Greenhorn

Joined: Aug 19, 2009
Posts: 2
Hi,

I'm novice to JBOSS and this question has been asked a few times, but
none of the responses that I've read have got me through.

I'm using mysql5.1.3 with MySQL connectorj 5.1.6, I'm trying to integrate it with MDM and deploy on JBOSS. I looked into all the tutorials and tried modifying all the appropriate files.

MySql-ds.xml File




Log shows the following error.

2009-08-18 16:00:48,671 WARN [org.jboss.ejb3.interceptors.aop.InterceptorsFactory] (http-127.0.0.1-8080-4) EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
2009-08-18 16:00:48,750 WARN [org.jboss.ejb3.interceptors.aop.InterceptorsFactory] (http-127.0.0.1-8080-4) EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
2009-08-18 16:00:48,953 WARN [org.jboss.ejb3.interceptors.aop.InterceptorsFactory] (http-127.0.0.1-8080-4) EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
2009-08-18 16:00:49,015 WARN [org.jboss.ejb3.interceptors.aop.InterceptorsFactory] (http-127.0.0.1-8080-4) EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
2009-08-18 16:00:49,203 SEVERE [com.sun.mdm.index.edm.presentation.handlers.LoginHandler] (http-127.0.0.1-8080-4) Tue Aug 18 16:00:49 IST 2009 - MDM-MI-LGH007: Error Loading Initialization Parameters. :MDM-MI-SRS505: Failed to instantiate CodeLookup manager: MDM-MI-MSC566: Failed to obtain a database connection: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: jdbc not bound]
java.lang.Exception: MDM-MI-SRS505: Failed to instantiate CodeLookup manager: MDM-MI-MSC566: Failed to obtain a database connection: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: jdbc not bound]
at com.sun.mdm.index.edm.services.security.Logon.initializeQWSControllerValidationDate(Logon.java:146)
at com.sun.mdm.index.edm.presentation.handlers.LoginHandler.initializeApplication(LoginHandler.java:199)
at org.apache.jsp.results_jsp._jspService(results_jsp.java:86)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:468)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at net.sf.yui4jsf.filter.YUI4JSFFilter.doFilter(YUI4JSFFilter.java:79)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)


I'm sure MySql is up and running on the port 3306.

When I delete hsql-ds.xml from jboss-5.1.0.GA\server\default\deploy directory and replace hsqldb-persistence-service.xml with mysql-persistence-service.xml in jboss-5.1.0.GA\server\default\deploy\messaging directory.

I'm getting the dependency error while starting the server...

2009-08-18 17:54:43,359 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "JBossTimerServiceFactory" is missing the following dependencies:
Dependency "jboss.ejb:service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is missing the following dependencies:
Dependency "jboss.jdbc:datasource=DefaultDS,service=metadata" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **")
Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")
Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=BatchReportGeneratorEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=BatchReportGeneratorEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=BatchReportGeneratorEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=BatchReportGeneratorEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=CodeLookupEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=CodeLookupEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=CodeLookupEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=CodeLookupEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:ejb/PersonPageData' **")
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:ejb/PersonSequenceEJB' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PageDataEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PageDataEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PageDataEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PageDataEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PersonEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PersonEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PersonEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:Person/MasterControllerEJB/local-com.sun.mdm.index.ejb.master.MasterControllerLocal' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PersonEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PersonEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=ReportGeneratorEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=ReportGeneratorEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=ReportGeneratorEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:Person/MasterControllerEJB/local-com.sun.mdm.index.ejb.master.MasterControllerLocal' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=ReportGeneratorEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=ReportGeneratorEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=SequenceEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=SequenceEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=SequenceEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=SequenceEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=UserCodeLookupEJB,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=UserCodeLookupEJB,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=UserCodeLookupEJB,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=UserCodeLookupEJB,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.jca:name=JmsXA,service=ConnectionFactoryBinding" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=TxCM" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionPool" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=TxCM" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionPool" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging:service=JMSUserManager" is missing the following dependencies:
Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")
Deployment "jboss.messaging:service=PersistenceManager" is missing the following dependencies:
Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")
Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")
Deployment "jboss.messaging:service=ServerPeer" is missing the following dependencies:
Dependency "jboss.messaging:service=JMSUserManager" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=PersistenceManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq:service=DestinationManager" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss:service=KeyGeneratorFactory,type=HiLo" is missing the following dependencies:
Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")

DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PageDataEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **, ** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=CodeLookupEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=PersonEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jndi:Person/MasterControllerEJB/local-com.sun.mdm.index.ejb.master.MasterControllerLocal' **, ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=SequenceEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=ReportGeneratorEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jndi:Person/MasterControllerEJB/local-com.sun.mdm.index.ejb.master.MasterControllerLocal' **, ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=BatchReportGeneratorEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=UserCodeLookupEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "jboss.jdbc:datasource=DefaultDS,service=metadata" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **
Deployment "jboss.jca:name=DefaultDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:ear=Person.ear,jar=Person-ejb.jar,name=MasterControllerEJB,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jndi:ejb/PersonSequenceEJB' **, ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **, ** UNRESOLVED Demands 'jndi:ejb/PersonPageData' **

2009-08-18 17:54:50,765 INFO [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
2009-08-18 17:54:50,828 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
2009-08-18 17:54:50,875 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 2m:13s:454ms

I'm using jdbc in my app to connect to the MySql database, and I didn't modify any thing in the mysql-persistence.xml file.

My guess is that the app is referencing to hsqldb that is the reason it is giving Failed to obtain a database connection: javax.naming.NamingException Expection and when I tried deleting hsql-ds.xml from the deploy directory its giving dependency error as I said previously.

Please help me out in fixing this issue....

Your help is much appreciated.

Thanks & Regards,
Sasidhar
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
I got the same problem. Anybody out there know how to fix this?
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

Jim Jim, welcome to Java Ranch!

So you are saying that you are also using MDM (whatever that is) and your *-ds.xml file looks exactly like the original poster's?

See if this helps: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232520#4232520
If not, please open a new topic and post your *-ds.xml file, and the code the looks up the data source.


JBoss In Action
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
Actually I take it back. I don't have the same problem. The mdm is the name of the original users database. They have a permission problem or something.

I am attempting to replace hsqldb with mysql as the DefaultDS.

My mysqld-ds.xml file looks like this:



This appears to be correct and I get a datasource that appears in the admin console.

I am removing hsqldb-persistence-service.xml from the ...deploy/messaging directory.

The problem begins when I drop the mysql-persistence-service.xml into the ....deploy/messaging directory.



THere is more but it looks like things aren't getting created in the JMS area.

I compared the hsqldb-persistence-service.xml and mysql-persistence-service.xml and they couldn't be more different. I am looking into why this is.

Thanks for any help.

Jim
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
When I run mysql-persistence-service.xml the tables get created that are specified in the mbean JDBCPersistenceManagerService and the JDBCJMSUserManagerService. The tables are not created for the MessagingPostOfficeService.


Why does the hsqld-persistence-service.xml not have the sql statments in it that the other database persistence files have?

Continuing to figure this out.
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
When I remove the following block from mysql-persistence-service.xml most things work.



Unfortunately the JmsXA is not working. Nor it the jBPM Queue working that depends on it.
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
The whole problem is the mysql-persistence-service.xml needs to be used in a clustered environment. Once I moved all of my mysql configuration files to the "all" server in JBoss it came right up. This has to do with the new jgroups that was added in JBoss 5.

Happy coding.
ravikanth reddy
Ranch Hand

Joined: Aug 18, 2009
Posts: 46
Hi,

We face same problem while looking for the data source.
I think you need to add one more tag in *-ds.xml while looking for the data source.

<use-java-context>false</use-java-context>


Thanks,
Ravi
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

I am removing hsqldb-persistence-service.xml from the ...deploy/messaging directory.


Why did you do this? This is not a requirement for using MySQL with your apps. You only have to do this if you want to replace the database that JBoss Messaging uses. So decide what it is that you are try to do. Are you trying to use MySQL with your apps? Or are you trying to replace the database used by JBoss Messaging?

By the way, I asked to to start a new topic if your question did not exactly match the original poster's question. You admitted that your question does not concern MD and thus did not match the original poster's question, yet did not do create a new topic and in effect have hijacked the original poster's question to instead focus this topic on your question, which is considered to be rude. Therefore I will ask you once again to start a new topic and in that topic clearly define what it is that your are trying to accomplish.
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
Peter,

Thanks for your input and your kindness. I think you are mistaken. The original post in my understanding is about replacing Hypersonic with MySql. The original user can use my posts to most likely solve their problem. My posts are relevant.

To answer you specific questions. I am replacing HSQL with MySql for everything. Hypersonic is not a production database. So yes it was my intention to replace the database for the Messaging Queues as well.

The MDM that the original post was referring to is the name of the database that they are connecting to. So that is really not something that would be a separate topic of discussion.

I can leave the forum if you like. I am finding it less than friendly. Plus I solved my own problem. ;-)

Jim


Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10033
    
163

Jim Jim Dwyer wrote:

Thanks for your input and your kindness. I think you are mistaken. The original post in my understanding is about replacing Hypersonic with MySql. The original user can use my posts to most likely solve their problem. My posts are relevant.

...
The MDM that the original post was referring to is the name of the database that they are connecting to. So that is really not something that would be a separate topic of discussion.


Didn't you already admit that:

Jim Jim Dwyer wrote:Actually I take it back. I don't have the same problem. The mdm is the name of the original users database. They have a permission problem or something.


Jim Jim Dwyer wrote:
I can leave the forum if you like. I am finding it less than friendly.


All we asked you to do was create a separate topic so that we don't mix different issues in a single thread. That's not unfriendly. Everyone here is willing to help you, but to keep these forums friendly and helpful we do have some simple rules that we expect the ranchers to follow


[My Blog] [JavaRanch Journal]
Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
Sasidhar Madhira,

Sorry to get off topic.. What exactly is MDM?

Jim
Sasidhar Madhira
Greenhorn

Joined: Aug 19, 2009
Posts: 2
Hi all,

Sorry for the late response, I was on vacation...

We are working on SUN MDM (Master Data Management) product, its an open source and we customized the code to deploy it on JBOSS.

Its working fine when we connect to Oracle database, but when we are trying to connect to MySQL we are getting the following error...

Error Loading Initialization Parameters. : MDM-MI-SRS505: Failed to instantiate CodeLookup manager: MDM-MI-MSC566: Failed to obtain a database connection: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: jdbc not bound]


I wrote a sample web application to pull the data out from MySQL and it is working fine...I'm not sure what the problem with MDM.

To recap...

My LookUp code


My *-ds.xml coe


<resource-ref> in web.xml


My JBOSS.xml code


I'm not able to figure out where the problem is...
Please help me out in debugging this problem.

Regards,
Sasidhar
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

Deja vu!

http://faq.javaranch.com/java/BeForthrightWhenCrossPostingToOtherSites

Jim Jim Dwyer
Greenhorn

Joined: Aug 20, 2009
Posts: 8
Sasidhar Madhira,

Your original posting had many errors pertaining to DefaultDS and lots of UNRESOLVED items do to your changing of the hsqld.xml and the hsqldb-persistence-service.xml to mysql.xml and mysql-persistence-service.xml. Have you fixed that yet? If not see my previous posts on how to clean that up. Until you resolve your DefaultDS issues you need not go further.

You also changed your mysql.xml quite a bit from the original post so that is something new.

You may have some naming issues as your lookup name is BBEDataSource and the jndi-name in the -ds.xml is PersonDataSource. You might want to look at that.

Jim
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Connecting to MySql in JBOSS5.1.0.GA