If clustered is set to false, then none of the cluster related attributes
should be parsed - that is the way it used to work.
I believe Clebert added ChannelFactory at a later date. If ChannelFactory is
being parsed when clustered = false then that's a bug.
Can someone add a JIRA? It should be
https://jira.jboss.org/jira/browse/JBAS-6333
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197392#4197392
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4197392
___
jboss-user
anonymous wrote : mysql-persistence-service.xml placed in examples is very
misleading, as it has clustered attribute set to false by defaulf, while
ChannelFactoryName is not commented,
I heartily agree and pointed this out once before in this forum as being a
possible issue when GA came out.
Thanks PeterJ, I've done all these steps before with JBoss 4.2.2 and 4.2.3
(most of them is done by the build process). The only difference is that I have
2 data sources, so that JBM has DefaultDS, and the app has another. That always
worked fine.
The only exceptions I can see in logs are
PeterJ wrote : 4) If you don't need clustering, in
mysql-persistence-service.xml set Clustered to false and comment out the
ChannelFactoryName attribute.
Ok, so I lied about the last one. After commenting it out PostOffice starts and
there are no problems with JBM. Thanks PeterJ!
anonymous wrote : mysql-persistence-service.xml placed in examples is very
misleading, as it has clustered attribute set to false by defaulf,
We had users complaining the opposite on having clustered=true by default.
You would see an exception on a ClassNotFound error for JGroups on that case.
Sorry, I was not paying attention. Clustered is indeed set to false in GA, but
you also need to comment out the dependency on ChannelFactoryName to get it to
work.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197246#4197246
Reply to the post :
Configuring messaging to use MySQL instead of Hypersonic is a multi-step
process. I imagine you missed a step or two. Here are the steps (hope it didn't
forget any):
1) Place the JDBC JAR file into the server/xx/lib directory
2) Remove server/xxx/deploy/messaging/hsqldb-persistence-service.xml
