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-name>MSSQL2000XADS</jndi-name> | <track-connection-by-tx/> | <isSameRM-override-value>false</isSameRM-override-value> | <xa-datasource-class>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</xa-datasource-class> | <xa-datasource-property name="ServerName">12.0.0.12</xa-datasource-property> | <xa-datasource-property name="DatabaseName">TEST</xa-datasource-property> | <xa-datasource-property name="SelectMethod">cursor</xa-datasource-property> | <xa-datasource-property name="User">abc</xa-datasource-property> | <xa-datasource-property name="Password">test</xa-datasource-property> | | <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> | <metadata> | <type-mapping>MS 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="MessageCache">jboss.mq:service=MessageCache</depends> | <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends> | <depends optional-attribute-name="StateManager">jboss.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="HighMemoryMark">50</attribute> | <attribute name="MaxMemoryMark">60</attribute> | <attribute name="CacheStore">jboss.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="ConnectionManager">jboss.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 DESTINATION=? | MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=? | UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=? | UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? | UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=? | DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=? | DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ? | DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=? | DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T' | DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=? | CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB IMAGE) | CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID) | CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION) | CREATE_IDX_MESSAGE_MESSAGEID_DESTINATION = CREATE UNIQUE CLUSTERED INDEX JMS_MESSAGES_IDX ON JMS_MESSAGES (MESSAGEID, DESTINATION) | CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) ) | CREATE_TABLES_ON_STARTUP = TRUE | </attribute> | <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds --> | <!--attribute name="RecoveryTimeout">0</attribute--> | <!-- The number of blobs to load at once during message recovery --> | <attribute name="RecoverMessagesChunk">0</attribute> | </mbean> | | </server> | The Server has the following stack trace: =============================================================================== | | JBoss Bootstrap Environment | | JBOSS_HOME: C:\Programme\Java\JBoss\jboss-4.2.2.GA | | JAVA: C:\Programme\Java\jdk1.5.0_14\bin\java | | JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli | ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 | | CLASSPATH: C:\Programme\Java\jdk1.5.0_14\lib\tools.jar;C:\Programme\Java\JBoss | \jboss-4.2.2.GA\bin\run.jar | | =============================================================================== | | 18:20:19,490 INFO [Server] Starting JBoss (MX MicroKernel)... | 18:20:19,490 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag= | JBoss_4_2_2_GA date=200710221139) | 18:20:19,490 INFO [Server] Home Dir: C:\Programme\Java\JBoss\jboss-4.2.2.GA | 18:20:19,490 INFO [Server] Home URL: file:/C:/Programme/Java/JBoss/jboss-4.2.2. | GA/ | 18:20:19,490 INFO [Server] Patch URL: null | 18:20:19,490 INFO [Server] Server Name: default | 18:20:19,490 INFO [Server] Server Home Dir: C:\Programme\Java\JBoss\jboss-4.2.2 | .GA\server\default | 18:20:19,490 INFO [Server] Server Home URL: file:/C:/Programme/Java/JBoss/jboss | -4.2.2.GA/server/default/ | 18:20:19,490 INFO [Server] Server Log Dir: C:\Programme\Java\JBoss\jboss-4.2.2. | GA\server\default\log | 18:20:19,506 INFO [Server] Server Temp Dir: C:\Programme\Java\JBoss\jboss-4.2.2 | .GA\server\default\tmp | 18:20:19,506 INFO [Server] Root Deployment Filename: jboss-service.xml | 18:20:19,931 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc. | 18:20:19,931 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_14-b03 | ,Sun Microsystems Inc. | 18:20:19,931 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 | 18:20:20,671 INFO [Server] Core system initialized | 18:20:24,058 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 | / | 18:20:24,058 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour | ce:jboss-log4j.xml | 18:20:24,845 INFO [TransactionManagerService] JBossTS Transaction Service (JTA | version) - JBoss Inc. | 18:20:24,845 INFO [TransactionManagerService] Setting up property manager MBean | and JMX layer | 18:20:25,192 INFO [TransactionManagerService] Starting recovery manager | 18:20:25,318 INFO [TransactionManagerService] Recovery manager started | 18:20:25,318 INFO [TransactionManagerService] Binding TransactionManager JNDI R | eference | 18:20:29,680 INFO [EJB3Deployer] Starting java:comp multiplexer | 18:20:30,121 INFO [STDOUT] no object for null | 18:20:30,121 INFO [STDOUT] no object for null | 18:20:30,169 INFO [STDOUT] no object for null | 18:20:30,200 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType | 18:20:30,216 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType | 18:20:33,429 INFO [NativeServerConfig] JBoss Web Services - Native | 18:20:33,429 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=20071021 | 0837) | 18:20:34,957 INFO [Embedded] Catalina naming disabled | 18:20:35,224 INFO [AprLifecycleListener] The Apache Tomcat Native library which | allows optimal performance in production environments was not found on the java | .library.path: C:\Programme\Java\jdk1.5.0_14\bin;.;C:\WINDOWS\system32;C:\WINDOW | S;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\IBM\SQLLIB | \BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;C:\PROG | RA~1\XRay | 18:20:35,366 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0 | .1-8080 | 18:20:35,366 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80 | 09 | 18:20:35,366 INFO [Catalina] Initialization processed in 410 ms | 18:20:35,366 INFO [StandardService] Starting service jboss.web | 18:20:35,382 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA | 18:20:35,461 INFO [Catalina] Server startup in 93 ms | 18:20:35,665 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w | eb.deployer/ROOT.war/ | 18:20:36,658 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/ | http-invoker.sar/invoker.war/ | 18:20:36,941 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/ | jbossws.sar/jbossws-context.war/ | 18:20:37,114 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../ | deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ | 18:20:38,327 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep | loy/management/console-mgr.sar/web-console.war/ | 18:20:39,099 INFO [MailService] Mail Service bound to java:/Mail | 18:20:39,461 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/jboss-ha-local-jdbc.rar | 18:20:39,556 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/jboss-ha-xa-jdbc.rar | 18:20:39,619 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/jboss-local-jdbc.rar | 18:20:39,697 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/jboss-xa-jdbc.rar | 18:20:39,823 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/jms/jms-ra.rar | 18:20:39,886 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/mail-ra.rar | 18:20:39,981 INFO [RARDeployment] Required license terms exist, view META-INF/r | a.xml in .../deploy/quartz-ra.rar | 18:20:39,997 INFO [QuartzResourceAdapter] start quartz!!! | 18:20:40,123 INFO [SimpleThreadPool] Job execution threads will use class loade | r of thread: main | 18:20:40,170 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. | 18:20:40,170 INFO [RAMJobStore] RAMJobStore initialized. | 18:20:40,170 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule | r' initialized from default resource file in Quartz package: 'quartz.properties' | | 18:20:40,186 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 | 18:20:40,186 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS | TERED started. | 18:20:41,052 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb | oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' | 18:20:41,587 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb | oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' | 18:20:41,729 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb | oss.jca:service=DataSourceBinding,name=MSSQL2000XADS' to JNDI name 'java:MSSQL20 | 00XADS' | 18:20:42,501 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep | loy/jmx-console.war/ | 18:20:42,674 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=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=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=StateManager | State: NOTYETINSTALLED | Depends On Me: | jboss.mq:service=DestinationManager | | | 18:20:43,084 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8 | 080 | 18:20:43,131 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 | 18:20:43,162 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos | s_4_2_2_GA date=200710221139)] Started in 23s:656ms View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121025#4121025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121025 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
