February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3536) Review the inter-module dependencies directly relating to domain security

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3536: ------------------------------------- Summary: Review the inter-module dependencies directly relating to domain security Key: AS7-3536 URL: https://issues.jboss.org/browse/AS7-3536 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 The domain-management module containing a lot of the Remoting/SASL security services was added after a lot of the other inter-module dependencies had been established, now before the next major phase of development need to review the resulting dependencies and clean up. Most notably the API/SPI aspect of the security classes should be better separated from the domain operations acting on them - there are numerous places where access to the API is required or other services need to implement an SPI interface but the close coupling of management operations causes cyclic dependency issues. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-2638) a Message driven bean that implements MessageListener in a superclass is considered invalid.

by Davide Gesino (Created) (JIRA)

a Message driven bean that implements MessageListener in a superclass is considered invalid. -------------------------------------------------------------------------------------------- Key: AS7-2638 URL: https://issues.jboss.org/browse/AS7-2638 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.0.2.Final Environment: windows vista Reporter: Davide Gesino Assignee: Clebert Suconic a Message driven bean that implements MessageListener in a superclass is considered invalid. I have: public abstract class AsynchReplyManager implements MessageListener { public void onMessage(Message message) {... } ...} @MessageDriven(mappedName = "myMappedName") public class MyMessageDrivenBean extends AsynchReplyManager { ... } The deployment validator complains that: "MyMessageDrivenBean does not implement 1 interface nor specifies message listener interface" I think it should deal with the validator here: https://github.com/jbossas/jboss-as/blob/master/ejb3/src/main/java/org/jb... -- 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

13 years, 9 months

7
8
0 / 0

[JBoss JIRA] (AS7-2958) Add HA singleton support

by Paul Ferraro (Created) (JIRA)

Add HA singleton support ------------------------ Key: AS7-2958 URL: https://issues.jboss.org/browse/AS7-2958 Project: Application Server 7 Issue Type: Feature Request Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Blocker -- 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

13 years, 9 months

4
16
0 / 0

[JBoss JIRA] Created: (LOGMGR-24) Bad level "OFF" when using JDK7

by Jesper Pedersen (JIRA)

Bad level "OFF" when using JDK7 ------------------------------- Key: LOGMGR-24 URL: https://jira.jboss.org/browse/LOGMGR-24 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.2.0.CR6 Reporter: Jesper Pedersen Assignee: David Lloyd When using JDK7 I get Caused by: java.lang.ExceptionInInitializerError at sun.util.logging.PlatformLogger.<init>(PlatformLogger.java:164) at sun.util.logging.PlatformLogger.getLogger(PlatformLogger.java:128) at sun.net.www.protocol.http.HttpURLConnection.<clinit>(HttpURLConnection.java:298) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:62) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:57) at java.net.URL.openConnection(URL.java:969) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:628) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1292) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1259) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:260) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1169) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1065) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:978) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:551) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1234) at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:114) at org.jboss.jca.common.metadata.MetadataFactory.getStandardMetaData(MetadataFactory.java:105) at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:166) ... 26 more Caused by: java.lang.IllegalArgumentException: Bad level "OFF" at java.util.logging.Level.parse(Level.java:355) at java.util.logging.LoggingProxyImpl.parseLevel(LoggingProxyImpl.java:95) at sun.util.logging.LoggingSupport.parseLevel(LoggingSupport.java:134) at sun.util.logging.PlatformLogger$JavaLogger.getLevelObjects(PlatformLogger.java:504) at sun.util.logging.PlatformLogger$JavaLogger.<clinit>(PlatformLogger.java:496) ... 46 more -- 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

13 years, 9 months

3
13
0 / 0

[JBoss JIRA] (AS7-3962) EJB timers in cluster and failover support

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3962: ----------------------------------- Summary: EJB timers in cluster and failover support Key: AS7-3962 URL: https://issues.jboss.org/browse/AS7-3962 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, EJB Affects Versions: 7.1.0.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: Open To Community Support for clustered EJB timer service providing failover. -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1535) More management operations for timers

