September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1364) JGRP-2.10.0.GA deos not disable ipv6

by rsolanki rsolanki (JIRA)

JGRP-2.10.0.GA deos not disable ipv6 ------------------------------------ Key: JGRP-1364 URL: https://issues.jboss.org/browse/JGRP-1364 Project: JGroups Issue Type: Bug Environment: windows 7 Reporter: rsolanki rsolanki Assignee: Bela Ban JGRP-2.10.0.GA deos not disable ipv6, Even After -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Stack=false. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1571) System package list is ignored for resources

by William Louth (JIRA)

System package list is ignored for resources -------------------------------------------- Key: AS7-1571 URL: https://issues.jboss.org/browse/AS7-1571 Project: Application Server 7 Issue Type: Bug Components: Modules Affects Versions: 7.0.1.Final Reporter: William Louth Assignee: David Lloyd https://issues.jboss.org/browse/MODULES-93 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1572) jboss.modules.system.pkgs set in standalone.conf[.bat] and domain.conf[.bat]

by William Louth (JIRA)

jboss.modules.system.pkgs set in standalone.conf[.bat] and domain.conf[.bat] ---------------------------------------------------------------------------- Key: AS7-1572 URL: https://issues.jboss.org/browse/AS7-1572 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.1.Final, 7.0.0.CR1, 7.0.0.Beta3 Reporter: William Louth Assignee: Jason Greene Priority: Blocker Fix For: 7.0.2.Final In both the domain.conf and standalone.conf the following is being set. -Djboss.modules.system.pkgs=org.jboss.byteman This complicates matters for integration with other javaagents which alter the script because this property must also be set and it is not defined in the JVM what precedence is given to multiple same property settings on the command line. Please remove or uncomment in both conf files including window versions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBWEB-213) JBoss Web Native Connectors bundles contain wrong paths

by Dan Mazzell (JIRA)

JBoss Web Native Connectors bundles contain wrong paths ------------------------------------------------------- Key: JBWEB-213 URL: https://issues.jboss.org/browse/JBWEB-213 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: Non-Winows, Linux x86, X64, IA64, Solaris, Reporter: Dan Mazzell Assignee: Remy Maucherat Priority: Minor When extracting the jboss-native 2.x tar bundles, the location of the libs should match what the startup script, (run.sh) is expecting. For example, for a Linux x64 system, the run.sh expects the native libraries to be placed into the jboss/bin/META-INF/lib/linux2/x64/ directory, however when tar-gunzipping the jboss-native-2.0.10-linux2-x64-ssl.tar.gz, the binaries are placed in the bin/naitive dir. The tar file path should match what JBoss's run.sh sets up the path as. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1832) Fix the descriptors for the Deployment part of the model

by Kabir Khan (JIRA)

Fix the descriptors for the Deployment part of the model -------------------------------------------------------- Key: AS7-1832 URL: https://issues.jboss.org/browse/AS7-1832 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan This part of the model is currently removed in org.jboss.as.test.surefire.servermodule.ValidateModelTestCase (The test may be moved somewhere else, ping me if you need to find it). The missing parts are: {code} "deployment" => { "description" => "A list of deployments available for use on the server.", "min-occurs" => 0, "model-description" => {"*" => { "description" => "A deployment represents anything that can be deployed (e.g. an application such as EJB-JAR, WAR, EAR, any kind of standard archive such as RAR or JBoss-specific deployment) into a server.", "head-comment-allowed" => true, "tail-comment-allowed" => false, "attributes" => {SNIP}, "operations" => {SNIP}, "children" => { "subsystem" => {"model-description" => {"web" 1) NEEDS A DESCRIPTION => {"children" => {"servlet" 2) NEEDS A DESCRIPTION => {"model-description" => {"*" => undefined 4) WHAT GOES HERE?} }}}}}, "subdeployment" => {"model-description" => {"*" => 5) NEEDS A DESCRIPTION { "description" => "A deployment represents anything that can be deployed (e.g. an application such as EJB-JAR, WAR, E AR, any kind of standard archive such as RAR or JBoss-specific deployment) into a server.", "head-comment-allowed" => true, "tail-comment-allowed" => false, "attributes" => {SNIP}, "operations" => {SNIP}, "children" => {"subsystem" 6) NEEDS A DESCRIPTION => {"model-description" => {"web" 7) NEEDS A DESCRIPTION=> {"children" => {"servlet" 8) NEEDS A DESCRIPTION=> {"model-description" => {"*" => undefined 9) WHAT GOES HERE????}}}}}}} }}} } }} }, {code} This currently lives in https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
6
0 / 0

[JBoss JIRA] Created: (AS7-1851) CLONE - Domain reflects jboss.server.xy properties

by Rostislav Svoboda (JIRA)

