[JBoss JIRA] Issue Comment Edited: (MODCLUSTER-254) AS7-1718 CLONE - mod_cluster needs consistent naming
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl... ]
Jean-Frederic Clere edited comment on MODCLUSTER-254 at 9/5/11 10:05 AM:
-------------------------------------------------------------------------
mod_cluster : C module + project name (that is why it mod_cluster*.jar).
modcluster: AS7 subsystem
mod-cluster : prefix or suffix for the AS7 operations or attributes.
was (Author: jfclere):
mod_cluster : C module + project name
modcluster: AS7 subsystem
mod-cluster : prefix or suffix for the AS7 operations or attributes.
> AS7-1718 CLONE - mod_cluster needs consistent naming
> ----------------------------------------------------
>
> Key: MODCLUSTER-254
> URL: https://issues.jboss.org/browse/MODCLUSTER-254
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.1.3.Final
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Critical
>
> Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster.
> ---
> We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names.
> *project name = mod_cluster
> *console name = "Mod_cluster Status"
> *xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
> *xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
> *xs elements = mod-cluster (eg mod-cluster-config)
> *schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
> *jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
> I am not going to name the EAP5 components where names are significantly changed too.
> We need this madness to stop soon enough ;-(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Commented: (MODCLUSTER-254) AS7-1718 CLONE - mod_cluster needs consistent naming
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl... ]
Jean-Frederic Clere commented on MODCLUSTER-254:
------------------------------------------------
mod_cluster : C module + project name
modcluster: AS7 subsystem
mod-cluster : prefix or suffix for the AS7 operations or attributes.
> AS7-1718 CLONE - mod_cluster needs consistent naming
> ----------------------------------------------------
>
> Key: MODCLUSTER-254
> URL: https://issues.jboss.org/browse/MODCLUSTER-254
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.1.3.Final
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Critical
>
> Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster.
> ---
> We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names.
> *project name = mod_cluster
> *console name = "Mod_cluster Status"
> *xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
> *xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
> *xs elements = mod-cluster (eg mod-cluster-config)
> *schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
> *jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
> I am not going to name the EAP5 components where names are significantly changed too.
> We need this madness to stop soon enough ;-(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Updated: (MODCLUSTER-254) AS7-1718 CLONE - mod_cluster needs consistent naming
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-254:
--------------------------------------
Summary: AS7-1718 CLONE - mod_cluster needs consistent naming (was: CLONE - mod_cluster needs consistent naming)
Description:
Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster.
---
We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names.
*project name = mod_cluster
*console name = "Mod_cluster Status"
*xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
*xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
*xs elements = mod-cluster (eg mod-cluster-config)
*schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
*jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
I am not going to name the EAP5 components where names are significantly changed too.
We need this madness to stop soon enough ;-(
was:
We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names.
*project name = mod_cluster
*console name = "Mod_cluster Status"
*xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
*xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
*xs elements = mod-cluster (eg mod-cluster-config)
*schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
*jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
I am not going to name the EAP5 components where names are significantly changed too.
We need this madness to stop soon enough ;-(
> AS7-1718 CLONE - mod_cluster needs consistent naming
> ----------------------------------------------------
>
> Key: MODCLUSTER-254
> URL: https://issues.jboss.org/browse/MODCLUSTER-254
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.1.3.Final
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Critical
>
> Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster.
> ---
> We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names.
> *project name = mod_cluster
> *console name = "Mod_cluster Status"
> *xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
> *xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
> *xs elements = mod-cluster (eg mod-cluster-config)
> *schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
> *jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
> I am not going to name the EAP5 components where names are significantly changed too.
> We need this madness to stop soon enough ;-(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Moved: (MODCLUSTER-254) CLONE - mod_cluster needs consistent naming
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl... ]
Radoslav Husar moved AS7-1718 to MODCLUSTER-254:
------------------------------------------------
Project: mod_cluster (was: Application Server 7)
Key: MODCLUSTER-254 (was: AS7-1718)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: 1.1.3.Final
(was: 7.0.0.Final)
(was: 7.0.1.Final)
Component/s: (was: Clustering)
> CLONE - mod_cluster needs consistent naming
> -------------------------------------------
>
> Key: MODCLUSTER-254
> URL: https://issues.jboss.org/browse/MODCLUSTER-254
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.1.3.Final
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Critical
>
> We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names.
> *project name = mod_cluster
> *console name = "Mod_cluster Status"
> *xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
> *xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
> *xs elements = mod-cluster (eg mod-cluster-config)
> *schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
> *jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
> I am not going to name the EAP5 components where names are significantly changed too.
> We need this madness to stop soon enough ;-(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
Not able to configure mod_cluster with JBoss 6.0.0.M1
by Mohan Singh
Hi,
1.
I have gone through http://209.132.182.48/message/545331 link and followed
"To use 1.1.0.CR2, with a vanilla JBoss AS 6.0.0.Mx release, all you need to
do is replace the existing
$JBOSS_HOME/server/<profile>/deploy/mod_cluster.sar with the corresponding
sar from the mod_cluster release tarball. "
I have downloaded JBoss 6.0.0.M4 and replace mod_cluster.sar of JBoss
6.0.0.M1 with JBoss 6.0.0.M4 mod_cluster.sar
Now I am getting the below error
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "ModClusterListener" is missing the following dependencies:
Dependency "WebServer" (should be in state "Create", but is actually in
state "Configured")
Deployment "WebServer" is missing the following dependencies:
Dependency "ModClusterListener" (should be in state "Create", but is
actually in state "Configured")
Deployment "jboss.web.deployment:war=/ROOT" is missing the following
dependencies:
Dependency "jboss.web:service=WebServer" (should be in state "Create",
but is actually in state "Configured")
Deployment "jboss.web.deployment:war=/admin-console" is missing the
following dependencies: ....................
2.
I have also tried to deploy my application in JBoss 6.0.0.M4 but I am
getting the bleow error
Deployment
"vfs:///D:/Softwares/jboss-6.0.0.20100721-M4/server/default/deploy/MyApp.war
" is in error due to the following reason(s): java.lang.SecurityException:
class "org.apache.commons.logging.impl.Log4jFactory"'s signer information
does not match signer information of other classes in the same package
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersI
mpl.java:1228) [:2.2.0.Alpha6]
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployer
Impl.java:905) [:2.2.0.Alpha6]
at
org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkCom
plete(MainDeployerPlugin.java:87) [:6.0.0.20100721-M4]
at
org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllCo
mplete(ProfileDeployerPluginRegistry.java:118) [:0.1.0.Alpha1]
at
org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstra
p.start(BasicProfileServiceBootstrap.java:133) [:6.0.0.20100721-M4]
at
org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstra
p.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.20100721-M4]
at
org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(Abstract
Server.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at
org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(Abst
ractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Unknown Source) [:1.6.0_26]
My priority is to continue with
Deployment
"vfs:///D:/Softwares/jboss-6.0.0.20100721-M4/server/default/deploy/FirstGrou
pRailApps.war" is in error due to the following reason(s):
java.lang.SecurityException: class
"org.apache.commons.logging.impl.Log4jFactory"'s signer information does not
match signer information of other classes in the same package
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersI
mpl.java:1228) [:2.2.0.Alpha6]
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployer
Impl.java:905) [:2.2.0.Alpha6]
at
org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkCom
plete(MainDeployerPlugin.java:87) [:6.0.0.20100721-M4]
at
org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllCo
mplete(ProfileDeployerPluginRegistry.java:118) [:0.1.0.Alpha1]
at
org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstra
p.start(BasicProfileServiceBootstrap.java:133) [:6.0.0.20100721-M4]
at
org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstra
p.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.20100721-M4]
at
org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(Abstract
Server.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at
org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(Abst
ractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Unknown Source) [:1.6.0_26]
I am new to JBOSS
Please help me
Thanks
12 years, 7 months