[Datasource Configuration] - You have not defined a jta-data-source for a JTA enabled persistence
by lurker_huang
lurker_huang [http://community.jboss.org/people/lurker_huang] created the discussion
"You have not defined a jta-data-source for a JTA enabled persistence"
To view the discussion, visit: http://community.jboss.org/message/598870#598870
--------------------------------------------------------------
Hi,
When i deploy my Ejb on JBOSS6.0Final,it appear the follow exception:
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.j2ee:jar=RAEjb.jar,name=HelloWorldBean,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=RAEjb.jar,name=HelloWorldBean,service=EJB3" (should be in state "Installed", but is actually in state "**ERROR**")
DEPLOYMENTS IN ERROR:
Deployment "persistence.unit:unitName=RAEjb.jar#RAEjb" is in error due to the following reason(s): java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: RAEjb
Deployment "jboss.j2ee:jar=RAEjb.jar,name=HelloWorldBean,service=EJB3" is in error due to the following reason(s): org.jboss.ejb3.common.registrar.spi.DuplicateBindException: Cannot install org.jboss.ejb3.proxy.impl.factory.session.stateless.StatelessSessionRemoteProxyFactory@12245e0 under name "ProxyFactory/RAEjb/HelloWorldBean/HelloWorldBean" as there is already an existing object there: org.jboss.ejb3.proxy.impl.factory.session.stateless.StatelessSessionRemoteProxyFactory@3c5759, **ERROR**
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:82) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.java:138) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:246) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_05]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_05]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_05]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_05]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_05]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [:1.6.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [:1.6.0_05]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_05]
this my xml of datasource
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>RaOracleDs</jndi-name>
<use-java-context>false</use-java-context>
<connection-url>jdbc:oracle:thin:@132.35.81.59:1521:essdemo</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>top_sysmanm</user-name>
<password>topsysmanm</password>
<check-valid-connection-sql>SELECT 1 FROM DUAL</check-valid-connection-sql>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>Oracle</type-mapping>
</metadata>
<use-java-context>false</use-java-context>
<min-pool-size>50</min-pool-size>
<max-pool-size>200</max-pool-size>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>2</idle-timeout-minutes>
</local-tx-datasource>
</datasources>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/598870#598870]
Start a new discussion in Datasource Configuration at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 12 months
[JBoss Web Services] - JBossWS - AS 7 FAQ
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/asoldano] modified the document:
"JBossWS - AS 7 FAQ"
To view the document, visit: http://community.jboss.org/docs/DOC-16722
--------------------------------------------------------------
h1. JBossWS - AS 7 FAQ
This page is about the JBossWS integration with JBoss Application Server 7, which comes with a completely new architecture based on modules.
*Since 4.0.0*
h4. Which modules belong to JBossWS? Am I supposed to modify them?
The org.jboss.as.webservices.* and org.jboss.ws.* modules belongs to the JBossWS - AS7 integration. Users should not need to change anything in them.
h4. I'm getting a ClassNotFoundException with an application that used to work on AS6, what's happening?
On JBoss AS7 the user deployment classloader does not have any visibility over JBoss internals; so for instance you can't directly use JBossWS +implementation+ classes unless you explicitly set a dependency to the corresponding module.
h4. How do I add dependencies to modules on my deployments?
Dependencies are configured in the deployment MANIFEST.MF file:
Manifest-Version: 1.0
Dependencies: org.jboss.ws.cxf.jbossws-cxf-client services export, foo.bar
Here above +org.jboss.ws.cxf.jbossws-cxf-client+ and +foo.bar+ are the module you want to set dependencies to; +services+ tells the modules framework that you want to also import +META-INF/services/..+ declarations from the dependency, while +export+ exports the classes in the module so that you can actually use them in your code.
h4. How can I use JAXB classes?
In order for successfully use JAXB contexts, etc. in your client or endpoint running in-container, you need to properly setup a JAXB implementation; that is performed setting the following dependency:
Dependencies: com.sun.xml.bind services export
h4. How can I use JBossWS APIs?
The JBossWS APIs are always available by default whenever the webservices subsystem is available on AS7. So you just use them.
h4. How can I use Apache CXF APIs?
In order for using Apache CXF APIs you need to add a dependency to the org.apache.cxf module:
Dependencies: org.apache.cxf
...however, please note that would not come with any JBossWS-CXF customizations nor additional extensions. See next FAQ.
h4. Is there an aggregation client side module with all WS dependencies?
Yes. Whenever you simply want to use all the JBossWS feature/functionalities, you can set a dependency to the convenient client module. For the JBossWS-CXF stack that's:
Dependencies: org.jboss.ws.cxf.jbossws-cxf-client services export
h4. What is the org.jboss.ws.jaxws-client module for?
That is the generic JAXWS client module that is internally loaded when the first call to the configured JAXWS Provider is performed. Depending on the configured ws stack, that pulls in the required modules for basic jaxws functionalities.
h4. How do I use Spring with JBossWS-CXF?
The JBossWS-CXF modules have optional dependencies to the +org.springframework.spring+ module. So either create that manually in the application server or use the JBossWS-CXF installation scripts for doing that.
h4. What SAAJ impl do I get doing MessageFactory.getFactory()?
...
h4. My annotations are being ignored (and I get no special warning about that)!
When using annotations on your endpoints / handlers such as the Apache CXF ones (@InInterceptor, @GZIP, ...), or JBossWS Native ones (@EndpointConfig, @Documentation, ...) remember to add the proper module dependency in your manifest. Otherwise your annotations are not picked up and added to the annotation index by JBoss AS7, resulting in them being completely ignored (even silently in many cases -this needs to be fixed-).
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16722]
Create a new document in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 12 months
[Snowdrop] - Snowdrop 1.1 error
by Joe Thomas
Joe Thomas [http://community.jboss.org/people/jpalakunnel] created the discussion
"Snowdrop 1.1 error"
To view the discussion, visit: http://community.jboss.org/message/600172#600172
--------------------------------------------------------------
We're trying out Spring with our JBoss5.0 EAP. My understaning is that by using snowdrop we get better intergration with JBoss and Spring. I downloaded the snowdrop 1.1 distro and unzipped itnto my /{config}/deployers directory:
http://community.jboss.org/servlet/JiveServlet/showImage/2-600172-16159/s... http://community.jboss.org/servlet/JiveServlet/downloadImage/2-600172-161...
I also have a 3rd party poral .war that uses spring internally, I noticed the following exception when starting the server:
Deployment "vfsfile:/C:/jboss-eap-5.0/jboss-as/server/production/deploy/liferay.war/" is in error due to the following reason(s): java.lang.IllegalArgumentException: Multiple matching files not allowed: [ZipEntryHandler(a)6825008[path=liferay.war/WEB-INF/lib/portal-impl.jar/META-INF/base-spring.xml context=file:/C:/jboss-eap-5.0/jboss-as/server/production/deploy/ real=file:/C:/jboss-eap-5.0/jboss-as/server/production/deploy/liferay.war/WEB-INF/lib/portal-impl.jar/META-INF/base-spring.xml], ZipEntryHandler@18873538[path=liferay.war/WEB-INF/lib/portal-impl.jar/META-INF/counter-spring.xml....etc
however, when I add the following stanza to spring-deployers-jboss-beans.xml, the exception is gone:
<bean name="SpringParserDeployer" class="org.jboss.spring.deployers.SpringParserDeployer">
*<property name="allowMultipleFiles">true</property>*
</bean>
is this how we go 2 bat if we have multiple spring-based application on Jboss5.0?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/600172#600172]
Start a new discussion in Snowdrop at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss Cache] - PojoCacheException when trying to attach a java object (POJO) to the PojoCache.
by MeeNam Park
MeeNam Park [http://community.jboss.org/people/mpark] created the discussion
"PojoCacheException when trying to attach a java object (POJO) to the PojoCache."
To view the discussion, visit: http://community.jboss.org/message/600138#600138
--------------------------------------------------------------
On our project, we are using JBOSS Cache to replicate ~20,000 simple POJO objects among 28 jvm’s. When attaching a java object (POJO) to the PojoCache, we get “PojoCacheException”. When this occurs, most of the subsequent attempt to attach additional POJO to the PojoCache result in the same exception. When the application (Jvm) is restarted, sometime this problem goes away.
This PojoCacheException problem does not occur 100% – however, when it happens, it usually happens when adding the 1^st^ POJO to the PojoCache, and usually, all subsequent POJO attachment will fail.
PojoCacheException logged indicate all exceptions appear to be cause by one of the 2 root causes:
* - “Root cause is Suspected member: 192.168.209.108:60978”
* - “Root cause is State retrieval timed out waiting for flush unblock. (timeout = 80000 millis)”
The port number (60978) sited is different for different runs. Any idea what’s causing either of the problems? Would like to know if the ip & port sited as root cause have anything to do with JGroup?
Our project has 2 redundant servers that are deployed on *JBOSS-5.0.0 GA*, using *jbosscache-core-3.0.0.GA and jbosscache-pojo-3.0.0.GA* which are included in the JBOSS-5.0.0 GA. All the POJO attachment is being on the servers deployed on the JBOSS appserver, thereforefore, all of the PojoCacheExceptions are coming from the JBOSS jvm’s.
Below is the PojoCacheException stack trace for the 2 types of PojoCacheExceptions we’re seeing:
Org.jboss.cache.pojo.PojoCacheException: attach failed “OBJECT KEY”
At org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:111)
At org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
At org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:88)
At java.lang.Thread.run (Thread.java:619)
*Caused by: org.jboss.cache.SuspectException: Suspected member: 192.168.209.108:60978*
At org.jboss.cache.RPCManagerImpl.callRemoteMethods (RPCManagerImpl.java:472)
At org.jboss.cache.RPCManagerImpl.callRemoteMethods (RPCManagerImpl.java:432)
At org.jboss.cache.RPCManagerImpl.callRemoteMethods (RPCManagerImpl.java:437)
At org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall (BaseRpcInterceptor.java:161)
At org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall (BaseRpcInterceptor.java:135)
At org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall (BaseRpcInterceptor.java:107)
At org.jboss.cache.interceptors.ReplicationInterceptor.handleCrudeMethod (ReplicationInterceptor.java:160)
at org.jboss.cache.interceptors.ReplicationInterceptor.visitPutKeyValueCommand(ReplicationInterceptor.java:107)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:131)
at org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.based.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:119)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at org.jboss.cache.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:178)
at org.jboss.cache.interceptors.InvocationContextInterceptor.visitPutKeyValueCommand(InvocationContextInterceptor.java:82)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:265)
at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:560)
at org.jboss.cache.pojo.impl.InternalHelper.lockPojo(InternalHelper.java:342)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObject(PojoCacheDelegate.java:101)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:102)
*Root cause is Suspected member: 192.168.209.108:60978*
*************************************************************************
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:111)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:88)
at java.lang.Thread.run (Thread.java:619)
*Caused by: org.jboss.cache.lock.TimeoutException: state retrieval timed out waiting for flush unblock. (timeout = 80000 milis)*
at org.jboss.cache.RPCManagerImpl.callRemoteMethods(RPCManagerImpl.java:455)
at org.jboss.cache.RPCManagerImpl.callRemoteMethods(RPCManagerImpl.java:432)
at org.jboss.cache.RPCManagerImpl.callRemoteMethods(RPCManagerImpl.java:437)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:161)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:135)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:107)
at org.jboss.cache.interceptors.ReplicationInterceptor.handleCrudeMethod(ReplicationInterceptor.java:160)
at org.jboss.cache.interceptors.ReplicationInterceptor.visitPutKeyValueCommand(ReplicationInterceptor.java:107)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:131)
at org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.based.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:119)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at org.jboss.cache.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:178)
at org.jboss.cache.interceptors.InvocationContextInterceptor.visitPutKeyValueCommand(InvocationContextInterceptor.java:82)
at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:265)
at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:560)
at org.jboss.cache.pojo.impl.InternalHelper.lockPojo(InternalHelper.java:342)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObject(PojoCacheDelegate.java:101)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:102)
*Root cause is State retrieval timed out waiting for flush unblock. (timeout = 80000 millis)*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/600138#600138]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss Tools] - JBoss Tools deployment scanner error when building
by Benjamin Maisano
Benjamin Maisano [http://community.jboss.org/people/ben.maisano] created the discussion
"JBoss Tools deployment scanner error when building"
To view the discussion, visit: http://community.jboss.org/message/600107#600107
--------------------------------------------------------------
Hi,
I have an error building and deploying my projects. I'm using the following:
Eclipse Helios - 3.6
JDK 6 update 24
Windows 7 64 bit
JBoss 5.0.1 latest stable (company requires this version)
Seam 2.1.2
JBoss Tools 3.2 - downloaded latest from within Eclipse
Often when I clean/build I get the following error showing up in my IDE:
+JBossTools was unable to resume the JBoss deployment scanner. Your deployment may not be recognized by the server. Please ensure your version of JBoss includes an unsecured JMX adapter+
Along with exception at bottom of this post. It seems semi-random, though happens very often. If I look into the build dir (ie bin) of my projects after I see this usually the .class files are not generated. This then causes issues deploying to JBoss AS. Also sometimes I have a working EAR deployed but on making a change and trying to publish I get errors about the WAR and/or EJB modules of the EAR not being present. I have a basic setup:
1 WAR with mostly web resources and some java files
1 EJB module with the majority of the seam entity beans and such
1 EAR referencing WAR and EJB modules
Any help with this would be grealy appreciated, thank you.
Exception that gets logged along with message above:
javax.management.MBeanException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:184)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.management.InstanceNotFoundException: jboss.deployment:flavor=URL,type=DeploymentScanner is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529)
at org.jboss.mx.server.registry.BasicMBeanRegistry.getValue(BasicMBeanRegistry.java:567)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
... 47 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/600107#600107]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
