[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
No you don't need to create SQL function , the
org.jboss.mq.pm.jdbc2.PersistenceManager takes care of creation of the tables .
Table creation is controlled by defining the sqlproperties , have a look at
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQStateJDBC
I don't understand why the setting of CREATE_TABLES_ON_STARTUP= false is still
creating the SQL tables , you seem to be doing something wrong . You should
enable trace logging for org.jboss.mq to troubleshoot this issue .
Go to the Jboss Messaging user forum , this issues is not JCA related .
Let me point out the code which reads the CREATE_TABLES_ON_STARTUP property
| public void startService() throws Exception
|{
| .
| createTables = sqlProperties.getProperty(CREATE_TABLES_ON_STARTUP,
true).equalsIgnoreCase(true);
| ..
| }
|
|
|
|
if (createTables)
| {
| c = this.getConnection();
|
| boolean createdMessageTable = false;
| try
| {
|stmt = c.prepareStatement(CREATE_MESSAGE_TABLE);
|stmt.executeUpdate();
|createdMessageTable = true;
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/messaging/src/main/org/jboss/mq/pm/jdbc2/PersistenceManager.java
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/messaging/src/main/org/jboss/mq/pm/jdbc2/MSSQLPersistenceManager.java
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113178#4113178
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4113178
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
I tried setting CREATE_TABLES_ON_STARTUP = FALSEthat did not seem to have any impact. I was concerned about the error, because it was evident that it stopped processing the initialization at the point of the error, because there were other errors that would have been reported had it continued. i.e. there were other tables that were already created which would have caused identical errors that were not being reported. So I did a bit of work and changed the SQL in mssql-jdbc2-service.xml config file. hsqldb-jdbc-state-service.xml also contained code which generated the errors, so I made a copy and renamed it to mssql-jdbc-state-service.xml The changes that I made are as follows: mssql-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 | | |-- | mbean code=org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager | name=jboss.mq:service=PersistenceManager | depends optional-attribute-name=ConnectionManagerjboss.jca:service=DataSourceBinding,name=DefaultDS/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 = IF OBJECT_ID (N'dbo.JMS_MESSAGES', N'U') IS NULL CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB IMAGE) |
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
anonymous wrote : If I delete the table it will recreate it without an error, but the next time that it starts up it will throw the same exception again. Once the tables are created for the first time, how about changing the CREATE_TABLES_ON_STARTUP attribute in xxx-jdbc-state-service.xml and xxx-jdbc2-service.xml (both files present in %JBOSS_HOME%/server/ serverName/deploy/jms folder) to false : CREATE_TABLES_ON_STARTUP = FALSE View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109701#4109701 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109701 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
anonymous wrote : 2007-11-30 10:35:22,513 WARN [org.jboss.mq.sm.jdbc.JDBCStateManager] Error initialising state manag | er db The log contain the DEBUG/WARN messages and not the the ERROR one so these might be ignored :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109435#4109435 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109435 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
If I delete the table it will recreate it without an error, but the next time that it starts up it will throw the same exception again. The point of a persistant queue is tjhat the state is stored in it. :) So I guess the question now is more a matter of what is the state of the system has it recovered from this error? - nested throwable: (javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction. | arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] | Can't commit because the transaction is in aborted state) When it talks about a transaction here, is it MSSQL transaction, or the XA monitor that JBoss is maintaining, or are they the same thing? Rather than write a test.jsp I have some code that I can exercise the datasource with. Is there anything in particular that I should be testing? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109463#4109463 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109463 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
I realized after I submitted the post, that I did not have the portion of the server.log that overlaps the time when the exception is logged. 2007-11-30 10:35:20,138 DEBUG [org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService] Started jboss.jca:service=DataSourceBinding,name=DefaultDS | 2007-11-30 10:35:20,138 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.jca:service=DataSourceBinding,name=DefaultDS dependent components: [ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database | State: CREATED | I Depend On: | jboss.jca:service=DataSourceBinding,name=DefaultDS | , ObjectName: jboss:service=juddi | State: CREATED | I Depend On: | jboss.jca:service=DataSourceBinding,name=DefaultDS | , ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo | State: CREATED | I Depend On: | jboss:service=TransactionManager | jboss.jca:service=DataSourceBinding,name=DefaultDS | , ObjectName: jboss.mq:service=StateManager | State: CREATED | I Depend On: | jboss.jca:service=DataSourceBinding,name=DefaultDS | Depends On Me: | jboss.mq:service=DestinationManager | , ObjectName: jboss.mq:service=PersistenceManager | State: CREATED | I Depend On: | jboss.jca:service=DataSourceBinding,name=DefaultDS | Depends On Me: | jboss.mq:service=DestinationManager | ] | 2007-11-30 10:35:20,138 DEBUG [org.jboss.system.ServiceController] starting service jboss.ejb:service=EJBTimerService,persistencePolicy=database | 2007-11-30 10:35:20,138 DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Starting jboss.ejb:service=EJBTimerService,persistencePolicy=database | 2007-11-30 10:35:20,185 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: registering pool with interval 90 old interval: 9223372036854775807 | 2007-11-30 10:35:20,185 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: about to notify thread: old next: 1196444570185, new next: 1196444570185 | 2007-11-30 10:35:22,169 DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Started jboss.ejb:service=EJBTimerService,persistencePolicy=database | 2007-11-30 10:35:22,169 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.ejb:service=EJBTimerService,persistencePolicy=database dependent components: [] | 2007-11-30 10:35:22,169 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=juddi | 2007-11-30 10:35:22,185 DEBUG [org.jboss.jaxr.juddi.JUDDIService] Starting jboss:service=juddi | 2007-11-30 10:35:22,185 DEBUG [org.jboss.jaxr.juddi.JUDDIService] JUDDIService: Inside startService with dropOnStart=false createOnStart=false | 2007-11-30 10:35:22,185 DEBUG [org.jboss.jaxr.juddi.JUDDIService] Started jboss:service=juddi | 2007-11-30 10:35:22,185 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=juddi dependent components: [] | 2007-11-30 10:35:22,185 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=KeyGeneratorFactory,type=HiLo | 2007-11-30 10:35:22,185 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo | 2007-11-30 10:35:22,200 TRACE [org.jboss.tm.TransactionManagerLocator] Got a transaction manager from jndi [EMAIL PROTECTED] | 2007-11-30 10:35:22,200 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Executing SQL: select HIGHVALUES from HILOSEQUENCES where SEQUENCENAME='general' | 2007-11-30 10:35:22,356 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Started jboss:service=KeyGeneratorFactory,type=HiLo | 2007-11-30 10:35:22,356 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=KeyGeneratorFactory,type=HiLo dependent components: [] | 2007-11-30 10:35:22,356 DEBUG [org.jboss.system.ServiceController] starting service jboss.mq:service=StateManager | 2007-11-30 10:35:22,356 DEBUG [org.jboss.mq.sm.jdbc.JDBCStateManager] Starting jboss.mq:service=StateManager | 2007-11-30 10:35:22,513 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true | 2007-11-30 10:35:22,513 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false | 2007-11-30 10:35:22,513 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true | 2007-11-30 10:35:22,513 WARN [org.jboss.mq.sm.jdbc.JDBCStateManager] Error initialising state manager db | org.jboss.mq.SpyJMSException: Could not commit/rollback a transaction with the transaction manager.; - nested throwable: (javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted]
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
anonymous wrote : Could not create table | with SQL: CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, | TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB IMAGE) | com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'JMS_MESSAGES' in | the database. Looks like the table has already been created earlier , can you check this form the Jboss messaging forums ? BTW , you can delete the tables manually from the MSSQL and then try restarting the Jboss ... that might work . anonymous wrote : Is there something that I am doing wrong? You should understand that with Jboss4.2 version the older TM has been replaced with new Arjuna TM that supports RecoveryManager feature which was missing in earlier old TM . So TM related logging should be done on com.arjuna.ats.internal.jta . Ronald , why don't you test a simple jsp and get it verified first that datasource is configured properly , the DS seems to be configured properly . I don't see the issue here with Jboss JCA , the configurations seems to be ok ... let us get it verified from the test jsp . Alternatively you can use in the ds configuration and see from the logs if it doesn't show errors . View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109429#4109429 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109429 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
Last things first: anonymous wrote : Do you mean to say that every time you restart the MSSQL server it listens on different ports? There should be some way to configure the fixed port , I wanted to try this but I have fedora installed on my laptop . | | Ronald , I don't believe that the MS doesn't provide a way to configure the fixed port to listen :) , google to know more configuration No that is not what I mean to say. The default port the SQL Server listens on is 1433. But it must have an algorithm for picking a different port if it discovers that that port is in use, because on my laptop it came up on port 1961. This caused me some delay in trackinig down what happened, because there was no indication that it had changed from 1433 other than a connection refused message. After Googling around I bit I found a hint that I needed to check at the place I described in the post to find out what port it was listening on. You can also set the port that it listens on at the same location. I have not researched it enough to know why / when it changes, but I suspect it only occurs the first time that the TCP/IP connectivity is enabled. Sorry for any confusion that this may have caused. My intent was good. I was just trying to help anyone who was following in my tracks. Now to the real point of the post. Perhaps I am doing this wrong, but I have not seen any difference after enabeling trace The same information goes to the console, and there is no error displayed in the server log, or any indicative information in the server.log This is how I am enabeling trace. In the conf directory of my server, I edit the file jboss-log4j.xml. i.e. (jboss-4.2.1.GA/server/fast2market/conf/jboss-log4j.xml I add the following: category name=org.jboss.tm | priority value=TRACE class=org.jboss.logging.XLevel/ |/category |category name=org.jboss.jdbc | priority value=TRACE class=org.jboss.logging.XLevel/ |/category |category name=org.jboss.mq.sm.jdbc.JDBCStateManar | priority value=TRACE class=org.jboss.logging.XLevel/ |/category Is there something that I am doing wrong? This is the information in the service.log: 2007-11-30 10:35:00,778 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying jbossmq-httpil.sar | 2007-11-30 10:35:00,778 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/JBoss/jboss-4.2.1.GA/server/fast2market/deploy-hasingleton/jms/hsqldb-jdbc-state-service.xml | 2007-11-30 10:35:00,778 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/C:/JBoss/jboss-4.2.1.GA/server/fast2market/deploy-hasingleton/jms/hsqldb-jdbc-state-service.xml | 2007-11-30 10:35:00,778 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.mq:service=StateManager with code: org.jboss.mq.sm.jdbc.JDBCStateManager | 2007-11-30 10:35:00,841 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.mq:service=StateManager | 2007-11-30 10:35:00,856 DEBUG [org.jboss.system.ServiceController] recording that jboss.mq:service=StateManager depends on jboss.jca:service=DataSourceBinding,name=DefaultDS | 2007-11-30 10:35:00,856 DEBUG [org.jboss.system.ServiceConfigurator] considering ConnectionManager with object name jboss.jca:service=DataSourceBinding,name=DefaultDS | 2007-11-30 10:35:00,856 DEBUG [org.jboss.system.ServiceConfigurator] SqlProperties set to CREATE_TABLES_ON_STARTUP = TRUE | CREATE_USER_TABLE = CREATE TABLE JMS_USERS (USERID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, \ | CLIENTID VARCHAR(128) NULL, PRIMARY KEY(USERID)) | CREATE_ROLE_TABLE = CREATE TABLE JMS_ROLES (ROLEID VARCHAR(32) NOT NULL, USERID VARCHAR(32) NOT NULL, \ | PRIMARY KEY(USERID, ROLEID)) | CREATE_SUBSCRIPTION_TABLE = CREATE TABLE JMS_SUBSCRIPTIONS (CLIENTID VARCHAR(128) NOT NULL, \ | SUBNAME VARCHAR(128) NOT NULL, TOPIC VARCHAR(255) NOT NULL, \ | SELECTOR VARCHAR(255) NULL, PRIMARY KEY(CLIENTID, SUBNAME)) | GET_SUBSCRIPTION = SELECT TOPIC, SELECTOR FROM JMS_SUBSCRIPTIONS WHERE CLIENTID=? AND SUBNAME=? | LOCK_SUBSCRIPTION = SELECT TOPIC, SELECTOR FROM JMS_SUBSCRIPTIONS WHERE CLIENTID=? AND SUBNAME=? | GET_SUBSCRIPTIONS_FOR_TOPIC = SELECT CLIENTID, SUBNAME, SELECTOR FROM JMS_SUBSCRIPTIONS WHERE TOPIC=? | INSERT_SUBSCRIPTION = INSERT INTO JMS_SUBSCRIPTIONS (CLIENTID, SUBNAME, TOPIC, SELECTOR) VALUES(?,?,?,?) | UPDATE_SUBSCRIPTION = UPDATE JMS_SUBSCRIPTIONS SET TOPIC=?, SELECTOR=? WHERE CLIENTID=? AND SUBNAME=? | REMOVE_SUBSCRIPTION = DELETE FROM JMS_SUBSCRIPTIONS WHERE CLIENTID=? AND SUBNAME=? | GET_USER_BY_CLIENTID = SELECT USERID, PASSWD, CLIENTID FROM JMS_USERS WHERE
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
at org.jboss.mq.sm.jdbc.JDBCStateManager$JDBCSession.close(JDBCStateManager.java:638) The error appears to come from here , enable the TRACE logging on org.jboss.mq.sm.jdbc.JDBCStateManager class and trace the flow . Also make sure that datasource configuration is working , you can write a simple jsp to test that . First let us make sure that the datasource is configured properly. anonymous wrote : | One thing that you have to be careful of, SQL Server will frequently change the port that it listens on to some other number (that's Microsoft for ya) if you get a connection refused on startup check and see what port it is actually listening on. Do you mean to say that every time you restart the MSSQL server it listens on different ports? There should be some way to configure the fixed port , I wanted to try this but I have fedora installed on my laptop . Ronald , I don't believe that the MS doesn't provide a way to configure the fixed port to listen :) , google to know more configuration !!! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109249#4109249 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109249 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
you can find out what port it is listening on by going to the Configuration manager and following the links for Protocolse for MSSQLSERVER-TCP/IP Properties and clicking on the IP Address tab. Ronald Trask XAware inc Professional Services. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109142#4109142 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109142 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
One thing that you have to be careful of, SQL Server will frequently change the port that it listens on to some other number (that's Microsoft for ya) if you get a connection refused on startup check and see what port it is actually listening on. This happened to me when I tried to configure it on my XP based laptop. I don't think it happens on 2003. I have not been successful at getting it to run on a XP workstation, but I think that is because the DTS is not running. I'll try that later and let you know what happens. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109140#4109140 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109140 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
