April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9230) Expose deployment details via the domain management API

by Brian Stansberry (JIRA)

Expose deployment details via the domain management API ------------------------------------------------------- Key: JBAS-9230 URL: https://issues.jboss.org/browse/JBAS-9230 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta4 We need to provide access to deployment configuration and runtime information. I don't consider modifying configuration (i.e. persistent modification) to be a requirement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8968) MDB Support

by David Lloyd (JIRA)

MDB Support ----------- Key: JBAS-8968 URL: https://issues.jboss.org/browse/JBAS-8968 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta2 Parent task for MDB support. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-9020) Deployment content management enhancement

by David Lloyd (JIRA)

Deployment content management enhancement ----------------------------------------- Key: JBAS-9020 URL: https://issues.jboss.org/browse/JBAS-9020 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 In order to keep deployment state sane and meet various external requirements, we need to support multiple content items per deployment. Presently deployments are permanently, uniquely identified by SHA1. We need to move this SHA1 identifier to the content of the deployment element. So rather than: {noformat} <deployment name="foo.ear" runtime-name="foo.ear" sha1="d37ede977b022a1456ec5e7a5eee07549cb1c414"/> {noformat} It should be structured as: {noformat} <deployment name="foo.ear" runtime-name="foo.ear"> <content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/> </deployment> {noformat} If there is filesystem content it should be listed differently: {noformat} <deployment name="foo.ear" runtime-name="foo.ear"> <fs-archive path="deployments/foo.ear" relative-to="jboss.server.base.dir"/> <fs-exploded path="deployments/foo.war" relative-to="jboss.server.base.dir"/> </deployment> {noformat} For filesystem hot-deployment purposes, it is up to the FS scanner to take care of tracking and removing deployments whose content was removed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
16
0 / 0

[JBoss JIRA] Created: (JBAS-9372) Remove profile element's "name" attribute from standalone.xml's part of the xsd

by Brian Stansberry (JIRA)

Remove profile element's "name" attribute from standalone.xml's part of the xsd ------------------------------------------------------------------------------- Key: JBAS-9372 URL: https://issues.jboss.org/browse/JBAS-9372 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Minor Fix For: 7.0.0.CR1 It's not used by the server in standalone mode, so remove it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (AS7-684) Interface criteria matching misses subinterfaces (aka virtual interfaces)

by Brian Stansberry (JIRA)

Interface criteria matching misses subinterfaces (aka virtual interfaces) ------------------------------------------------------------------------- Key: AS7-684 URL: https://issues.jboss.org/browse/AS7-684 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 NetworkInterfaceService.resolveInterface() is only iterating through the NetworkInterface enumeration returned by NetworkInterface.getNetworkInterfaces(). It also needs to iterate through any NI's returned by calling ni.getSubInterfaces() on each of the non-virtual interfaces. Goal: we want this to work: <nic name="eth0:1"/> Right now only this will work: <nic name="eth0"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9328) Implement or remove "priority" and "cpu affinity" attributes in server config

by Brian Stansberry (JIRA)

Implement or remove "priority" and "cpu affinity" attributes in server config ----------------------------------------------------------------------------- Key: JBAS-9328 URL: https://issues.jboss.org/browse/JBAS-9328 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 In domain mode the server config has "cpu-affinity" and "priority" elements. Either implement or remove. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-9326) Deploy operation reported as failure even if it was successful

by Heiko Rupp (JIRA)

Deploy operation reported as failure even if it was successful -------------------------------------------------------------- Key: JBAS-9326 URL: https://issues.jboss.org/browse/JBAS-9326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta2 Reporter: Heiko Rupp I've created a new servergroup 'frobnitz' with one managed AS that was not started. I have deployed a war to it and get a failure back. This makes on one side some sense, as it was not applied to the downed host, but as the war was applied to the SG itself, it should get a different kind of result: After I have started the managed AS, the war file got successfully installed in it and deployed and I can call it as it should. I think the scenario of deploying stuff to downed AS is common in scenarios, where you only want to start machines on demand when the load increases. Upload: {"outcome":"success","result":{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="},"compensating-operation":null} Adding + deploy: Json to send: {"steps":[{"address":[{"deployment":"test-simple.war"}],"operation":"add","runtime-name":"test-simple.war","hash":{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="},"name":"test-simple.war"},{"address":[{"server-group":"frobnitz"},{"deployment":"test-simple.war"}],"operation":"add","enabled":"true"}],"address":[],"operation":"composite"} Return value from the domain: ==> {"outcome" : "failed", "result" : {"server-groups" : {"frobnitz" : {"myDemo" : {"host" : "local", "response" : {"outcome" : "failed", "failure-description" : [{ "java.lang.IllegalStateException" : "No handler for add at address [\n (\"host\" => \"local\"),\n (\"server\" => \"myDemo\"),\n (\"deployment\" => \"test-simple.war\")\n]" }]}}}}}, "failure-description" : "Operation was not applied successfully to any servers"} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (AS7-686) Domain mode server restart op doesn't restart

by Brian Stansberry (JIRA)

Domain mode server restart op doesn't restart --------------------------------------------- Key: AS7-686 URL: https://issues.jboss.org/browse/AS7-686 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 Executing: [localhost:9999 /] /host=local/server-config=server-three:restart { "outcome" => "success", "result" => "STOPPING", "compensating-operation" => undefined } Results in: [localhost:9999 /] /host=local/server-config=server-three:read-attribute(name=status) { "outcome" => "success", "result" => "DISABLED", "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-9338) Prevent concurrent write requests to the DomainController

by Brian Stansberry (JIRA)

Prevent concurrent write requests to the DomainController --------------------------------------------------------- Key: JBAS-9338 URL: https://issues.jboss.org/browse/JBAS-9338 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 The parent task handles ServerControllerImpl and DomainModelImpl, but we also need to prevent concurrent multi-process ops via DomainControllerImpl. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-438) LdapAttributeMappingProvider should check for empty attribute list

by Anil Saldhana (JIRA)

LdapAttributeMappingProvider should check for empty attribute list ------------------------------------------------------------------ Key: SECURITY-438 URL: https://jira.jboss.org/jira/browse/SECURITY-438 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.4.SP1 Reporter: Anil Saldhana Assignee: Anil Saldhana ============= java.lang.NullPointerException at java.util.StringTokenizer.<init>(StringTokenizer.java:182) at java.util.StringTokenizer.<init>(StringTokenizer.java:204) at org.jboss.security.mapping.providers.attribute.LdapAttributeMappingProvider.getNeededAttributes(LdapAttributeMappingProvider.java:336) at org.jboss.security.mapping.providers.attribute.LdapAttributeMappingProvider.performMapping(LdapAttributeMappingProvider.java:204) at org.jboss.security.mapping.providers.attribute.LdapAttributeMappingProvider.performMapping(LdapAttributeMappingProvider.java:93) at org.jboss.security.mapping.MappingContext.performMapping(MappingContext.java:54) ================== -- 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

15 years, 1 month

2
3
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 April 2011