November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated AS7-5403: -------------------------------- Fix Version/s: 7.2.0.Alpha1 The way I want to fix this for 7.2 is to add 'connector' as mandatory parameter to the add operation. Making 'connector' attribute optional does not seem reasonable, as we need that as dependency for the subsystem. Using lists instead seems to only workaround the issue of not supporting runtime mode for attributes properly. Most of the problems should go away if it gets addressed. Objections? > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Joe Wertz > Fix For: 7.2.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5077) "JBAS014101: Failed to find SFSB instance with session ID" calling @javax.ejb.Remove method

by Marek Schmidt (JIRA)

Marek Schmidt created AS7-5077: ---------------------------------- Summary: "JBAS014101: Failed to find SFSB instance with session ID" calling @javax.ejb.Remove method Key: AS7-5077 URL: https://issues.jboss.org/browse/AS7-5077 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Marek Schmidt Assignee: jaikiran pai Calling a SFSB @javax.ejb.Remove method results an ugly INFO message in the logs: e.g. (modified helloworld-jsf quickstart): {code} @Named @Stateless public class RichBean { @Resource SessionContext sessionContext; public void greet() { TestEjb testEjb = (TestEjb)sessionContext.lookup("java:app/jboss-as-helloworld-jsf/TestEjb"); System.out.println(testEjb.greet()); testEjb.remove(); } } {code} {code} @Stateful public class TestEjb { @Remove public void remove() { } public String greet() { return "Hello"; } } {code} {code} <h:form id="helloWorld"> <h:commandButton action="#{richBean.greet()}" value="Greet" /> </h:form> {code} {noformat} 14:35:46,105 INFO [stdout] (http-/127.0.0.1:8080-1) Hello 14:35:46,106 INFO [org.jboss.as.ejb3] (http-/127.0.0.1:8080-1) JBAS014101: Failed to find SFSB instance with session ID {[95, 12, 97, -35, -110, -123, 79, -16, -116, -95, -99, -57, 52, 38, 81, 85]} in cache {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, 7 months

7
10
0 / 0

[JBoss JIRA] (AS7-5085) Operations to read content from the content repository

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5085: ------------------------------------- Summary: Operations to read content from the content repository Key: AS7-5085 URL: https://issues.jboss.org/browse/AS7-5085 Project: Application Server 7 Issue Type: Feature Request Reporter: Brian Stansberry -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] (AS7-5500) Admin Console writes incorrect standalone.xml content

by Scott Matthews (JIRA)

Scott Matthews created AS7-5500: ----------------------------------- Summary: Admin Console writes incorrect standalone.xml content Key: AS7-5500 URL: https://issues.jboss.org/browse/AS7-5500 Project: Application Server 7 Issue Type: Bug Environment: Mac OS x 10.6.8, JBoss 7.1.1 Final Reporter: Scott Matthews I added a Security Domain (manually) to my JBoss application. It included a definition of a custom login module as well as a reference to the module in which it was contained: <login-module code="com.atlassian.crowd.application.jaas.CrowdLoginModule" flag="required" module="com.atlassian.crowd"> Through multiple startups and shutdowns my configuration worked as I expected. When I attempted to use the Admin Console to add new module options to this security domain, my ability to login failed. Upon further investigation I discovered that the admin console removed the module property from the login-module tag. to prove this I repeated the process with the same result. -- 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, 7 months

4
7
0 / 0

[JBoss JIRA] (AS7-4529) a "failure-causes-rollback="false"" attribute for the filesystem scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4529?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4529: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 > a "failure-causes-rollback="false"" attribute for the filesystem scanner > ------------------------------------------------------------------------ > > Key: AS7-4529 > URL: https://issues.jboss.org/browse/AS7-4529 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > Fix For: 7.3.0.Alpha1 > > > JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments. > Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback. > Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4998) Describe inheritance relationships in the resource description metadata

by Brian Stansberry (JIRA)

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-4997) Add reference description information to resource metadata

by Brian Stansberry (JIRA)

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8139) Ability to rollback AS version updates

by Brian Stansberry (JIRA)

Ability to rollback AS version updates -------------------------------------- Key: JBAS-8139 URL: https://jira.jboss.org/browse/JBAS-8139 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> A fixpack installer that handles version rollbacks would be fantastic. >> Of course it needs to remain flexible to work with JBoss installs that >> have been manually modified. Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
4
0 / 0

[JBoss JIRA] (AS7-5182) properly transform/resolve expression values

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-5182: ---------------------------------------- Summary: properly transform/resolve expression values Key: AS7-5182 URL: https://issues.jboss.org/browse/AS7-5182 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Emanuel Muckenhuber Priority: Critical Fix For: 7.2.0.CR1 We need to be able to properly handle values which are getting changed to allow expressions. The problem is that older HCs won't understand the expression value, therefore they need be resolved before sending the initial model. At this point this can only be done against domain/host specific system properties. Server-group and server level overrides would be lost when starting a managed server. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] (AS7-4595) Better reporting if a master and slave HC are both launched from the same directory

by Kabir Khan (JIRA)

Kabir Khan created AS7-4595: ------------------------------- Summary: Better reporting if a master and slave HC are both launched from the same directory Key: AS7-4595 URL: https://issues.jboss.org/browse/AS7-4595 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan The only symptom at the moment is hangs on startup on the slave as mentioned in AS7-4593. -- 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, 7 months

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 November 2012