CLONE - Domain reflects jboss.server.xy properties -------------------------------------------------- Key: AS7-1851 URL: https://issues.jboss.org/browse/AS7-1851 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Scripts Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Alpha1 Domain reflects jboss.server.xy properties, tested with jboss.server.log.dir property. The same server.log file is used for both server-one and server-two. Only file boot.log is created in domain/servers/server-one/log and domain/servers/server-two/log directory. In my case file server.log contains log only for server-one, there is no log for server-two. I think jboss.server.xy properties shouldn't be reflected in domain instances. Even structure of https://docs.jboss.org/author/display/AS71/Command+line+parameters implies that jboss.server.xy properties are used for Standalone. Reproducer of my steps: {code} rm -rf domain/servers bin/domain.sh -Djboss.server.log.dir=/tmp/ ls -aR domain/servers/server-one/log ls -aR domain/servers/server-two/log ls -l /tmp/server* {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1852) CLONE - Domain - system properties for log, data, temp aren't reflected

by Rostislav Svoboda (JIRA)

CLONE - Domain - system properties for log, data, temp aren't reflected ----------------------------------------------------------------------- Key: AS7-1852 URL: https://issues.jboss.org/browse/AS7-1852 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Scripts Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Alpha1 Some properties defined in https://docs.jboss.org/author/display/AS71/Command+line+parameters and in {{HostControllerEnvironment}} (org.jboss.as.host.controller) aren't reflected by current implementation. Affected properties: - jboss.domain.data.dir - jboss.domain.log.dir - jboss.domain.temp.dir In my scenario only jboss.domain.deployment.dir and jboss.domain.servers.dir were reflected. Structure for host-controller and process-controller logs + structure for data, log, tmp directories for server instances can't be mapped to that three properties. Maybe these properties could work: - jboss.domain.host-controller.log.dir - jboss.domain.process-controller.log.dir - jboss.domain.server-one.data.dir - jboss.domain.server-one.log.dir - jboss.domain.server-one.temp.dir - jboss.domain.server-xy.data.dir - jboss.domain.server-xy.log.dir - jboss.domain.server-xy.temp.dir Reproducer of my steps: {code} rm -rf xx-data xx-log xx-temp xx-deployment xx-servers mkdir xx-data xx-log xx-temp xx-deployment xx-servers bin/domain.sh -Djboss.domain.data.dir=xx-data -Djboss.domain.log.dir=xx-log -Djboss.domain.temp.dir=xx-temp -Djboss.domain.deployment.dir=xx-deployment -Djboss.domain.servers.dir=xx-servers bin/jboss-admin.sh --connect controller=127.0.0.1 command='deploy /home/rsvoboda/devel/JBQA-5161-scripts-testing/target/props.war --all-server-groups' bin/jboss-admin.sh --connect controller=127.0.0.1 command='undeploy props.war --all-relevant-server-groups' ls -al xx-data xx-log xx-temp xx-deployment xx-servers {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Commented: (AS7-1702) Accept <any-address/> in Jboss AS7 configuration

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on AS7-1702: ------------------------------------- This issue should be resolved with this commit: https://github.com/jbossas/jboss-as/commit/283c032f30711aa69760abb509af0e... > Accept <any-address/> in Jboss AS7 configuration > ------------------------------------------------ > > Key: AS7-1702 > URL: https://issues.jboss.org/browse/AS7-1702 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.0.1.Final > Environment: JBoss AS 7.0.1.Final > Reporter: Alexandre Gattiker > > ERROR ArquillianServiceDeployer - Cannot deploy arquillian service > java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) > at org.jboss.dmr.ModelNode.asList(ModelNode.java:1096) > at org.jboss.as.arquillian.container.ManagementClient.getInterface(ManagementClient.java:185) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:177) > at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148) > at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98) > at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.doServiceDeploy(ArquillianServiceDeployer.java:58) > After changing the JBoss AS 7 configuration from: > <interface name="public"> > <inet-address value="127.0.0.1"/> > </interface> > to: > <interface name="public"> > <any-address/> > </interface> > Presumed cause: > in org.jboss.as.arquillian.container.ManagementClient in jboss-as-arquillian-common-7.0.1.Final.jar: > return rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address").asString(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWEB-212) CVE-2011-3190 - authentication bypass and information disclosure

by Mustafa Musaji (JIRA)

CVE-2011-3190 - authentication bypass and information disclosure ---------------------------------------------------------------- Key: JBWEB-212 URL: https://issues.jboss.org/browse/JBWEB-212 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-7.0.1.GA Reporter: Mustafa Musaji Assignee: Remy Maucherat Incorporate the fixes by Jean-Frederic Clere here for this CVE https://home.corp.redhat.com/wiki/jboss-web-cve -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1138) Port displayed incorrectly for sockets with port 0

by Brian Stansberry (JIRA)

Port displayed incorrectly for sockets with port 0 -------------------------------------------------- Key: AS7-1138 URL: https://issues.jboss.org/browse/AS7-1138 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.0.0.CR1 Reporter: Brian Stansberry The console shows negative port values for the JGroups sockets in the ha-sockets socket binding group. My assumption is this has something to do with them having '0' as their port value. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011