[JBoss Messaging] - Re: MQ migration help
by konami
"tnine" wrote :
|
| Steps to migrate DefaultDS to MySQL and set up messaging.
|
|
| | * Download the latest MySQL client jar and put it in server/lib
| | * Set up the following in a mysql-ds.xml file, and remove the hsqldb-ds.xml file
| |
| |
| |
| | | <datasources>
| | | <local-tx-datasource>
| | | <jndi-name>DefaultDS</jndi-name>
| | | <connection-url>
| | | jdbc:mysql://localhost:3306/jboss
| | | </connection-url>
| | | <driver-class>com.mysql.jdbc.Driver</driver-class>
| | | <user-name>jboss</user-name>
| | | <password>password</password>
| | | <exception-sorter-class-name>
| | | org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
| | | </exception-sorter-class-name>
| | | <metadata>
| | | <type-mapping>mySQL</type-mapping>
| | | </metadata>
| | | <!-- Required for Messaging to work correctly -->
| | | <transaction-isolation>
| | | TRANSACTION_READ_COMMITTED
| | | </transaction-isolation>
| | | </local-tx-datasource>
| | |
| | | </datasources>
| | |
| |
| | * Download the messaging distribution that has the same version as the one in your application server. For the JEMS 1.2.1.CR4 installer, I installed messaging version 1.4.0.SP3 (build: CVSTag=JBossMessaging_1_4_0_
| | SP3 date=200712131418)
| |
| | * Copy mysql-persistence-service.xml from examples/config of your messaging download to server/deploy/jboss-messaging.sar, and either delete or rename hsqldb-persistence-service.xml.bak
| |
| | * Restart the server, and everything should work!
| |
Thanks for the tip. It worked for me.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208826#4208826
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208826
17 years, 5 months
[Beginners Corner] - Re: installation questions on XP home.
by kishjeff
"kishjeff" wrote : "PeterJ" wrote : You want "Java IDE for Java EE Developers", the 163MB download. Then install JBoss Tools 3.0 into that like I suggested earlier.
| |
| Oh thanks, OK. I just deleted the old eclipse directory and unzipped the bigger one into c:\eclipse (c:\ actually)
| So now I'm unpacking this over it: eclipse-jee-ganymede-SR1-win32.zip
|
| "PeterJ" wrote :
| | Your standalone JBoss AS 5.0.0.GA install is just fine, but see this post for a correction you need to make: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202195#4202195
| |
| I'll give it a shot.
|
| "PeterJ" wrote :
| | Also, what JDK are you using? 5 or 6? Did you get the JBoss AS download that corresponds to that JDK? The JBoss AS download for JDK6 has 'jdk6' in the name, the other one is for JDK 5.
|
| I'm using jdk1.6.0_12 - and the JBoss I downloaded was named: jboss-5.0.0.GA-jdk6.zip so I guess that is OK, eh?
|
| Hopefully this works better! I really appreciate the fine tuning of the information I read.
OK. Things seem better but I can't add jboss as a server. I did see the bug report at https://bugs.eclipse.org/bugs/show_bug.cgi?id=257823
however I'm a little confused as to what the correct solution is.
Basically in eclipse I get this message:
Missing classpath entry C:\Apps\JBoss\jboss-5.0.0.GA\server\default\lib\mail.jar
when I try to add the server using application server directory:
C:\Apps\JBoss\jboss-5.0.0.GA
I assume from the bug discussion that the serverdef was still wrong.
I am replacing the current one with the one mentioned by wolfgang there at https://bugs.eclipse.org/bugs/show_bug.cgi?id=257823
hoping it allows me to add the JBoss server after staring eclipse with a -clean
no I'm still getting the same error trying to add the JBoss server.
Can anyone point out some obvious problem? thanks
Jeff
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208814#4208814
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208814
17 years, 5 months
[EJB/JBoss] - Re: Node Removal In mvcc-entity Cache Through JMX Console
by Burnison
"frank.stillford" wrote : ... If not, are there any similar alternatives or workarounds?
I have not found a way to invalidate entities out-of-the-box, but you can create your own MBean to accomplish the task. You can get a handle on the CacheManager through JNDI, and you can obtain a reference to the entity cache thusly:
| public void remove(String jndi, String cacheName, String node) throws Exception
| {
| CacheManager cm = null;
| Cache<?, ?> c = null;
|
| try{
| cm = this.getCacheManager(jndi);
| c = cm.getCache(cacheName, false);
| c.removeNode(node);
| } finally{
| if(c != null){
| try {
| cm.releaseCache(cacheName);
| } catch (NamingException ex) {
| }
| }
| }
| }
|
|
| private CacheManager getCacheManager(String jndi) throws NamingException
| {
| Context ic = null;
|
| try{
| ic = new InitialContext();
| return (CacheManager)ic.lookup(jndi);
| } finally {
| if(ic != null) {
| try {
| ic.close();
| } catch (NamingException ex) {
| }
| }
| }
| }
|
By default, the cache manager is bound to java:/CacheManager.
Regards,
Richard Burnison
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208811#4208811
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208811
17 years, 5 months