I would like to see the pooled invoker redone to suppor the concurrent pool interfaces and make better use of its concurrency classes. However, we are moving to the remoting versions in 4.2+ as far as I understand. What version are you targetting for this change?

We decided to move to a 4.2.x basis for the javaee 1.4 platform to make java5 the base jdk and update some jboss/thirdparty dependencies that could not go into another minor release of 4.0.x. At this point 4.0.x is in maintence mode with no planned next release and 4.2.0 will essentially be the next javaee 1.4 platform release.

This will still have the pooled invoker available as far as I understand. The question back is do you really want to use that invoker or would you want to switch to the remoting/unified invoker?

The full testsuite is run using the tests target in the testsuite module. There are several other sub starting points:

[starksm@succubus testsuite]$ ant -projecthelp
Buildfile: build.xml

Main targets:

all Builds everything.
clean Cleans up most generated files.
clobber Cleans up all generated files.
compile Compile all source files.
deployment-service-tests Tests targeting the deployment service
docs Builds all documentation.
help Displays the project help
iiop-test Execute a single test.
jars Builds all jar files.
jboss-all-config-tests The units tests which are run against the jboss all config
jboss-minimal-tests Validate the minimal config
main Executes the default target (most).
most Builds almost everything.
netboot-tests Tests run against a custom netboot configuration
one-test Execute a single test.
one-test-debug Execute a single test.
one-test-ssl Execute a single test.
reports Generates all reports.
test Execute a a group of tests
test-example-binding-manager Test the example binding configuration
tests Execute all non-benchmark tests.
tests-aop-scoped AOP tests requiring a native classloader hook
tests-apache Test that apache can be started/stopped from ant
tests-apache-tomcat-clustering Execute clustering tests requiring an apache load balanced two TC nodes.
tests-clustering Execute clustering tests requiring two nodes.
tests-clustering-all-stacks Execute clustering tests requiring two nodes.
tests-compatibility Checks compatibility on SerialUUID
tests-custom-securitymgr Tests run against a jboss server with custom security manager configured
tests-deployment Execute deployment Tests
tests-ha Execute ha tests.
tests-jacc-security Tests run against a jboss server with JACC configured
tests-jacc-security-external Tests run against a jboss server with JACC configured with an external policy provider
tests-jacc-securitymgr Tests run against a jboss server with JACC configured + security manager
tests-jboss-cluster Test that two jboss cluster nodes can be started/stopped from ant
tests-matrix Executes only the version check compatibility suite. Use -Dmatrix-versions=[version container] for this task
tests-security-manager Tests run against a jboss server with a security manager
tests-stress Execute all stress tests.
tests-webservice Execute JBossWS Tests
tests-webservice-ssl Tomcat tests requiring an SSL connector
tests-wsrp-integration Execute WSRP Integration Tests
tomcat-federation-tests Tomcat tests requiring Federation configured
tomcat-ssl-tests Tomcat tests requiring an SSL connector
tomcat-sso-clustered-tests Tomcat tests requiring clustered SSO configured
tomcat-sso-tests Tomcat tests requiring SSO configured
tomcat-webctx-tests Tomcat tests requiring classloader set to the web loader
Default target: main

Nothing uses the pooled invoker by default though, so to run the basic pooled invoker tests from the org.jboss.test.pooled package:

ant -Dtest=pooled test

You need to launch it manually. A pain, although you'll mind less if you end up running your test 10 times while you debug the test and only have to wait for the server to start once. :)

No objections. It should be synced with trunk as well.