Configuring (triming) JBOOS 4.0.0DR2

[azovko]

Hi,

I would like to trim JBOSS configuration. My customer requirements is to start-up and run my company application (with JBOSS server) as faster as possible.

The services I need:

JMX
EJB 2.0 - CMP,....
cache-invalidation
transactions (I need it for CMP)
JBOSSMQ (JMS)
log4j
Hypersonic
JDBC


I do not need these services:

web services
jca
mail services
scheduler
uuid-key-generation

I have tried to trim default configuration but I had a lot of errors. I started with minimal, but my MQ is not working.

Any help will be appreciated.

Aurelije

[juha]

showing the errors would be helpful.

also if you plan on going production soon you should be working with 3.2.1 not 4.0 betas.

-- Juha

[azovko]

Hi,

We are not planing on going production soon (we want to use new JBoss MQ implementation). There is concern that JBOSS will not perform well and it will take a lot of time to come up. I am trimming JBOSS to resolve these issues.
I have started from scratch. I copied default configuration and trimmed web & console stuff and EJB 1.x for beginning.

Delete from Config:

standardjaws.xml


Delete from deploy:

jbossweb.sar
web-console.war
console-mgr.sar


I have this error:
_________________________________________________
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[{ 'jboss-net.war' URL: 'file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/jboss-net.sar/jboss-net.war/' localURL: 'file:/C:
/jboss-4.0.0DR2/server/phoenix/deploy/jboss-net.sar/jboss-net.war/' watching: 'file:/C:/jboss-4.0.0DR2/server/phoenix/de
ploy/jboss-net.sar/jboss-net.war/' SubDeployer: null }, { 'ejb-management.jar' URL: 'file:/C:/jboss-4.0.0DR2/server/phoe
nix/deploy/ejb-management.jar' localURL: 'file:/C:/jboss-4.0.0DR2/server/phoenix/tmp/deploy/server/phoenix/deploy/ejb-ma
nagement.jar/35.ejb-management.jar' watching: 'file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/ejb-management.jar' SubDepl
oyer: null }, { 'jmx-ejb-adaptor.jar' URL: 'file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/jmx-ejb-adaptor.jar' localURL:
'file:/C:/jboss-4.0.0DR2/server/phoenix/tmp/deploy/server/phoenix/deploy/jmx-ejb-adaptor.jar/36.jmx-ejb-adaptor.jar' wa
tching: 'file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/jmx-ejb-adaptor.jar' SubDeployer: null }]
Incompletely deployed packages:
[{ 'ejb-management.jar' URL: 'file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/ejb-management.jar' localURL: 'file:/C:/jbos
s-4.0.0DR2/server/phoenix/tmp/deploy/server/phoenix/deploy/ejb-management.jar/35.ejb-management.jar' watching: 'file:/C:
/jboss-4.0.0DR2/server/phoenix/deploy/ejb-management.jar' SubDeployer: null }, { 'jmx-ejb-adaptor.jar' URL: 'file:/C:/jb
oss-4.0.0DR2/server/phoenix/deploy/jmx-ejb-adaptor.jar' localURL: 'file:/C:/jboss-4.0.0DR2/server/phoenix/tmp/deploy/ser
ver/phoenix/deploy/jmx-ejb-adaptor.jar/36.jmx-ejb-adaptor.jar' watching: 'file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/jmx-ejb-adaptor.jar' SubDeployer: null }]
MBeans waiting for classes
_________________________________________

Do I need Axis service?
Do I need Aspect Management?
Do I need JSR-77 Single JBoss Server Management Domain?



I have this WebService too - how to disable it :
15:36:20,092 INFO [WebService] Started WebServer with address: 10.4.20.72:8083
15:36:20,092 INFO [WebService] Using RMI server codebase: http://AZOVKOLAP-2K:8083/
15:36:20,092 INFO [WebService] Started jboss:service=WebService
15:36:20,382 INFO [LocalInvoker] Started jboss:service=invoker,type=local
15:36:20,492 INFO [EJBSubsystemInvocationHandler] Started jboss.ejb:service=RemotingToEJBAdapter
15:36:20,733 INFO [MainDeployer] Deployed package: file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/ejb-service.xml
15:36:20,763 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-4.0.0DR2/server/phoenix/deploy/hilo-idgen-service.xml

[juha]

You've removed your servlet container so you're going to have to remove all servlets as well, including jboss-net.war.

You need Axis service if you plan on using Web Services.

You need Aspect Management if you plan on using AOP.

I can't remember if you can completely remove JSR-77 or not, experiment with it.

You can't remove 8083 for a stupid programming reason, make sure you don't allow all server classes be downloaded and block the port with a firewall.

-- Juha