1:32 p.m.
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
2:42 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
[
https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on JBAS-8164:
------------------------------------
If we don't want to increase our image size (all + production share those small jars),
we could also move the related clustering jars from server/all/lib to common/lib.
Solving this jira might also help resolve an (unexplained) ClassCastException problem we
hit on the Session_Ownership branch.
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
4 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
[
https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow updated JBAS-8164:
-------------------------------
Attachment: JBAS-8164.patch
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
7:50 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
[
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
8:22 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
[
https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on JBAS-8164:
------------------------------------
The workaround for #1 (mod_cluster is noted above).
The workaround for #2 deployers/clustering-deployer-jboss-beans.xml, is to comment out the
contents of clustering-deployer-jboss-beans.xml which might cause ugly deployment error
messages. Email from Brian on the subjectl:
"
My guess is those deployers result in better error messages when people
try to deploy clustered EJBs in default. Instead of getting CNFEs, those
deployers introduce a dependency on HAPartition. That dependency can't
be resolved, so the user gets a nice missing dependency error message
instead of an obscure CNFE.
" Or something to that effect. I believe that commenting out the current beans and
adding mock replacements if needed to handle giving proper deployment error messages would
work.
3. Didn't look into the ejb3 deployer error. That work needs to happen if we decide
to apply the patch attached to this jira. I'll leave this assigned tome but not for
an AS release.
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
8:24 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
[
https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow updated JBAS-8164:
-------------------------------
Fix Version/s: (was: 6.0.0.Final)
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
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
1:27 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib
[
https://issues.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin....
]
Jason Greene reopened JBAS-8164:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all
unscheduled AS6 issues that are a year or less old. This will make it easier community
members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.
Move jboss-ha-server-* jars from common/lib to server/all/lib
-------------------------------------------------------------
Key: JBAS-8164
URL: https://issues.jboss.org/browse/JBAS-8164
Project: Legacy JBoss Application Server 6
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: No Release
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5491
days inactive
5777
days old
6 comments
3 participants
participants (3)
-
Jason Greene (JIRA) -
Paul Ferraro (JIRA)
-
Scott Marlow (JIRA)