March 2014 - jboss-jira - Jboss List Archives

[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: ------------------------------------- I have created a seperate discussion for it as well.... https://community.jboss.org/message/861415#861415 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-3007) Ipv6 addresses may not be canonized properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3007?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3007: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1067348|https://bugzilla.redhat.com/show_bug.cgi?id=1067348] from POST to MODIFIED > Ipv6 addresses may not be canonized properly > -------------------------------------------- > > Key: WFLY-3007 > URL: https://issues.jboss.org/browse/WFLY-3007 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > On an ipv6 environment we may obtain IP addresses that are not properly canonized which may lead to strange issue with http proxies since the JDK ProxySelector relies on char per char matching. > All call to InetAddress.getHostName() may produce such an uncanonized address. -- 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-3077) Convert command line IPv6 URL literals to address literals

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3077?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3077: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1064771|https://bugzilla.redhat.com/show_bug.cgi?id=1064771] from POST to MODIFIED > Convert command line IPv6 URL literals to address literals > ---------------------------------------------------------- > > Key: WFLY-3077 > URL: https://issues.jboss.org/browse/WFLY-3077 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 8.0.1.Final > > > When people provide URL-style values like [::1] for command line args like -b, convert them to address values (i.e. strip the enclosing brackets.) -- 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] (LOGMGR-104) SyslogHandler doesn't handle multi-byte characters correctly

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-104?page=com.atlassian.jira.plugin... ] David Lloyd commented on LOGMGR-104: ------------------------------------ I'm thinking the issue isn't multi-byte characters, it's surrogate pairs. > SyslogHandler doesn't handle multi-byte characters correctly > ------------------------------------------------------------ > > Key: LOGMGR-104 > URL: https://issues.jboss.org/browse/LOGMGR-104 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 1.5.2.Final > Environment: - WildFly 8.0.0.Final > - Oracle JDK7u51 > - OS X 10.9.2 > Reporter: Kyle Shanahan > Assignee: David Lloyd > > SyslogHandler doesn't handle multi-byte characters correctly. > I tried to log multi-byte message with both of org.jboss.logmanager.handlers.SyslogHandler and org.apache.log4j.net.SyslogAppender for same message, only SyslogHandler output were corrupted. > Step to reproduce (It might need to define -Dfile.encoding=UTF-8 in _JAVA_OPTIONS): > 1. define a facility local1 at localhost and make syslog accept UDP packets. > 2. define a logger: > {noformat} > /subsystem=logging/logger=utf8mb4log:add(level=INFO) > {noformat} > 3. define a SyslogHandler: > {noformat} > /subsystem=logging/custom-handler=TEST_SH:add(class="org.jboss.logmanager.handlers.SyslogHandler", module="org.jboss.logmanager", formatter="SyslogHandler: %s%e", level=INFO, properties={serverHostname="localhost:514", facility="LOCAL_USE_1", truncate=false, maxLength=1024, syslogType="RFC3164" }) > /subsystem=logging/logger=utf8mb4log:assign-handler(name=TEST_SH) > {noformat} > 4. define a SyslogAppender: > {noformat} > /subsystem=logging/custom-handler=TEST_LOG4J:add(class="org.apache.log4j.net.SyslogAppender", module="org.apache.log4j", formatter="log4j: %s%e", level=INFO, properties={syslogHost="localhost:514", facility="local1"}) > /subsystem=logging/logger=utf8mb4log:assign-handler(name=TEST_LOG4J) > {noformat} > 5. get and deploy example project at https://github.com/lbtc-xxx/utf8mb4log > 6. Access the servlet http://localhost:8080/utf8mb4log/ > And you will get like this: (I can't put 4 byte UTF-8 characters here... because database error occured): > {noformat} > Mar 8 17:29:09 UNKNOWN_HOSTNAME java[9896]: SyslogHandler: ???????????? > {noformat} > I would send a pull request later. -- 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-3093) Undertow doesn't show the correct error page (401)

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-3093?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-3093: ------------------------------------------ To reproduce: 1) Deploy a web app with BASIC authentication 2) Invoke a protected page in a webbrowser 3) Ignore the browser's dialog box for BASIC authentication 4) The page with "401 - Unauthorized" appears. > Undertow doesn't show the correct error page (401) > -------------------------------------------------- > > Key: WFLY-3093 > URL: https://issues.jboss.org/browse/WFLY-3093 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > > I'm using the WildFly snapshot from last Thursday with Undertow 1.0.1. > When I try to invoke a protected web page, I'm getting an almost blank web page with just the contents "401 - Unauthorized". > However, in WEB-INF/web.xml I'm having this declaration: > {code} > <error-page> > <error-code>401</error-code> > <location>/rf/error/accessDenied.jsf</location> > </error-page> > {code} -- 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-3093) Undertow doesn't show the correct error page (401)

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-3093: ---------------------------------------- Summary: Undertow doesn't show the correct error page (401) Key: WFLY-3093 URL: https://issues.jboss.org/browse/WFLY-3093 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Undertow) Affects Versions: 8.0.0.Final Reporter: Juergen Zimmermann Assignee: Stuart Douglas I'm using the WildFly snapshot from last Thursday with Undertow 1.0.1. When I try to invoke a protected web page, I'm getting an almost blank web page with just the contents "401 - Unauthorized". However, in WEB-INF/web.xml I'm having this declaration: {code} <error-page> <error-code>401</error-code> <location>/rf/error/accessDenied.jsf</location> </error-page> {code} -- 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-3092) ServerUpdateResultHandler does nothing

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3092: -------------------------------------- Summary: ServerUpdateResultHandler does nothing Key: WFLY-3092 URL: https://issues.jboss.org/browse/WFLY-3092 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.1.Final The domain op rollout logic's AbstractServerUpdateTask.ServerUpdateResultHandler interface is serving no purpose and should be removed. It's cruft left from earlier implementations. The only impl stores data in a map that never gets read. -- 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-3091) Cancellation of management ops does not properly propagate to server update tasks

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3091: -------------------------------------- Summary: Cancellation of management ops does not properly propagate to server update tasks Key: WFLY-3091 URL: https://issues.jboss.org/browse/WFLY-3091 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.1.Final When an op is cancelled on a managed domain after the domain rollout has begun, the server update tasks are not properly cancelled / cleaned up. -- 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-3088) Cannot Inject Validator using @Inject

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3088?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-3088: --------------------------------------- Please attach the server.log. Also, it would be great if you could attach the deployments that would allow us to replicate the issue. > Cannot Inject Validator using @Inject > ------------------------------------- > > Key: WFLY-3088 > URL: https://issues.jboss.org/browse/WFLY-3088 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Final > Reporter: Sat B > Assignee: Eduardo Martins > > I have a very simple bean and I am trying to inject the Validator using the @Inject annotation. But I am ending up getting a null when I try to use the Validator. I have the beans.xml defined to bean-discovery-mode="all". Below is the code > -------- > import javax.inject.Inject; > import javax.validation.ConstraintViolation; > import javax.validation.Validation; > import javax.validation.Validator; > import javax.validation.ValidatorFactory; > import javax.validation.constraints.*; > import java.util.Map; > import java.util.Set; > public class SimpleCommand { > @Inject > private Validator validator; > > @Email > private String email; > > public SimpleCommand(){ > } > public SimpleCommand(Map<String, String[]> params){ > this.email = params.get("email")!=null ? params.get("email")[0] : null; > } > public void validate(){ > //USING VALIDATOR THAT IS INJECTED IS NULL HERE > //USING THE BELOW METHOD WORKS > ValidatorFactory factory = Validation.buildDefaultValidatorFactory(); > Validator validator1 = factory.getValidator(); > Set<ConstraintViolation<SimpleCommand>> contstraintViolations = validator1.validate(this); //USING INJECTED VALIDATOR WILL THROW NULL POINTER EXCEPTION > for (ConstraintViolation<SimpleCommand> violation : contstraintViolations){ > System.out.println(violation.getMessage()); > } > } > } > -------- > Then, from a JAX-RS controller, I call this validator > ------ > SimpleCommand cmd = new SimpleCommand(req.getParameterMap()); > cmd.validate(); > ----- -- 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-3088) Cannot Inject Validator using @Inject

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3088?page=com.atlassian.jira.plugin.... ] Eduardo Martins reassigned WFLY-3088: ------------------------------------- Assignee: Eduardo Martins (was: Stuart Douglas) > Cannot Inject Validator using @Inject > ------------------------------------- > > Key: WFLY-3088 > URL: https://issues.jboss.org/browse/WFLY-3088 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Final > Reporter: Sat B > Assignee: Eduardo Martins > > I have a very simple bean and I am trying to inject the Validator using the @Inject annotation. But I am ending up getting a null when I try to use the Validator. I have the beans.xml defined to bean-discovery-mode="all". Below is the code > -------- > import javax.inject.Inject; > import javax.validation.ConstraintViolation; > import javax.validation.Validation; > import javax.validation.Validator; > import javax.validation.ValidatorFactory; > import javax.validation.constraints.*; > import java.util.Map; > import java.util.Set; > public class SimpleCommand { > @Inject > private Validator validator; > > @Email > private String email; > > public SimpleCommand(){ > } > public SimpleCommand(Map<String, String[]> params){ > this.email = params.get("email")!=null ? params.get("email")[0] : null; > } > public void validate(){ > //USING VALIDATOR THAT IS INJECTED IS NULL HERE > //USING THE BELOW METHOD WORKS > ValidatorFactory factory = Validation.buildDefaultValidatorFactory(); > Validator validator1 = factory.getValidator(); > Set<ConstraintViolation<SimpleCommand>> contstraintViolations = validator1.validate(this); //USING INJECTED VALIDATOR WILL THROW NULL POINTER EXCEPTION > for (ConstraintViolation<SimpleCommand> violation : contstraintViolations){ > System.out.println(violation.getMessage()); > } > } > } > -------- > Then, from a JAX-RS controller, I call this validator > ------ > SimpleCommand cmd = new SimpleCommand(req.getParameterMap()); > cmd.validate(); > ----- -- 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