RE: [JBoss-dev] InstanceAlreadyExistsException afterundeployandrepeated deploy in JBoss AS 5.0.0 Beta
by Brian Stansberry
There is a clustering test case (HAJndiTestCase) that fails in HEAD for
this same reason -- an earlier test deploys and undeploys the same ejb
jar HAJndiTestCase uses. I've looked at the test log and there is no
indication of a problem with the earlier test. In Jaroslaw's first post
before, the log of the undeploy is also clean.
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
________________________________
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Jaroslaw
Kijanowski
Sent: Monday, August 14, 2006 1:56 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] InstanceAlreadyExistsException
afterundeployandrepeated deploy in JBoss AS 5.0.0 Beta
I run the tests in one-test mode, so no time outs in previous
tests are the reason for IAEE. The first time I run test "X" everything
is fine, deploying jar, binding home interfaces and finally unbinding
home interfaces (what's not true because there are still visible in the
JMXConsole). When I run the test again I get the IAEE. The whole package
org.jboss.test.cmp2.* (over 250 tests) would run without any errors (now
over 230 errors), when unbinding would work correct.
For example, many tests have to bind EJBTestRunner to jndi, but
only the first test can do it successfully, the others can't because
EJBTestRunner isn't properly unbound and a repeated bind cause the IAEE.
I doesn't happen with JBoss4.
________________________________
From: jboss-development-bounces(a)lists.jboss.org on behalf of
Ryan Campbell
Sent: Mon 2006-08-14 13:42
To: JBoss.org development list
Subject: RE: [JBoss-dev] InstanceAlreadyExistsException
afterundeployandrepeated deploy in JBoss AS 5.0.0 Beta
Jaroslaw, look for any test timeouts. As Adrian mentioned, it
is some test failing to teardown and tests timing out are likely
suspects. Debug them first. If you see no test timeouts, then the
problem becomes harder.
In that case, would it be realistic for JBossTestCase to assert
that the number of deployments remain constant between each deploy and
undeploy()? Could be a simple mechanism to flag bad tests.
________________________________
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Jaroslaw
Kijanowski
Sent: Saturday, August 12, 2006 10:58 AM
To: jboss-development(a)lists.jboss.org
Subject: [JBoss-dev] InstanceAlreadyExistsException
afterundeploy andrepeated deploy in JBoss AS 5.0.0 Beta
Hello,
I've got the following issue with JBoss AS 5.0.0 Beta:
After I run a test (in "one-test" mode, so no previous test
caused an time out etc.), I see on the server console that the
corresponding jar is undeploying and the home interfaces are unbinding.
But when I run the test again, I get InstanceAlreadyExistsException:
11:43:12,406 INFO [Server] JBoss (MX MicroKernel) [5.0.0.Beta
(build: CVSTag=HE
AD date=200608071122)] Started in 1m:3s:563ms
11:43:53,046 INFO [EjbModule] Deploying Customer
11:43:53,234 INFO [EjbModule] Deploying Account
11:43:53,250 INFO [EjbModule] Deploying Teller
11:43:53,281 INFO [EjbModule] Deploying Bank
11:43:54,687 INFO [ProxyFactory] Bound EJB Home 'Customer' to
jndi 'bank/Custom
er'
11:43:54,703 INFO [ProxyFactory] Bound EJB Home 'Account' to
jndi 'bank/Account
'
11:43:54,718 INFO [ProxyFactory] Bound EJB Home 'Teller' to
jndi 'bank/Teller'
11:43:54,734 INFO [ProxyFactory] Bound EJB Home 'Bank' to jndi
'bank/Bank'
11:43:54,734 INFO [EJBDeployer] Deployed:
file:/D:/jboss-svn4/jboss-head/testsu
ite/output/lib/bank.jar
11:44:02,093 INFO [EJBDeployer] Undeploying:
file:/D:/jboss-svn4/jboss-head/tes
tsuite/output/lib/bank.jar
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Bank' from
jndi 'bank/Bank'
11:44:02,125 INFO [EjbModule] Undeployed Bank
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Teller' from
jndi 'bank/Telle
r'
11:44:02,125 INFO [EjbModule] Undeployed Teller
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Account' from
jndi 'bank/Acco
unt'
11:44:02,140 INFO [EjbModule] Undeployed Account
11:44:02,140 INFO [ProxyFactory] Unbind EJB Home 'Customer'
from jndi 'bank/Cus
tomer'
11:44:02,140 INFO [EjbModule] Undeployed Customer
*************
An now I run the test again:
*************
11:44:17,390 INFO [EjbModule] Deploying Customer
11:44:17,421 INFO [EjbModule] Deploying Account
11:44:17,421 INFO [EjbModule] Deploying Teller
11:44:17,437 INFO [EjbModule] Deploying Bank
11:44:17,453 INFO [EntityContainer] Registration is not done ->
stop
11:44:17,453 ERROR [AbstractKernelController] Error installing
to Create: name=j
boss.j2ee:module=bank.jar,service=EjbModule,uid=29596937
state=Configured mode=M
anual requiredState=Create
javax.management.InstanceAlreadyExistsException:
jboss.j2ee:jndiName=bank/Custom
er,service=EJB already registered.
at
org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistr
y.java:765)
at
org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMB
eanRegistry.java:234)
.
.
.
11:44:17,531 INFO [EJBDeployer] Deployed:
file:/D:/jboss-svn4/jboss-head/testsu
ite/output/lib/bank.jar
11:44:17,968 INFO [EJBDeployer] Undeploying:
file:/D:/jboss-svn4/jboss-head/tes
tsuite/output/lib/bank.jar
******************
I saw similar issues for previous versions of the AS (all
resolved) but I think this is the first for the Beta 5.0 version.
19 years, 8 months
RE: [JBoss-dev] InstanceAlreadyExistsException afterundeploy andrepeated deploy in JBoss AS 5.0.0 Beta
by Ryan Campbell
Jaroslaw, look for any test timeouts. As Adrian mentioned, it is some
test failing to teardown and tests timing out are likely suspects.
Debug them first. If you see no test timeouts, then the problem becomes
harder.
In that case, would it be realistic for JBossTestCase to assert that the
number of deployments remain constant between each deploy and
undeploy()? Could be a simple mechanism to flag bad tests.
________________________________
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Jaroslaw
Kijanowski
Sent: Saturday, August 12, 2006 10:58 AM
To: jboss-development(a)lists.jboss.org
Subject: [JBoss-dev] InstanceAlreadyExistsException afterundeploy
andrepeated deploy in JBoss AS 5.0.0 Beta
Hello,
I've got the following issue with JBoss AS 5.0.0 Beta:
After I run a test (in "one-test" mode, so no previous test caused an
time out etc.), I see on the server console that the corresponding jar
is undeploying and the home interfaces are unbinding. But when I run the
test again, I get InstanceAlreadyExistsException:
11:43:12,406 INFO [Server] JBoss (MX MicroKernel) [5.0.0.Beta (build:
CVSTag=HE
AD date=200608071122)] Started in 1m:3s:563ms
11:43:53,046 INFO [EjbModule] Deploying Customer
11:43:53,234 INFO [EjbModule] Deploying Account
11:43:53,250 INFO [EjbModule] Deploying Teller
11:43:53,281 INFO [EjbModule] Deploying Bank
11:43:54,687 INFO [ProxyFactory] Bound EJB Home 'Customer' to jndi
'bank/Custom
er'
11:43:54,703 INFO [ProxyFactory] Bound EJB Home 'Account' to jndi
'bank/Account
'
11:43:54,718 INFO [ProxyFactory] Bound EJB Home 'Teller' to jndi
'bank/Teller'
11:43:54,734 INFO [ProxyFactory] Bound EJB Home 'Bank' to jndi
'bank/Bank'
11:43:54,734 INFO [EJBDeployer] Deployed:
file:/D:/jboss-svn4/jboss-head/testsu
ite/output/lib/bank.jar
11:44:02,093 INFO [EJBDeployer] Undeploying:
file:/D:/jboss-svn4/jboss-head/tes
tsuite/output/lib/bank.jar
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Bank' from jndi
'bank/Bank'
11:44:02,125 INFO [EjbModule] Undeployed Bank
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Teller' from jndi
'bank/Telle
r'
11:44:02,125 INFO [EjbModule] Undeployed Teller
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Account' from jndi
'bank/Acco
unt'
11:44:02,140 INFO [EjbModule] Undeployed Account
11:44:02,140 INFO [ProxyFactory] Unbind EJB Home 'Customer' from jndi
'bank/Cus
tomer'
11:44:02,140 INFO [EjbModule] Undeployed Customer
*************
An now I run the test again:
*************
11:44:17,390 INFO [EjbModule] Deploying Customer
11:44:17,421 INFO [EjbModule] Deploying Account
11:44:17,421 INFO [EjbModule] Deploying Teller
11:44:17,437 INFO [EjbModule] Deploying Bank
11:44:17,453 INFO [EntityContainer] Registration is not done -> stop
11:44:17,453 ERROR [AbstractKernelController] Error installing to
Create: name=j
boss.j2ee:module=bank.jar,service=EjbModule,uid=29596937
state=Configured mode=M
anual requiredState=Create
javax.management.InstanceAlreadyExistsException:
jboss.j2ee:jndiName=bank/Custom
er,service=EJB already registered.
at
org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistr
y.java:765)
at
org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMB
eanRegistry.java:234)
.
.
.
11:44:17,531 INFO [EJBDeployer] Deployed:
file:/D:/jboss-svn4/jboss-head/testsu
ite/output/lib/bank.jar
11:44:17,968 INFO [EJBDeployer] Undeploying:
file:/D:/jboss-svn4/jboss-head/tes
tsuite/output/lib/bank.jar
******************
I saw similar issues for previous versions of the AS (all resolved) but
I think this is the first for the Beta 5.0 version.
19 years, 8 months
RE: [JBoss-dev] problem starting JBoss AS 5.0.0 Beta in qa-lab
by Ryan Campbell
To pass the -u option to all testsuite server instances, use the
udpgroup option:
./build.sh -DudpGroup=128.1.2.3 tests
http://docs.jboss.org/process-guide/en/html/testsuite.html#testsuite-clu
stering-tests-configuration
This should always be set when running the JBoss testsuite in a
multi-user environment.
________________________________
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Brian
Stansberry
Sent: Sunday, August 13, 2006 2:40 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] problem starting JBoss AS 5.0.0 Beta in qa-lab
AS HEAD is using JGroups 2.4.beta, which doesn't interoperate with the
2.2.7 version used in 4.0.x. Presumably someone was running a 4.0.x
instance of the AS.
To make the error go away, I have changed the port used by the JGroups
multiplexer in HEAD to not match any of those used in 4.0.x. The
clustered services now all use the multiplexer.
It's a good practice to start your AS instance with the -u switch, to
give yourself your own multicast address so you don't unintentionally
form a cluster with someone else. But, there are a couple problems that
make this not a perfect solution:
1) JVM or OS bug on Linux:
http://wiki.jboss.org/wiki/Wiki.jsp?page=PromiscuousTraffic
2) Right now the value of the -u switch isn't picked up by the
multiplexer; that's something we need to take care of.
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
________________________________
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Jaroslaw
Kijanowski
Sent: Saturday, August 12, 2006 2:53 PM
To: jboss-development(a)lists.jboss.org
Subject: [JBoss-dev] problem starting JBoss AS 5.0.0 Beta in
qa-lab
Hello,
I've got the following problem to start the AS 5.0 beta in
qa-lab (JBoss AS 4_0_3_SP1 works fine):
[jkijanowski@dev03 bin]$ env|grep IP
MYTESTIP_4=10.64.9.18
MYTESTIP_1=10.64.9.15
MYTESTIP_2=10.64.9.16
MYTESTIP_3=10.64.9.17
MYTESTIPS=10.64.9.15 10.64.9.16 10.64.9.17 10.64.9.18
[jkijanowski@dev03 bin]$ ./run.sh -c all -b $MYTESTIP_1
========================================================================
=
JBoss Bootstrap Environment
JBOSS_HOME:
/home/jkijanowski/jboss-head/build/output/jboss-5.0.0.Beta
JAVA: /opt/jdk1.5.0_06/bin/java
JAVA_OPTS: -Xms128m -Xmx512m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
CLASSPATH:
/home/jkijanowski/jboss-head/build/output/jboss-5.0.0.Beta/bin/run.jar:/
opt/jdk1.5.0_06/lib/tools.jar
========================================================================
=
15:01:59,351 INFO [Server] Starting JBoss (MX MicroKernel)...
.
.
.
15:02:52,635 INFO [Server] JBoss (MX MicroKernel) [5.0.0.Beta
(build: CVSTag=HEAD date=200608071140)] Started in 53s:276ms
15:02:57,622 WARN [UDP] packet from 10.64.48.180:49526 has
different version (12338) from ours (241). This may cause problems
15:02:57,622 ERROR [UDP] failed unmarshalling message
java.io.EOFException
at
java.io.DataInputStream.readFully(DataInputStream.java:178)
at
org.jgroups.stack.IpAddress.readFrom(IpAddress.java:268)
at org.jgroups.Message.readFrom(Message.java:607)
at org.jgroups.protocols.TP.bufferToMessage(TP.java:983)
at
org.jgroups.protocols.TP.handleIncomingPacket(TP.java:839)
at org.jgroups.protocols.TP.access$200(TP.java:45)
at
org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1294)
at java.lang.Thread.run(Thread.java:595)
15:03:03,321 WARN [UDP] packet from 10.64.48.180:49522 has
different version (12338) from ours (241). Packet is discarded
15:03:18,891 WARN [UDP] packet from 10.64.48.180:49526 has
different version (12338) from ours (241). This may cause problems
15:03:18,892 ERROR [UDP] failed unmarshalling message
java.io.EOFException
at
java.io.DataInputStream.readFully(DataInputStream.java:178)
at
org.jgroups.stack.IpAddress.readFrom(IpAddress.java:268)
at org.jgroups.Message.readFrom(Message.java:607)
at org.jgroups.protocols.TP.bufferToMessage(TP.java:983)
at
org.jgroups.protocols.TP.handleIncomingPacket(TP.java:839)
at org.jgroups.protocols.TP.access$200(TP.java:45)
at
org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1294)
at java.lang.Thread.run(Thread.java:595)
15:03:20,731 WARN [UDP] packet from 10.64.48.180:49522 has
different version (12338) from ours (241). Packet is discarded
15:03:35,861 WARN [UDP] packet from 10.64.48.180:49526 has
different version (12338) from ours (241). This may cause problems
15:03:35,862 ERROR [UDP] failed unmarshalling message
java.io.EOFException
at
java.io.DataInputStream.readFully(DataInputStream.java:178)
at
org.jgroups.stack.IpAddress.readFrom(IpAddress.java:268)
at org.jgroups.Message.readFrom(Message.java:607)
at org.jgroups.protocols.TP.bufferToMessage(TP.java:983)
at
org.jgroups.protocols.TP.handleIncomingPacket(TP.java:839)
at org.jgroups.protocols.TP.access$200(TP.java:45)
at
org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1294)
at java.lang.Thread.run(Thread.java:595)
15:03:38,701 WARN [UDP] packet from 10.64.48.180:49522 has
different version (12338) from ours (241). Packet is discarded
15:03:52,361 WARN [UDP] packet from 10.64.48.180:49526 has
different version (12338) from ours (241). This may cause problems
15:03:52,362 ERROR [UDP] failed unmarshalling message
java.io.EOFException
.
.
.
and it continues until I stop the server. No such problem on my
laptop. This issue doesn't prevent me from running tests.
P.S.
IP 10.664.48.180 is assigned in /opt/assigend-ips two times:
[jkijanowski@dev03 testsuite]$ grep 10.64.48.180
/opt/assigned-ips
dev13 dsicore 10.64.48.180
dev13 rrajasekaran 10.64.48.180
19 years, 8 months
Quartz MBean
by Sacha Labourey
In JBoss HEAD, it seems there is a problem with the Quartz MBean, a
fresh start gives this:
17:34:39,468 INFO [WrapperDataSourceService] Bound ConnectionManager
'jboss.jca
:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
17:34:39,734 WARN [TimerServiceFactory] sql failed: CREATE TABLE
qrtz_job_detai
ls(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL,
DESCRIPTION VA
RCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE
VARCHAR(1) NOT
NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL,
REQUEST
S_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY
(JOB_NAME,JOB_
GROUP))
java.sql.SQLException: Table already exists: QRTZ_JOB_DETAILS in
statement [CREA
TE TABLE qrtz_job_details]
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.execute(Unknown Source)
at
org.jboss.resource.adapter.jdbc.CachedPreparedStatement.execute(Cache
dPreparedStatement.java:216)
at
org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execute(Wrap
pedPreparedStatement.java:209)
at
org.jboss.ejb3.timerservice.TimerServiceFactory.execute(TimerServiceF
actory.java:170)
at
org.jboss.ejb3.timerservice.TimerServiceFactory.createSchema(TimerSer
viceFactory.java:86)
at
org.jboss.ejb3.timerservice.TimerServiceFactory.start(TimerServiceFac
tory.java:241)
at
org.jboss.ejb3.timerservice.jmx.EJB3TimerService.startService(EJB3Tim
erService.java:105)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
19 years, 8 months
Exception when starting AS-HEAD
by Sacha Labourey
Hello,
Any idea what this exception is? it happens whenever starting a fresh
HEAD of JBoss on my windows laptop:
17:31:34,265 ERROR [AbstractKernelController] Error installing to Start:
name=jb
oss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
mode=Manual re
quiredState=Installed
java.net.MalformedURLException: Bad URL path:
_Sacha/jndi/rmi://Laptop_Sacha:109
0/jmxconnector
at
javax.management.remote.JMXServiceURL.validate(JMXServiceURL.java:348
)
at
javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:208)
at
org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConn
ectorServerService.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java
:182)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installActio
n(StartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.ServiceControllerContextAction.instal
l(ServiceControllerContextAction.java:46)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:226)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(Serv
iceControllerContext.java:186)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:596)
at
org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:346)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:438)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:379)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:263)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:164)
at
org.jboss.system.ServiceController.start(ServiceController.java:376)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1018)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:812)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:140)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java
:165)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installActio
n(StartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.ServiceControllerContextAction.instal
l(ServiceControllerContextAction.java:46)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:226)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(Serv
iceControllerContext.java:186)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:596)
at
org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:346)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:438)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:379)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:263)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:164)
at
org.jboss.system.ServiceController.start(ServiceController.java:376)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:157)
19 years, 8 months
