From the 4.0.0 release notes:
The 4.0.0 release ships with a different set of pre-configured server configuration file sets:
default: The default configuration with all required j2ee 1.4 services. It also uses
scoped deployments for ears with call by value semantics for ejb calls, and jndi lookups. Note that this can cause migration difficulties when porting from a 3.2.x release which was not using scoped class loading. Try the standard configuration if you see class loading issues during migration.
standard: The configuration consistent with the legacy 3.2.x 'default' configuration
that uses unscoped deployments and call by reference semantics for same VM ejb calls
and jndi lookups.
minimal: A minimal configuration with hot deployment of services, and a logging and jndi
all: The all inclusive configuration of the services avaliable in jboss.
We are reverting back to the 3.2.x default configuration file sets for the 4.0.1 release since this has caused so many issues.
Thanks for the quick reply...but I tried it with the standard config instead of default, and there was no difference. Same problems in all my apps. It also seems that I can't set the jndi-name of any bean. JBoss just gives it either BeanName if it's a remote EJB, or local/BeanName if it's a local bean. This makes it impossible to reference them any other way, which is obviously no good. Any ideas on what to do?