[JBoss JIRA] Created: (JBAS-8033) Can not deploy JAXWS war file to Jboss 5.1 and 6.0.0.M2
by jay ZHAO (JIRA)
Can not deploy JAXWS war file to Jboss 5.1 and 6.0.0.M2
-------------------------------------------------------
Key: JBAS-8033
URL: https://jira.jboss.org/browse/JBAS-8033
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.M2, JBossAS-5.1.0.GA
Environment: RHEL 2.6.18-194.el5
Reporter: jay ZHAO
Assignee: Ales Justin
Priority: Critical
We have a JAXWS war file which has been successfully deployed to GlassFish and WebLogic, but cannot be deployed to JBoss AS 5.1 and 6.0.0.M2. On AS 5.1 there is no detailed log info, here is the error log on 5.1:
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/opt/jboss-5.1.0.GA/server/default/tmp/4sge1w-qbnvnk-g9bavwnj-1-g9d3hmos-4t8/JAXWSDiscoveryService.war/ deployment failed
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
... 16 more
2010-05-18 15:06:31,508 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-15) Remove, [vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/]
2010-05-18 15:06:31,523 WARN [org.rhq.core.pc.inventory.CreateResourceRunner] (ResourceFactory.executor-1) Throwable was found in creation report for request [1]: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/opt/jboss-5.1.0.GA/server/default/tmp/4sge1w-qbnvnk-g9bavwnj-1-g9d3hmos-4t8/JAXWSDiscoveryService.war/ deployment failed
The errors we got when we deployed the same war file to 6.0.0.M2 are:
Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.derby.jdbc.EmbedXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/derby/jdbc/EmbedXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
at java.lang.Class.getDeclaredMethods(Class.java:1791)
at org.jboss.deployment.AnnotatedClassFilter.hasAnnotations(AnnotatedClassFilter.java:194)
at org.jboss.deployment.AnnotatedClassFilter.accepts(AnnotatedClassFilter.java:122)
at org.jboss.deployment.AnnotatedClassFilter.visit(AnnotatedClassFilter.java:102)
at org.jboss.virtual.plugins.vfs.helpers.WrappingVirtualFileHandlerVisitor.visit(WrappingVirtualFileHandlerVisitor.java:62)
at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:362)
at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:307)
at org.jboss.virtual.VFS.visit(VFS.java:438)
at org.jboss.virtual.VirtualFile.visit(VirtualFile.java:448)
at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.getClasses(WarAnnotationMetaDataDeployer.java:180)
at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.processMetaData(WarAnnotationMetaDataDeployer.java:153)
at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.deploy(WarAnnotationMetaDataDeployer.java:127)
at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.deploy(WarAnnotationMetaDataDeployer.java:80)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
... 39 more
2010-05-18 10:45:15,790 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-2) Failed to complete command: [start] for deployment: names=[vfszip:/opt/jboss-6.0.0.20100216-M2/server/default/deploy/JAXWSDiscoveryService.war/]: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS)
We have not seen the same problem in other major AS platforms.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBAS-8651) Typo in ClusteringDefaultsDeployer make the global passivationMaxIdleTime prop not being picked up
by Jean Deruelle (JIRA)
Typo in ClusteringDefaultsDeployer make the global passivationMaxIdleTime prop not being picked up
--------------------------------------------------------------------------------------------------
Key: JBAS-8651
URL: https://jira.jboss.org/browse/JBAS-8651
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.1.0.GA
Reporter: Jean Deruelle
Assignee: Remy Maucherat
Priority: Minor
in addPassivationConfigDefaults method of ClusteringDefaultsDeployer
line 246 contains a bad copy paste
if (passCfg.getPassivationMinIdleTime() == null)
passCfg.setPassivationMaxIdleTime(new Integer(this.passivationMaxIdleTime));
it should be
if (passCfg.getPassivationMaxIdleTime() == null)
passCfg.setPassivationMaxIdleTime(new Integer(this.passivationMaxIdleTime));
It affects EAP 5 version as well
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBAS-8381) Widen the range of raw SNMP types permitted by RequestHandlerImpl
by Kenny MacLeod (JIRA)
Widen the range of raw SNMP types permitted by RequestHandlerImpl
-----------------------------------------------------------------
Key: JBAS-8381
URL: https://jira.jboss.org/browse/JBAS-8381
Project: JBoss Application Server
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: SNMP adapter
Affects Versions: JBossAS-5.1.0.GA
Reporter: Kenny MacLeod
Assignee: Dimitris Andreadis
Priority: Minor
RequestHandlerImpl.getValue() for includes logic for determining how to express a JMX attribute in terms of an SNMP type. It supports Long, Integer, and String, as well as values of the raw SnmpTimeTicks and SnmpObjectId types.
I think this should be widened, by removing the check for SnmpTimeTicks and SnmpObjectId, and replacing it with a single check for the SnmpSyntax interface. This would allow beans to return the full range of SNMP types. Also, an explicit check for null should be performed, and represented by the SnmpNull type.
Note that setValueFor() is already more restrictive than getValueFor(), so we wouldn't be introducing any new asymmetry.
Patch for RequestHandlerImpl.java to follow.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBAS-7884) javax.transaction.TransactionManager not found after OSGi integration
by Thomas Diesler (JIRA)
javax.transaction.TransactionManager not found after OSGi integration
---------------------------------------------------------------------
Key: JBAS-7884
URL: https://jira.jboss.org/jira/browse/JBAS-7884
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: OSGi integration
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossAS-6.0.0.M3
18:36:17,250 WARN [org.jboss.deployment.MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossas/trunk/testsuite/output/lib/simple-session.jar: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "vfs:///home/tdiesler/svn/jbossas/trunk/testsuite/output/lib/simple-session.jar" is missing the following dependencies:
Dependency "interface javax.transaction.TransactionManager" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'interface javax.transaction.TransactionManager' **")
Dependency "interface javax.transaction.TransactionManager" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'interface javax.transaction.TransactionManager' **")
DEPLOYMENTS IN ERROR:
Deployment "interface javax.transaction.TransactionManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'interface javax.transaction.TransactionManager' **
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
by Paul Ferraro (JIRA)
Move jboss-ha-server-* jars from common/lib to server/all/lib
-------------------------------------------------------------
Key: JBAS-8164
URL: https://jira.jboss.org/browse/JBAS-8164
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 6.0.0.M3
Reporter: Paul Ferraro
Assignee: Scott Marlow
Fix For: 6.0.0.Final
Currently, the build puts the following jars into common/lib:
jboss-ha-server-api.jar
jboss-ha-server-cache-jbc.jar
jboss-ha-server-cache-spi.jar
jboss-ha-server-core.jar
This will likely cause classloader issues, especially for classes that extend/implement jbosscache or jgroups classes (e.g. CacheManager, ChannelFactory), since these jars reside in server/all/lib
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBAS-8773) Log configuration errors are hard to debug
by David Lloyd (JIRA)
Log configuration errors are hard to debug
------------------------------------------
Key: JBAS-8773
URL: https://issues.jboss.org/browse/JBAS-8773
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: TBD-6.x
Because of the way the log services are coordinated, some log configuration problems and runtime errors do not occur until after the bootstrap log handlers have already been removed. It would be better to not remove these handlers until the new ones are known to be good. Maybe by using replaceHandlers() in the logger service.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBAS-8652) Thread deadlock in org.jboss.aop.asintegration.jboss5.ToClassInvoker.toClass()
by martin walla (JIRA)
Thread deadlock in org.jboss.aop.asintegration.jboss5.ToClassInvoker.toClass()
------------------------------------------------------------------------------
Key: JBAS-8652
URL: https://jira.jboss.org/browse/JBAS-8652
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: AOP
Affects Versions: JBossAS-5.1.0.GA
Environment: JBossAS 5.1.0.GA, JAVA 1.6.0_17, Sun Solaris
Reporter: martin walla
Assignee: Kabir Khan
On startup of JBoss 5.1.0-GA sometimes (seen it several times) it comes to a Thread deadlock between the main thread and an other Thread.
We use XA datasources and we have configured in the file conf/jbossts-properties.xml the Arjuna Transaction Manager Recovery Module.
<properties depends="arjuna" name="jta">
<property name="com.arjuna.ats.jta.recovery.XAResourceRecoveryJDBC" value="com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery;jndiname=nxcore/resource/DS"/>
This RecoveryModule is triggered during startup in a Thread which causes together with the "main" Thread a deadlock
in the method toClass() of the class org.jboss.aop.asintegration.jboss5.ToClassInvoker.
1.) The "main" Thread has already locked the org.jboss.classloader.spi.base.BaseClassLoader and waits to lock the "tmplock" Object in class ToClassInvoker.
2.) The other Thread ("Thread-20") has already locked the "tmplock" Object and waits to lock the BaseClassLoader for the call
of the synchronized method loadClass() (myloader.loadClass()).
Source can be seen here:
http://grepcode.com/file/repository.jboss.com/maven2/org.jboss.aop/jboss-...
IMHO a locking of the BaseClassLoader "synchronized (myloader)" before the locking of the "tmplock" Object should prevent this deadlock situation.
"main":
at org.jboss.aop.asintegration.jboss5.ToClassInvoker.toClass(ToClassInvoker.java:72)
- waiting to lock <0xffffffff64f63d00> (a java.lang.Object)
at org.jboss.aop.classpool.jbosscl.JBossClDelegatingClassPool.toClass(JBossClDelegatingClassPool.java:81)
at javassist.CtClass.toClass(CtClass.java:1094)
at org.jboss.aop.instrument.TransformerCommon$ToClassAction$2.toClass(TransformerCommon.java:331)
at org.jboss.aop.instrument.TransformerCommon.compileOrLoadClass(TransformerCommon.java:103)
at org.jboss.aop.instrument.TransformerCommon.compileOrLoadClass(TransformerCommon.java:65)
at org.jboss.aop.instrument.MethodJoinPointGenerator$BaseClassGenerator.generate(MethodJoinPointGenerator.java:239)
at org.jboss.aop.instrument.MethodJoinPointGenerator.createJoinpointBaseClass(MethodJoinPointGenerator.java:172)
at org.jboss.aop.instrument.GeneratedAdvisorMethodExecutionTransformer.createJoinpointClass(GeneratedAdvisorMethodExecutionTransformer.java:95)
at org.jboss.aop.instrument.GeneratedAdvisorMethodExecutionTransformer.addJoinpoint(GeneratedAdvisorMethodExecutionTransformer.java:83)
at org.jboss.aop.instrument.GeneratedAdvisorMethodExecutionTransformer.addMethodInfoFieldToGenAdvisor(GeneratedAdvisorMethodExecutionTransformer.java:58)
at org.jboss.aop.instrument.GeneratedAdvisorMethodExecutionTransformer.transformMethod(GeneratedAdvisorMethodExecutionTransformer.java:304)
at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:146)
at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:744)
at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:119)
at org.jboss.aop.SuperClassesFirstWeavingStrategy.instrumentClass(SuperClassesFirstWeavingStrategy.java:202)
at org.jboss.aop.SuperClassesFirstWeavingStrategy.translate(SuperClassesFirstWeavingStrategy.java:69)
at org.jboss.aop.AspectManager.translate(AspectManager.java:1071)
at org.jboss.aop.AspectManager.transform(AspectManager.java:1015)
at org.jboss.aop.standalone.AOPTransformer.aspectTransform(AOPTransformer.java:87)
at org.jboss.aop.standalone.AOPTransformer.transform(AOPTransformer.java:75)
at sun.instrument.TransformerManager.transform(TransformerManager.java:169)
at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:365)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:63)
at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:572)
at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:532)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:530)
- locked <0xffffffff60aba990> (a org.jboss.classloader.spi.base.BaseClassLoader)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:507)
at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:134)
at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:452)
at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:251)
at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:150)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:265)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1119)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:798)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:441)
- locked <0xffffffff60aba990> (a org.jboss.classloader.spi.base.BaseClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
- locked <0xffffffff60aba990> (a org.jboss.classloader.spi.base.BaseClassLoader)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:63)
at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:572)
at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:532)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:530)
- locked <0xffffffff60aba990> (a org.jboss.classloader.spi.base.BaseClassLoader)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:507)
at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:134)
at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:452)
at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:251)
at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:150)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:265)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1119)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:798)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:441)
- locked <0xffffffff65eda3b0> (a org.jboss.classloader.spi.base.BaseClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
- locked <0xffffffff65eda3b0> (a org.jboss.classloader.spi.base.BaseClassLoader)
at org.jboss.resource.deployers.builder.ConnectionManagerBuilder.getCode(ConnectionManagerBuilder.java:245)
at org.jboss.resource.deployers.builder.AbstractBuilder.buildService(AbstractBuilder.java:54)
at org.jboss.resource.deployers.builder.AbstractBuilder.build(AbstractBuilder.java:65)
at org.jboss.resource.deployers.ManagedConnectionFactoryDeployer.deploy(ManagedConnectionFactoryDeployer.java:177)
at org.jboss.resource.deployers.ManagedConnectionFactoryDeployer.deploy(ManagedConnectionFactoryDeployer.java:52)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
"Thread-20":
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:437)
- waiting to lock <0xffffffff60aba990> (a org.jboss.classloader.spi.base.BaseClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.jboss.aop.asintegration.jboss5.ToClassInvoker.toClass(ToClassInvoker.java:88)
- locked <0xffffffff64f63d00> (a java.lang.Object)
at org.jboss.aop.classpool.jbosscl.JBossClDelegatingClassPool.toClass(JBossClDelegatingClassPool.java:81)
at javassist.CtClass.toClass(CtClass.java:1094)
at org.jboss.aop.instrument.TransformerCommon$ToClassAction$2.toClass(TransformerCommon.java:331)
at org.jboss.aop.instrument.TransformerCommon.toClass(TransformerCommon.java:139)
at org.jboss.aop.instrument.JoinPointGenerator.toClass(JoinPointGenerator.java:315)
at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:380)
at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:284)
at org.jboss.aop.instrument.JoinPointGenerator.access$300(JoinPointGenerator.java:76)
at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1729)
at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:249)
- locked <0xfffffffe7d0d0538> (a org.jboss.aop.instrument.MethodJoinPointGenerator)
at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1044)
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor$AuthenticationInterceptorAdvisor.invoke_N_5788773513025575775(AuthenticationInterceptor$AuthenticationInterceptorAdvisor.java)
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java)
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.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy247.invoke(Unknown Source)
at com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery.createDataSource(AppServerJDBCXARecovery.java:189)
at com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery.hasMoreResources(AppServerJDBCXARecovery.java:144)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:659)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:200)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:799)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:412)
Found 1 deadlock.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months