Get your CodeRanch badge!*
The moose likes JBoss/WildFly and the fly likes configuring persistence Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "configuring persistence" Watch "configuring persistence" New topic
Author

configuring persistence

John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
I'm trying to configure a mysql persistence store for jms. I copied the
mysql-jdbc2-service.xml file into the deploy/jms folder of my server.
The directions said to delete the hsqldb-jdbc2-service.xml file, so I
moved it to a different location. I restarted the server as suggested
after changing the name of my datasource MyMsgDS. When I did this,
I got a whole slew of errors! Way too many to post.

Do I have to configure a datasource in my mysql-ds.xml file? If so,
what url, username & password do I use -- or can I leave these blank?

thanks,

John
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 9340
    
110

Originally posted by John Gregory:
I'm trying to configure a mysql persistence store for jms. I copied the
mysql-jdbc2-service.xml file into the deploy/jms folder of my server.
The directions said to delete the hsqldb-jdbc2-service.xml file, so I
moved it to a different location.


That's just one part of the changes.

Originally posted by John Gregory:

Do I have to configure a datasource in my mysql-ds.xml file? If so,
what url, username & password do I use -- or can I leave these blank?



Yes, you have to setup a datasource. The main intention of replacing HSQLDB with your own DB is to be able to persist the JMS related information in your own DB tables. This effectively means, that you have to point, through the datasource file, a valid database with a valid username and password.

Please go through this wiki which lists down all the steps required to change the default datasource. Use either Approach#1 or Approach#2 mentioned in that wiki.


[My Blog] [JavaRanch Journal]
John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
Jaikiran,

Sorry in taking so long to get back to this, but I've been busy learning other
things, so haven't had much time to get back to this.


Anyway, after I read the wiki you recommended, I understand there are
about 8 basic steps in configuring persistence. I've added comments
so you can see if I understood this correctly. Please feel free to make
any comments you feel necessary...

1) Install the driver
This seems easy enough...no questions

2) deploy the datasource descriptor for mysql and remove the
hsqldb-db.xml file

For simplicity sake, I'm going to create a datasource called
JBossPersistDS. I understand how to create a datasource.
However, you previously mentioned that I had to configure a
datasource. Does this also mean I have to create a database
in mysql to match the table name in the datasource, or just
configure the datasource part?

What is this {-hasingleton} thing that keeps cropping up?

3) update persistence manager service
This seems easy enough, just change to match jndi name I gave
it in #2 above

4) update state manager service

The only difference in this area was the service="SOMETHING"
for mysql, what should that something be? LocalTxCM or
DataSourceBinding

5) change the login config

For this, if the name in #2 is JBossPersistDS, do i just change
it to that, or do I need the java:/ prefix of the name, as well?

6) update the timer service

This seems easy enough, just change to match jndi name I gave
it in #2 above

7) update HiLo generator service
This seems easy enough, just change to match jndi name I gave
it in #2 above

8) update the juddi-service
This seems easy enough, just change to match jndi name I gave
it in #2 above

If you see anything I've missed or misunderstood, please let me know! Thanks for the assist.

John
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 9340
    
110

Does this also mean I have to create a database in mysql to match the table name in the datasource


Yes, you will have to create a database and use that in the datasource configuration. Also the username and password you specify in the datasource should be valid.

What is this {-hasingleton} thing that keeps cropping up?


Ignore that. That applies, if you are using the "all" profile (%JBOSS_HOME%/server/all) which supports clustering. Since you are not using clustering, i would recommend you use "default" profile and change the files in this profile.

The only difference in this area was the service="SOMETHING" for mysql, what should that something be? LocalTxCM or DataSourceBinding

For JBoss-4.x, its DataSourceBinding.

For this, if the name in #2 is JBossPersistDS, do i just change it to that, or do I need the java:/ prefix of the name, as well?


By default, the datasources are bound to java: namespace. So you will have to use java:/JBossPersistDS

If you see anything I've missed or misunderstood, please let me know!


Looks fine. In case you run into any issues, please post back with the details.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5779
    
    7

I guess I should add that all of the steps to configuring JBossAS 5.0 to use a database (and remove Hypersonic) are included in the Going to Production chapter of JBoss In Action.


JBoss In Action
John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
Jaikiran,

Ok, one last db question vis-a-vis this topic. When I create
the database, do I create the tables, too? I noticed in one of
the files I was supposed to modify that there was some form of sql
code to create them. So my first thought is I just run the sql
command to create the database, not the tables.

If this is true, suppose I wanted to persist say, an object message.
How would this get accomplished?

John
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5779
    
    7

No, you do not have to manually create the tables. Each service that needs tables will create them itself. That is what those DDL statements (sql code to create tables) you referred to are for.
John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
Peter,

Thanks! I'll give it a whirl and see what happens.

John
John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
Jakirian,

Ok, I did the configuration and started the server. I got an error
which I'll post in a minute. That said, I checked out the mysql
query editor and under the db I created, there were 2 tables there.
So, it appeared to have created them. Are there only supposed to be
2?

here is the error I received:


06:48:07,729 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer

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.security:service=JaasSecurityManager
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=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=DestinationManager
State: NOTYETINSTALLED
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


Do you see anything that looks obvious?

John
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5779
    
    7

Earlier in the console log there should be a stack trace that details the error. You want the very first stack trace (you might have to change the number of buffer lines for the command window to get this).

