August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5366) runtime attribute is described with configuration storage in domain mode

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5366: -------------------------------- Summary: runtime attribute is described with configuration storage in domain mode Key: AS7-5366 URL: https://issues.jboss.org/browse/AS7-5366 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jeff Mesnil Assignee: Brian Stansberry a messaging subsystem resource defines a *runtime* read-only attribute "started". In standalone mode, the attribute storage is described as "runtime". In domain mode, it is also the case when accessing the server directly: {noformat} [domain@localhost:9999 /] /host=master/server=server-one/subsystem=messaging/hornetq-server=default/in-vm-acceptor=in-vm:read-resource-description { ... "started" => { "description" => "Whether this acceptor is started.", "type" => BOOLEAN, "nillable" => false, "access-type" => "read-only", "storage" => "runtime" } } {noformat} However when the resource is described through the domain's profile, it is erroneously described with a "configuration" storage: {noformat} [domain@localhost:9999 /] /profile=full/subsystem=messaging/hornetq-server=default/in-vm-acceptor=in-vm:read-resource-description { ... "started" => { "description" => "Whether this acceptor is started.", "type" => BOOLEAN, "nillable" => false, "access-type" => "read-only", "storage" => "configuration" } } {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

12 years, 2 months

3
7
0 / 0

[JBoss JIRA] (EJBTHREE-2286) Exception handling of EJB container for MDB is incorrect

by Adam Kovari (JIRA)

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-5329) Transaction leak protection for web requests is too restrictive (possibly violating the spec)

by Marko Strukelj (JIRA)

Marko Strukelj created AS7-5329: ----------------------------------- Summary: Transaction leak protection for web requests is too restrictive (possibly violating the spec) Key: AS7-5329 URL: https://issues.jboss.org/browse/AS7-5329 Project: Application Server 7 Issue Type: Bug Components: Transactions, Web Affects Versions: 7.1.2.Final (EAP) Reporter: Marko Strukelj Assignee: Jason Greene In order to prevent leaking active transactions from processing of web requests a TransactionRollbackSetupAction is installed by transactions subsystem for web subsystem to use. This causes usecases where we want JTA TX to span different web apps over cross-context includes to fail, as the setup action is applied around each cross-context include, and forcefully rolls back any TX still active at the end of dispatching. A concrete use case are portals that rely on cross-context includes. Java EE Platform 6 Spec says the following in section EE.4.2.2: "Returning from the service method to the network client with an active transaction context is an error. The web container is required to detect this error and abort the transaction. As specified above in Section EE.4.2.1.2, “Transaction Non-Requirements,” requests made within a web container using the RequestDispatcher must propagate any transaction context to the called class. Unless the called class commits or aborts the transaction, the transaction must remain active when the called class returns." There is no talk here about cross-context includes or application boundaries. Therefore it seems the current implementation is not spec-compliant. TransactionRollbackSetupAction should only be applied on an original incoming web request, not on each cross-context include. -- 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

12 years, 2 months

4
5
0 / 0

[JBoss JIRA] (AS7-2832) subdeployment dependency to a module with optional="true" leads to a deployment failure when the dependency not available

by Radim Hanus (Created) (JIRA)

subdeployment dependency to a module with optional="true" leads to a deployment failure when the dependency not available ------------------------------------------------------------------------------------------------------------------------- Key: AS7-2832 URL: https://issues.jboss.org/browse/AS7-2832 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Beta1 Reporter: Radim Hanus details in referenced forum thread -- 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

12 years, 2 months

4
4
0 / 0

[JBoss JIRA] (JGRP-1503) RSVP: view change callback is not handled and membership list needs to be updated

by Bela Ban (JIRA)

Bela Ban created JGRP-1503: ------------------------------ Summary: RSVP: view change callback is not handled and membership list needs to be updated Key: JGRP-1503 URL: https://issues.jboss.org/browse/JGRP-1503 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.2, 3.0.13 2 problems: #1 A view is handled in the down() callback, however, as RSVP is usually at the top of the stack, this is never called ! SOLUTION: handle the view callback in up(). #2 In down(), if we create an Entry with {A,B,C,D}, but - *before* we add it to the ids hashmap - a new view {A,B,C} is installed, Entry will *never* get updated. SOLUTION: update the Entry *after* adding it to the ids hashmap -- 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

12 years, 2 months

1
1
0 / 0

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

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Tom Fonteyne moved JBPAPP-9717 to AS7-5403: ------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5403 (was: JBPAPP-9717) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.2.Final (EAP) (was: EAP 6.0.0 (CR1)) Component/s: CLI (was: Scripts and Commands) Security: (was: Public) Docs QE Status: (was: NEW) > 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 > > 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5401) Web Console, wrong version

by Frank Langelage (JIRA)

Frank Langelage created AS7-5401: ------------------------------------ Summary: Web Console, wrong version Key: AS7-5401 URL: https://issues.jboss.org/browse/AS7-5401 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.2.0.Alpha1 Reporter: Frank Langelage Assignee: Heiko Braun Priority: Minor The Web Console of the current AS7 build 7.2.0.Alpha1-SNAPSHOT shows "JBoss Application Server 7.1" in the head. Seems to be a fixed text and not determined from the real version. The server configuration screen show the right Relese version. -- 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

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-5399) Ability to flush queues/topics, etc

by Heiko Braun (JIRA)

Heiko Braun created AS7-5399: -------------------------------- Summary: Ability to flush queues/topics, etc Key: AS7-5399 URL: https://issues.jboss.org/browse/AS7-5399 Project: Application Server 7 Issue Type: Feature Request Components: JMS Reporter: Heiko Braun Assignee: Andy Taylor -- 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

12 years, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-3724) Build option to exclude Jacorb / IIOP

by Carlo de Wolf (JIRA)

Carlo de Wolf created AS7-3724: ---------------------------------- Summary: Build option to exclude Jacorb / IIOP Key: AS7-3724 URL: https://issues.jboss.org/browse/AS7-3724 Project: Application Server 7 Issue Type: Enhancement Components: IIOP Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-4321) OSGi management console needs inspector of wiring

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-4321?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-4321: ----------------------------- Component/s: (was: Console) > OSGi management console needs inspector of wiring > ------------------------------------------------- > > Key: AS7-4321 > URL: https://issues.jboss.org/browse/AS7-4321 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi > Affects Versions: 7.1.1.Final > Environment: Mac OS X 10.7.3 > Reporter: Tim Diekmann > Assignee: David Bosschaert > Fix For: No Release > > > The OSGi management console for AS 7 needs a viewer of the current wiring. The console log showed the following error on start of the bundle and there is no way to inspect the wiring to see where the problem lies and how to solve it. There is some inconsistency in the deployment, but how to find out what? > {code} > 00:09:14,480 ERROR [org.mortbay.log] (HttpManagementService-threads - 3) Error starting handlers: java.lang.IncompatibleClassChangeError: Class org.eclipse.equinox.http.servlet.HttpServiceServlet does not implement the requested interface javax.servlet.Servlet > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.init(HttpServerManager.java:294) > at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431) > at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:681) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:140) > at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) > at org.mortbay.jetty.Server.doStart(Server.java:224) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:109) > at org.eclipse.equinox.http.jetty.internal.Activator.start(Activator.java:60) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) > at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132) > at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89) > at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304) > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) > at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) > at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- 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

12 years, 2 months

1
0
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