September 2011 - jboss-jira - Jboss List Archives

[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

14 years, 10 months

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

14 years, 10 months

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

14 years, 10 months

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

14 years, 10 months

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

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-966) admin console randomly show defined datasources

by Marek Novotny (JIRA)

admin console randomly show defined datasources ----------------------------------------------- Key: AS7-966 URL: https://issues.jboss.org/browse/AS7-966 Project: Application Server 7 Issue Type: Bug Components: Console Environment: JBoss AS 7 Beta4-SNAPSHOT - Build #1158 (Jun 7, 2011 11:25:21 AM) Revision: a004da8272d7717225bfa1bc65534bb4b599bc1b Firefox 4.0.1, Ubuntu 11.04 Reporter: Marek Novotny Loading admin console at http://localhost.localdomain:9990/console/App.html#server/datasources shows empty datasource list. After creating new datasource it shows 2 datasources - one created myself and default H2DS. When I go to Deployments and back to Datasources it again shows only empty list. When I open standalone/configuration/standalone.xml both datasources are there. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Updated: (AS7-1557) WAB support for servlet 3.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-1557?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1557: -------------------------------- Fix Version/s: (was: 7.1.0.CR1) Forum Reference: http://community.jboss.org/message/619443#619443 (was: http://community.jboss.org/message/619443#619443) > WAB support for servlet 3.0 > --------------------------- > > Key: AS7-1557 > URL: https://issues.jboss.org/browse/AS7-1557 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > Bruno says, > ... in JBoss AS 7, how can I make the DemoServlet work with Servlet 3.0 annotations? I've tried this, but it does not work. The JBoss OSGi deployment interceptor is expecting a web.xml, which is not required with WebServlet 3.0 specs. > > Caused by: org.jboss.osgi.deployment.interceptor.LifecycleInterceptorException: Cannot obtain web.xml from: vfs: > Am I missing something here or WebServlet 3.0 is not yet supported in JBoss AS 7 WABs? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (AS7-1556) Support OSGi webapp deployments in JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-1556?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1556: -------------------------------- Fix Version/s: (was: 7.1.0.CR1) Forum Reference: http://community.jboss.org/message/17257#17257 (was: http://community.jboss.org/message/17257#17257) > Support OSGi webapp deployments in JBossWeb > ------------------------------------------- > > Key: AS7-1556 > URL: https://issues.jboss.org/browse/AS7-1556 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > OSGi webapps are currently deployed onto jboss-osgi-webapp, which contains an embedded PAX-Web WAR extender that in turn delegates to the PAX-Web provided WebContainer based on Jetty. > In the future, OSGi webapps should be handled by JBossWeb and be deployed onto the JBoss embedded Tomcat instance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1733) Console: dialogs like "JMS Subsystem Configuration" ignore selected profile

by Radoslav Husar (JIRA)

Console: dialogs like "JMS Subsystem Configuration" ignore selected profile --------------------------------------------------------------------------- Key: AS7-1733 URL: https://issues.jboss.org/browse/AS7-1733 Project: Application Server 7 Issue Type: Bug Components: Console, Domain Management Affects Versions: 7.0.1.Final Reporter: Radoslav Husar Assignee: Heiko Braun While managing domain, if you for instance create new queue for the profile, it gets created in a wrong profile. # open console # go to profiles # switch to another profile "ha" # Messaging -> JMS -> Add #* the dialog is wrong (everything is required even though they are optional -- other jira) #* queue is not shown in the list (other jira) #* queue was added to wrong profile, to default, not ha -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
12
0 / 0

[JBoss JIRA] Created: (JBRULES-3209) ReloadSessionTest fails when trying to unmarshall FactHandle

by Marco Rietveld (JIRA)

ReloadSessionTest fails when trying to unmarshall FactHandle ------------------------------------------------------------ Key: JBRULES-3209 URL: https://issues.jboss.org/browse/JBRULES-3209 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Reporter: Marco Rietveld Assignee: Mark Proctor Priority: Minor The org.drools.persistence.session.ReloadSessionTest fails at the moment. I'm seeing a npe thrown here: {code} ConcurrentNodeMemories.getNodeMemory(NodeMemory) line: 65 ReteooStatefulSession(AbstractWorkingMemory).getNodeMemory(NodeMemory) line: 1040 InputMarshaller.readFactHandles(MarshallerReaderContext) line: 373 InputMarshaller.readSession(MarshallerReaderContext, int, ExecutorService, Environment, SessionConfiguration) line: 255 DefaultMarshaller.unmarshall(InputStream, KnowledgeSessionConfiguration, Environment) line: 92 SessionMarshallingHelper.loadSnapshot(byte[], StatefulKnowledgeSession) line: 91 SingleSessionCommandService.initKsession(Integer, KnowledgeBase, KnowledgeSessionConfiguration) line: 221 {code} The cause of this seems to be that when InputMarshaller.readFactHandles(MarshallerReaderContext) runs in this test, the sinkId retrieved from the stream is _6_, but should be 2. The context contains an ObjectTypeNode with id 2, but not 6, in other words (and id 2 maps correctly). When I change the value (during debugging) to 2, the test completes successfully. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
15
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 September 2011