[JBoss JIRA] Created: (JBAS-5377) Manage clustered caches using a JBC CacheManager
by Brian Stansberry (JIRA)
Manage clustered caches using a JBC CacheManager
------------------------------------------------
Key: JBAS-5377
URL: http://jira.jboss.com/jira/browse/JBAS-5377
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
Deploy an impl of the JBC CacheManager interface for use as a central source for JBC instances.
CacheManager serves as a centralized registry/factory for a named set of caches. The standalone Hibernate 3.3 integration with JBC expects to find caches using a CacheManager, so we'll deploy one in the AS so the Hibernate usage inside the AS can use standard Hibernate classes.
I'll switch the other AS uses of JBC to use the std CacheManager as well.
This JIRA is a container for the smaller tasks related to this change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (JBAS-4734) Flush failures on MuxChannel connection
by Brian Stansberry (JIRA)
Flush failures on MuxChannel connection
---------------------------------------
Key: JBAS-4734
URL: http://jira.jboss.com/jira/browse/JBAS-4734
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Vladimir Blagojevic
Fix For: JBossAS-5.0.0.CR1
Getting WARN messages about startFlush failures when multiplexed channels connect:
2007-09-18 03:04:02,936 WARN [org.jboss.ha.framework.server.JChannelFactory] Flush failed at 127.0.0.1:51382 DefaultPartition-SFSBCache
Adrian took a thread dump before one of those was logged and saw:
"main" prio=1 tid=0x80cbdfa0 nid=0x2847 in Object.wait() [0x804d2000..0x804d5130]
at java.lang.Object.wait(Native Method)
- waiting on <0xaf1e6838> (a org.jgroups.util.Promise)
at org.jgroups.util.Promise.doWait(Promise.java:104)
at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:60)
at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:28)
- locked <0xaf1e6838> (a org.jgroups.util.Promise)
at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:207)
at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229)
at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229)
at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:263)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:339)
at org.jgroups.JChannel.downcall(JChannel.java:1240)
at org.jgroups.JChannel.startFlush(JChannel.java:1504)
at org.jgroups.JChannelFactory.connect(JChannelFactory.java:364)
- locked <0xade09c70> (a org.jgroups.JChannelFactory$Entry)
I'll attach a server.log file from a hudson run that shows a bunch of these. Look at lines 4153-4193 for the first one, where the underlying JChannel connection happens.
I'm not seeing these on my local system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Updated: (JBAS-2282) JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2282?page=all ]
Dimitris Andreadis updated JBAS-2282:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
(was: JBossAS-5.0.0.CR1)
Pushing non-critical issues to the next CR2. If you think they are critical for CR1, please re-schedule them.
> JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs
> ---------------------------------------------------------------------------------
>
> Key: JBAS-2282
> URL: http://jira.jboss.com/jira/browse/JBAS-2282
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XML services
> Affects Versions: JBossAS-4.0.3RC2
> Reporter: Scott M Stark
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-5.0.0.CR2
>
> Attachments: jboss-entity-resolver.zip
>
>
> The org.jboss.util.xml.JBossEntityResolver is not dealing with systemIDs that are valid non-file URLs. For example, this xml fragment from a testcase which uses the jboss resource URL:
> <?xml version="1.0" encoding="UTF-8"?>
> <!-- $Id: config.xml,v 1.1 2005/07/31 23:13:44 starksm Exp $ -->
> <jaas:policy
> xsi:schemaLocation="urn:jboss:security-config resource:security-config_4_1.xsd"
> xmlns:jaas="urn:jboss:security-config"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >
> does map to a valid URL which can be loaded, but the parsing of this URL by the getLocalEntityName ends up throwing away the full path info to produce a resource name of schema/security-config_4_1.xsd. This would work inside the jboss server provided the security-config_4_1.xsd is bundled into a classpath location following the location conventions expected by the JBossEntityResolver, but does not work in the testsuite where this is not the case, and would not work for user defined schemas located elsewhere. It would seem we should try to load the schema from systemIDs that are valid URLs before defaulting to the jboss specific logic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Updated: (JBAS-2577) isolating Hibernate as an internal impl detail
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2577?page=all ]
Dimitris Andreadis updated JBAS-2577:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
(was: JBossAS-5.0.0.CR1)
Pushing non-critical issues to the next CR2. If you think they are critical for CR1, please re-schedule them.
> isolating Hibernate as an internal impl detail
> ----------------------------------------------
>
> Key: JBAS-2577
> URL: http://jira.jboss.com/jira/browse/JBAS-2577
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Hibernate service
> Reporter: Steve Ebersole
> Assigned To: Steve Ebersole
> Fix For: JBossAS-5.0.0.CR2
>
>
> Currently Hibernate is used within JBossAS for EJB3 as well as the Hibernate-intg code, with plans/discussions to expand usage to JBoss Messaging and JBossMQ. This represents Hibernate usage as an internal implementation detail
> Additionally, Hibernate is also used within JBossAS by user applications. This represents Hibernate usage as a deployment detail.
> Currently, the two are not isolated from each other. Thus, a user attempting to bundle Hibernate with their application is actually using the Hibernate bundled with EJB3 and/or the integration code. This can cause problems when we have internal usage and external usage needing to rely on different releases of Hibernate.
> Need to devise a scheme to isolate the internal usages of Hibernate. Two potential solutions:
> 1) source-level import and package renaming of Hibernate code (i.e. org.jboss.hibernate)
> 2) some form of classloader isolation
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Updated: (JBAS-1151) deadlock during cluster failover
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1151?page=all ]
Dimitris Andreadis updated JBAS-1151:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
(was: JBossAS-5.0.0.CR1)
Pushing non-critical issues to the next CR2. If you think they are critical for CR1, please re-schedule them.
> deadlock during cluster failover
> --------------------------------
>
> Key: JBAS-1151
> URL: http://jira.jboss.com/jira/browse/JBAS-1151
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: JBossAS-3.2.6 Final
> Reporter: SourceForge User
> Assigned To: Brian Stansberry
> Fix For: JBossAS-5.0.0.CR2
>
>
> SourceForge Submitter: eiman .
> We are running JBoss 3.2.5 on jdk 1.4.2 running on
> redhat linux.
> In our environment we are running a two node cluster
> (node A and node B). We restarted node A and then
> within a minute restarted node B. Upon doing that we
> found a deadlock in node B:
>
> Java stack information for the threads listed above:
> ===================================================
> "MessageDispatcher up processing thread":
> at
> org.jboss.system.ServiceController.create(ServiceController.java:229)
> - waiting to lock <0x56505440> (a
> org.jboss.system.ServiceController)
> 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:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy33.create(Unknown Source)
> at
> org.jboss.web.AbstractWebContainer.create(AbstractWebContainer.java:291)
> at
> org.jboss.deployment.MainDeployer.create(MainDeployer.java:790)
> at
> org.jboss.deployment.MainDeployer.create(MainDeployer.java:782)
> at
> org.jboss.deployment.MainDeployer.create(MainDeployer.java:782)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:644)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
> 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:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.ha.singleton.HASingletonController.invokeSingletonMBeanMethod(HASingletonController.java:114)
> at
> org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:63)
> at
> org.jboss.ha.singleton.HASingletonSupport.makeThisNodeMaster(HASingletonSupport.java:137)
> at
> org.jboss.ha.singleton.HASingletonSupport.partitionTopologyChanged(HASingletonSupport.java:118)
> at
> org.jboss.ha.jmx.HAServiceMBeanSupport$1.replicantsChanged(HAServiceMBeanSupport.java:197)
> at
> org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:701)
> - locked <0x56609350> (a java.util.HashMap)
> at
> org.jboss.ha.framework.server.DistributedReplicantManagerImpl._remove(DistributedReplicantManagerImpl.java:512)
> 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:324)
> at
> org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236)
> at
> org.jboss.ha.framework.server.HAPartitionImpl.handle(HAPartitionImpl.java:826)
> at
> org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615)
> at
> org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512)
> at
> org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326)
> at
> org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722)
> at
> org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554)
> at
> org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691)
> at java.lang.Thread.run(Thread.java:534)
> "main":
> at
> org.jboss.ha.framework.server.DistributedReplicantManagerImpl.registerListener(DistributedReplicantManagerImpl.java:398)
> - waiting to lock <0x56609350> (a java.util.HashMap)
> at
> org.jboss.ha.framework.server.HATarget.updateHAPartition(HATarget.java:130)
> at
> org.jboss.ha.framework.server.HATarget.<init>(HATarget.java:58)
> at
> org.jboss.proxy.ejb.ProxyFactoryHA.setupInvokers(ProxyFactoryHA.java:102)
> at
> org.jboss.proxy.ejb.ProxyFactory.start(ProxyFactory.java:186)
> at
> org.jboss.proxy.ejb.ProxyFactoryHA.start(ProxyFactoryHA.java:85)
> at
> org.jboss.ejb.StatelessSessionContainer.startService(StatelessSessionContainer.java:205)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
> at $Proxy17.start(Unknown Source)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:367)
> - locked <0x56505440> (a
> org.jboss.system.ServiceController)
> at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy48.start(Unknown Source)
> at
> org.jboss.ejb.EjbModule.startService(EjbModule.java:367)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
> at $Proxy17.start(Unknown Source)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:367)
> - locked <0x56505440> (a
> org.jboss.system.ServiceController)
> at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy14.start(Unknown Source)
> at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:570)
> - locked <0x56679000> (a org.jboss.ejb.EJBDeployer)
> at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
> at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:828)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
> at
> sun.reflect.GeneratedMethodAccessor36.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy7.deploy(Unknown Source)
> at
> org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
> at
> org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
> - locked <0x56505080> (a
> org.jboss.deployment.scanner.URLDeploymentScanner)
> at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
> at
> org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
> - locked <0x565044c0> (a
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
> at $Proxy0.start(Unknown Source)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:367)
> - locked <0x56505440> (a
> org.jboss.system.ServiceController)
> at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown
> Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy4.start(Unknown Source)
> at
> org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
> at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
> 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:324)
> at
> org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
> at
> org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
> at
> org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy5.deploy(Unknown Source)
> at
> org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
> at
> org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
> at org.jboss.Main.boot(Main.java:145)
> at org.jboss.Main$1.run(Main.java:399)
> at java.lang.Thread.run(Thread.java:534)
> Found 1 deadlock.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months