August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4293) Support property expansion in redirect-port attribute of the web system's connector

by Sven-Jørgen Karlsen (JIRA)

Sven-Jørgen Karlsen created AS7-4293: ---------------------------------------- Summary: Support property expansion in redirect-port attribute of the web system's connector Key: AS7-4293 URL: https://issues.jboss.org/browse/AS7-4293 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Environment: Standalone JBoss AS 7 on RHEL Linux and Windows 7 Enterprise x64 Reporter: Sven-Jørgen Karlsen Assignee: Remy Maucherat Priority: Optional The connector element of the web subsystem doesn't support property expansion, forcing you to hardwire the port number. E.g., writing: ... <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="${jboss.web.https.port}"/> ... causes a NumberFormatException. Runtime properties for this attribute was supported in previous versions. Another problem is that there is no predefined property with the above name. An alternative solution is to allow a reference to a socket binding groups in the attribute value, as discussed in http://community.jboss.org/thread/176339 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
3
0 / 0

[JBoss JIRA] (AS7-4080) @Ignored tests (tracking)

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4080: --------------------------------- Summary: @Ignored tests (tracking) Key: AS7-4080 URL: https://issues.jboss.org/browse/AS7-4080 Project: Application Server 7 Issue Type: Tracker Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
10
0 / 0

[JBoss JIRA] (AS7-4011) TS: Bad approach used as fallback mechanism for gathering IP address

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4011?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka resolved AS7-4011. ------------------------------- Resolution: Duplicate Issue JBPAPP-8337 > TS: Bad approach used as fallback mechanism for gathering IP address > -------------------------------------------------------------------- > > Key: AS7-4011 > URL: https://issues.jboss.org/browse/AS7-4011 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Minor > > There are several places in TS where we can see similar code like this: > {code} > static final String someIPproperty = System.getProperty("<some key>", "localhost"); > {code} > or > {code} > static final String someIPproperty = System.getProperty("<some key>", "127.0.0.1"); > {code} > As you can see above, this fallback mechanism is bound in this case (key value isn't found) to IPv4 only IP address at all. This approach is bad because we can run in other network stack - IPv6 is presented in these days - and in this case the such testcase fails with some strange error due to this issue. > I think we have two option how to resolve this issue: > # Don't use fallback mechanism at all and fix (= remove) them in present testcases > # Create auxiliary class which return 127.0.0.1 or ::1 string (but not string "localhost" because we can't be sure how it is translated (*)) > (*) common setup in Linux is to translate localhost -> 127.0.0.1 and localhost6 -> ::1 > Ad 1) I prefer this option because some forget/miss setting is very easy to catch > Ad 2) This auxiliary class should need to make some magic decision in which IP network stack mode we are now running and return IPv4 or IPv6 lookpack address accordingly. > I've been asking for decision in jboss-as7-dev mailing list [[1|http://lists.jboss.org/pipermail/jboss-as7-dev/2012-March/005449.html]] and we should wait for feedback from developers for final decision how to fix this issue. > [1] http://lists.jboss.org/pipermail/jboss-as7-dev/2012-March/005449.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-855) Fungal 0.11.0.Beta11

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-855: ------------------------------------- Summary: Fungal 0.11.0.Beta11 Key: JBJCA-855 URL: https://issues.jboss.org/browse/JBJCA-855 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2213) When the decider doesn't pick a move, the DefaultLocalSearchSolver shouldn't terminate by exception by try again, especially with relativeSelection on

by Geoffrey De Smet (JIRA)

When the decider doesn't pick a move, the DefaultLocalSearchSolver shouldn't terminate by exception by try again, especially with relativeSelection on ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2213 URL: https://jira.jboss.org/jira/browse/JBRULES-2213 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Critical a random bad relativeSelection could select only moves that are tabu that no reason to stop, because the next relativeSelection could be great. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
5
0 / 0

[JBoss JIRA] (JBRULES-3598) Planner: topSize move selector (was removed for 5.5.0.Beta1, bring it back)

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3598: ----------------------------------------- Summary: Planner: topSize move selector (was removed for 5.5.0.Beta1, bring it back) Key: JBRULES-3598 URL: https://issues.jboss.org/browse/JBRULES-3598 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Priority: Optional This never worked well and it was trouble to migrate in the new selector architecture. Nevertheless, it might work well if properly implemented. So bring it back if enough people vote for this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5313) Deployment of multiple .rar's with ironjacamar.xml

by Brad Maxwell (JIRA)

Brad Maxwell created AS7-5313: --------------------------------- Summary: Deployment of multiple .rar's with ironjacamar.xml Key: AS7-5313 URL: https://issues.jboss.org/browse/AS7-5313 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Brad Maxwell Assignee: Stefano Maestri Priority: Critical Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 Deploying an .ear with multiple .rar's, which all have an ironjacamar.xml file results in {noformat} 11:17:24,899 ERROR [org.jboss.msc.service] (MSC service thread 1-14) MSC000002: Invocation of listener "org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1@16c5f7e" failed: java.lang.IllegalArgumentException: JBAS014809: Ein Knoten ist bereits registriert unter '(deployment => *)(subdeployment => *)(subsystem => resource-adapters)(ironjacamar => ironjacamar)' at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:108) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.controller.registry.AbstractResourceRegistration.registerSubModel(AbstractResourceRegistration.java:68) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.connector.subsystems.resourceadapters.IronJacamarRegistrator.invoke(IronJacamarRegistrator.java:33) [jboss-as-connector-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1.registerIronjacamar(ParsedRaDeploymentProcessor.java:158) [jboss-as-connector-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.connector.deployers.ra.processors.AbstractResourceAdapterDeploymentServiceListener.transition(AbstractResourceAdapterDeploymentServiceListener.java:131) [jboss-as-connector-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5300) Enhance user-name vs. security domain check

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-5300: ------------------------------------ Summary: Enhance user-name vs. security domain check Key: AS7-5300 URL: https://issues.jboss.org/browse/AS7-5300 Project: Application Server 7 Issue Type: Task Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 Enhance the check of user-name vs. security domain so only one can be defined at a time -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-5240) The naming subsystem is not shown in the profiles subsystem view if the server is started in domain mode

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-5240: ------------------------------------- Summary: The naming subsystem is not shown in the profiles subsystem view if the server is started in domain mode Key: AS7-5240 URL: https://issues.jboss.org/browse/AS7-5240 Project: Application Server 7 Issue Type: Bug Components: Console, Domain Management Affects Versions: 7.1.2.Final (EAP) Environment: Domain mode Reporter: Wolf-Dieter Fink Assignee: Heiko Braun The naming subsystem is not shown in domain mode for the different profiles. If the server is started in standalone mode the naming subsystem is shown in the tree of Profile/Container between Transaction and EJB3. In domain mode I expect it if I select a profile at the same location. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] (AS7-5269) HornetQ interceptors are not supported

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5269: -------------------------------- Summary: HornetQ interceptors are not supported Key: AS7-5269 URL: https://issues.jboss.org/browse/AS7-5269 Project: Application Server 7 Issue Type: Feature Request Components: JMS Affects Versions: 7.1.2.Final (EAP) Reporter: Jeff Mesnil Assignee: Jeff Mesnil HornetQ interceptors are not supported by the messaging subsystem. Their attributes are handled by the XML parser but they are not set when adding the HornetQ server instance. Moreover, passing the interceptor class name is not enough. Since they are loaded by HornetQ, its classloader must be able to access them. The interceptors must be put in a JBoss module that is declared as a transitive dependency of org.hornetq module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012