[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-23 Thread benjiii
I retried again with using DefaultDS - now it's working.  Don't know, what 
changes I did before that weren't ok (or did not but would be necessary) ...
Thanks for your help!

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4122504#4122504

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4122504
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-19 Thread jaikiran
anonymous wrote : Didn't knew about a state-xml-file before?! Do I need this? 
In the jms dir is no state-xml-file, none for hypersonic and - clear - non for 
mssql. I also not found a mssql-jdbc-state-service.xml in the googled sites or 
in the example dir of jboss... 

JBoss-4.2.2 does have hssql-jdbc-state-service.xml in the jms folder. 
Surprising that you did not find one. Even  
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB mentions that for 
version greater than 3.2.4 you have to update this file (and one other file) 
for changing HSQL DB to some other DB. Did you follow those steps?


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121524#4121524

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121524
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-17 Thread benjiii
No, that is not the problem here - I already changed correctly to the JNDI-name 
MSSQL2000XADS

depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=MSSQL2000XADS/depends

but perhaps there should be an entry to define the state manager? 'cause there 
none... (only for destination manager and message cache)

or can I ignore this message? Is the state manager necessary?

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120830#4120830

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120830
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-17 Thread jaikiran
Sorry, i mentioned a incorrect filename in my post dated Wed Jan 16, 2008 10:41 
AM. I know, you already changed the mssql-jdbc2-service.xml to use the 
MSSQL2000XADS name. In addition to that you will also have to change the 
mssql-jdbc-state-service.xml (i am just guessing the name of the file) as 
follows:

mbean code=org.jboss.mq.sm.jdbc.JDBCStateManager
  |   name=jboss.mq:service=StateManager
  | depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=MSSQL2000XADS/depends

If even this does not work, then you will have to post the entire exception 
stacktrace and all these configuration files. Without these information, i will 
just have to keep guessing.


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120904#4120904

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120904
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-17 Thread benjiii
Didn't knew about a state-xml-file before?! Do I need this? In the jms dir is 
no state-xml-file, none for hypersonic and - clear - non for mssql. I also not 
found a mssql-jdbc-state-service.xml in the googled sites or in the example dir 
of jboss...

To post these files will cause a really big posting, but perhaps you've got an 
idea then

Here my mssql-xa-ds.xml:
?xml version=1.0 encoding=UTF-8?
  | 
  | !-- = 
--
  | !--   
--
  | !--  JBoss Server Configuration   
--
  | !--   
--
  | !-- = 
--
  | 
  | 
  | datasources
  |   xa-datasource
  | jndi-nameMSSQL2000XADS/jndi-name
  | track-connection-by-tx/
  | isSameRM-override-valuefalse/isSameRM-override-value
  | 
xa-datasource-classcom.microsoft.jdbcx.sqlserver.SQLServerDataSource/xa-datasource-class
  | xa-datasource-property 
name=ServerName12.0.0.12/xa-datasource-property
  | xa-datasource-property 
name=DatabaseNameTEST/xa-datasource-property
  | xa-datasource-property 
name=SelectMethodcursor/xa-datasource-property
  | xa-datasource-property name=Userabc/xa-datasource-property
  | xa-datasource-property name=Passwordtest/xa-datasource-property
  | 
  |   !-- corresponding type-mapping in the standardjbosscmp-jdbc.xml 
(optional) --
  |   metadata
  |  type-mappingMS SQLSERVER2000/type-mapping
  |   /metadata
  |   /xa-datasource
  | 
  | /datasources

and the mmsql-jdbc2-service.xml

?xml version=1.0 encoding=UTF-8?
  | 
  | !-- $Id: mssql-jdbc2-service.xml 63369 2007-06-05 22:22:14Z dbhole $ --
  | 
  | server
  | 
  |   !--  
--
  |   !-- Persistence and caching using MSSQL  
--
  |   !-- IMPORTANT: Remove hsqldb-jdbc2-service.xml   
--
  |   !-- Provided by [EMAIL PROTECTED] --
  |   !--  
--
  | 
  |   !--
  |  | The destination manager is the core service within JBossMQ
  |   --
  |   mbean code=org.jboss.mq.server.jmx.DestinationManager 
name=jboss.mq:service=DestinationManager
  | depends 
optional-attribute-name=MessageCachejboss.mq:service=MessageCache/depends
  | depends 
optional-attribute-name=PersistenceManagerjboss.mq:service=PersistenceManager/depends
  | depends 
optional-attribute-name=StateManagerjboss.mq:service=StateManager/depends
  |   /mbean
  | 
  |   !--
  |  | The MessageCache decides where to put JBossMQ message that
  |  | are sitting around waiting to be consumed by a client.
  |  |
  |  | The memory marks are in Megabytes.  Once the JVM memory usage hits
  |  | the high memory mark, the old messages in the cache will start 
getting
  |  | stored in the DataDirectory.  As memory usage gets closer to the
  |  | Max memory mark, the amount of message kept in the memory cache 
aproaches 0.
  |--
  |   mbean code=org.jboss.mq.server.MessageCache
  |  name=jboss.mq:service=MessageCache
  | attribute name=HighMemoryMark50/attribute
  | attribute name=MaxMemoryMark60/attribute
  | attribute 
name=CacheStorejboss.mq:service=PersistenceManager/attribute
  |   /mbean
  | 
  |   !-- The PersistenceManager is used to store messages to disk. --
  |   !--
  |  | The jdbc2 PersistenceManager is the new improved JDBC implementation.
  |  | This implementation allows you to control how messages are stored in
  |  | the database.
  |  |
  |  | This jdbc2 PM configuration has been tested against MS SQL Server 
2000
  |  | http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMSSQLDatasource
  |--
  |   mbean code=org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager
  |  name=jboss.mq:service=PersistenceManager
  | depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=MSSQL2000XADS/depends
  | attribute name=SqlProperties
  |   BLOB_TYPE=BINARYSTREAM_BLOB
  |   INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
  |   INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, 
MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
  |   SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
  |   SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
  |   DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
  |   SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM 
JMS_MESSAGES WHERE DESTINATION=?
  |   SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES 
WHERE DESTINATION=?
  |   SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES 
WHERE MESSAGEID=? AND 

[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread jaikiran
Post the entire exception stacktrace. Are you using persistence.xml? If yes, 
then post the contents.

Remember to use the 'Code' button (available in the message editor window) to 
wrap the contents of the xml in a code block while posting

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120382#4120382

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120382
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread benjiii
Oh sorry, didn't see the button - Newbie error

But there isn't any other error message - the error occurs in the console when 
starting the server. No own code used yet, I only tried to start the default 
JBoss (version 4.2.2) installation with a database connection.
And: No, no persistance.xml - I don't know this file.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120401#4120401

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120401
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread benjiii
Yes, that's what I tried: I have to use a SQLServer database instead of the 
hypersonic. 
And I did like it's written in your link - what I wrote above. I think the 
problem is the xml I posted above - that's the only part that differs from the 
way in the text that you linked because the syntax is another one. (Ok - and 
the fact that I copied the 3 driver libs into the lib folder also differs - in 
the example there is only one lib to copy.)

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120412#4120412

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120412
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread jaikiran
I believe the error is in your msql-jdk2-service.xml. I guess(you havent posted 
the contents of the msql-jdk2-service.xml so cant say for sure), you have 
something like this 

depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=TEST/depends

in your msql-jdk2-service.xml. You might have to change it to

depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=MSSQL2000XADS/depends


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120417#4120417

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120417
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread benjiii
Hey - thanks - you were right - that was a naming problem between the 
msql-jdk2-service.xml and the datasource xml! Great!

There's now another error 

Could not find stored procedure 'master..xp_jdbc_open'

but I worry that this is a problem of the driver I use, so that this is no 
problem for this forum here... :-(

But nevertheless: Thank you very much!

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120423#4120423

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120423
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread jaikiran
anonymous wrote : I put the msql-jdk2-service.xml in the correct directory 
(deploy/jms), the 3 driver libs in the lib (for MSSQL 2000 there are 3 libs 
necessary, not a single one) dir and I wrote the file for the database 
connections into the deploy dir (the original hsqldb-ds.xml also is in the dir 
or even more errors occure):
  | 

Are you trying to replace HSQLDB with MSSQL? Looks like the changes that you 
did in the deploy/jms folder might have resulted in this error. If at all you 
are trying to switch to MSSQL DB for persistence instead of the default HSQLDB 
then go through http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB. There 
are 2 approaches mentioned in that wiki article, choose the one which best 
suits you.


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120404#4120404

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120404
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread benjiii
So now I solved the problem with the driver - and got a new on: Now the 
StateManager is not yet installed (says the server console). I only changed the 
name for DataSourceBinding in the mssql-jdbc2-service.xml, nothing else. And I 
removed the corresponding file for the hypersonic database.

What could this be now?

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120449#4120449

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120449
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: DataSourceBinding not yet installed

2008-01-16 Thread jaikiran
Again a guess. I think you have 

depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=TEST/depends

in your mssql-jdbc2-service.xml. Change it to

depends 
optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=MSSQL2000XADS/depends


In short, i think you are using TEST(which is your database name) in most of 
configuration files when you should actually be using the jndi-name of the 
datasource (MSSQL2000XADS).



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120506#4120506

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4120506
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user