[jboss-user] [Clustering/JBoss] - 4.0.5GA cluster with mySQL
geniusfox
do-not-reply at jboss.com
Wed Mar 14 06:18:37 EDT 2007
Hi
I have configure 2 jboss server with an mysql database server. But when i start occure this message:
18:12:28,437 INFO [RegistryServlet] Initializing jUDDI components.
18:12:29,031 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
deploy-hasingleton/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
18:12:29,375 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
18:12:30,468 INFO [MailService] Mail Service bound to java:/Mail
18:12:30,687 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
18:12:30,734 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
18:12:30,765 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
18:12:30,796 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
18:12:30,859 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
18:12:30,890 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/mail-ra.rar
18:12:31,359 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:name=JmsXA,service=ConnectionFactoryBinding' to JNDI name 'java:JmsXA'
18:12:31,609 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca
:name=DefaultDS,service=DataSourceBinding' to JNDI name 'java:DefaultDS'
18:12:32,078 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
loy/jmx-console.war/
18:12:32,625 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:name=testTopic,service=Topic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:name=securedTopic,service=Topic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:name=testDurableTopic,service=Topic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:name=testQueue,service=Queue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:name=A,service=Queue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:name=B,service=Queue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:name=C,service=Queue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:name=D,service=Queue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:name=ex,service=Queue
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.mq:service=DestinationManager
Depends On Me:
jboss.mq.destination:name=testTopic,service=Topic
jboss.mq.destination:name=securedTopic,service=Topic
jboss.mq.destination:name=testDurableTopic,service=Topic
jboss.mq.destination:name=testQueue,service=Queue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:name=DLQ,service=Queue
ObjectName: jboss.mq.destination:name=DLQ,service=Queue
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:name=testTopic,service=Topic
jboss.mq.destination:name=securedTopic,service=Topic
jboss.mq.destination:name=testDurableTopic,service=Topic
jboss.mq.destination:name=testQueue,service=Queue
jboss.mq.destination:name=A,service=Queue
jboss.mq.destination:name=B,service=Queue
jboss.mq.destination:name=C,service=Queue
jboss.mq.destination:name=D,service=Queue
jboss.mq.destination:name=ex,service=Queue
jboss.mq:service=SecurityManager
jboss.mq.destination:name=DLQ,service=Queue
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:12:32,765 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0
-8080
18:12:32,843 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
18:12:32,875 INFO [JkMain] Jk running ID=0 time=0/79 config=null
18:12:32,890 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Bran
ch_4_0 date=200610162339)] Started in 24s:453ms
Then, i can't looking XAConnecitonFactory form JNDI tree. What's the problem with it? My mysql-ds.xml content as:
<local-tx-datasource>
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:mysql://192.168.0.163:3306/jboss</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>jboss</user-name>
jboss
<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) -->
<type-mapping>mySQL</type-mapping>
</local-tx-datasource>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027866#4027866
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027866
More information about the jboss-user
mailing list