April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5359) CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5359?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5359: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Alpha1) > CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error) > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-5359 > URL: https://issues.jboss.org/browse/AS7-5359 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Pavel Janousek > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as: > {code} > <server xmlns="urn:jboss:domain:1.3"> > {code} > The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd. > The very common Linux system has implemented and enabled dualstack in these days. If we instruct AS instance to bind to +any+ IPv4 address via {code}<interface name="public"> > <any-ipv4-address /> > </interface>{code} > The real result is to bind running AS instance to +any+ IP address, not only in IPv4 address space but in IPv6 too! > With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound to ANY IPv4 addresses only. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6470) Improve reporting during deployment hang

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6470?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6470: ---------------------------------- Assignee: (was: Brian Stansberry) Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha1) > Improve reporting during deployment hang > ---------------------------------------- > > Key: AS7-6470 > URL: https://issues.jboss.org/browse/AS7-6470 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Environment: http://java.net/jira/browse/EJB_SPEC-60 > java version "1.7.0_09" > OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > Ubuntu 12.10 > Reporter: Carlo de Wolf > Fix For: 8.0.0.Beta1 > > Attachments: deployment-hang-20130205.txt, server.log > > > Management Thread waits indefinitely for, what seems to be, a finished operation. > {noformat} > "management-handler-thread - 2" prio=10 tid=0x00007fa1380d0000 nid=0x7683 in Object.wait() [0x00007fa136deb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:503) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:464) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:148) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:299) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {noformat} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6964) Recursive expression resolution

by Jess Sightler (JIRA)

[ https://issues.jboss.org/browse/AS7-6964?page=com.atlassian.jira.plugin.s... ] Jess Sightler commented on AS7-6964: ------------------------------------ I have added an initial pass at an implementation (with the above feature missing) in order to solicit some feedback. Basically, variable resolution happens in two places: - The model node itself (System Property and Environment Variable resolution) - The ExpressionResolver (vault) I have worked around this by moving the call to node.resolve() into the resolveExpressionsRecursively itself for the moment. I don't really see a way around this with the current design, but it doesn't seem ideal to me. Suggestions? > Recursive expression resolution > ------------------------------- > > Key: AS7-6964 > URL: https://issues.jboss.org/browse/AS7-6964 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jess Sightler > > When resolving an expression, keep resolving until the output of the resolution matches the input. > Use case: > ${sys.prop.with.host.specific.value} > resolves to > ${VAULT::xxxxx} > which resolves to > thesecret > Basically, the main mechanism for customizing domain-level configs on a per-host basis is to use expressions and use different values on each host. But this breaks down when a vault expression is added to the mix. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6890) Change call to GetRestful in JaxrsComponentDeployer

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6890?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6890. --------------------------------- Resolution: Done > Change call to GetRestful in JaxrsComponentDeployer > --------------------------------------------------- > > Key: AS7-6890 > URL: https://issues.jboss.org/browse/AS7-6890 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 8.0.0.Alpha1 > Reporter: Ron Sigal > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > The method > {code} > public static Class<?>[] getSubResourceClass(Class<?> clazz) > {code} > is now called > {code} > public static Class<?>[] getSubResourceClasses(Class<?> clazz) > {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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6755) JaxRsComponentDeployer should use GetRestful.getSubResourceClasses()

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6755?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6755. --------------------------------- Resolution: Done > JaxRsComponentDeployer should use GetRestful.getSubResourceClasses() > -------------------------------------------------------------------- > > Key: AS7-6755 > URL: https://issues.jboss.org/browse/AS7-6755 > Project: Application Server 7 > Issue Type: Feature Request > Components: REST > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6970) Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6970?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6970: ---------------------------------- Description: With a socket-binding-group config like the following, the outbound-socket-binding=mail-smtp:add op is not included in the list of boot ops sent to domain server. {code} <socket-binding-groups> <socket-binding-group name="sockets1" default-interface="public"> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="1111"/> </outbound-socket-binding> </socket-binding-group> {code} was: With a socket-binding-group config like the following, the no outbound-socket-binding=mail-smtp:add op is included in the list of boot ops sent to domain server. {code} <socket-binding-groups> <socket-binding-group name="sockets1" default-interface="public"> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="1111"/> </outbound-socket-binding> </socket-binding-group> {code} > Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings > ---------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6970 > URL: https://issues.jboss.org/browse/AS7-6970 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > With a socket-binding-group config like the following, the outbound-socket-binding=mail-smtp:add op is not included in the list of boot ops sent to domain server. > {code} > <socket-binding-groups> > <socket-binding-group name="sockets1" default-interface="public"> > <outbound-socket-binding name="mail-smtp"> > <remote-destination host="localhost" port="1111"/> > </outbound-socket-binding> > </socket-binding-group> > {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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6970) Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6970: ------------------------------------- Summary: Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings Key: AS7-6970 URL: https://issues.jboss.org/browse/AS7-6970 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.0.Alpha1 With a socket-binding-group config like the following, the no outbound-socket-binding=mail-smtp:add op is included in the list of boot ops sent to domain server. {code} <socket-binding-groups> <socket-binding-group name="sockets1" default-interface="public"> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="1111"/> </outbound-socket-binding> </socket-binding-group> {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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6923) Undertow breaks some JSF apps

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6923?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6923. --------------------------------- Resolution: Done > Undertow breaks some JSF apps > ----------------------------- > > Key: AS7-6923 > URL: https://issues.jboss.org/browse/AS7-6923 > Project: Application Server 7 > Issue Type: Bug > Components: JSF, Web > Affects Versions: 8.0.0.Alpha1 > Reporter: Stan Silvert > Assignee: Stuart Douglas > Priority: Critical > Attachments: InjectionTest.zip > > > Undertow breaks some JSF apps. I haven't narrowed the problem down yet but I want to go ahead and post this JIRA because it is a blocker for AS8. > I'm attaching a small JSF project that demonstrates the problem. When you run the WAR with -c standalone-jbossweb.xml it works fine. > With Undertow it breaks. You are unable to navigate based on the return value of a MethodExpression. > Also, you get this warning: > {noformat} > 12:17:30,572 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (default task-1) JSF1091: No mime type could be found for file /index.xhtml. To resolve this, add a mime-type mapping to the applications web.xml. > {noformat} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6969) Config and log property overrides should be honored in domain.bat

by James Perkins (JIRA)

James Perkins created AS7-6969: ---------------------------------- Summary: Config and log property overrides should be honored in domain.bat Key: AS7-6969 URL: https://issues.jboss.org/browse/AS7-6969 Project: Application Server 7 Issue Type: Enhancement Components: Scripts Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 8.0.0.Alpha1 The {{jboss.domain.config.dir}} and {{jboss.domain.log.dir}} properties should be parsed in the {{domain.bat}} file to allow overrides. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-75) Validation matching for translated formats should accept %s always

by James Perkins (JIRA)

James Perkins created LOGTOOL-75: ------------------------------------ Summary: Validation matching for translated formats should accept %s always Key: LOGTOOL-75 URL: https://issues.jboss.org/browse/LOGTOOL-75 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Example: {code} "Invalid byte token. Expecting '%d' received '%d'" {code} Should allow the {{'%d'}} to be defined as {{'%s'}}. Print a warning, but accept the translation. -- 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, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013