[
https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on JBAS-8164:
------------------------------------
http://pastebin.com/FuDQrh6u contains the boot.log that results when attempting to boot
the default profile. There appears to be 3 HA references from default:
1. mod_cluster
The workaround for mod_cluster is to comment out the HAModClusterService
bean in mod_cluster-jboss-beans.xml. It must not be enough to be marked
"on demand", the classes are still loaded it seems.
2. deployers/clustering-deployer-jboss-beans.xml reference to
org.jboss.ha.framework.server.deployers.DefaultHAPartitionDependencyCreator. workaround
unknown at this point.
3. ejb3 deployer seems to reference DistributedReplicantManager$ReplicantListener.
Workaround unknown at this point.
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
Attachments: JBAS-8164.patch
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