by Stuart Douglas (JIRA)

More management operations for timers ------------------------------------- Key: AS7-1535 URL: https://issues.jboss.org/browse/AS7-1535 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas Using the management api it should be possible to perform additional operations on timers such as: suspending cancelling invoking a timeout method -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
3
0 / 0

[JBoss JIRA] (AS7-3940) bundled jsf deployment fails when org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL true

by Juergen Hoffmann (JIRA)

Juergen Hoffmann created AS7-3940: ------------------------------------- Summary: bundled jsf deployment fails when org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL true Key: AS7-3940 URL: https://issues.jboss.org/browse/AS7-3940 Project: Application Server 7 Issue Type: Bug Reporter: Juergen Hoffmann It is impossible for Applications to bundle their own JSF Implementations even with org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL defined in web.xml, because jboss-as-web provides META-INF/services/com.sun.faces.spi.annotationprovider and injectionprovider please see https://github.com/jbossas/jboss-as/tree/master/web/src/main/resources/ME... and therefor will always try to use the JandexAnnotationProvider, which cannot work on different JSF Versions 12:29:30,105 SCHWERWIEGEND [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-8) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! Class org.jboss.as.web.deployment.jsf.JandexAnnotationProvider is not an instance of com.sun.faces.spi.AnnotationProvider -- 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

13 years, 9 months

9
15
0 / 0

[JBoss JIRA] (AS7-2597) Cannot use same binding name in resource-ref

by Thomas Diesler (Created) (JIRA)

Cannot use same binding name in resource-ref --------------------------------------------- Key: AS7-2597 URL: https://issues.jboss.org/browse/AS7-2597 Project: Application Server 7 Issue Type: Bug Components: Naming Reporter: Thomas Diesler Assignee: John Bailey Fix For: 7.1.0.CR1 Using this mapping (as the TCK does) {code} <jboss-web> <resource-ref> <res-ref-name>eis/JAXR</res-ref-name> <jndi-name>eis/JAXR</jndi-name> </resource-ref> </jboss-web> {code} I get {code} 17:56:29,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."jaxr-connection-test.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxr-connection-test.war".INSTALL: Failed to process phase INSTALL of deployment "jaxr-connection-test.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] Caused by: org.jboss.msc.service.CircularDependencyException: Service jboss-as has a circular dependency at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:617) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:588) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:562) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:212) at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:103) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] {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

13 years, 9 months

8
15
0 / 0

[JBoss JIRA] Created: (AS7-1972) Create nice way of registering different JNDI namespaces

by Stuart Douglas (JIRA)

Create nice way of registering different JNDI namespaces --------------------------------------------------------- Key: AS7-1972 URL: https://issues.jboss.org/browse/AS7-1972 Project: Application Server 7 Issue Type: Feature Request Components: Naming Affects Versions: 7.1.0.Alpha1 Reporter: Stuart Douglas Assignee: John Bailey As we can't really use Context.URL_PKG_PREFIXES we need some other way of registering JNDI namespaces -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-3601) Component context not available on spawned threads

by Johannes Odland (JIRA)

Johannes Odland created AS7-3601: ------------------------------------ Summary: Component context not available on spawned threads Key: AS7-3601 URL: https://issues.jboss.org/browse/AS7-3601 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.0.CR1b Reporter: Johannes Odland Assignee: John Bailey When a request is processed, the JavaNamespaceSetup pushes an InjectedEENamespaceContextSelector onto a ThreadLocalStack, making the app and component contexts available for lookups through InitialContext().lookup(). As a result, the application and component contexts are only available on the same thread as the request, and not on threads spawned by the application itself. Many applications, such as Solr, spawns its own threads for doing asynchronous processing. These are not able to access the JNDI component context (java:comp/env/). Perhaps one should use InheritableThreadLocal to store the selector instead? -- 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

13 years, 9 months

3
2
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 February 2012