Makes sense. We've switched to the unified invokers for the default
config.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf
Of Rajesh Rajasekaran
Sent: Thursday, January 11, 2007 1:55 PM
To:
JBoss.org development list
Cc: jboss-as(a)redhat.com; Tom Elrod
Subject: RE: [jboss-dev] Unified-tests
The testsuite does not complain if config specific files are
not found under resources/test-configs.
In this case too it is just a warning that is thrown.
The actual problem is the unified-jboss config doesn't boot.
The UnifiedInvoker service is added dynamincally to
jboss-service.xml (in testsuite/imports/server-config.xml)
when creating the unified-jboss config. There seems to be
some problem in that.
07:39:05,438 ERROR [MainDeployer] Could not create deployment:
file:/home/rrajasekaran/jboss-4.2.x/build/output/jboss-4.2.0.C
R1/server/
unified-jboss/conf/jboss-service.xml
org.jboss.deployment.DeploymentException: Trying to install
an already registered mbean: jboss:service=invoker,type=unified
at
org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
at
org.jboss.system.ServiceConfigurator.internalInstall(ServiceCo
nfigurator
.java:449)
at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurat
or.java:17
1)
at
org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
orImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
odAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedD
ispatcher.
java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanI
nvoker.jav
a:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.install(Unknown Source)
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf
Of Dimitris Andreadis
Sent: Thursday, January 11, 2007 4:55 AM
To:
JBoss.org development list
Cc: jboss-as(a)redhat.com; Tom Elrod
Subject: [jboss-dev] Unified-tests
Anybody knows what is the story with 'tests-unified' in the
JBossAS testsuite?
A special configuration is supposedly needed in
resources/test-configs/unified-jboss, but this configuration
is missing from all branches I checked (4.0, 4.2, HEAD)
The 4.0 testsuite somehow proceed without it (?!), the 4.2
testsuite complains, so I disabled those tests there.
Any clues?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development