-
1. Re: slimming 5.1 for JBoss messaging cluster
peterj Jul 28, 2009 12:25 PM (in response to augustsimonelli)This worked for me (by the way, I am not using an MDB, if you are you will need a few more things). I copied server/default as server/minmsg. Then I removed a lot of stuff. Here is the final deployers directory:
jboss-aop-jboss5.deployer/
jboss-jca.deployer/
messaging-definitions-jboss-beans.xml
metadata-deployer-jboss-beans.xml
security-deployer-jboss-beans.xml
And here is the deploy directory:
messaging/
security/
hdscanner-jboss-beans.xml
hsqldb-ds.xml
jboss-local-jdbc.rar
jboss-xa-jdbc.rar
jca-jboss-beans.xml
jms-ra.rar
remoting-jboss-beans.xml
transaction-jboss-beans.xml
transaction-service.xml
vfs-jboss-beans.xml
You might be able to remove even a few more things and have it work but like I said the above works for me. -
2. Re: slimming 5.1 for JBoss messaging cluster
augustsimonelli Jul 30, 2009 11:49 PM (in response to augustsimonelli)Thanks Peter!
I used what you posted as starting point. Then, because we also require a clustered JMS set up i had to work back from an "all" config. Then because the developers need jmx-console access i had to add in JbossWS!
So, i wound up with:
deploy:
cluster/
deploy.last/
hdscanner-jboss-beans.xml
jboss-local-jdbc.rar
jbossweb.sar/
jboss-xa-jdbc.rar
jca-jboss-beans.xml
jms-ra.rar
jmx-console.war/
jmx-invoker-service.xml
jmx-remoting.sar
legacy-invokers-service.xml
messaging/
mysql-ds.xml
properties-service.xml
remoting-jboss-beans.xml
security/
snmp-adaptor.sar
sqlexception-service.xml
transaction-jboss-beans.xml
transaction-service.xml
vfs-jboss-beans.xml
deployers:
ejb3.deployer/
jboss-aop-jboss5.deployer/
jboss-jca.deployer/
jbossweb.deployer/
messaging-definitions-jboss-beans.xml
metadata-deployer-jboss-beans.xml
security-deployer-jboss-beans.xml
Now I'm CERTAIN i still have too much due to the JBossWS need (could not get it to start without ejb3.deployer). My guess is now i need to look into what services are getting called via the xml files.
But in production i wouldn't have JBossWS anyway for the JMS solution.
But this has been helpful and your info gave the me what i needed to get to this stage!
Thanks so much!
August -
3. Re: slimming 5.1 for JBoss messaging cluster
augustsimonelli Jul 30, 2009 11:54 PM (in response to augustsimonelli)Course i mean jbossweb not ws!
-
4. Re: slimming 5.1 for JBoss messaging cluster
peterj Jul 31, 2009 1:58 PM (in response to augustsimonelli)You need jbossweb because of jmx-console - it is a web application. As an alternative, you might try using twiddle. Or look into using JConsole (there are some forum posts, and I think even a wiki page on that). Then you can remove jmx-console, jbossweb, and the associated components.