March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3064) Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3064: -------------------------------------- Summary: Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case. Key: WFLY-3064 URL: https://issues.jboss.org/browse/WFLY-3064 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.CR1 A new test case was added under WFLY-3063 that demonstrates the correct way to do this so now remove the original way that depended on internal APIs. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode

by John Patton (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] John Patton commented on WFLY-3051: ----------------------------------- Stuck on this, as well. Thanks for looking into it. > JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3063) Duplicate existing test that replicates ejb-security-interceptors quickstart so we can use new API

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3063: -------------------------------------- Summary: Duplicate existing test that replicates ejb-security-interceptors quickstart so we can use new API Key: WFLY-3063 URL: https://issues.jboss.org/browse/WFLY-3063 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.1.Final -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3051: ---------------------------------------- I have scheduled this issue so that I can investigate it further, at this point I have no further information. > JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode

by Rituraj Sinha (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Rituraj Sinha commented on WFLY-3051: ------------------------------------- Hi Darran, is there any progress related to the issue ...? Thanks > JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-444) NOT conditional element is broken when used with subnetworks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-444: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1072462|https://bugzilla.redhat.com/show_bug.cgi?id=1072462] from ASSIGNED to MODIFIED > NOT conditional element is broken when used with subnetworks > ------------------------------------------------------------ > > Key: DROOLS-444 > URL: https://issues.jboss.org/browse/DROOLS-444 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3062) Update to HAL 2.2.0.Beta3

by Harald Pehl (JIRA)

Harald Pehl created WFLY-3062: --------------------------------- Summary: Update to HAL 2.2.0.Beta3 Key: WFLY-3062 URL: https://issues.jboss.org/browse/WFLY-3062 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Priority: Blocker Fix For: 8.0.1.Final -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-444) NOT conditional element is broken when used with subnetworks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-444: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1072462 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1072462, https://bugzilla.redhat.com/show_bug.cgi?id=1072463) > NOT conditional element is broken when used with subnetworks > ------------------------------------------------------------ > > Key: DROOLS-444 > URL: https://issues.jboss.org/browse/DROOLS-444 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-444) NOT conditional element is broken when used with subnetworks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-444: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1072462, https://bugzilla.redhat.com/show_bug.cgi?id=1072463 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1072462) > NOT conditional element is broken when used with subnetworks > ------------------------------------------------------------ > > Key: DROOLS-444 > URL: https://issues.jboss.org/browse/DROOLS-444 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-444) NOT conditional element is broken when used with subnetworks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-444: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1072462|https://bugzilla.redhat.com/show_bug.cgi?id=1072462] from NEW to ASSIGNED > NOT conditional element is broken when used with subnetworks > ------------------------------------------------------------ > > Key: DROOLS-444 > URL: https://issues.jboss.org/browse/DROOLS-444 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- 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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014