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!
I tried to migrate my app from 4.2.3 (with new messaging), to 5.0.0GA, both on
mysql. The app havily relies on queues, and JMS also uses mysql for persistence.
Now, raw JBoss has messaging on Hypersonic, and this starts ok. But when
configured with the mysql-persistence-service.xml, which I
I tried to migrate my app from 4.2.3 (with new messaging), to 5.0.0GA, both on
mysql. The app havily relies on queues, and JMS also uses mysql for persistence.
Now, raw JBoss has messaging on Hypersonic, and this starts ok. But when
configured with the mysql-persistence-service.xml, which I
sorry, wrong topic
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196915#4196915
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4196915
___
jboss-user mailing list
