[JBoss JIRA] (WFLY-1278) Upgrade HornetQ to 2.3.0.Final
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-1278:
---------------------------------
Summary: Upgrade HornetQ to 2.3.0.Final
Key: WFLY-1278
URL: https://issues.jboss.org/browse/WFLY-1278
Project: WildFly
Issue Type: Component Upgrade
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.Alpha1
HornetQ 2.3.0.Final depends on Netty 3.6.2.Final which is the version in WildFly (no need to also upgrade Netty)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (WFLY-886) JBAS014884: No operation named 'composite' exists at address
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-886?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on WFLY-886:
----------------------------------
Managed to reproduce problem with whole script that teiid uses.
https://github.com/teiid/teiid/blob/master/build/kits/jboss-as7/bin/scrip...
when this script is used it breaks, otherwise command on itself works.
Further investigation revealed that it only breaks after
/server-group=main-server-group:write-attribute(name=profile, value=ha)
/server-group=main-server-group:write-attribute(name=socket-binding-group, value=ha-sockets)
operations are called.
and problem is gone if this two operations are put at end of the script (before :restart-servers)
which is also proper way to do it, as in, first configure profile, then activate it.
> JBAS014884: No operation named 'composite' exists at address
> ------------------------------------------------------------
>
> Key: WFLY-886
> URL: https://issues.jboss.org/browse/WFLY-886
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Environment: RHEL 6, JDK 1.7
> Reporter: Van Halbert
> Assignee: Tomaz Cerar
>
> I'm using EAP 6.1 ER5, and trying to execute the following using CLI:
>
> /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default)
> /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}])
> but I get the message:
> …
> "failure-description" => "JBAS014884: No operation named 'composite' exists at address [
> …
> (see forum for full discussion)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (WFLY-886) JBAS014884: No operation named 'composite' exists at address
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-886?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar edited comment on WFLY-886 at 4/24/13 9:28 AM:
-----------------------------------------------------------
I cannot reproduce this problem.
Tested with latest WildFly master, EAP 6.1.0.Beta(ER4) and EAP6.1 ER5
was (Author: ctomc):
I cannot reproduce this problem.
Tested with latest WildFly master, EAP 6.1.0.Beta(ER5) and EAP6.1 ER5
> JBAS014884: No operation named 'composite' exists at address
> ------------------------------------------------------------
>
> Key: WFLY-886
> URL: https://issues.jboss.org/browse/WFLY-886
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Environment: RHEL 6, JDK 1.7
> Reporter: Van Halbert
> Assignee: Tomaz Cerar
>
> I'm using EAP 6.1 ER5, and trying to execute the following using CLI:
>
> /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default)
> /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}])
> but I get the message:
> …
> "failure-description" => "JBAS014884: No operation named 'composite' exists at address [
> …
> (see forum for full discussion)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (WFLY-886) JBAS014884: No operation named 'composite' exists at address
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-886?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on WFLY-886:
----------------------------------
I cannot reproduce this problem.
Tested with latest WildFly master, EAP 6.1.0.Beta(ER5) and EAP6.1 ER5
> JBAS014884: No operation named 'composite' exists at address
> ------------------------------------------------------------
>
> Key: WFLY-886
> URL: https://issues.jboss.org/browse/WFLY-886
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Environment: RHEL 6, JDK 1.7
> Reporter: Van Halbert
> Assignee: Tomaz Cerar
>
> I'm using EAP 6.1 ER5, and trying to execute the following using CLI:
>
> /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default)
> /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}])
> but I get the message:
> …
> "failure-description" => "JBAS014884: No operation named 'composite' exists at address [
> …
> (see forum for full discussion)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months