Re: mysql as DefaultDS in jboss

hi there!!!
Thanks for Your quick answer

Here it seems your datasource is correctly bound. Is DefaultDS a MySQL
database or a HyperSonic SQL database?

HyperSonic was default. Now, I deleted Hsqldb-ds.xml from the deploy
folder.

If you have modified the DefaultDS to connect a MySQL database, it won't
work. Here your stack trace shows there is a problem with JMS. If you
look at the folder (if you run the 'default' configuration):
<path-to-jboss>\server\default\deploy\jms
there is a file 'hsqldb-jdbc-state-service.xml'
you need to replace it with the file:
<path-to-jboss>\docs\examples\jms\mysql-jdbc2-service.xml

there are two similar files:
1. 'hsqldb-jdbc-state-service.xml' --> this I replaced with the mysql
one from examples
and changed MySQLDS to DefaultDS.

2. hsqldb-jdbc2-service.xml --> Am I supouse to get rid of that or
leave it?

But this file uses the MySQLDS datasource, not DefaultDS, so you need to
edit it and change MySQLDS by DefaultDS to follow you settings.

There might have other files needing similar changes in other services
deployed by JBoss.
I changed all the 'MySQLDS' entries in mysql-ds.xml,
standardjbosscmp-jdbc.xml, standardjaws.xml and login-config.xml to the
' DefaultDS'
==============================
I decided to remove file hsqldb-jdbc2-service.xml and after I run the
server I get such a results:

14:58:58,559 INFO [Server] Starting JBoss (MX MicroKernel)...
14:58:58,559 INFO [Server] Release ID: JBoss [Zion] 4.0.4.CR2 (build:
CVSTag=JBoss_4_0_4_CR2 date=200603311500)
14:58:58,569 INFO [Server] Home Dir: C:\j2eeServer
14:58:58,569 INFO [Server] Home URL: file:/C:/j2eeServer/
14:58:58,569 INFO [Server] Patch URL: null
14:58:58,569 INFO [Server] Server Name: default
14:58:58,569 INFO [Server] Server Home Dir:
C:\j2eeServer\server\default
14:58:58,569 INFO [Server] Server Home URL:
file:/C:/j2eeServer/server/default/
14:58:58,579 INFO [Server] Server Log Dir:
C:\j2eeServer\server\default\log
14:58:58,579 INFO [Server] Server Temp Dir:
C:\j2eeServer\server\default\tmp
14:58:58,579 INFO [Server] Root Deployment Filename: jboss-service.xml
14:58:59,180 INFO [ServerInfo] Java version: 1.5.0_06,Sun Microsystems
Inc.
14:58:59,180 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM
1.5.0_06-b05,Sun Microsystems Inc.
14:58:59,180 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:59:00,642 INFO [Server] Core system initialized
14:59:03,376 INFO [WebService] Using RMI server codebase:
http://moor2:8083/
14:59:03,426 INFO [Log4jService$URLWatchTimerTask] Configuring from
URL: resource:log4j.xml
14:59:03,887 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099,
RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server
SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
14:59:08,554 INFO [Embedded] Catalina naming disabled
14:59:08,724 INFO [ClusterRuleSetFactory] Unable to find a cluster
rule set in the classpath. Will load the default rule set.
14:59:08,724 INFO [ClusterRuleSetFactory] Unable to find a cluster
rule set in the classpath. Will load the default rule set.
14:59:09,335 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on
http-0.0.0.0-8080
14:59:09,335 INFO [Catalina] Initialization processed in 611 ms
14:59:09,335 INFO [StandardService] Starting service jboss.web
14:59:09,345 INFO [StandardEngine] Starting Servlet Engine: Apache
Tomcat/5.5.16
14:59:09,485 INFO [StandardHost] XML validation disabled
14:59:09,545 INFO [Catalina] Server startup in 210 ms
14:59:09,836 INFO [TomcatDeployer] deploy, ctxPath=/invoker,
warUrl=.../deploy/http-invoker.sar/invoker.war/
14:59:10,446 INFO [WebappLoader] Dual registration of jndi stream
handler: factory already defined
14:59:11,178 INFO [TomcatDeployer] deploy, ctxPath=/,
warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
14:59:12,780 INFO [TomcatDeployer] deploy, ctxPath=/jbossws,
warUrl=.../tmp/deploy/tmp61127jbossws-exp.war/
14:59:13,090 INFO [SubscriptionManager] Bound event dispatcher to
java:comp/env/EventDispatcher
14:59:13,421 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil,
warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
14:59:16,485 INFO [TomcatDeployer] deploy, ctxPath=/web-console,
warUrl=.../deploy/management/console-mgr.sar/web-console.war/
14:59:17,757 INFO [MailService] Mail Service bound to java:/Mail
14:59:18,107 INFO [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
14:59:18,178 INFO [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
14:59:18,258 INFO [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
14:59:18,338 INFO [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
14:59:18,468 INFO [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/jms/jms-ra.rar
14:59:18,548 INFO [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/mail-ra.rar
14:59:19,129 INFO [ConnectionFactoryBindingService] Bound
ConnectionManager
'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name
'java:JmsXA'
14:59:19,409 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console,
warUrl=.../deploy/jmx-console.war/
14:59:19,660 ERROR [URLDeploymentScanner] Incomplete Deployment
listing:

--- MBeans waiting for other MBeans ---
ObjectName:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS

ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer

ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: CONFIGURED
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS

ObjectName: jboss.mq.destination:service=Topic,name=testTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Queue,name=testQueue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Queue,name=A
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=B
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=C
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=D
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=ex
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager

ObjectName: jboss.mq:service=Invoker
State: CONFIGURED
I Depend On:
jboss.mq:service=TracingInterceptor
jboss:service=Naming
Depends On Me:
jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
jboss.mq:service=InvocationLayer,type=UIL2

ObjectName: jboss.mq:service=TracingInterceptor
State: CONFIGURED
I Depend On:
jboss.mq:service=SecurityManager
Depends On Me:
jboss.mq:service=Invoker

ObjectName: jboss.mq:service=SecurityManager
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:service=Queue,name=DLQ

ObjectName: jboss.mq.destination:service=Queue,name=DLQ
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

ObjectName: jboss.mq:service=InvocationLayer,type=JVM
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker

ObjectName: jboss.mq:service=DestinationManager
State: CONFIGURED
I Depend On:
jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq.destination:service=Queue,name=A
jboss.mq.destination:service=Queue,name=B
jboss.mq.destination:service=Queue,name=C
jboss.mq.destination:service=Queue,name=D
jboss.mq.destination:service=Queue,name=ex
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ

ObjectName: jboss.mq:service=PersistenceManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager

ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker

ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: CONFIGURED
I Depend On:
jboss.jca:service=LocalTxCM,name=DefaultDS

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=PersistenceManager

ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.jca:service=DataSourceBinding,name=DefaultDS


14:59:19,860 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on
http-0.0.0.0-8080
14:59:20,170 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
14:59:20,200 INFO [JkMain] Jk running ID=0 time=0/120 config=null
14:59:20,211 INFO [Server] JBoss (MX MicroKernel) [4.0.4.CR2 (build:
CVSTag=JBoss_4_0_4_CR2 date=200603311500)] Started in 21s:632ms
========================================================
Is that mean there is still something wrong.
Before deleting the mentioned file I received totally different errors
+ some dependencies errors like here.
I don't see anymore the DefaultDS=Hypersonic entry in jmx console
anymore(that is caused by deleting hsqldb-ds.xml from /deploy), but
thought this should be replaced by mysql. Now there's no DefaultDS at
all.
is anything still wrong?
Greetings,
Marek

.