March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3098) Complete Undertow to JAAS Digest Integration

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3098: -------------------------------------- Summary: Complete Undertow to JAAS Digest Integration Key: WFLY-3098 URL: https://issues.jboss.org/browse/WFLY-3098 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Security, Web (Undertow) 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3051: ---------------------------------------- Hello [~rituraj], at this point the forum topic you have started is going to be the best place to discuss this. > http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Priority: Critical > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3094) Warn if there is no resource bound for address-settings expiry and dead-letter addresses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3094: ----------------------------------------------- Jeff Mesnil <jmesnil(a)redhat.com> changed the Status of [bug 1014099|https://bugzilla.redhat.com/show_bug.cgi?id=1014099] from NEW to POST > Warn if there is no resource bound for address-settings expiry and dead-letter addresses > ---------------------------------------------------------------------------------------- > > Key: WFLY-3094 > URL: https://issues.jboss.org/browse/WFLY-3094 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > > Warns the user if a address-setting has defined an expiry-address or a dead-letter-address with no queue bound for them as this will result in unintended message loss. > WildFly default full configuration specifies an expiry address (jms.queue.ExpiryQueue) and dead-letter-addres (jms.queue.DLQ) for the # address settings (i.e. matching all addresses). > To have a consistent configuration, we must also define 2 queues that will be bound to these settings. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-364) ClasspathKieProject fails vfs: path for jar deployments and exploded ear

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-364: ------------------------------------------------ Ivo Bek <ibek(a)redhat.com> changed the Status of [bug 1058254|https://bugzilla.redhat.com/show_bug.cgi?id=1058254] from ON_QA to VERIFIED > ClasspathKieProject fails vfs: path for jar deployments and exploded ear > ------------------------------------------------------------------------ > > Key: DROOLS-364 > URL: https://issues.jboss.org/browse/DROOLS-364 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: JBoss AS 7.1.1 > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Mario Fusco > Fix For: 6.1.0.Beta1 > > Attachments: jbossas-deploy-reproducer.zip, windows-jboss-as-deploy-server.log > > > Drools is not able to load kmodule.xml from an exploded ear. > 17:24:45,116 WARN Unable to load pom.properties tried recursing down from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent > null > 17:24:45,116 ERROR Unable to build index of kmodule.xml url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml > null -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3069) slaves cannot reconnect to a restarted master if RBAC is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3069: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1072915|https://bugzilla.redhat.com/show_bug.cgi?id=1072915] from POST to MODIFIED > slaves cannot reconnect to a restarted master if RBAC is enabled > ---------------------------------------------------------------- > > Key: WFLY-3069 > URL: https://issues.jboss.org/browse/WFLY-3069 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 8.0.1.Final > > > Enable RBAC in an Wilfly domain setup. "reload --host=master" and the slaves will no longer be connected to the master -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3078) directory-grouping configuration is not getting persisted via CLI when no servers defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3078?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3078: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1073715|https://bugzilla.redhat.com/show_bug.cgi?id=1073715] from POST to MODIFIED > directory-grouping configuration is not getting persisted via CLI when no servers defined > ----------------------------------------------------------------------------------------- > > Key: WFLY-3078 > URL: https://issues.jboss.org/browse/WFLY-3078 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Environment: All Operating System > Reporter: Jay Kumar SenSharma > Assignee: Emanuel Muckenhuber > Fix For: 8.0.1.Final > > > - If none of the servers are defined in "host.xml" (means <servers></servers> empty tag is present) and if the user tries to run the following CLI command to change the "directory-grouping" to "by-type" then the value is not persisted in the configuration file (host.xml) and the <servers></servers> tag is also removed from the host.xml > {code} > /host=master/:write-attribute(name=directory-grouping,value=by-type) > {code} > - The value of "directory-grouping" is stored "in memory" so this change does not survive the host restart. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management

by Rituraj Sinha (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Rituraj Sinha commented on WFLY-3051: ------------------------------------- Hi Darran, can you give us some idea how can we proceed with it ... Thanks Rituraj > http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Priority: Critical > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3060) Rare KrbException: Request is a replay issue in negotiation tests

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3060?page=com.atlassian.jira.plugin.... ] Dominik Pospisil closed WFLY-3060. ---------------------------------- Resolution: Done > Rare KrbException: Request is a replay issue in negotiation tests > ----------------------------------------------------------------- > > Key: WFLY-3060 > URL: https://issues.jboss.org/browse/WFLY-3060 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Final > Reporter: Dominik Pospisil > Assignee: Ondrej Zizka > > The failures happend while sending second TGS-REQ ticket from client to kerberos KDC server. > The cause seems to be a limitation of ApacheDS kerberos server used in the test case. The ApacheDS employs simple replay detection mechanism based on in-memory ticket cache service. The cache stores client and server credentials and ticket timestamp. Specificaly, the cache do not store ticket content. > During GSS SecContext establishment, there are 2 TGS-REQ tickets sent from the client (sun.security.jgss.krb5.GSSContextSpi). First to acquire service credentials ticket and second to get SecContext ticket. The second ticket is being send immediatelly after the fisrt one. If the second (valid) ticket is sent with the same timestamp as the first one, the ApacheDS treats the second one as a false positive and throw Request is a replay kerberos exception. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1254) Fix NoRouteToHost exception in UDP._send()

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1254?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1254: -------------------------------- The code for catching IOExceptions has been removed in JGRP-1765 as we're now using the DatagramSocket to send multicasts > Fix NoRouteToHost exception in UDP._send() > ------------------------------------------ > > Key: JGRP-1254 > URL: https://issues.jboss.org/browse/JGRP-1254 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 2.6.18, 2.11.1, 2.12 > > > We did the same test with Weblogic and it is able to reconnect after a network failure. > I had a quick look at the code of JGroups and I think that we can override this limit by a minor modification. It is not necessary to recreate a socket in case of the raise of an NoRouteToHostException, we can bind the socket to the interface. I've modified the code to catch the NoRouteToHostException and now my cluster works well and JBoss and reconnect properly. > I've modified the _send method of UDP class like this : > org.jgroups.protocols.UDP._send : > private void _send(InetAddress dest, int port, boolean mcast, byte[] data, int offset, int length) throws Exception { > DatagramPacket packet=new DatagramPacket(data, offset, length, dest, port); > try { > if(mcast) { > if(mcast_send_sockets != null) { > MulticastSocket s; > for(int i=0; i < mcast_send_sockets.length; i++) { > s=mcast_send_sockets[i]; > try { > s.send(packet); > } > // solve reconnection issue with Windows > catch(NoRouteToHostException e){ > log.warn(e.getMessage() +", reset interface"); > s.setInterface(s.getInterface()); > } > catch(Exception e) { > log.error("failed sending packet on socket " + s); > } > } > } > else { // DEFAULT path > if(mcast_sock != null) { > try { > mcast_sock.send(packet); > } > // solve reconnection issue with Windows > catch(NoRouteToHostException e){ > log.warn(e.getMessage() +", reset interface"); > mcast_sock.setInterface(mcast_sock.getInterface()); > } > } > } > } > else { > if(sock != null) > sock.send(packet); > } > } > catch(Exception ex) { > throw new Exception("dest=" + dest + ":" + port + " (" + length + " bytes)", ex); > } > } -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3097) Allow user configuration of omitted log files

by James Livingston (JIRA)

James Livingston created WFLY-3097: -------------------------------------- Summary: Allow user configuration of omitted log files Key: WFLY-3097 URL: https://issues.jboss.org/browse/WFLY-3097 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JDR Affects Versions: 8.0.0.Final Reporter: James Livingston Assignee: Jesse Jaggars AS7Plugin gathers all *.log files and does not currently provide a way of omitting them. It would be useful to be able to provide a list that were skipped, if they contain sensitive application information. -- 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, 4 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