>> I fail to understand why [use of HSQL] is an issue.
Supposedly it's not to be used in production.
>> You also have to realize that you are using a beta...
I'm just pointing out an issue in replacing HSQL as the DefaultDS. It's not an
issue when you leave it alone and simply add your own da
1. Here is what I wrote:
anonymous wrote : I just now looked at the docs/examples/jms directory in
5.1.0-beta1. The file you need is not there. Looks like you will have to
download JBoss Messaging and get the persistence config files from there.
after which I wrote:
anonymous wrote : I looked
"PeterJ" wrote : Wow, no word whatsoever as to if you followed my advice and
copied over the mssql-persistence-service.xml file...
There were a couple of issues with that.
1. No such file in my 5.1.0.Beta1 installation.
2. Keeping DefaultDS with HSQL and adding another datasource works fine.
Received a response from Microsoft on the need for sqljdbc4.jar.
"...The Microsoft SQL Server JDBC Driver 2.0 supports the JDBC 4 API that is
part of the Java SE 6 platform. To use the JDBC 4 API, you must use the
sqljdbc4.jar, which only works with Java SE 6 (1.6). If you only need the JDBC
Wow, no word whatsoever as to if you followed my advice and copied over the
mssql-persistence-service.xml file...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220447#4220447
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=repl
I guess this means there's a disconnect between the expectations created by the
server documentation and reality. HSQL is described as convenience not
suitable for production. The prescribed solution for production is to point
your DefaultDS at a production quality database.
The problem is cus
OK, I was focusing too much on the work Quartz in the log entries you posted.
There are no quartz-related tables in the database. The database entry in
question is for one of the messaging tables. So the information I provided in
my earlier response for replacing the messaging persistence file s
I looked at messaging in AS 5.1.0 - it is version 1.4.3.GA. But there is no
such version on the JBoss Messaging download page, so it would appear that
version 1.4.3.GA is a AS 5.1.0 Beta-specific version only. However, I noticed
that there is no difference between the hsqldb-persistence-service.
I juts now lokked at the docs/examples/jms directory in 5.1.0-beta1. The file
you need is not there. Looks like you will have to download JBoss Messaging and
get the persistence config files from there.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220116#4
Sounds like all you did was replace hsqldb-sd.xml with mssql-ds.xml, which, as
I pointed out, is not sufficient to change the DefaultDS data source to use a
different database. You also have to change the SQL statements used my Quartz
and by the messaging service. The messaging ones should be f
The only change was to use DefaultDS as the jndi-name in mssql-ds.xml and
remove hsqldb-ds.xml to eliminate the conflict. The assumption being the file
name is irrelevant (any *-ds.xml pattern will do) and that all JDBC drivers
must adhere to precisely the same interface.
Looks like Quartz is
What all did you do to change DefaultDS to use SQL Server instead of HSQL?
Simply replacing hsqldb-ds.xml is not sufficient because for various services,
such as messaging, there are database-specific configuration files that must be
deployed. Such a configuration file for SLQ Server would not u
Oops! Just read "this is not a database forum" sticky message. Can I move or
duplicate post?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220042#4220042
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220042
Another Failure Point: SQL Server fails as DefaultDS because CLUSTERED is a
reserved word. If HSQL truly cannot be used in production, then the use of
reserved words has to be addressed.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220010#4220010
Reply to
14 matches
Mail list logo