What you posted is the report at the end of the deployment phase that says what failed to deploy. Unfortunately, it rarely gives a clue as to why those things did not deploy.

Also, could you post you *-ds.xml file?
John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
Peter,

Here's the entire start-up printout...

=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /programs/jboss-4.2.2.GA

JAVA: /programs/jdk1.6.0_04/bin/java

JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true

CLASSPATH: /programs/jboss-4.2.2.GA/bin/run.jar:/programs/jdk1.6.0_04/lib/tools.jar

=========================================================================

18:44:56,150 INFO [Server] Starting JBoss (MX MicroKernel)...
18:44:56,153 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
18:44:56,155 INFO [Server] Home Dir: /programs/jboss-4.2.2.GA
18:44:56,156 INFO [Server] Home URL: file:/programs/jboss-4.2.2.GA/
18:44:56,157 INFO [Server] Patch URL: null
18:44:56,157 INFO [Server] Server Name: default
18:44:56,157 INFO [Server] Server Home Dir: /programs/jboss-4.2.2.GA/server/default
18:44:56,158 INFO [Server] Server Home URL: file:/programs/jboss-4.2.2.GA/server/default/
18:44:56,158 INFO [Server] Server Log Dir: /programs/jboss-4.2.2.GA/server/default/log
18:44:56,159 INFO [Server] Server Temp Dir: /programs/jboss-4.2.2.GA/server/default/tmp
18:44:56,159 INFO [Server] Root Deployment Filename: jboss-service.xml
18:44:57,289 INFO [ServerInfo] Java version: 1.6.0_04,Sun Microsystems Inc.
18:44:57,289 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b19,Sun Microsystems Inc.
18:44:57,290 INFO [ServerInfo] OS-System: Linux 2.6.24-19-generic,i386
18:44:58,149 INFO [Server] Core system initialized
18:45:02,400 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
18:45:02,402 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
18:45:03,207 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
18:45:03,207 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
18:45:03,420 INFO [TransactionManagerService] Starting recovery manager
18:45:03,636 INFO [TransactionManagerService] Recovery manager started
18:45:03,636 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
18:45:09,450 INFO [EJB3Deployer] Starting java:comp multiplexer
18:45:10,251 INFO [STDOUT] no object for null
18:45:10,256 INFO [STDOUT] no object for null
18:45:10,301 INFO [STDOUT] no object for null
18:45:10,318 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
18:45:10,325 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
18:45:13,319 INFO [NativeServerConfig] JBoss Web Services - Native
18:45:13,319 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
18:45:17,300 INFO [Embedded] Catalina naming disabled
18:45:17,650 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /programs/jdk1.6.0_04/jre/lib/i386/server:/programs/jdk1.6.0_04/jre/lib/i386:/programs/jdk1.6.0_04/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
18:45:17,767 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
18:45:17,768 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
18:45:17,768 INFO [Catalina] Initialization processed in 468 ms
18:45:17,769 INFO [StandardService] Starting service jboss.web
18:45:17,770 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
18:45:17,806 INFO [Catalina] Server startup in 37 ms
18:45:18,228 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
18:45:20,626 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
18:45:20,918 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
18:45:21,397 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
18:45:22,680 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
18:45:23,746 INFO [MailService] Mail Service bound to java:/Mail
18:45:24,072 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
18:45:24,367 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
18:45:24,426 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
18:45:24,531 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
18:45:24,705 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
18:45:24,758 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
18:45:24,830 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
18:45:24,835 INFO [QuartzResourceAdapter] start quartz!!!
18:45:24,882 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
18:45:24,897 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
18:45:24,899 INFO [RAMJobStore] RAMJobStore initialized.
18:45:24,899 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
18:45:24,899 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
18:45:24,899 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
18:45:26,979 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java efaultDS'
18:45:27,690 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
18:45:27,794 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=eBooksDS' to JNDI name 'java:eBooksDS'
18:45:27,799 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jbossMsgDS' to JNDI name 'java:jbossMsgDS'
18:45:28,911 INFO [EjbModule] Deploying BMPCustomerBean
18:45:29,072 INFO [ProxyFactory] Bound EJB Home 'BMPCustomerBean' to jndi 'BMPCustomerBean'
18:45:29,075 INFO [EJBDeployer] Deployed: file:/programs/jboss-4.2.2.GA/server/default/deploy/EntityTest.jar
18:45:29,260 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
18:45:29,675 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer

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.security:service=JaasSecurityManager
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=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=DestinationManager
State: NOTYETINSTALLED
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


18:45:29,821 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
18:45:29,868 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
18:45:29,881 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 33s:714ms

==================================

The mysql-ds.xml:

<?xml version="1.0" encoding="UTF-8"?>

<datasources>
<local-tx-datasource>
<jndi-name>eBooksDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/eBookStore</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>jjgrego</user-name>
<password>password</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>mySQL</type-mapping>
</metadata>
</local-tx-datasource>
<local-tx-datasource>
<jndi-name>jbossMsgDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/JBossMsgDB</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>jjgrego</user-name>
<password>password</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>mySQL</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: configuring persistence
 
Similar Threads
Datasource Configuration in JBoss
MySql and JBoss
How to use MySQL for JMS
problem in configuring jboss-3.2.3 with mssqlserver2000
Jboss- DataSource Problem