12 Replies Latest reply on Sep 4, 2008 5:12 PM by Dan Man

    jboss-4.2.3.GA with MySQL Server 5.0 configuration problem

    Dan Man Newbie

      Hi,

      I am new to Jboss. I just installed it and I wanted to configure the JMS persistence with MySql.
      When the server starts up it goes through the creation of a few tables that I can see in the dedicated database:

      mysql> show tables;
      +-----------------+
      | Tables_in_jboss |
      +-----------------+
      | jbm_counter |
      | jbm_dual |
      | jbm_msg_ref |
      | jbm_role |
      | jbm_tx |
      | jbm_user |
      | timers |
      +-----------------+
      7 rows in set (0.04 sec)


      But then I get the following error on the server start window:

      3:54:01,768 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to
      JNDI name 'java:DefaultDS'
      3:54:02,140 WARN [JDBCPersistenceManager]

      Boss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently REPEATABLE_READ.
      Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
      Using an isolation level more strict than READ_COMMITTED may lead to deadlock.

      3:54:02,374 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component w
      ich sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Me
      saging user guide for instructions on how to do this.
      3:54:02,418 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3 server [0] started
      3:54:02,447 WARN [JDBCSupport] SQLException caught, SQLState 42000 code:1064- assuming deadlock detected, try:1
      om.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds t
      your MySQL server version for the right syntax to use near 'CONDITION, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES FROM JBM_POSTOFF
      CE WHERE ' at line 1
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
      at com.mysql.jdbc.Util.getInstance(Util.java:381)
      at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030)
      at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
      at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491)
      at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423)


      It retries forever.
      Are the initial warning an indication of some problem or they are just warnings (for the moment I am not too concerned about security).
      It didn't look like a configuration problem to me since it has been able to access the database.
      Can anybody help please? Thanks.

      Dan

        • 1. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
          Peter Johnson Master

          Which version of JBossAS?

          It appears you are using JBoss Messaging. You will have to replace the hsqldb-persistence-service.xml with the equivalent file for MySQL (how to do that depends on your version of JBossAS).

          • 2. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
            Dan Man Newbie

            Hi Peter,

            I am using jboss-4.2.3.GA if this was your question.
            I don't see any hsqldb-persistence-service.xml in the deploy directory of the configuration I am running.
            Thanks.

            Dan

            • 3. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
              Dan Man Newbie

               

              "dan jboss" wrote:
              Hi Peter,

              I am using jboss-4.2.3.GA if this was your question.
              I don't see any hsqldb-persistence-service.xml in the deploy directory of the configuration I am running.
              Thanks.

              Dan


              BTW, I do have in the deploy directory the following two files:

              mysql-jdbc2-service.xml
              mysql-ds.xml



              • 4. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                Dan Man Newbie

                 

                "dan jboss" wrote:
                Hi,

                I am new to Jboss. I just installed it and I wanted to configure the JMS persistence with MySql.
                When the server starts up it goes through the creation of a few tables that I can see in the dedicated database:

                mysql> show tables;
                +-----------------+
                | Tables_in_jboss |
                +-----------------+
                | jbm_counter |
                | jbm_dual |
                | jbm_msg_ref |
                | jbm_role |
                | jbm_tx |
                | jbm_user |
                | timers |
                +-----------------+
                7 rows in set (0.04 sec)


                But then I get the following error on the server start window:

                3:54:01,768 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to
                JNDI name 'java:DefaultDS'
                3:54:02,140 WARN [JDBCPersistenceManager]

                Boss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently REPEATABLE_READ.
                Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
                Using an isolation level more strict than READ_COMMITTED may lead to deadlock.

                3:54:02,374 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component w
                ich sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Me
                saging user guide for instructions on how to do this.
                3:54:02,418 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3 server [0] started
                3:54:02,447 WARN [JDBCSupport] SQLException caught, SQLState 42000 code:1064- assuming deadlock detected, try:1
                om.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds t
                your MySQL server version for the right syntax to use near 'CONDITION, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES FROM JBM_POSTOFF
                CE WHERE ' at line 1
                at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
                at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
                at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
                at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
                at com.mysql.jdbc.Util.getInstance(Util.java:381)
                at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030)
                at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
                at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491)
                at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423)


                It retries forever.
                Are the initial warning an indication of some problem or they are just warnings (for the moment I am not too concerned about security).
                It didn't look like a configuration problem to me since it has been able to access the database.
                Can anybody help please? Thanks.

                Dan


                I discovered the reason for the warnings at the beginning and got rid of them. I am left with the syntax error:

                17:01:01,152 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                17:01:01,154 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                17:01:01,326 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA'
                to JNDI name 'java:JmsXA'
                17:01:01,427 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to
                JNDI name 'java:DefaultDS'
                17:01:02,064 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component w
                hich sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Me
                ssaging user guide for instructions on how to do this.
                17:01:02,082 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3 server [0] started
                17:01:02,124 WARN [JDBCSupport] SQLException caught, SQLState 42000 code:1064- assuming deadlock detected, try:1
                com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds t
                o your MySQL server version for the right syntax to use near 'CONDITION, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES FROM JBM_POSTOFF
                ICE WHERE ' at line 1
                at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
                at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
                at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
                at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
                at com.mysql.jdbc.Util.getInstance(Util.java:381)
                at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030)

                I guess the warning about MessageSucker is not important. I deliberately left it unchanged.
                Thanks again.

                Dan

                • 5. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                  Peter Johnson Master

                  What version of JBoss Messaging did you install? How did you install it?

                  The mysql-jdbc2-service.xml file belongs to JBossMQ and not JBoss Messaging. You should not be using that file.

                  Did you follow the steps under "JBossMQ" at http://wiki.jboss.org/wiki/SetUpAMysqlDatasource to set up MySQL? If so, those instructions do not apply to JBoss Messaging.

                  • 6. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                    Dan Man Newbie

                     

                    "PeterJ" wrote:
                    What version of JBoss Messaging did you install? How did you install it?

                    The mysql-jdbc2-service.xml file belongs to JBossMQ and not JBoss Messaging. You should not be using that file.

                    Did you follow the steps under "JBossMQ" at http://wiki.jboss.org/wiki/SetUpAMysqlDatasource to set up MySQL? If so, those instructions do not apply to JBoss Messaging.


                    Sorry to keep bugging. I am not spamming. As I was working last night I got different errors that I believed belonged to different forums.

                    I have reinstalled and configured JBoss Messaging. I discovered that I was indeed missing a couple of steps in the configuration. I still have the "Trying to install an already registered mbean" problem, as you can see in the log below. I there anything in JBoss itself (outside Messaging) that I might have done wrong?

                    I really appreciate the help.
                    Thanks.

                    Dan

                    08:55:38,429 INFO [TransactionManagerService] Starting recovery manager
                    08:55:38,506 INFO [TransactionManagerService] Recovery manager started
                    08:55:38,506 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

                    Anything wrong here below?

                    08:55:41,587 INFO [EJB3Deployer] Starting java:comp multiplexer
                    08:55:44,666 WARN [UDP] failed to join /224.0.0.75:7500 on net2: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:44,666 WARN [UDP] failed to join /224.0.0.75:7500 on net3: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:44,673 INFO [STDOUT]

                    -------------------------------------------------------
                    GMS: address is 127.0.0.1:50501
                    -------------------------------------------------------
                    08:55:46,693 INFO [TreeCache] viewAccepted(): [127.0.0.1:50501|0] [127.0.0.1:50501]
                    08:55:46,711 INFO [TreeCache] TreeCache local address is 127.0.0.1:50501
                    08:55:46,711 INFO [TreeCache] State could not be retrieved (we are the first member in group)
                    08:55:46,711 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
                    08:55:49,169 INFO [NativeServerConfig] JBoss Web Services - Native
                    08:55:49,169 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
                    08:55:50,098 INFO [SnmpAgentService] SNMP agent going active
                    08:55:50,595 INFO [DefaultPartition] Initializing
                    08:55:50,753 WARN [UDP] failed to join /224.0.0.75:7500 on net2: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:50,754 WARN [UDP] failed to join /224.0.0.75:7500 on net3: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:50,755 INFO [STDOUT]
                    -------------------------------------------------------
                    GMS: address is 127.0.0.1:50505
                    -------------------------------------------------------
                    08:55:52,781 INFO [DefaultPartition] Number of cluster members: 1
                    08:55:52,781 INFO [DefaultPartition] Other members: 0
                    08:55:52,781 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
                    08:55:52,782 INFO [DefaultPartition] State could not be retrieved (we are the first member in group)
                    08:55:52,831 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/127.0.0.1
                    08:55:52,932 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /127.0.0.1:1102, group=230.0.0.4, HA-JNDI address=127.0
                    .0.1:1100
                    08:55:53,176 INFO [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used
                    08:55:53,468 WARN [UDP] failed to join /224.0.0.75:7500 on net2: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:53,470 WARN [UDP] failed to join /224.0.0.75:7500 on net3: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:53,473 INFO [STDOUT]
                    -------------------------------------------------------
                    GMS: address is 127.0.0.1:50508
                    -------------------------------------------------------
                    08:55:55,499 INFO [TreeCache] viewAccepted(): [127.0.0.1:50508|0] [127.0.0.1:50508]
                    08:55:55,502 INFO [TreeCache] TreeCache local address is 127.0.0.1:50508
                    08:55:55,767 WARN [UDP] failed to join /224.0.0.75:7500 on net2: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:55,770 WARN [UDP] failed to join /224.0.0.75:7500 on net3: java.net.SocketException: Unrecognized Windows Sockets error: 0: n
                    o Inet4Address associated with interface
                    08:55:55,774 INFO [STDOUT]
                    -------------------------------------------------------
                    GMS: address is 127.0.0.1:50511
                    -------------------------------------------------------
                    08:55:57,800 INFO [TreeCache] viewAccepted(): [127.0.0.1:50511|0] [127.0.0.1:50511]
                    08:55:57,803 INFO [TreeCache] TreeCache local address is 127.0.0.1:50511
                    08:55:59,230 INFO [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E7
                    46578744578743A312E3000000000000200000000000000F4000102000000000A3132372E302E302E31000DC8000000114A426F73732F4E616D696E672F726F6F740
                    00000000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000007
                    000000000000000010000000000000024000000200000007E00000000000000010000000E3139322E3136382E312E313031000DC9004000000000000806066781020
                    10101000000170401000806066781020101010000000764656661756C7400000000000000000000000000000000000000002000000004000000000000001F0000000
                    400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
                    08:55:59,380 INFO [CorbaTransactionService] TransactionFactory: [IOR:000000000000003049444C3A6F72672F6A626F73732F746D2F69696F702F54
                    72616E73616374696F6E466163746F72794578743A312E30000000000200000000000000F4000102000000000A3132372E302E302E31000DC8000000144A426F7373
                    2F5472616E73616374696F6E732F46000000050000000000000008000000004A414300000000010000001C0000000000010001000000010501000100010109000000
                    0105010001000000210000007000000000000000010000000000000024000000200000007E00000000000000010000000E3139322E3136382E312E313031000DC900
                    400000000000080606678102010101000000170401000806066781020101010000000764656661756C74000000000000000000000000000000000000000020000000
                    04000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
                    08:55:59,867 INFO [Embedded] Catalina naming disabled
                    08:56:00,020 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environmen
                    ts was not found on the java.library.path: C:\Sun\SDK\jdk\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\sy
                    stem32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio
                    Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\Program
                    Files\QuickTime\QTSystem\;C:\Program Files\Java\jdk1.6.0_06\bin;C:\apache-ant-1.7.1\bin;C:\Sun\SDK\bin;C:\Sun\SDK\bin;C:\Sun\SDK\bin
                    ;;C:\Program Files\SSH Communications Security\SSH Secure Shell
                    08:56:00,090 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
                    08:56:00,107 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                    08:56:00,110 INFO [Catalina] Initialization processed in 242 ms
                    08:56:00,113 INFO [StandardService] Starting service jboss.web
                    08:56:00,118 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
                    08:56:00,184 INFO [Catalina] Server startup in 70 ms
                    08:56:00,318 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
                    08:56:00,963 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/httpha-invoker.sar/invoker.war/
                    08:56:01,214 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
                    08:56:01,468 INFO [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddi.war/
                    08:56:01,780 INFO [RegistryServlet] Loading jUDDI configuration.
                    08:56:01,783 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
                    08:56:01,785 INFO [RegistryServlet] Initializing jUDDI components.
                    08:56:02,254 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
                    08:56:03,034 INFO [MailService] Mail Service bound to java:/Mail
                    08:56:03,319 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
                    08:56:03,359 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
                    08:56:03,396 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
                    08:56:03,437 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
                    08:56:03,523 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms-ra.rar
                    08:56:03,559 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
                    08:56:03,616 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
                    08:56:03,635 INFO [QuartzResourceAdapter] start quartz!!!
                    08:56:03,688 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                    08:56:03,716 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                    08:56:03,720 INFO [RAMJobStore] RAMJobStore initialized.
                    08:56:03,722 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz
                    package: 'quartz.properties'
                    08:56:03,725 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                    08:56:03,728 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                    08:56:04,020 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA'
                    to JNDI name 'java:JmsXA'
                    08:56:04,244 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.3.GA/server/jms/deploy/jms-ds.xml
                    org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.messaging:service=ServerSessionPoolMB
                    ean,name=StdJMSPool
                    at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
                    at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
                    at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
                    at org.jboss.system.ServiceController.install(ServiceController.java:226)
                    at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:597)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
                    at $Proxy4.install(Unknown Source)
                    at org.jboss.deployment.SARDeployer.create(SARDeployer.java:251)
                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:597)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
                    at $Proxy51.create(Unknown Source)
                    at org.jboss.deployment.XSLSubDeployer.create(XSLSubDeployer.java:192)
                    at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
                    at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:597)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
                    at $Proxy9.deploy(Unknown Source)
                    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
                    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
                    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
                    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
                    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
                    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
                    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:597)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
                    at $Proxy0.start(Unknown Source)
                    at org.jboss.system.ServiceController.start(ServiceController.java:417)
                    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:597)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
                    at $Proxy4.start(Unknown Source)
                    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
                    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:597)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
                    at $Proxy5.deploy(Unknown Source)
                    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
                    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
                    at org.jboss.Main.boot(Main.java:200)
                    at org.jboss.Main$1.run(Main.java:508)
                    at java.lang.Thread.run(Thread.java:619)
                    08:56:04,774 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to J
                    NDI name 'java:MySqlDS'
                    08:56:04,801 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
                    08:56:05,099 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

                    --- Incompletely deployed packages ---
                    org.jboss.deployment.DeploymentInfo@b2d4b9d2 { url=file:/C:/jboss-4.2.3.GA/server/jms/deploy/jms-ds.xml }
                    deployer: org.jboss.deployment.XSLSubDeployer@1c6cc9c
                    status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.messaging:service=ServerSessionPoolMBean,na
                    me=StdJMSPool
                    state: FAILED
                    watch: file:/C:/jboss-4.2.3.GA/server/jms/deploy/jms-ds.xml
                    altDD: null
                    lastDeployed: 1220543764233
                    lastModified: 1220543764214
                    mbeans:

                    --- MBeans waiting for other MBeans ---
                    ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
                    State: CONFIGURED
                    I Depend On:
                    jboss.jca:service=DataSourceBinding,name=DefaultDS



                    • 7. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                      Peter Johnson Master

                      It appears that you did not install JBoss Messaging properly. How did you install it? (I asked this before, you never answered.) Did you run the installation script that comes with it?

                      The error you are getting is due to pieces of JBossMQ still being present.

                      To install JBoss Messaging and convert it to use MySQL, you need to:

                      1) Run the install script, [jboss_messaging]/util/release-admin.xml, it will remove JBossMQ and copy all the files to support JBoss Messaging. (I tried to find the notes for how to run this but did not see them, they are not in the readme.html but they might be on the wiki.)

                      2) Create a *-ds.xml file for MySQL (instructions are in the wiki, I already gave you the link). Do NOT use "DefaultDS" as the JNDI name unless you want to make a lot of other configuration changes; use amother name such as "MessagingDS".

                      3) Replace the deploy/jboss-messaging.sar/hsqldb-persistence-service.xml file (I hope I got this directory name correct) with the mysql-persistence-service.xml file from the [jboss_messaging]/examples/config directory. Edit this file to use the JNDI name you chose in step 2. The name appears several time, you will have to change it in every location.

                      I think that is it.

                      • 8. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                        Dan Man Newbie

                         

                        "PeterJ" wrote:
                        It appears that you did not install JBoss Messaging properly. How did you install it? (I asked this before, you never answered.) Did you run the installation script that comes with it?

                        Yes, I ran the command:

                        ant -f release-admin.xml -Dmessaging.config.source=all -Dmessaging.config.name=jms

                        The error you are getting is due to pieces of JBossMQ still being present.

                        To install JBoss Messaging and convert it to use MySQL, you need to:

                        1) Run the install script, [jboss_messaging]/util/release-admin.xml, it will remove JBossMQ and copy all the files to support JBoss Messaging. (I tried to find the notes for how to run this but did not see them, they are not in the readme.html but they might be on the wiki.)

                        Did that.

                        2) Create a *-ds.xml file for MySQL (instructions are in the wiki, I already gave you the link). Do NOT use "DefaultDS" as the JNDI name unless you want to make a lot of other configuration changes; use amother name such as "MessagingDS".

                        Did that.

                        3) Replace the deploy/jboss-messaging.sar/hsqldb-persistence-service.xml file (I hope I got this directory name correct) with the mysql-persistence-service.xml file from the [jboss_messaging]/examples/config directory. Edit this file to use the JNDI name you chose in step 2. The name appears several time, you will have to change it in every location.

                        Did that. I can see the jbm_* tables created in the database.

                        I still see the following error:

                        10:25:44,501 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA'
                        to JNDI name 'java:JmsXA'
                        10:25:44,597 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.3.GA/server/jms/deploy/jms-ds.xml
                        org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.messaging:service=ServerSessionPoolMB
                        ean,name=StdJMSPool
                        at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
                        at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
                        at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
                        at org.jboss.system.ServiceController.install(ServiceController.java:226)

                        in addition to the socket warnings in my previous message.

                        Would you recommend that I reinstall JBoss and do it all over?
                        Thanks a lot.

                        Dan



                        I think that is it.


                        • 9. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                          Peter Johnson Master

                          The jms-ds.xml file is one of the configuration files that comes with JBoss Messaging when using in AS 4.2.x. Based on the error message, there must be another configuration file that contains the MBean jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool. Could you do a text search of all *.xml files in server/jms for that MBean?

                          Also, could you post the contents of the *-ds.xml file you created for MySQL? When you do that, make sure you enclose the XML text within code brackets (select the text and click the Code button above the editor window). Also, click Preview to ensure that the text is formatted correctly before clicking Submit.

                          • 10. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                            Dan Man Newbie

                             

                            "PeterJ" wrote:
                            The jms-ds.xml file is one of the configuration files that comes with JBoss Messaging when using in AS 4.2.x. Based on the error message, there must be another configuration file that contains the MBean jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool. Could you do a text search of all *.xml files in server/jms for that MBean?

                            Also, could you post the contents of the *-ds.xml file you created for MySQL? When you do that, make sure you enclose the XML text within code brackets (select the text and click the Code button above the editor window). Also, click Preview to ensure that the text is formatted correctly before clicking Submit.


                            Thanks a lot for your patience. I got my problem fixed. I had the file hajndi-jms-ds.xml in the deploy directory, and it contained the same MBean defined. I am not sure the instructions told me to remove it and I missed it.

                            Here is the content of my mysql-ds.xml file:

                            <?xml version="1.0" encoding="UTF-8"?>
                            
                            <!-- $Id: mysql-ds.xml 71535 2008-04-01 07:05:03Z adrian@jboss.org $ -->
                            <!-- Datasource config for MySQL using 3.0.9 available from:
                            http://www.mysql.com/downloads/api-jdbc-stable.html
                            -->
                            
                            <datasources>
                             <local-tx-datasource>
                             <jndi-name>MySQLDS</jndi-name>
                             <connection-url>jdbc:mysql://localhost:3306/jboss</connection-url>
                             <driver-class>com.mysql.jdbc.Driver</driver-class>
                             <user-name>jbossuser</user-name>
                             <password>jbosspass</password>
                             <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
                             <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
                             <!-- should only be used on drivers after 3.22.1 with "ping" support
                             <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
                             -->
                             <!-- sql to call when connection is created
                             <new-connection-sql>some arbitrary sql</new-connection-sql>
                             -->
                             <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
                             <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                             -->
                            
                             <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
                             <metadata>
                             <type-mapping>mySQL</type-mapping>
                             </metadata>
                             </local-tx-datasource>
                            </datasources>
                            
                            


                            Thanks again.

                            Dan

                            • 11. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                              Peter Johnson Master

                              Both hajndi-jms-ds.xml and jms-ds.xml should not have ended up in the deploy directory. There should be only one of them, depending on if you are clustering or not. Because of the install command line you gave:

                              ant -f release-admin.xml -Dmessaging.config.source=all -Dmessaging.config.name=jms

                              the hajndi-jms-ds.xml is the correct file and jms-ds.xml is incorrect (and should be removed).

                              The 'all' configuration includes clustering support. The 'default' configuration contains everything except clustering. You did not by any chance run release-admin.xml twice, once without any options? That would explain the duplication.

                              • 12. Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
                                Dan Man Newbie

                                 

                                "PeterJ" wrote:
                                Both hajndi-jms-ds.xml and jms-ds.xml should not have ended up in the deploy directory. There should be only one of them, depending on if you are clustering or not. Because of the install command line you gave:

                                ant -f release-admin.xml -Dmessaging.config.source=all -Dmessaging.config.name=jms

                                the hajndi-jms-ds.xml is the correct file and jms-ds.xml is incorrect (and should be removed).

                                The 'all' configuration includes clustering support. The 'default' configuration contains everything except clustering. You did not by any chance run release-admin.xml twice, once without any options? That would explain the duplication.


                                Yes I have run release-admin.xml multiple times and generated different configurations as I was trying to start over after suspecting a mess in the current one. Initially I ran it without parameters, then as the old configuration was in the way I started running it with parameters on the same installation of JBoss. You explanation is totally consistent.
                                Thanks.